What should audit trail review cover, and how often should it happen?
By Savi C., Co-Founder · Published Nov 16, 2026
What the regulators say
FDA defines an audit trail as a secure, computer-generated, time-stamped electronic record that allows reconstruction of the course of events relating to the creation, modification or deletion of an electronic record. Its guidance treats audit trail review as the equivalent of assessing cross-outs on paper: the people responsible for reviewing a record under CGMP should review the audit trails that capture changes to its data as they review the rest of it.
On frequency, FDA is specific. If the regulations set a review frequency for the data, the audit trail follows it. Section 211.188(b) requires documentation that each significant step was accomplished, and 211.22 requires data review before release, so the audit trails behind batch data share those points. Where no frequency is specified, FDA expects one based on knowledge of the process and a risk assessment covering data criticality, control mechanisms and impact on product quality.
EU GMP Annex 11, clause 9, says audit trails should be available, convertible to a generally intelligible form and regularly reviewed, and that the reason for a change or deletion of GMP-relevant data should be documented. PIC/S PI 041-1 section 9.6 separates critical audit trails, reviewed with all other records for the operation before it is completed, for example before batch release, from non-critical ones reviewed during system reviews at a predefined frequency. The MHRA’s GXP guidance, section 6.13, adds that review may be limited to entries with GXP relevance and may use a validated exception report.
A revised Annex 11 with more detailed audit trail expectations was released for consultation in July 2025. It is a draft and is not in force, so this guide relies on the 2011 text.
Typical review points for each kind of audit trail
Your risk assessment decides where each system falls.
Audit trail
Changes to batch data in an EBR, MES or recipe system
When it is usually reviewed
With the batch record, by the person reviewing that step or record, and in full before QA approves release
Audit trail
Changes to laboratory results that support release
When it is usually reviewed
With the test record by the second analyst, and confirmed before the result is relied on for release
Audit trail
Process control and equipment data used as batch evidence
When it is usually reviewed
With the batch record, where the data is part of the record of a significant step
Audit trail
Configuration, user and permission changes
When it is usually reviewed
At a defined periodic system review, and whenever an investigation touches the system
Audit trail
Instrument status, communication logs and alerts
When it is usually reviewed
On a risk-based frequency, which FDA gives as an example of where periodic review may be appropriate
Audit trail
Audit trails across all systems
When it is usually reviewed
Sampled during self-inspection, both at random and targeted by risk, as PIC/S expects of the quality unit
What a batch-level audit trail review should cover
Changes to data
- Every modification or deletion of a GMP-relevant value, with the old value, the new value and the user
- A documented reason for each change, as Annex 11 clause 9 requires
- Where a change needed approval, the name of the person who authorised it
- Results that were reprocessed, re-entered or invalidated, and whether the original is still retained
Timing and sequence
- Entries time-stamped when the action happened, not batched at the end of a session
- Steps recorded in the order the master record requires
- No entries after the record was signed, or, if there are, the signature shows as invalidated and re-applied
Access and system state
- Actions attributed to named individual accounts, not shared or generic logins
- No sign that the audit trail was switched off, and an entry recorded if an administrator changed it
- Changes to setpoints, limits or recipes during the batch, matched to change control
The review itself
- Performed to an SOP that says which trails to review, what to look for and how to search
- Recorded, with the reviewer, the date and the scope covered
- Anything unexpected investigated and linked to a deviation where it affects the batch
Two layers, not one
Most sites need two separate reviews. The first is routine and batch-level: the reviewer checks the audit trail entries behind the data in front of them before the record is approved. The second is periodic and system-level: the quality unit checks that controls are working, that permissions are right and that routine reviews are actually finding what they should. PIC/S expects that second layer to sit in the self-inspection programme, with audit trails selected both randomly and by risk.
A periodic system review does not replace the batch-level review FDA and PIC/S expect before release, and a batch-level review does not show whether system configuration has drifted.
How Litewave fits
Litewave reads paper or electronic records, checks every entry against your master record and specifications, and shows QA only the exceptions, each linked to the page it came from. It supports 21 CFR Part 11 electronic records, signatures and audit trails. Litewave proposes, qualified people approve, and the decision on what your audit trail review covers stays in your own procedure and risk assessment.
Questions we get asked
Do we have to review every entry in an audit trail?
No. The MHRA says it is not necessary for audit trail review to include every system activity, such as user log on and off or keystrokes. PIC/S expects an assessment, during qualification, of which trails and which entries matter, and the review then focuses on those.
Can an exception report replace reading the audit trail?
It can, if it is validated. The MHRA describes an exception report as a validated search tool that identifies predetermined abnormal data or actions for the reviewer to follow up. The rules behind it, and their validation, need to be documented.
What if a system has no audit trail?
Both PIC/S and the MHRA accept alternative controls for a time, such as a paper log of changes, SOPs and secondary checks, provided they are shown to be effective and the site is working towards a system with a proper audit trail.
Sources
- FDA, Data Integrity and Compliance With Drug CGMP: Questions and Answers (December 2018)
- 21 CFR 211.22, Responsibilities of quality control unit (eCFR)
- 21 CFR 211.188, Batch production and control records (eCFR)
- EudraLex Volume 4, Annex 11: Computerised Systems (2011)
- PIC/S PI 041-1, Good Practices for Data Management and Integrity in Regulated GMP/GDP Environments (2021)
- MHRA, GXP Data Integrity Guidance and Definitions, Revision 1 (March 2018)
