Audit Trail
An audit trail preserves the history of relevant electronic-record actions so reviewers can reconstruct who changed what and when, without losing the original information.

On this page · 13 sections
- 1What an audit trail records
- 2US and EU compared
- 3Who reviews it and how often
- 4Common failure modes and checks
- 5Inside V5: review history in the record context
- 6Define the record before you define the trail
- 7Make a change event understandable
- 8A practical audit trail review sequence
- 9Worked example: a corrected weight is not a corrected history
- 10Test the configuration, not just the demonstration
- 11Pitfalls that hide the real issue
- 12Explain it for your operation
- 13Questions to ask before choosing software
How does Audit Trail apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What an audit trail records
Part 11 describes secure, computer-generated, time-stamped audit trails that independently record the date and time of operator entries and actions that create, modify or delete electronic records. Changes must not obscure previously recorded information, and the trail must be kept at least as long as the underlying record and be available for FDA review and copying.
Annex 11 clause 9 adds that, for changes or deletions of GMP-relevant data, the reason should be documented, and audit trails should be available, convertible to a readable form and regularly reviewed.
These are jurisdiction-specific controls, not a universal definition of every business log. <a href="https://www.govinfo.gov/content/pkg/CFR-2025-title21-vol1/xml/CFR-2025-title21-vol1-part11.xml">21 CFR 11.10(e)</a> is U.S. regulatory text for electronic records within its scope. FDA’s <a href="https://www.fda.gov/media/75414/download">August 2003 Scope and Application guidance, III.C.2</a> describes enforcement discretion for specific Part 11 audit-trail requirements while preserving applicable predicate-rule obligations, including changes not obscuring prior entries. Enforcement discretion does not repeal the rule or justify abandoning record integrity.
For EU GMP, read <a href="https://health.ec.europa.eu/system/files/2016-11/annex11_01-2011_en_0.pdf">published Annex 11, clauses 9 and 12.4</a> together: clause 9 uses risk-based consideration of GMP-relevant change and deletion trails, and clause 12.4 addresses recording operator identity and date/time for entering, changing, confirming or deleting data. The Commission’s <a href="https://health.ec.europa.eu/medicinal-products/eudralex/eudralex-volume-4_en">published guideline index</a> lists the January 2011 revision, operative from 30 June 2011. Consultation proposals are not substituted for this published text here.
02US and EU compared
| Point | 21 CFR 11.10(e) | EU GMP Annex 11 clause 9 |
|---|---|---|
| Status | U.S. regulation for records in Part 11 scope | EU GMP guideline |
| When needed | Regulatory control in scope; see FDA enforcement-discretion guidance and predicate rules | Considered based on risk |
| Reason for change | Not stated in 11.10(e) | Should be documented for GMP-relevant changes |
| Review | Covered by predicate-rule record review (FDA Q&A) | Should be regularly reviewed |
03Who reviews it and how often
FDA's 2018 Q&A says people responsible for reviewing CGMP records should review the audit trails that capture changes to that data as part of the same review — for example, the quality unit's review under 211.192. Where regulations set a review frequency, the audit trail follows it; otherwise frequency is set by risk assessment based on data criticality and controls.
The source for these review expectations is <a href="https://www.fda.gov/media/119267/download">FDA’s December 2018 Data Integrity Q&A, questions 7 and 8</a>. It is nonbinding guidance explaining drug CGMP record-review expectations, not a new stand-alone regulation imposing one interval on every industry.
04Common failure modes and checks
- Audit trail switched off or configurable by ordinary users.
- Trail exists but is never reviewed, or reviewed only during inspections.
- Review of a full system log rather than changes relevant to the record.
- Reasons for change left as free text like 'update'.
05Inside V5: review history in the record context
The inspected V5 app implementation includes a batch audit history combining audit events and electronic-signature entries associated with a work order and linked records. Event fields include time, operation, record reference, changed fields, actor information and previous/new snapshots where present. These fields provide review context; their presence in code does not prove every workflow captures every event or that each field is always populated.
Evaluate the specific workflow and configuration with the team. Confirm applicable access, retention and review arrangements rather than assuming availability on every plan. Customers define record scope, review procedures and authorised decisions. Heavily regulated or validated use belongs in an Enterprise private-cloud discussion; V5 IQ/OQ and validation support are Enterprise-only, and customers retain responsibility for validation, PQ and approvals. Software history does not itself establish compliance or a validated state.
06Define the record before you define the trail
Start with the decision the record supports: accepting an incoming material, executing a production instruction, approving an analytical result or releasing a batch. Identify the original data, associated metadata, calculations and approvals needed to reconstruct that decision. The audit trail belongs to this record context. A list of user logins alone cannot explain why a reported result changed, while a result-change history alone cannot explain whether someone had the authority to make the change.
An activity log, security log and audit trail may overlap, but they answer different questions. A security log can show an unsuccessful login; an activity log may show that a screen was opened; a record audit trail should expose relevant creation, modification or deletion events. A business transaction history can trace stock movements without necessarily recording changes to the transaction itself. Ask what is captured rather than accepting the label on the menu.
Map boundaries between instruments, spreadsheets, middleware and the manufacturing system. If an instrument generates a dynamic result and only a PDF is transferred downstream, reviewing the downstream history may miss reprocessing in the original instrument. The record inventory should identify the authoritative source, transfer method, reviewer and retention location. This is a practical system-design exercise, not a claim that every supporting application must use the same audit-trail implementation.
07Make a change event understandable
A useful event connects a stable record reference with the action, identity and time. For an altered value, the reviewer needs to understand the previous value and the resulting value without losing the original evidence. A change description should distinguish correction, recalculation, replacement and deletion. If the record includes units, status or specification revision, those details can matter as much as the number. Changing a unit can change the meaning even when the displayed value stays identical.
Reasons for change should explain the event rather than repeat the action. “Updated” says little; “Corrected material lot selected in error, checked against the intake scan” identifies an evidence trail to inspect. The explanation must not invent certainty. If the reason is not known, an investigation may be needed. A required reason field can improve completeness but cannot establish that the explanation is true or that the change was appropriate.
Time needs context when sites, instruments and people operate across time zones. Decide how timestamps are displayed, how clocks are managed and how changes to system time are controlled. Reviewers should understand the difference between an event occurring and a delayed event being synchronised. Test these behaviours using the intended configuration; do not assume a timestamp in a screen means every connected source uses the same clock or time zone.
08A practical audit trail review sequence
First confirm that the record set is complete for the activity under review. Establish the batch, sample, equipment event or material transaction and the relevant execution window. Then compare the underlying record with changes that could affect its interpretation. Look for amended results, removed entries, changed statuses and changes after apparent completion. Filtering should make the review manageable without hiding relevant events or severing the relationship with the original data.
Next assess each significant exception against evidence: the approved instruction, raw result, instrument output, material identity or documented correction. Ask whether the user was authorised, whether the reason is supported and whether the change affected a quality decision. A legitimate correction can still reveal a process weakness. Conversely, an unusual timestamp is a signal to understand, not automatic proof of wrongdoing. Avoid turning exception counts into accusations.
Record the scope reviewed, the conclusion and any follow-up. If the review found a material discrepancy, link it to the appropriate deviation or investigation rather than resolving it through an informal comment. Preserve unresolved questions for the person responsible for disposition. The review record should let a later reader distinguish “no significant exceptions identified” from “exceptions investigated and accepted” and from “review incomplete.” Those are different states with different decision consequences.
Set the procedure around the applicable record-review obligation and a documented risk assessment. Do not invent a universal weekly or monthly frequency. Routine record review, periodic system checks and security monitoring serve different purposes and may use different intervals. See <a href="/glossary/audit-trail-review-workflow">audit trail review workflow</a> for organising the operational handoffs; this article explains what the trail is and what its evidence means.
09Worked example: a corrected weight is not a corrected history
Consider a hypothetical batch where an operator records 49.6 g against an instruction requiring 50.0 g within an approved tolerance. Later the displayed value becomes 50.1 g. The new result appears acceptable, but its acceptability cannot be judged from the final screen alone. The reviewer asks when the change occurred, who performed it, what the original weighing evidence says and whether the original material addition actually occurred at the recorded amount. These quantities illustrate a review problem, not a V5 performance result.
If a contemporaneous balance record supports 50.1 g and the operator entered 49.6 g incorrectly, the correction may be justified through the site procedure. Preserve both values and the explanation. If the balance record instead supports 49.6 g, rewriting the electronic number does not change what went into the vessel. The team needs an impact assessment and an authorised decision about the physical batch. The audit trail exposes the change; it does not decide the disposition.
Now suppose the correction was made after the batch had already been reviewed. The change may require re-review or another controlled action under the approved procedure. Ask whether the reviewer was notified and whether the record status still reflects the decision actually made. This distinguishes data correction from review status, electronic signature and product release. A signature is evidence of a particular approval act; it is not a substitute for understanding the history of the record being approved.
10Test the configuration, not just the demonstration
Select representative records and document expected behaviour before testing. Create a record, correct a value, amend a status and attempt a prohibited change using an ordinary operator account. Examine whether the resulting history can be related back to the affected record. Include rejected actions where the security or activity log is expected to capture them, but do not assume rejected actions and successful record changes belong to the same log.
Test privileged access separately. Identify who can change audit settings, alter permissions, manage clocks or perform data maintenance. An administrator may require exceptional powers, but those powers should be understood and governed. Explore whether privileged actions are themselves recorded and whether the reviewer can obtain evidence independently of the person whose actions are reviewed. A button labelled “audit trail” does not answer these questions.
Check migration, export and restoration scenarios with the system owner. A readable export should retain enough context for its intended use; a spreadsheet stripped of record identifiers or time-zone information may be misleading. Confirm how old records and their trails are retrieved after an upgrade or retention transition. Qualification and validation evidence should match intended use. Enterprise-only V5 IQ/OQ and validation support does not transfer responsibility for customer validation, PQ or approvals to the supplier.
11Pitfalls that hide the real issue
The first pitfall is reviewing only the latest version. Final values can be internally consistent while concealing a sequence that matters to interpretation. The second is reviewing everything indiscriminately: thousands of low-relevance events can bury a changed analytical result. A justified review approach identifies what is critical, retains access to the wider history and documents why the selected scope is appropriate. Filtering is a review aid, not permission to remove evidence.
Another pitfall is treating reasons as a compliance checkbox. Repeated “typing error” explanations may reflect weak interfaces, rushed recording, unclear instructions or a more serious issue. Investigate the pattern proportionately before deciding that retraining is sufficient. Trend by record type and cause when useful, taking account of workload and the number of opportunities for errors. A higher count at a larger site is not automatically evidence of worse control.
Shared accounts weaken attribution. When several operators use one identity, a history that records the account name does not reliably identify the person. Similarly, approval recorded through an already-open session requires appropriate identity controls. Discuss these issues alongside <a href="/glossary/e-signature">electronic signatures</a> and <a href="/glossary/data-integrity">data integrity</a>, while keeping the distinctions clear: trustworthy attribution, record preservation and approval meaning are connected but not identical controls.
12Explain it for your operation
For pharmaceutical batch review, start with records used to judge execution and product quality. Changes to material identity, critical process observations and laboratory conclusions deserve attention in the context of the batch decision. For a warehouse operation, focus on inventory identity, status, quantity and location changes that influence picking or dispatch. A stock movement is not necessarily an error; the question is whether the transaction and any subsequent amendment can be reconstructed.
For equipment and calibration, consider changes to results, acceptance criteria, instrument status and next-due dates. A changed due date may be an authorised schedule adjustment or may conceal overdue work; the surrounding evidence distinguishes them. For QMS records, examine who changed findings, actions and closure conclusions. Each workflow needs a meaningful record boundary, not a generic assertion that all clicks are equally important.
Food, supplements, devices and nonregulated manufacturing have different applicable requirements. Do not copy drug CGMP review obligations into every operation as though Part 211 universally applies. Even where Part 11 is not applicable, a business may still need traceable changes for contractual, quality or operational reasons. Begin with the actual product, jurisdiction and record purpose, then identify the relevant requirement and practical control.
13Questions to ask before choosing software
Ask a supplier to demonstrate the actual record type you intend to use, not an unrelated administrative history. Which events are captured? Can you see the original value? Is the user identifiable? How are reasons recorded? What happens to history when a record is deleted or moved? Can a reviewer navigate from the event to the record and supporting evidence? Request explanations of limitations rather than a blanket statement that the system is compliant.
Ask how your intended roles, configuration and hosting model affect these answers. Clarify retention, exports, privileged access and connected instruments. Agree what evidence the supplier can provide and what your organisation must test, approve and maintain. During a trial, explore the review workflow using suitable nonsensitive sample records; do not treat a successful demonstration or trial as validation or evidence of suitability for a heavily regulated deployment. Such V5 requirements belong in an Enterprise private-cloud discussion.
Frequently asked questions
Q.Does Part 11 require a reason for change?+
11.10(e) does not state one; EU Annex 11 clause 9 expects reasons for GMP-relevant changes and deletions, and many firms record them for both.
Q.How long must an audit trail be kept?+
Under Part 11, at least as long as the subject record. Record retention periods come from the predicate rules.
Q.Who should review audit trails?+
FDA's 2018 Q&A says the people who review the associated CGMP records, as part of that review.
Q.Is audit trail review required for every record?+
Frequency follows the record's review requirement, or risk where none is specified.
Q.Is a security log the same as an audit trail?+
Not necessarily. Login and access events explain security activity; an electronic-record audit trail explains relevant record creation, changes and deletions. Confirm the contents and record linkage rather than relying on the name.
Q.Can an audit trail prove that a corrected result is right?+
No. It preserves evidence of the change. The reviewer still checks the supporting raw data, justification, authority and impact before accepting the correction.
Q.Does a trial establish validated use?+
No. A trial helps evaluate the workflow. Intended-use assessment, controlled qualification or validation, customer PQ and approvals are separate responsibilities; V5 IQ/OQ and validation support are Enterprise-only.
Primary sources
Further reading
Explore this topic
Audit Trail sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
Electronic records, signatures, audit trail and ALCOA+ data-integrity principles.
HCT/Ps, blood cGMP, donor eligibility, ISBT 128 labeling and forward-tracing lookback.
Want to see how Audit Trail could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
