Audits and Evidence · 9 min read
The Audit That Turns into a Two-Week Project
Sooner or later an auditor, an investor or an insurer asks for proof: which version of the data policy was in force last March, who approved the expense rules, and whether staff confirmed the security update before the incident. Without a document audit trail, answering those questions turns into two weeks of digging through inboxes and shared drives. An audit is also a good test of any policy management software, because most of what an auditor asks for should come from one record.
When I was building my previous company, we hit exactly this during due diligence. We had made the right decisions and the policies were real, but none of it had left a record that a system could confirm, so we were rebuilding it from memory, which is an uncomfortable place to be when someone outside the company is asking the questions.
Four signs your next audit will turn into a project:
- Policy approvals happen over email or in meetings.
- Your files are named “Final,” “Final v2” and “Final REVISED.”
- Policy updates go out as a Slack message, with no record of who read them.
- Nobody could say, in five minutes, which version of a policy was live on a given date.
Key takeaways
- A document audit trail records who created, changed, approved, sent and acknowledged a document, with names and times.
- The audit trail proves the process and version history proves the content, so an audit needs both.
- Approvals and acknowledgments only count as evidence when they’re tied to a specific version.
- The best audit trail builds itself as the work happens, so there’s nothing to assemble later.

Why the trail goes cold
Most teams never design a record. Policies get written in Google Docs, saved to a shared drive or a Notion page, approved in a meeting and announced on Slack, so each tool holds a piece and none of them holds the whole story.
Those tools were built for writing together rather than for proving what happened, so they show what a document says today but not who approved it, in what order, or which version someone confirmed six months ago. When the question finally comes, the answer is spread across inboxes and chat threads that nobody can find in a hurry.
What a document audit trail needs to capture
A document audit trail records every important action on a document, in time order, from the day it’s created. You don’t need every keystroke, only the actions an auditor is likely to ask about:
- who created the document, and for whom
- each saved version, with who saved it and when
- each approval and rejection, with the reason for a rejection
- who it was sent to, and whether they were asked to acknowledge it
- each acknowledgment, by name, with a date and time
- changes to who can see it, and where it lives
The acknowledgment line matters most, and it’s the one most tools miss. An acknowledgment of “the policy” is nearly worthless, while an acknowledgment of a specific version is real evidence, because if staff confirmed the security policy in February and it changed in April, you need to know which of the two they actually saw.
A document audit trail example
Here’s a real trail from a test policy in AllyMatter, read from the oldest line to the newest, with each line set against the question an auditor would ask.
| What the log says | What it proves |
|---|---|
| Paul Carus created document Remote Work Policy with tags: Global | Who wrote it, when, and who it was meant for |
| Paul Carus saved version V1.0 | The first version on record |
| Paul Carus updated the review by date | Someone owns keeping it current |
| Paul Carus started the workflow Policy Review | It went through a defined sign-off, not an email thread |
| Epictetus Freed rejected the document, with a comment | A reviewer pushed back, and why |
| Paul Carus saved version V1.1 and restarted the workflow | The fix went back through the full sign-off |
| Epictetus Freed approved, Lao Tzu Chen approved | Who signed off on the version that went live |
| Paul Carus sent an acknowledgement request to 9 people | Who it went to, with the full recipient list |
| Iris Murdoch acknowledged the document | A named person confirmed it, with a date and time |
Nobody typed any of this up, because every line was written by the system while the people involved simply did their work.
Version history versus version control
Version history is the list of how a document changed, while version control is the set of rules about how changes happen, covering who can make them, who has to approve them and what happens to the old version, and an audit needs both.
Picture a leave policy that is updated mid-year, reviewed by legal, approved by the HR head and put live. Six months later a dispute turns on the old wording and someone asks what the policy said on a given date, which a list of saves can’t answer, because what you need is the full text of the version that was live, along with who approved it and when.
In AllyMatter every saved version is kept and you can open any of them, and Version compare shows every word removed and added between two versions. Restoring an old version doesn’t overwrite anything, because it creates a new version that has to be approved again before anyone sees it, so the chain stays intact.

Approvals that leave a record
Email approvals don’t age well, because people leave, inboxes get archived and a reply-all from eight months ago doesn’t show which version was approved. When a review asks who cleared the updated policy and when, an old email thread is not an answer that holds up.
A structured approval workflow puts the sign-off on the document itself. In AllyMatter, the document is locked while it’s under review, so the approver sees exactly the version that goes live, and each approver is told when it’s their turn. A rejection has to come with a reason that stays on the record, as in the example above, and after a fix the document goes back through the whole sign-off from the first step.

