| Field | Value |
|---|---|
| Document ID | QC-REC-002 |
| Title | Batch Production Record (BPR) Governance Specification |
| Owner | Quality Unit (QU) |
| Approver | Quality Unit (QU) |
| Effective Date | 03/01/2026 |
| Version | v1.1 |
| Change Control | Required |
This specification establishes mandatory governance requirements for creation, completion, correction, review, approval, and control of Batch Production Records (BPRs) used in dietary supplement manufacturing.
This specification mitigates the risk of undocumented processing steps, undocumented deviations, calculation errors, data integrity compromise, material traceability loss, and product release without documented conformance to the approved Master Manufacturing Record (MMR).
Failure to comply with 21 CFR 111.255, 111.260, and 111.123 constitutes failure to prepare and review complete batch production records and may render product adulterated under Section 402(g)(1) of the Federal Food, Drug, and Cosmetic Act. This specification establishes enforceable documentation control to prevent regulatory exposure.
Applies To: All commercial production batches manufactured under 21 CFR Part 111.
Excludes: Research batches not intended for distribution and maintenance documentation governed under separate QC specifications.
Compliant State: BPR contains 100% of required data fields defined in the MMR, all entries are contemporaneously recorded, all corrections meet GDP standards, and QU review is documented prior to release decision.
Nonconforming State: BPR contains documented discrepancies that do not invalidate traceability or processing history but require QMS workflow entry.
Invalid State: BPR is missing required data elements, contains overwritten or obliterated entries, lacks required signatures or dates, references an obsolete MMR, or lacks QU review.
Escalation Trigger: Any objective documentation failure that compromises traceability, data integrity, or release control.
Stop-Execution Condition: Execution is prohibited when a BPR is in an Invalid State.
| Attribute | Compliant State | Nonconforming State | Invalid State | Escalation Trigger | Required QMS Process Entry | QU Authorization Required? |
|---|---|---|---|---|---|---|
| BPR Completeness | All required MMR-defined fields completed; zero blank required fields | Minor calculation error corrected with documented justification | Any required field missing | Missing processing parameter | Deviation | Yes |
| Documentation Timing | Entry timestamp matches date of execution | Late entry documented with reason and date/time of actual entry | Undated entry or backdated entry | Evidence of falsification | Quality Event + CAPA | Yes |
| Correction Control | Single-line strikeout; original legible; correction dated and initialed | Correction present but missing one GDP element | Obliterated or erased data | Data integrity compromise | Deviation + CAPA | Yes |
| MMR Traceability | BPR references current approved MMR revision | Incorrect revision cited but correct processing followed | Obsolete or unapproved MMR used | Use of obsolete MMR | Deviation | Yes |
| Independent Review | QU review documented prior to release authorization | Clarification required prior to approval | No documented QU review | Product disposition without QU review | Quality Event + CAPA | Yes |
| Trigger Condition | Execution May Continue? | Required Action | QMS Process Entry | Workflow (W)? | QU Authorization (A)? | Required Record |
|---|---|---|---|---|---|---|
| Compliant | Yes | QU authorization required prior to release | None | No | Yes | Approved BPR |
| Nonconforming | No | When documentation discrepancy is identified, Deviation entry is mandatory | Deviation | Yes | Yes | Deviation Record |
| Invalid | No | Execution is prohibited when Invalid State exists | Quality Event + CAPA | Yes | Yes | Investigation Record |
| Repeated Documentation Failure (≥2 events in 90 days) | No | When systemic pattern identified, CAPA entry is mandatory | CAPA | Yes | Yes | CAPA Record |
When documentation error impacts product quality, Deviation entry is mandatory.
When documentation failure compromises data integrity, Quality Event entry is mandatory.
When systemic documentation weakness is identified, CAPA entry is mandatory.
When BPR structure or required fields change, Change Control entry is mandatory and QU authorization is required prior to implementation.
Completed and signed Batch Production Record.
Deviation, Quality Event, CAPA, or Change Control records when triggered.
Documented QU approval prior to release decision.
E — Execution: Operations generate and complete BPR entries.
W — Workflow Entry: QA administers QMS workflows.
A — Authorization: QU authorizes release decisions.
Execution does not confer product disposition authority.
Compliant State: All acceptance criteria satisfied.
Nonconforming State: One or more acceptance criteria not satisfied but traceability intact.
Invalid State: Required element missing, authorization missing, or data integrity compromised.
Escalation Trigger: Objective failure condition requiring QMS workflow entry.
Stop-Execution Condition: Execution is prohibited when Invalid State exists.
Change Control entry is required for any modification to BPR format, required fields, review workflow, or approval structure.
Independent QU approval is required prior to implementation.
No implementation is permitted without documented QU authorization.