batch record

Core meaning

A **batch record** is the complete, traceable set of documentation and data that describes how a specific batch or lot of product was produced, tested, and released. It typically includes:

– The defined manufacturing instructions for that batch
– Evidence of how each instruction was executed (who, what, when, where)
– Material and component traceability (lot numbers, quantities, sources)
– Equipment and line use, including key settings and status
– In‑process and final quality control results
– Deviations, nonconformances, and approved changes impacting the batch
– Approvals and sign‑offs by authorized personnel

Batch records exist in both paper and electronic forms and are central to traceability and accountability in regulated manufacturing environments.

Use in industrial and regulated environments

In regulated industries (such as pharmaceuticals, medical devices, food and beverage, and specialty chemicals), batch records commonly refer to:

– **Master batch record (MBR):** The approved, standard template that defines how a batch *should* be made (recipes, steps, parameters, sampling, tests).
– **Executed batch record (EBR) or batch production record (BPR):** The completed record that shows how a specific batch *was actually* made, including real data, timestamps, and any deviations.

Manufacturing execution systems (MES), LIMS, and ERP systems frequently store or contribute data to batch records. In many plants, batch records are a mix of:

– Automatically captured data (e.g., from MES, SCADA, historians)
– Manually entered data (e.g., operator checks, visual inspections)
– Attached documents (e.g., certificates of analysis, calibration confirmations)

Boundaries and what it is not

– A batch record is **not** just a recipe or work instruction; it is the *combination* of instructions and the associated execution evidence.
– It is **not** the same as general equipment logbooks, training records, or maintenance histories, although those may be referenced.
– It should be distinguished from **production reports** or **dashboards**, which summarize performance but typically do not provide full, batch‑level traceability suitable for regulated review.

Role in operations and quality workflows

In day‑to‑day manufacturing and quality workflows, batch records are used to:

– Document that each required manufacturing and testing step was performed as intended
– Support lot genealogy and traceability, especially for recalls or investigations
– Enable quality review and disposition decisions (e.g., release, reject, rework)
– Provide structured data for deviation investigations, CAPA work, and process improvement

Electronic batch records (eBR/EBR) often enforce in‑process checks, conditional logic, and automated data capture to reduce transcription errors and missing entries, while still fulfilling the same fundamental purpose as paper batch records.

Common confusion and related terms

– **Batch record vs. master batch record (MBR):** The MBR is a standard, pre‑approved template. The batch record (often called BPR or EBR) is the instance for one specific batch, populated with actual data.
– **Batch record vs. device or lot history record:** In some industries (e.g., medical devices), similar concepts exist under different names (e.g., Device History Record). The structure and regulatory basis differ, but they serve a comparable traceability function.
– **Batch record vs. real‑time visibility:** Batch records are usually the authoritative, reviewable history; real‑time visibility views show in‑flight data that will later be consolidated into records.

Connection to real-time production visibility (site context)

In environments that seek real‑time production visibility, many of the data points shown on live dashboards (e.g., machine states, parameter values, operator actions, test results) ultimately become part of, or are reconciled with, the batch record.

Where systems are fragmented (legacy MES, ERP, SCADA, paper forms), batch records may be assembled from multiple sources. Real‑time visibility tools in such environments often focus on exposing or aligning the same information that will later be required for the complete, compliant batch record.