AI GxP validation for regulated life sciences
Data Integrity

Audit Trail Review: The Control Everyone Has and Almost Nobody Runs

Every validated system records an audit trail. Far fewer teams review one. What review actually means, how to make it proportionate instead of impossible, and why it is one of the most common inspection findings.

Cybroscape Technologies5 min read

Key takeaway

Every validated system records an audit trail. Far fewer teams review one. What review actually means, how to make it proportionate instead of impossible, and why it is one of the most common inspection findings.

Every validated system you own records an audit trail. Ask who reviews them, how often, and where the record of that review lives, and the room usually goes quiet.

That gap is one of the most reliable findings in a GxP inspection, and it is entirely fixable — but not by reviewing everything, which is what makes teams give up before they start.

Why 'the system captures it' isn't an answer

Both 21 CFR Part 11 and EU Annex 11 expect audit trails to be reviewed, not merely generated. MHRA's data integrity guidance is the most explicit about it: review is part of the control, not an optional extra.

The logic is simple. An audit trail nobody looks at deters nobody and detects nothing. It only becomes a control at the moment someone would notice.

So the inspector's question is never "do you have audit trails". It is who reviews them, against what, how often, and show me the last three.

Making it proportionate

Nobody can read every audit trail entry, and no regulator expects it. What they expect is a risk-based approach you can articulate. In practice that means deciding three things.

Which events matter. Not every entry is interesting. The ones that usually are: changes to results or data after initial entry, changes to specifications or limits, deletions, permission and role changes, changes to system date or time, disabled controls, and repeated failed logins. Everything else is background.

When review happens. The strongest model is review at the point of an existing decision — the reviewer approving a batch record or a lab result also reviews the audit trail for that record. It is contemporaneous, has a natural owner, and produces a record automatically. Periodic system-level review then covers what record-level review cannot: administrator activity, configuration changes, permission drift.

What a reviewer does when something looks wrong. If there is no defined escalation, reviews quietly become ticking exercises.

Writing it down

Your procedure needs to answer, per system or system class:

  • Which event types are reviewed, and the rationale for that selection.
  • Who reviews, and their independence from the activity being reviewed.
  • Frequency, tied to risk rather than to convenience.
  • How review is evidenced — a signed record, not a memory.
  • What happens on a finding: deviation, investigation, CAPA.
  • How review itself is verified — someone checking that reviews happen.

If your system can filter to the event types that matter, the whole thing becomes practical. If it cannot, that limitation belongs in your risk assessment — and in the requirements for whatever replaces it.

The failure modes

  • The procedure exists, the reviews don't. Most common by far, and trivially detectable: the inspector asks for the last three records.
  • Reviewing everything, so nothing gets reviewed. An unachievable procedure guarantees the finding.
  • The person reviewed is the person reviewing. A system administrator reviewing their own activity is not a control.
  • Findings with no trail. If a review has never produced a single question in two years, nobody believes it is happening.
  • Forgetting integrations. Data crossing between systems is where attribution is most often lost, and where audit trails are least often reviewed.

Related: data integrity (ALCOA+), preparing for a GxP audit, and for AI systems the same obligation applies to review records — see what inspectors ask about AI.

Where to go next

Explore Cybroscape GxP Copilot for AI-native validation, Cybroscape TraceDraft for source-traceable clinical documentation, or book a demo to see either on your own data.

Part of our guide to GxP software — categories, evaluation criteria and how the platforms compare.

Audit trail
  1. 14:32Signed: Approved for releaseQA Manager
  2. 11:05Changed risk of URS-015Validation lead · Supplier test evidence acceptedMedium → Low
  3. 10:48Edited expected result, OQ-07Validation lead · Lockout after 5 attempts, per URSv3 → v4
  4. 09:12Recorded result, OQ-07Tester · Evidence attachedPassed
