insight
What an audit trail has to prove
A log file is not evidence. An audit trail has to show who acted, on which matter, against which version, and whether a human accepted the risk before anything left the firm.
Legal technology loves the phrase “full audit trail.” Too often it means a firehose of events: logins, clicks, model calls, exports. Volume is not proof. When something goes wrong, the question is whether you can reconstruct a defensible story — not whether you stored every interrupt.
Logs record activity; trails record accountability
A system log answers “what happened in the machine?” An audit trail for supervised legal work has to answer something closer to:
- who initiated the work
- which matter and client context constrained it
- which sources or documents informed it
- who reviewed the output
- whether that review approved release
- what exactly was released
If your trail stops at “model returned text at 14:02,” you have telemetry. You do not have evidence of professional judgment.
Integrity beats completeness
An editable history is worse than a short one. If supervisors can quietly amend notes after a complaint lands, the trail is theatre. Prefer append-only decisions, immutable version references, and clear separation between draft state and released state.
That distinction matters under UK data protection duties as well as professional ones. The Data Protection Act 2018 expects organisations to demonstrate accountability for processing — not merely to claim it. Demonstration requires records that survive scrutiny, not screenshots assembled under pressure.
The minimum viable proof
For AI-assisted drafting and research, the minimum useful trail is smaller than vendors imply:
- Matter binding — the output is tied to a matter, not a free-floating chat.
- Source attribution — citations point to retrievable material, not vibes.
- Human gate — a named person accepted the risk before external use.
- Release snapshot — the bytes that left match the bytes that were approved.
Miss any one of those and you will spend the investigation rebuilding them from memory and Slack.
Design the trail for the hostile reader
Write the trail for the person who does not trust you: a regulator, an insurer, an opposing firm, a client’s GC. They will not be impressed by dashboards. They will ask for a sequence that holds together without narration from the people who built the system.
If that sequence cannot be exported cleanly, it is not an audit trail. It is a product feature waiting for a bad day.