Have the evidence before the auditor asks for it

Today the list exists in the head of whoever survived the last audit, and the assembly starts when the date is announced.

In Engrama the list is written down before it is needed, with who owes each item and what each item has to contain.

An audit closes. That is what makes this a job rather than the standing readiness `/teams/compliance` is about: this list is for one audit, on one date, and it finishes.

The order is what turns an audit from an assembly into a retrieval.

The list is written before the date

Not after it is announced. Ideally right after the last audit, while what was asked for is still fresh.

Each item is requested from whoever owes it

Some items are internal and some are a supplier’s or a contractor’s. The request goes to the holder, not to whoever is coordinating.

What comes back is checked

An expired certificate or a record covering the wrong period is refused before it joins the file.

The file is ready before the week

Complete is a state on the list, so the week before the audit is a review rather than a hunt.

You write the checks into each request when it goes out. Engrama runs them on what comes back, before it reaches you.

Some of them are a detail a machine can read: a date, an issuing body, the period covered. Some of them are not. Whether a record actually demonstrates the control it is filed under is a judgment.

You decide whether what arrived will hold up.

Today, ready means the file was assembled in the week before, from four places, by the person who could least afford the week.

With Engrama, ready is a state: every item on the list is in, each one passed the checks it was asked for, and each is filed against what it proves.

An auditor, a customer, a regulator, an insurer, the person you answer to: whoever asks, you open the record instead of building the answer.