Short answer
Audit trail software for batch release must record every change to batch-critical data with who, what, when and why, never overwrite earlier values, and let QA review those changes before signing. The release itself should be an electronic signature that only an authorised person can apply, bound to the batch record it approves.
Batch release is the moment a quality reviewer puts their name to a statement: this batch was made as the procedures say. The audit trail is how they know that is true, and how an inspector checks it later. If the trail cannot be reviewed quickly before release, it is not doing its job.
What the regulations actually ask at release
In the US, production and control records must be reviewed and approved by the quality unit before a batch is released or distributed (21 CFR 211.192). Where those records are electronic, Part 11 requires secure, computer-generated, time-stamped audit trails that do not obscure earlier entries (11.10(e)). FDA's data integrity guidance adds the practical consequence: audit trails that capture changes to critical data should be reviewed with each record, before its final approval.
In the EU, Annex 11 asks for a system-generated audit trail of GMP-relevant changes and deletions, with the reason documented, kept readable and regularly reviewed. Its batch release clause goes further: only a Qualified Person may certify release, and the system must identify and record that person through an electronic signature.
| Expectation | Where it comes from | What the software must do |
|---|---|---|
| Record review before release | 21 CFR 211.192 | Block release until every required review step is complete |
| Secure, time-stamped audit trail | 21 CFR 11.10(e) | Server-side timestamps; append-only entries that never overwrite |
| Audit trail reviewed with the record | FDA data integrity Q&A | Show critical-data changes beside the batch record QA is approving |
| Reason for change | EU GMP Annex 11, §9 | Require a reason when critical data is changed or deleted |
| Only authorised release | EU GMP Annex 11, §15 | Release action limited to the authorised role, signed electronically |
What a release-ready audit trail records
- Who: the individual, under their own unique login. Shared accounts make every downstream entry unattributable.
- What: the record, the field, the old value and the new value.
- When: a timestamp generated by the server, not the user's device.
- Why: a reason, required whenever batch-critical data is changed or deleted.
- Under which rules: the version of the procedure or approval chain in force at the time.
Review by exception, or review becomes a formality
A batch can generate thousands of audit entries. If QA has to scroll through all of them before every release, the review either delays release or quietly stops being read. The fix is to define which data is batch-critical and have the software surface only the changes that matter: edited results, late entries, reopened steps, deviations, and anything changed after a review was signed.
- 1Agree with QA which fields and events are critical for each record type.
- 2Flag those changes automatically on the batch record, with old value, new value, person and reason.
- 3Make the reviewer acknowledge each flag before the release action unlocks.
- 4Record the review itself in the audit trail, so it is provable that it happened.
The release signature
The release is the most consequential action in the system, so it gets the strictest controls. Only the authorised role can perform it, enforced on the server rather than by hiding a button. The signature shows the signer's name, the date and time, and its meaning, such as "released for distribution". It is bound to the exact version of the batch record it approves, so it cannot be copied to another record or survive a later edit unnoticed. For the full list of Part 11 controls behind this, see what Part 11 actually asks for.
Buy, extend or build
Many sites already run an MES, LIMS or QMS with an audit trail. The gap is usually between systems: release evidence spread across a LIMS, spreadsheets, email approvals and paper. Before buying anything, check whether a release workflow on top of what you have would close that gap.
| Approach | Fits when | Watch for |
|---|---|---|
| Configure your existing MES or QMS | It already holds the batch record and has a reviewable audit trail | Review screens that show every entry instead of exceptions |
| Packaged eBMR or QMS | No electronic batch record yet, standard processes | Customisation that breaks the vendor's validated state |
| Custom release workflow | Evidence spread across systems, or a process packages do not fit | Validation effort on your side; build the audit trail first, not last |
Questions to ask any vendor
- Can an administrator edit or delete an audit entry? The answer must be no.
- Where do timestamps come from, and how is the clock kept accurate?
- Can QA see only the critical changes for one batch, in plain language, on one screen?
- Is the release signature bound to a specific record version?
- Can the audit trail be exported in a readable form for an inspector?
- What validation documentation do you supply, and what remains your work?
Sources
- 1.21 CFR 211.192: Production record review, eCFR (U.S. National Archives). Supports: quality unit review and approval of batch records before release.
- 2.21 CFR 11.10: Controls for closed systems, eCFR (U.S. National Archives). Supports: secure, computer-generated, time-stamped audit trails (11.10(e)).
- 3.Data Integrity and Compliance With Drug CGMP: Questions and Answers, U.S. Food and Drug Administration. Supports: reviewing audit trails of critical data with each record before final approval.
- 4.EudraLex Volume 4, Annex 11: Computerised Systems, European Commission. Supports: audit trails with documented reasons (§9) and electronically signed batch release (§15).