Batch Records and Validation Documentation: GMP Explained
The two documentation pillars that prove a pharmaceutical batch was made right, every time, and that the equipment and process making it can be trusted.
GMP manufacturing rests on two documentation pillars: the batch record, which is the contemporaneous, product-specific account of how one batch was actually made, and validation documentation, which proves in advance that the equipment and process are capable of making it correctly. Both are legally binding quality records, and both are only as trustworthy as the data integrity behind them — commonly summarized by the ALCOA+ principles.
What a Batch Manufacturing Record Actually Is
A Batch Manufacturing Record (BMR), sometimes called a Batch Production Record (BPR), is the working document that travels with a specific batch of product from the first weighing to final release. It is not a summary written after the fact. It is filled in step by step, in real time, by the operators actually performing the work — which is why regulators describe it as a contemporaneous record rather than a report.
A properly designed BMR is built from a master batch record template that has already been reviewed and approved by quality. For each production run, that template is issued, filled, and becomes the batch-specific record. It typically captures:
Core Elements of a Batch Record
- Identity, quantity, and lot number of every raw material and component used, cross-checked against approved specifications.
- Equipment used at each step, including line clearance and cleaning status before the run started.
- Process parameters actually achieved — temperature, mixing time, pressure, fill weight — not just the target range.
- In-process checks and their results, recorded at the point they were performed.
- Any deviation from the approved procedure, however minor, with an explanation and the corrective action taken.
- Signatures and dates of the operator who performed each step and the second person who verified it.
- Final yield reconciliation and the quality release decision.
The underlying principle is simple to state and hard to execute consistently: if it was not written down when it happened, it did not happen — at least not in a way a regulator, an auditor, or a customer's quality team can verify. A batch record with gaps, corrections without initials, or entries added after the shift ended is a red flag long before anyone checks whether the product itself was good.
Validation Documentation: Proving the Process Before It Runs
Where the batch record proves what happened during one specific run, validation documentation proves that the equipment and the process are capable of producing consistent, quality output in the first place. It is forward-looking evidence, generated once (and re-verified periodically) rather than for every batch.
Equipment qualification is usually broken into three sequential stages, each with its own protocol and report:
| Stage | What It Confirms | Typical Evidence |
|---|---|---|
| Installation Qualification (IQ) | The equipment was installed correctly, matches specifications, and utilities are connected as designed. | Drawings, component checklists, calibration certificates, installation sign-off. |
| Operational Qualification (OQ) | The equipment operates as intended across its full operating range, including alarms and safety functions. | Test scripts run at operating extremes, alarm-trigger evidence, software function tests. |
| Performance Qualification (PQ) | The equipment, running the actual process, consistently produces product meeting quality attributes. | Multiple production-representative runs with full test results against acceptance criteria. |
Two further categories sit alongside IQ/OQ/PQ. Process validation confirms that the manufacturing process itself — not just the individual machine — reliably delivers a product that meets its specifications across the normal range of inputs and conditions, typically demonstrated through a defined number of production-scale runs plus ongoing verification. Cleaning validation confirms that the cleaning procedure between products or batches removes residues, cleaning agents, and microbial contamination to an acceptable, documented level, which matters enormously in shared equipment and multi-product facilities.
Every one of these activities produces a protocol (what will be tested and the acceptance criteria, approved before testing starts) and a report (what was actually observed, with a pass/fail conclusion). Both documents are retained and are frequently the first thing an auditor asks to see.