Append-only. Entries cannot be edited or deleted.
Who, what, when and whyOn every change
An audit trail an inspector can read: who did what, when, the old and new value and the reason. Entries are append-only and each one is linked to the one before, so a changed or missing entry shows.
See it on your own systemBring a URS or a system. We run GxP Copilot against it live on the call.

Sources

Primary documents referred to on this page, from their official publishers.

audit trail reviewaudit trail review procedurepart 11 audit trailwho reviews audit trailsaudit trail review frequencygxp compliance
FAQ

Frequently Asked Questions

Prefer to talk first? Chat with us on WhatsApp or book a call with an expert.

Is audit trail review actually required?

Yes. 21 CFR Part 11 and EU Annex 11 expect audit trails to be reviewed, not merely generated, and MHRA's data integrity guidance is explicit that review is part of the control. An audit trail nobody looks at deters nobody and detects nothing.

Do you have to review every audit trail entry?

No, and no regulator expects it. What is expected is a risk-based selection you can explain: which event types matter (data changed after entry, specification or limit changes, deletions, permission changes, system date/time changes, disabled controls, repeated failed logins), reviewed at a defined frequency.

Who should review audit trails and when?

The strongest model is review at the point of an existing decision — whoever approves a batch record or lab result also reviews the audit trail for that record, which is contemporaneous and produces a record naturally. Periodic system-level review then covers administrator activity, configuration changes and permission drift.

What does an audit trail review procedure need to state?

Which event types are reviewed and why, who reviews and their independence from the activity, frequency tied to risk, how review is evidenced with a signed record, what happens when something is found (deviation, investigation, CAPA), and how you verify that reviews are actually happening.

What are the common audit trail review failures?

A procedure that exists while the reviews do not; a procedure so broad it is unachievable; the system administrator reviewing their own activity; two years of reviews that never raised a single question; and forgetting integrations, where data crossing between systems is exactly where attribution is most often lost.

Keep reading

All articles
Data IntegrityUser access reviews that actually catch somethingA useful access review compares system accounts and roles against an approved access matrix and current employment data, then resolves every difference. Roles and admin accounts matter more than names. · 3 min readRegulatoryUS Says SI, Europe Says AI: One Quality System, Two VocabulariesThe rename applies to US federal writing only. EU GMP, the draft Annex 22, the EU AI Act and MHRA all still say artificial intelligence. How to run one set of procedures across both without creating a translation problem. · 5 min readData IntegrityBackup is not restore: validating GxP backup and disaster recoveryA backup is only proven by a restore. Validate by restoring to a separate environment and checking record counts, attachments, audit trails, metadata and recovery time against what the business needs. · 3 min readData IntegrityChromatography data system validation: where the findings come fromCDS validation is mostly about configuration: audit trail always on, individual logins, separated roles, every injection saved, and a risk-based audit trail review built into result approval. · 3 min readData IntegrityData integrity in 2026: ALCOA+ across GxP systemsA modern gap-assessment and remediation approach that keeps ALCOA+ from drifting. · 6 min readData IntegrityData Integrity Across ELN and LIMS: The ALCOA+ Gap Most Teams Miss at the Integration BoundaryWhere ALCOA+ evidence breaks down at the ELN-LIMS boundary, and how to build a validated integration architecture that keeps the chain unbroken through every data transfer. · 6 min readData IntegrityHybrid systems: where paper and electronic records meet, and drift apartIn a hybrid system the electronic data is part of the record, so a signed printout alone is rarely enough. The key control is a two-way link between each printout and the electronic data behind it. · 3 min readBuyer GuideGxP Compliance Software: What It Does, What It Doesn't, and How to ChooseGxP compliance software explained: what it covers, how it differs from eQMS and validation software, evaluation criteria, and the buying mistakes that cost quality teams time and budget. · 7 min read

Bring a system. We'll show you the package.

Book a demo, or ask a validation lead a quick question on WhatsApp.

  • We reply within one business day
  • We run your URS live on the call
  • You get a clear plan for your system
Chat on WhatsApp

Book a demo

Four fields. The right specialist replies within one business day.

Your details stay private. We never share them.