MMRMaster Manufacturing Record

A Master Manufacturing Record (MMR) — sometimes called a Master Batch Record, Master Production Record, or Master Formula — is the approved, controlled, immutable master document that defines exactly how a product is to be made. It contains the formula, the process steps, the equipment list, the in-process specifications, the sampling plan, the yield ranges, the labelling specification, and the approval signatures of the preparer and at least one independent reviewer. Every Batch Manufacturing Record (BMR) for that product must be an accurate reproduction of the MMR — that is the legal hook.

The MMR is required by 21 CFR 211.186 for finished pharmaceuticals, by 21 CFR 111.205 and 111.210 for dietary supplements, and by parallel clauses in EU GMP, PIC/S, ICH Q7 (APIs), 21 CFR 117 (food) and 21 CFR 507 (animal food). The wording differs slightly between regimes, but the concept is consistent: there must be a single, approved, version-controlled master from which all batches descend, and any change to the master must go through formal change control with re-approval.

Section 211.186(a) is the approval clause: 'To assure uniformity from batch to batch, master production and control records for each drug product, including each batch size thereof, shall be prepared, dated, and signed (full signature, handwritten) by one person and independently checked, dated, and signed by a second person.' This is the two-person rule, and it is non-negotiable.

Section 211.186(b) lists what the MMR must contain:

1. Name and strength of the product, dosage form.
2. Components — name, weight or measure of each.
3. Statement of theoretical yield at appropriate phases.
4. Description of drug product containers, closures, packaging materials, specimen or copy of each label.
5. Complete manufacturing and control instructions, sampling and testing procedures, specifications, special notations, precautions.
6. Theoretical weight or measure at appropriate phases of processing, together with a statement of any reasonable variations from theoretical.

Section 211.186(a)'s parenthetical 'full signature, handwritten' is the only place in 21 CFR 211 where a handwritten signature is explicitly named. Under 21 CFR Part 11, an electronic signature that satisfies Subpart C is the legal equivalent of a handwritten one (per 11.2(a) and 11.3(b)(7)), but only if the organisation has filed the 11.100(c) certification letter with the FDA. Without that letter, the parenthetical reverts to its literal meaning and the MMR approval must be on paper.

21 CFR 111.205 and 111.210 mirror this for dietary supplements, with the supplement-specific addition of a written justification for component specifications in 111.205(b)(2).

The most-cited word in 211.186(a) is 'independently'. The reviewer must be a different person from the preparer, must check the document themselves rather than rubber-stamping it, and must have the qualifications and authority to do so. 21 CFR 211.22(a) makes the QA function responsible for approving production records, which in most pharma organisations means the second signature on an MMR is a QA officer.

An eBMR system enforces this in three places: (1) the user interface refuses to display the approval button to the same person who created the document; (2) the database constraint refuses to insert the second approval row if the user_id matches the first; (3) the audit trail records the attempt and the rejection so that any pattern of self-approval attempts becomes visible. Application-tier enforcement alone is insufficient because the application can be bypassed; database-tier enforcement (typically via a security-definer function) is the standard.

