The fastest way to fail a data review is to hand over a polished narrative instead of a record. Auditors are trained to distrust summaries. What convinces them is the ability to pick any output and trace it, step by step, back to its source.
What a trail must contain
For each output: the contributor and their verification status, the instructions they followed, the review or override that happened, and a timestamp. For each batch: the dataset source, the acceptance criteria, and any quality signals such as inter-rater agreement.
Crucially, the trail should be immutable enough that no one can quietly rewrite it after the fact.
Capture it as work happens
Reconstructed provenance is the part reviewers trust least, because it can be curated. Provenance captured at the moment of work cannot. That is the difference between a document and evidence.
The questions an auditor will actually ask
Prepare for the concrete ones: for this labelled example, who produced it and are they verified? What instructions did they follow, and which version? Who reviewed it, and did they change anything? When did this happen? If you can answer those from a record rather than from memory, you are audit-ready.
Make the trail tamper-evident
A trail that anyone can quietly edit after the fact is weak evidence. The strong version is append-only and timestamped, so the record of who did what cannot be rewritten to look better before a review. That property is what turns a nice internal log into something an external auditor will accept.
See a real trail
Pathwize records this trail automatically, so an auditor can follow any output home. Book a demo to walk it end to end with your compliance team.