Why batch record review matters
Batch record review is the quality unit’s check that a batch was made, tested and packaged exactly as approved, and that every departure was found, explained and assessed. It is the last control before a batch reaches patients, and it is one of the most cited areas in FDA inspections.
In FY2025, FDA investigators cited 21 CFR 211.192 (production record review) in 164 Form 483 observations, according to GMP Insiders’ analysis of FDA’s data. That puts it among the most frequently cited drug GMP provisions. In a set of five warning letters summarized by ECA in May 2026, four included batch record review failures, from records with “no test results” for the active ingredient to firms that had no batch record at all.
What the rules require
US (finished drugs). Section 211.192 says all drug product production and control records, including packaging and labeling records, “shall be reviewed and approved by the quality control unit to determine compliance with all established, approved written procedures before a batch is released or distributed.” Any unexplained discrepancy, including yield outside the master record limits, must be “thoroughly investigated, whether or not the batch has already been distributed,” and the investigation must extend to other batches that may be affected.
APIs. ICH Q7 section 6.70 requires written procedures “for the review and approval of batch production” and laboratory records. Section 6.71 says records for critical process steps “should be reviewed and approved by the quality unit(s) before an API batch is released or distributed.” Section 6.72 adds that “all deviation, investigation, and OOS reports should be reviewed as part of the batch record review.”
EU. EU GMP Chapter 4 requires the batch processing record to be approved by the person responsible for the processing operations (4.20). Chapter 2 makes the head of quality control responsible for evaluating batch records. Annex 16 section 1.7.11 requires the QP to be assured that “all records are complete and endorsed by appropriate personnel.” The QP does not have to read every page personally; ECA notes that QPs commonly rely on checklist-based reviews by trained staff, with records available on request.
Who reviews, and in what order
Most companies run two levels of review:
| Level | Who | Focus |
|---|---|---|
| First (production) review | Production supervisor or batch record reviewer in operations | Completeness, entries, calculations, signatures, immediate corrections |
| Second (quality) review | QA reviewer for the quality unit | Compliance with approved procedures, deviations, investigations, test results, data integrity |
| Certification (EU) | Qualified Person | Assurance that all of the above is complete before certifying |
The production review should catch documentation errors while the people involved still remember the batch. The quality review should not be a second proofreading pass. If QA spends most of its time finding missing initials, the first review is not working.
What a GMP batch record review checks
A complete batch documentation review goes beyond the batch manufacturing record itself. It covers every record that supports the batch.
1. The batch record itself
- Correct master record version was issued
- Every field completed, or marked not applicable with a reason
- Recorded values within limits; calculations correct
- Performer and checker signatures present for each significant step
- Times and dates in a logical sequence
- Corrections made properly: single line, original readable, dated, signed, with a reason
- Yield and reconciliation within limits
2. Supporting records
- Equipment logbooks and cleaning records for equipment used
- Calibration status of instruments used
- Environmental monitoring results for the production period, where relevant
- Material release status for every component lot used
- Label issuance and reconciliation records
3. Laboratory results
- All in-process and finished product tests complete
- Results within specification
- Any OOS or OOT result investigated, with a conclusion
4. Deviations and changes
- Every deviation raised for the batch is referenced
- Each deviation is closed, or has a documented impact assessment that supports release
- Any change controls affecting the batch are approved and effective
5. Data integrity
- Audit trail entries for critical data reviewed. FDA’s data integrity Q&A says “all production and control records, which includes audit trails, must be reviewed and approved by the quality unit.”
- Electronic data match what the batch record reports (for example, balance printouts or historian data versus handwritten values)
- Any invalidated result has a documented scientific justification, and the original data remain in the record
Handling what you find
A reviewer will find issues on most batches. How they are handled determines whether the review stands up in an inspection.
Documentation errors (a missing date, a transcription mistake) can usually be corrected by the person who made the entry, following the good documentation practice SOP. The correction must be traceable.
Discrepancies (a value that does not match its source, a step done in the wrong order, a yield outside limits) need a deviation record. Section 211.192 does not allow a reviewer to explain them in a margin note.
Patterns matter too. If the same error appears in many batches, it points to a problem with the master record, training or the process. Trend reviewer findings by type and feed them into CAPA.
How to make review faster without making it weaker
Review time is a real business problem: product waits in quarantine while records move between desks. Approaches that work:
- Review during production. QA reviews completed sections while the batch is still running.
- Fix the master record. Unclear instructions cause most entry errors. Put limits next to every field.
- Use right-first-time metrics. Track errors per batch record by area and by section.
- Move to electronic records. A validated electronic batch record can enforce limits and sequence at entry, so review can focus on exceptions.
- Use a standard checklist. It keeps reviewers consistent and gives the QP evidence of what was checked.
What does not work is cutting checks without justification. Any reduction in what is reviewed must be backed by evidence that the risk is controlled elsewhere.
Common batch record compliance gaps
- Release before the quality unit’s review is complete
- Deviations open at release with no impact assessment
- Investigations that stay inside one batch when sister batches may be affected
- Audit trails never reviewed, or reviewed months after release
- Reviewer signatures with no evidence of what was checked
- No written procedure for review, or one that does not match practice (Section 211.22(d), procedures not followed, was the most cited drug provision in FY2025 at 243 observations)
Batch record review checklist
- Correct, approved master record version issued
- All entries complete, legible and within limits
- Calculations, yields and reconciliations verified
- Performer and checker signatures present
- Corrections follow good documentation practice
- Supporting records (logbooks, cleaning, calibration, EM) reviewed
- All test results complete and in specification
- Deviations and OOS results referenced and assessed
- Related batches considered for any investigation
- Audit trail entries for critical data reviewed
- Review findings recorded and trended
Review batch records with AskDona
A thorough review means cross-checking the batch record against the master, logbooks, test results and the deviation log. AskDona reads these documents together and flags missing entries, values outside limits, unreferenced deviations and mismatches between records, each with a link to the page it came from. Run a sample batch record review on a recently released batch. AskDona shows the evidence; your quality unit decides.
FAQ
What is batch record review? The documented check, by production and then by the quality unit, that a batch record is complete and shows compliance with approved procedures before release.
Who must review batch records under GMP? In the US, the quality control unit must review and approve them before release (211.192). For APIs, the quality unit under ICH Q7. In the EU, records must be available to the QP, who certifies the batch.
Does batch record review include audit trails? Yes. FDA’s data integrity Q&A treats audit trails as part of the production and control records the quality unit reviews.
What is batch documentation review? The same task, viewed more broadly: reviewing the batch record plus all supporting records such as logbooks, test results and deviations.
What happens if a discrepancy is found after release? Section 211.192 requires a full investigation whether or not the batch has been distributed, including other affected batches.
References
All pages opened and checked by October 14, 2026.
| Source | Type | Used for |
|---|---|---|
| 21 CFR Part 211 Subpart J (eCFR) | US regulation | 211.192 requirements |
| ICH Q7 (FDA) | ICH guideline | Sections 6.70–6.72 |
| EudraLex Volume 4, Chapter 4 (2011) | EU GMP guideline (copy hosted by ECA) | Section 4.20 approval |
| EU GMP Annex 16 | EU GMP guideline (copy hosted by ECA) | Section 1.7.11 |
| ECA, Batch Record: who needs to review? | Industry news | EU and US review roles |
| ECA, Five new Warning Letters – Four Batch Record Review Citations | Industry news (May 2026) | Warning letter examples |
| FDA, Data Integrity and Compliance With Drug CGMP: Q&A | FDA guidance | Audit trails; invalidated data |
| GMP Insiders, FY2025 FDA inspection observations | Industry analysis of FDA data | Citation counts |