Subordinate-reviewer patterns — where a junior reviewer signs and then the senior preparer signs on top — are a common audit finding because the reviewer is not truly independent (the preparer is the reviewer's manager). Most regulated organisations define independence by department rather than by hierarchy: the reviewer must come from QA, not from manufacturing.

An approved MMR is immutable. This is not a regulatory clause in so many words — it is the inevitable consequence of two clauses read together. 211.186(a) requires two-person approval; 211.188(a) requires the BMR to be an accurate reproduction of 'the appropriate master production or control record'. If the MMR can be edited after approval, then 'appropriate' becomes ambiguous and the accurate-reproduction rule loses meaning. Industry practice, codified in PIC/S PI 041 and EMA inspection guidance, is therefore: approved MMRs cannot be edited; changes create a new version which must itself be approved by two persons; the old version remains in the system for as long as any batch made under it is in retention.

Versioning has consequences. Every approved MMR version has a life span — the date range during which it was the active master. Every BMR is born under exactly one version. Inspectors test the version chain by pulling random batches and asking: 'Which version of the MMR was active on the day this batch was started? Show me that version. Show me how it differs from the current version.' A system that cannot answer this in under a minute is going to fail.

The 'snapshot on release' model is the standard solution. At the moment a work order is released against an MMR, the system copies the entire MMR — components, steps, specs, sampling plan, label — into an immutable column on the work order. From that point onward the BMR is generated against the snapshot, not against the live MMR. The live MMR can then be re-approved into a new version without affecting any open batches.

211.186(b) lists the minimum. A modern MMR — and an inspector-pleasing one — typically organises the content into the following structured sections. Each section is signed-off independently in the approval workflow so reviewers can comment at the right level of granularity.

1. Identity and revision header

Product code, name, strength, dosage form, batch size, manufacturing site, the MMR version, the date this version became effective, the supersession reference to the previous version, the change-control number that authorised this revision.

2. Bill of materials and components

Every component with its approved specification, quantity per batch (with tolerance), the approved suppliers, the in-process specification, and the storage and handling instructions.

3. Equipment and facility

Every major equipment item required, with the approved alternates if any. Cleaning verification requirements. Environmental conditions required (Grade C cleanroom, controlled humidity, etc).

4. Manufacturing instructions

Ordered steps with the action, the operator, the equipment, the parameters (with tolerances), the in-process checks and the acceptance criteria. Steps must be granular enough that the BMR can capture per-step evidence — a single 'mix and granulate' step is too coarse.

5. In-process and finished-product specifications

Every test, the method reference, the acceptance criteria, the sampling plan, the responsible function.

6. Labelling and packaging

The complete label specification, the packaging components, the reconciliation rules, the artwork version reference.

7. Theoretical yield and reconciliation

Theoretical yield at each appropriate phase, the expected range, the action limits if outside range.

8. Approvals

Preparer (full name, role, e-signature, date and time, meaning), reviewer (full name, role, e-signature, date and time, meaning, statement of independence), effective date.

Every change to an approved MMR must go through formal change control. The change-control system is itself a controlled record under 21 CFR 211.100. A typical change-control workflow for an MMR revision: (1) change request raised with rationale and impact assessment; (2) cross-functional review (manufacturing, QA, regulatory, sometimes engineering); (3) decision and approval; (4) execution of the change (drafting the new MMR version); (5) preparer and reviewer e-signature on the new version; (6) effective date and supersession of the old version.

Some changes are notifiable to the regulator before they take effect — for finished pharmaceuticals, anything that affects the product's approved registration may require an NDA supplement (21 CFR 314.70), a PAS (Prior Approval Supplement) for major changes or a CBE (Changes Being Effected) for moderate changes. The MMR system does not need to make this decision automatically, but it does need to flag changes that touch registered attributes so the regulatory function can decide.

The audit trail on an MMR is itself a regulated record. Every change to the MMR — including the change from 'draft' to 'pending approval' to 'approved' — must be timestamped, attributed to a logged-in user, and retained for the same period as the MMR itself.

The terminology varies across regimes and across firms. The artefact is the same; the name differs.

Confusion arises when a company uses two terms inconsistently — 'Master Formula' for the R&D-handover document and 'MMR' for the commercial-manufacturing version, for example. The auditor expectation is one term, one artefact, one approval chain. Multiple names for the same thing is itself a finding.

1. Approved MMR can be edited. The two-person approval becomes meaningless if either signatory can edit afterwards. 211.186 finding follows.
2. Same person approved as preparer and reviewer. Independence rule broken — 211.186(a) directly.
3. MMR referenced by link from the BMR rather than snapshotted. A revision approved mid-batch silently changes what the BMR's structure claims to reproduce.
4. Out-of-spec components quietly added without a new MMR version. The component change should have been a change-control event and a new MMR version.
5. Equipment substitution permitted at the kiosk without an MMR alternate entry. Operator picked a different mixer; the MMR did not allow it.
6. No theoretical yield specified, so the BMR cannot reconcile actual yield against an approved expectation. 211.186(b)(3) finding.
7. Label specification points to a separate artwork system that is not under the same change control. The label can drift independently of the MMR.
8. Old MMR versions purged after a new version is approved. Retention rules apply — old versions must be kept for as long as any batch made under them is in retention.

In V5, the MMR is the approved formula version. The model treats approval as a state transition — a draft formula is editable; an approved formula is immutable and any change creates a new version that must be approved again. The constraint is enforced at the database tier with row-level security, not in the application layer.

• Approval requires two distinct e-signatures (preparer + independent reviewer) per 21 CFR 211.186 / 111.205. The constraint that the two users must differ is enforced by a security-definer SQL function and an INSERT trigger on the approval table.
• Once approved, the formula record is immutable — UPDATE and DELETE are denied by RLS. Any change must create a new version, which itself must be approved.
• On work-order release, V5 copies the full approved formula into work_orders.mmr_snapshot (jsonb). The snapshot is the BMR's source of truth for the life of the record.
• Change-control records reference both the source MMR version and the target MMR version, with an impact assessment and a rationale.
• Old MMR versions are retained for the full retention period required by the predicate rule; they remain queryable but locked.