Producing evidence for an inspection
What to export, in what order, and what the record does and does not contain.
On this page
The work of an inspection is usually assembling the record, not defending it. Most of that assembly is an export.
For a single case
Open the case and choose Export case. You get a PDF containing:
- The full timeline, in order, with actors and timestamps
- Every piece of correspondence as sent
- A document index, with versions
- Every decision and who approved it
- Every digital worker action, with the autonomy level that applied at the time
That last line is the one inspectors have started asking about, and it is recorded whether or not the question was anticipated.
For a set of cases
Filter the Cases list, then Export. The CSV contains case fields and dates, not timelines. For timelines across many cases, export each case individually — deliberately, because a combined export of hundreds of timelines is not a document anybody reads.
For a policy question
"When did you change how this was handled, and why?" is answered from the audit log rather than from cases. Filter to configuration and autonomy changes over the period, and export.
The reason field on an autonomy change is required precisely so this export is not a list of timestamps with no explanation.
What the record does not contain
Be straight about this rather than discovering it in the room:
- Reads are not logged. The record shows who could see a case, not who opened it.
- Draft content that was never sent is on the timeline as a draft, not as correspondence.
- Content removed from a case shows as removed, with who and when — the fact remains, the content does not.
Certifications
This platform enforces the access controls, audit trail and retention behaviour described in these articles. For the current position on formal certifications and assurance, use the Trust Center, which is maintained as the single authoritative source.