The acknowledgment record that closes the loop
Approval is only half the picture, and the other half is proof that the right people read and confirmed the current version.
Say a healthcare team updates its data handling policy after a rule change, gets it approved and sends out a notice. Four months later an auditor asks them to show that staff confirmed the new version before it took effect, and all they have is the message they sent, with no way to tell who opened it, which version was live at the time, or who never responded.

In AllyMatter, sending a policy for acknowledgment writes its own line to the trail, with the full list of who it went to. Each person acknowledges on the policy itself while signed in, and their acknowledgment is recorded by name with the date, time and version, while automatic reminders go to anyone who hasn’t responded on the schedule you set. When the policy changes, the new version is approved again and sent back out, so the record always matches what’s live.
What auditors expect from a document audit trail
Auditors rarely care which tool you use. They care whether the history can stand up to questions, and they test it in the same five ways.
Nothing is overwritten
Earlier versions and earlier entries stay where they were when something changes. A history that replaces old information can help people collaborate, but it is weak evidence, because nobody can show what used to be there.
Every entry names a person
Each event points to whoever did it, whether that is an author, an approver, an admin or the person who acknowledged. If the trail says a document changed, nobody should have to guess who changed it.
Every entry has a date and time
The timestamp is what lets you show what was in force during an incident, a dispute or an audit period, so it has to be recorded by the system and not typed in by hand.
You can rebuild what a document said on a date
The real test is not today’s version. It is whether you can open the version that applied on a given day and show who had approved it and who had confirmed it.
The trail lasts as long as the record
Rules that require a record usually expect its history to be kept for the same period, and a trail that disappears when a document is deleted fails that test.
Audit log, version history and acknowledgment records
These three records are often treated as one, but they answer different questions, and an auditor will usually ask for all of them.
| Record | What it proves | The question it answers |
|---|---|---|
| Version history | What the document said at each point, and what changed between versions | What did this policy say on March 3? |
| Audit log | Who did what and when: created, edited, approved, rejected, sent, moved or deleted | Who approved this version, and when? |
| Approval status | Whether the version people see is the current approved one | Is this the version in force? |
| Acknowledgment records | Which people confirmed which version, and when | Did the people it covers confirm this version? |
A document can have a clean log and still be out of date, and it can have a current approved version while you need an older one for last year’s audit period. That is why the four belong together.
Audit trail requirements by standard
Regulations and standards use different words, from audit trails to documented information to logging, but they ask for the same things: a record that is time-stamped, tied to a person and kept.
| Rule or standard | What it asks for |
|---|---|
| FDA 21 CFR Part 11 | Secure, computer-generated, time-stamped audit trails that record the date and time of actions that create, change or delete electronic records. Changes must not obscure earlier information, and the trail is kept as long as the record. |
| HIPAA Security Rule | Audit controls that record and examine activity in systems holding electronic health information, and policy documentation kept for six years from when it was created or last in effect. |
| NIST SP 800-53 | Audit records that show what happened, when, where, the source, the outcome and who was involved, kept long enough to support later investigations. |
| ISO 27001:2022 | Logs that record activities and events, which are produced, kept, protected and reviewed. |
| ISO 9001:2015 | Control of documented information, including control of changes such as version control, and its retention and disposal. |
| SOC 2 | Changes that are authorized, documented, tested and approved before they are put in place, which auditors check through the record of each change. |
Sources: 21 CFR 11.10(e), 45 CFR 164.312(b) and 164.316(b)(2), NIST SP 800-53 Rev. 5, AU-3 and AU-11, ISO/IEC 27001:2022 Annex A 8.15, ISO 9001:2015 clause 7.5.3, AICPA Trust Services Criteria, CC8.1
How to show what a document said on a past date
- Fix the date. Start from the incident, the dispute or the audit period in question.
- Find the version in force. Use the version history to find which approved version applied on that day.
- Check what changed around it. Compare it with the versions before and after, so you know what the people involved actually read.
- Show who approved and who confirmed it. Take the approval entries and the acknowledgments for that version from the log.
- Export the evidence. Save the version and its log entries together, with the date range you used.
What each audit trail entry should record
NIST’s list of what an audit record should contain is a good template, even outside government. Here is how it applies to a policy or procedure.
| Field | What to record |
|---|---|
| Who | The named person, never a shared account |
| What | The action: created, edited, saved a version, approved, rejected, sent, acknowledged, moved, deleted or restored |
| When | The date and time, recorded by the system |
| Which document | The document and the version the action applied to |
| Outcome or reason | The result, and the reason for a rejection or an exception |
| Audience | For a send, who it went to |
Some teams also keep a version table at the top of each document. It is a useful summary, but it goes stale the first time someone forgets to update it, so the system’s own history should always be the record and the table only a summary of it.
One honest limit: software keeps the trail, but it doesn’t decide how long you must keep it or put a document on legal hold. Your retention schedule does that, and our guide to records retention schedules explains how to set one.
How AllyMatter builds the trail into the work
In AllyMatter the audit trail isn’t a report you run at the end, because it’s written as people work.
Every policy has its own trail. Open the audit log on any document to see its whole history, newest first, and filter it by date range or by person when you need one part of it.
Admins see the whole workspace. The workspace audit log shows every document’s activity in one place, for when the question is “what changed last quarter?”
The proof is a file. Export any document’s trail as a PDF or a CSV and hand it to the auditor.
History survives. If a document is deleted its history is kept, and completed acknowledgments stay on the record after someone leaves the company.
You can see who looked. Each policy’s analytics show who viewed it, how long it was on their screen and when they last opened it, along with each completed acknowledgment.
Together with version history, that means the record already exists by the time anyone asks for it. If you’re putting this in place early, our guide to startup compliance documentation covers the basics worth having first.
Start your 30-day free trial of AllyMatter. No credit card to start, and a 30-day money-back guarantee if you subscribe and change your mind. Free migration.
Want to look around first? Try the AllyMatter sandbox with sample data already loaded.
Three scenarios
An honest read on whether you need this yet:
If you’re under 30 people and nobody outside the company ever asks about your policies, a shared drive and careful file names will hold for now.
If you’re 30 to 200 people and the four signs at the top are familiar, this is the moment, and AllyMatter is what I built for exactly this.
If you answer to an auditor, a regulator or investors doing due diligence, a document audit trail isn’t optional, and we’d start with AllyMatter.
More on audits and evidence
- 10 Ways How AllyMatter Can Help Legal & Compliance Teams
- CARF Accreditation: How to Keep Your Policies and Procedures Survey-Ready
- Common Controls Mapping: How to Map Your Policies Once and Use Them Across Standards
- Delete or Archive, Your Compliance, Your Call
- Document Audit and History: 100% Visibility, Zero Gaps
- How to Prepare for a Compliance Audit: A Guide for Small and Growing Businesses
- How to Run ISO 9001 Document Control in AllyMatter
- ISO 9001 Surveillance Audit: What Auditors Check and How to Prepare
- PDF Export of Any Document
Questions about document audit trails
How long should you keep a document audit trail?
As long as the record it describes, which is what FDA Part 11 says for electronic records. HIPAA policy documentation is kept for six years from when it was created or last in effect. Set the period in your records retention schedule rather than leaving it to the tool.
What is the difference between an audit trail and version history?
Version history shows what the document said at each point. The audit trail shows who did what to it and when, including approvals, sends and acknowledgments. You need both to show what was in force and who agreed to it.
What is a document audit trail?
A document audit trail is a record, in time order, of everything important that happened to a document: who created it, each version, who approved or rejected it and why, who it was sent to, and who acknowledged it. Because the system writes it as the work happens, it answers an auditor’s questions without anyone having to remember what happened.
What should a document audit trail capture?
At a minimum it should capture the creation of the document, every saved version, each approval and rejection with its reason, each send with the list of people it went to, each acknowledgment by name, and any change to who can see it, with a person and a timestamp on every line.
What’s the difference between version history and an audit trail?
Version history shows what the document said at each point, while the audit trail shows what happened to it, such as who approved it, who it went to and who confirmed it. You need both, because one proves the content and the other proves the process.
Why does it matter which version someone acknowledged?
Policies change, and someone who confirmed the January version hasn’t confirmed the one you published in April. An acknowledgment that isn’t tied to a version can’t tell you which rules a person actually agreed to, which is usually the very thing a dispute turns on.
Why aren’t approval emails enough?
Email approvals are real, but they’re fragile, because people leave, inboxes get archived and a forwarded thread doesn’t prove which version was approved. A sign-off recorded on the document itself, with names and times attached, holds up much better when someone outside the company asks.
When should a growing company set up a document audit trail?
The right time is before the first serious review rather than during it, which for most companies is somewhere around 50 people, when policies start to touch several teams and informal sign-offs stop being reliable.
Start your 30-day free trial of AllyMatter. No credit card to start, and a 30-day money-back guarantee if you subscribe and change your mind. Free migration.
