Master vs Executed Batch Records

Batch records are central to GMP manufacturing control. They document how a product is made and provide traceable evidence that each batch was produced in accordance with approved procedures. The documentation and execution discipline is described in Pharmaceutical GMP Compliance.

However, there is a critical distinction between:

  • The Master Batch Record (MBR)

  • The Executed Batch Record (EBR)

Confusing the two - or managing them poorly - is a frequent source of inspection observations.

This article explains their differences, roles, and regulatory expectations.

What Is a Master Batch Record (MBR)?

The Master Batch Record is the controlled template that defines how a product must be manufactured.

It includes:

  • Product name and code

  • List of raw materials and quantities

  • Equipment to be used

  • Step-by-step manufacturing instructions

  • In-process control requirements

  • Sampling instructions

  • Acceptance criteria

  • Labeling instructions

  • Required documentation entries

The MBR is approved before use and maintained under document control.

It defines intent.

What Is an Executed Batch Record (EBR)?

The Executive Batch Record documents how a specific batch was actually produced.

It includes:

  • Completed entries for each manufacturing step

  • Operator signatures or electronic approvals

  • Recorded in-process control results

  • Deviations or comments

  • Corrections and annotations

  • QA review and release decisions

The EBR provides objective evidence of execution.

It reflects reality.

The Relationship Between MBR and EBR

The MBR establishes the approved process.

The EBR documents adherence to that process.

The EBR should:

  • Follow the MBR structure

  • Capture required data points

  • Demonstrate that all steps were performed

  • Highlight any deviations from the master

If the MBR is poorly designed, the EBR will be difficult to execute properly.

Weak batch record design often leads to recurring documentation errors.

Control and Version Management of MBRs

Master Batch Records must be:

  • Formally approved

  • Version controlled

  • Protected from unauthorized modification

  • Periodically reviewed

Changes to the MBR must follow structured change control procedures, including risk-based impact evaluation as outlined in Risk-Based Change Control Assessment.

Impact evaluation should consider:

  • Process validation status

  • Training updates

  • Labeling implications

  • In-process control modifications

Poor version control of MBRs is a frequent regulatory finding.

Accuracy and Completeness of EBRs

Executed Batch Records must be:

  • Completed contemporaneously

  • Legible and traceable

  • Accurate and complete

  • Reviewed prior to batch release

Common EBR issues include:

  • Missing entries

  • Incomplete calculations

  • Unjustified corrections

  • Backdated signatures

  • Inconsistent sampling documentation

Batch record review is a key component of quality oversight.

Batch release decisions rely heavily on EBR integrity. These records also provide primary evidence that validated process parameters were followed during routine production.

In-Process Controls Within Batch Records

In-process control requirements defined in the MBR must be clearly reflected in the EBR.

This includes:

  • Defined sampling frequency

  • Acceptance criteria

  • Escalation procedures

Inadequate alignment between defined IPC requirements and executed documentation may indicate weaknesses in process control.

For IPC fundamentals, see In-Process Controls Explained.

Electronic vs Paper Batch Records

Organizations may use:

  • Paper-based batch records

  • Hybrid systems

  • Fully electronic batch record system

Regardless of format, regulators expect:

  • Controlled access

  • Audit trail integrity

  • Clear traceability

  • Data integrity safeguards

Electronic systems must ensure that approved master instructions are used during execution.

Poor configuration of electronic systems can result in version mismatch between master and executed records.

Deviation Handling Within Batch Records

If deviations occur during production:

  • They must be documented in the EBR

  • Appropriate investigation must be initiated

  • Impact on product quality must be assessed

Executed batch records must accurately reflect all manufacturing activities, including unplanned events or deviations.

Inspection Perspective

During inspection, regulators often:

  • Review selected executed batch records

  • Compare execution against master instructions

  • Evaluate completeness and clarity

  • Examine correction practices

  • Assess review and approval controls

Inspectors frequently identify:

  • Unclear instructions in the MBR

  • Repeated documentation errors

  • Failure to update master records following process changes

  • Insufficient review depth

Batch records often serve as the primary evidence of process control.

Weaknesses here may trigger deeper system review.

Practical Perspective

The Master Batch Record defines how a product should be manufactured.
The Executed Batch Record proves how it was manufactured.

A strong GMP system ensures that:

  • Masters are clear and controlled

  • Execution is accurate and contemporaneous

  • Deviations are documented transparently

  • Version control is maintained

  • Review processes are robust

When MBR design is disciplined and EBR execution is accurate, batch records become a powerful demonstration of manufacturing control rather than an inspection vulnerability.


Previous
Previous

Control of Non-Conforming Product

Next
Next

Process Validation: Stage 1-3 Explained