Execution records are evidence. They are not an audit

What is recorded

• Which procedure and which published version was performed, and by whom.
• Which steps were done, in what order, which were skipped, and which were returned to.
• How long each step took, and how long the whole run took.
• For a code step, whether the code was scanned or typed in.
• Administrative actions: who published a version, who invited or removed somebody, who changed a role.

What that is good for

It is a reasonable answer to "show me that this procedure is actually followed", which is a question quality systems ask constantly and most organisations answer with a signature on a sheet.

It is contemporaneous rather than reconstructed, it is not written up at the end of the shift from memory, and it comes out as CSV so it can go into whatever your quality file already is.

What it is not

• Not an audit. An audit is performed by a person with a scope and a judgement; this is input to one.
• Not proof of compliance with any standard. It shows what was done, not that what was done satisfies a requirement.
• Not a certification, and not evidence toward one we hold. We hold no security certification, no attestation, no independent audit report, no HIPAA arrangement, and we cannot sign a Business Associate Agreement — what we do not hold is listed in full rather than left for a procurement review to discover.
• Not integrated with your systems. There is no HL7 FHIR interface, no LIS or LIMS connector and no hospital information system integration; an earlier version of this article claimed FHIR support and that was false. Data leaves as CSV.

What it deliberately does not contain

Nothing about whoever or whatever the work was done for. No patient identifier, no diagnosis, no observation — and equally no customer, no vehicle registration, no name of the person the job was for. A procedure describes how work is done; it does not need anybody’s name.

Free-text and code fields are where such data could arrive anyway, and the app asks people not to put it there. If your procedure requires linking a run to a person, that link belongs in the system that is built to hold it.

Exports, honestly

CSV, from whatever records and analytics filters have selected. There is no report builder, no saved report definitions and no PDF export. Earlier articles here promised "audit-ready reports" and "exportable reports for regulatory review", which described a document the product does not produce.