material review board (MRB): meaning, evidence and controls

A material review board (MRB) is a company-defined decision forum that evaluates nonconforming material and determines or recommends its disposition within documented authority. In common manufacturing practice, MRB describes an organizational arrangement, not a universal committee mandate.

Its practical question is: what should happen to this identified material, on what evidence, and with whose authority? The focus is a bounded material decision—not necessarily the broader cause of the problem or authorization for finished-product release. A company may connect those activities in one workflow while keeping their decisions and approvals distinct.

The following are company-practice distinctions; exact terminology depends on the quality system. The distinction between a nonconformance and a deviation helps identify what needs review before deciding who can resolve it.

Confirming conformity means the evidence demonstrates that the applicable requirement is met. Accepting a known departure means the requirement remains unmet; calling that decision MRB approval does not turn it into conformity. Keep that distinction explicit in the decision rationale. The available disposition routes belong in the disposition assessment; batch release remains a separate decision boundary.

An MRB is commonly a company review arrangement, not the source of disposition authority. A practical authority map separates who evaluates the evidence, who recommends an action and who is authorized to approve it. Define those roles by product and market before assigning them to a committee or workflow.

For US drugs under 21 CFR 211, 21 CFR 211.22(a) assigns the quality control unit responsibility and authority to approve or reject components, drug product containers, closures, in-process materials, packaging material, labeling, and drug products.

For US drugs under 21 CFR 211, 21 CFR 211.22(c) assigns the quality control unit responsibility for approving or rejecting procedures or specifications affecting drug identity, strength, quality, and purity. For the same US drug scope, 21 CFR 211.22(d) requires the quality control unit’s responsibilities and procedures to be written and followed.

For US medical-device manufacturers subject to Part 820, the current Quality Management System Regulation (effective 2 February 2026) is built on ISO 13485 by reference: 21 CFR 820.10(a) requires the manufacturer to "Document a quality management system that complies with the applicable requirements of ISO 13485 (incorporated by reference, see § 820.7 ) and other applicable requirements of this part". Map device disposition authority to that documented system and its applicable ISO 13485 nonconforming-product clause, rather than treating the former 820.90 text as the current foundation. Neither framework names a committee called an MRB; the review body is a company design choice.

For food, supplements, chemicals and non-US operations, assess disposition authority separately by product and jurisdiction; do not extend the US drug provisions to those operations. A supplement assessment, for example, can begin with the relevant 21 CFR 111 context, rather than borrowing a drug-site authority matrix.

The operational methods below are company practice, not official guidance. As a practical control, distinguish binding legal authority from guidance recommendations and internal decision procedures in the authority map. Document whether an MRB decision is a recommendation awaiting approval or the recorded action of an authorized approver. Treat any software workflow as an administrative mechanism, not as an independent grant of disposition authority. Committee membership and access permissions should reflect that distinction.

MRB participation commonly draws on quality, manufacturing, engineering, laboratory staff, warehousing and supplier quality, selected for the case rather than attendance alone. Separate technical contributors who assess evidence, decision owners who authorize disposition, execution owners who carry it out, and escalation contacts who resolve authority gaps or unresolved risks. One person may fill several roles, but record each responsibility separately.

Use a proposed authority matrix within the quality assurance process. For US drugs, refer to the quality-unit authority mapped above.

Define quorum by necessary expertise and decision authority, not headcount or majority vote. If a reviewer is unavailable, use documented delegation within its limits or defer the decision. Record conflicts of interest and arrange independent review where impartiality is compromised. Preserve dissent, its technical basis and the approver’s response; escalate unresolved safety or suitability concerns. Commercial urgency may inform scheduling, but should not replace technical evidence or authorization. Label a technical recommendation separately from the authorized decision.

MRB disposition routes are a practical taxonomy, not a fixed legally prescribed menu. Availability depends on the product, jurisdiction and decision authority. In the proposed company workflow, make the technical basis, applicable authority and unresolved departure explicit before deciding. A concession or use-as-is label is a proposal for evaluation, not permission to bypass acceptance criteria.

Keep rework and reprocessing separate in the procedure. Define the actual operations, intended result and verification for each rather than treating local names as interchangeable. Where a test result triggered the hold, connect the decision to out-of-specification handling; a disposition label does not explain why the original concern is resolved.

For US drugs under 21 CFR 211, 21 CFR 211.115(a) requires written procedures to be established and followed for reprocessing batches that do not conform to standards or specifications, including steps to ensure that reprocessed batches conform with all established standards, specifications, and characteristics. For US drugs under 21 CFR 211, 21 CFR 211.115(b) prohibits reprocessing without quality control unit review and approval.

In the company workflow, distinguish authorization to perform work from acceptance of its result. Record the post-operation evidence needed before clearing the disposition; keep any separate batch release decision visible.

A practical MRB evidence package starts with the decision requested, not an attachment index. Organize it around the unmet requirement, observed condition, affected population, containment boundary, proposed disposition route and remaining uncertainty. Use requirements traceability to connect the discrepancy to the applicable acceptance criterion rather than a general concern about quality.

Identify source records and applicable revisions, then explain what each contributes:

Keep observed facts, technical interpretation, assumptions and unresolved questions separate. A recorded temperature is a fact; its likely effect is an interpretation; unrecorded exposure duration remains uncertain. Where equipment accuracy is questioned, as-found and as-left calibration can help distinguish the condition discovered from the condition after adjustment.

Test validity and material acceptability are different questions. A favorable result from a valid method supports only the attributes and population addressed by that method and sampling rationale; it does not resolve unrelated defects or establish the condition of unrepresented material.

Use a practical decision-readiness gate: sufficient evidence for the requested route, bounded material scope, identified decision authority and explicit conditions. If a consequential uncertainty remains, defer for investigation, naming the question, owner and evidence needed. Deferral is a legitimate workflow outcome, not an obligation to select a disposition prematurely.

Treat MRB authorization and completed disposition as separate milestones. The following proposed workflow separates decision-making from physical and electronic execution; it is a practice model, not a universal regulatory sequence.

Keep deferred or incomplete cases visibly open, with an owner, outstanding action and next review trigger. An authorization timestamp alone should not advance a case to closure.

Define an integration contract across quality, enterprise resource planning, warehouse and laboratory records. Include shared case and lot identifiers, units of measure, location, hold status, decision version, transaction reference and execution acknowledgement. Specify which record owns each field and how receiving systems acknowledge acceptance or rejection. For warehouse integration, distinguish a requested movement from a confirmed movement; for laboratory integration, associate results with the affected material and review context rather than treating result arrival as disposition authorization.

Route missing acknowledgements, duplicate transactions, stale hold statuses and partial execution to a reconciliation queue. Keep affected inventory blocked while its authorized state is uncertain. Assign the warehouse lead physical reconciliation, the inventory systems owner electronic reconciliation, and the quality case owner review of the resolved state. Before retrying, establish whether the original action occurred; avoid posting an already completed movement again.

For controlled manual recovery, record the action and reason, preserve the original transaction reference, reconcile quantities, verify the resulting status and obtain the appropriate review before clearing the exception. Retain the failed transaction and corrective action as linked records, not an overwritten history.

These hypothetical cases illustrate company practice, not actual outcomes or universally permitted dispositions. Each separates evidence for taking an action from evidence that the action succeeded.

US drug batch: proposed reprocessing after a specification failure

Assume a batch fails an established process-related residual-solvent specification. Material quantities are recorded in kg; the established test reports residual solvent in mg/kg. A relevant written reprocessing procedure exists, and the proposal remains subject to the quality-unit authority described above. The evidence conflict is a failing laboratory result despite production records showing the intended process settings.

Keep the batch on hold while reviewing sample identity, analytical validity, actual process conditions and the procedure’s applicability. For US drugs under 21 CFR 211, 21 CFR 211.115(b) requires quality control unit review and approval before reprocessing. The proposed route therefore stops at that authorization gate; an MRB recommendation alone does not authorize execution.

If authorized, record execution conditions, deviations, material movements and reassessment results. Reconcile input mass against retained material, samples, waste and documented losses on a consistent basis; net-versus-gross reconciliation helps avoid counting container mass. Applicable procedure, resolved evidence conflicts and quality-unit approval support starting reprocessing. Complete execution records and conclusive reassessment support the next disposition review; they do not release the material by themselves; see the batch release checklist. Missing mass explanations or inconclusive reassessment leave disposition unresolved. Approval of the action does not establish its successful outcome.

Device components: sorting incoming housings

Assume individual housings belong to an identifiable supplier lot, the applicable drawing revision is established, and a specified measurement method expresses the disputed dimension in mm. Incoming measurements show a mismatch, while the supplier’s report states conformity. Hold the receipt while checking drawing references, instrument suitability, measurement setup and unit identification.

Assess whether the mismatch could affect other containers or receipts from that lot. A proposed sorting plan identifies the characteristic, method, acceptance criteria already established by the drawing, and means of separating results. The decision gate is approval of a technically justified plan—not acceptance of the supplier’s report over conflicting measurements.

Reconcile receipt quantity as conforming housings plus nonconforming housings plus unresolved housings, counting each housing once. Valid measurements linked to identified units support their next disposition review; they do not establish conformity of unmeasured units or other characteristics. Unresolved method disagreement or lost unit identity prevents accepting the affected population.

Packaged food: evaluating a relabeling proposal

Assume product identity is traceable, affected packs are physically segregated, and package condition can be assessed. The observed label differs from the approved master, although the packaging record names that master. Count material in packs. Investigate actual label issuance and affected production boundaries rather than treating the record entry as proof of correct labeling.

Evaluate relabeling only if product-specific review supports that route for this defect. The authorization gate considers identity, affected scope, package integrity and whether the proposed operation can produce the correct presentation. Reconcile replacement labels issued against applied, returned and destroyed labels; separately reconcile affected packs across mutually exclusive statuses. Correct-master verification, label accounting and package checks support the next disposition review. Uncertain identity or scope prevents that step and leads to continued hold or a rejection decision.

These practical safeguards test the integrity of an MRB decision; they are not a universal regulatory checklist.

A shipping deadline explains urgency, not technical acceptability. Challenge unsupported risk statements by identifying the failure mechanism, relevant evidence, uncertainty and consequences. Repeated concessions are not precedent that makes another exception defensible; assess the present case on its own evidence.

A technical rationale can record conflicting interpretations, dissenting reviewers, unresolved questions and why the decision owner considers the evidence sufficient—or insufficient. Link open uncertainties to the quality risk register where useful, without substituting a risk label for analysis.

• Weak record: a generic acceptability conclusion based on satisfactory testing.
• Improved record: identifies the requirement, assesses the complete evidence, bounds the affected material, names the authorized decision owner and specifies the verification condition before disposition execution.

As the opening comparison explains, MRB disposition and CAPA serve different purposes. A practical escalation screen considers recurrence across lots, widening affected scope, an ineffective previous action, uncertain containment or evidence of a common process weakness. Select criteria appropriate to the product and process risk rather than a universal numerical trigger. Use backward genealogy tracing where shared inputs may connect otherwise separate cases.

In the proposed workflow, link the MRB case to the investigation or CAPA record, but retain separate owners, decisions and closure criteria. Identify who controls the affected material and who leads the causal investigation; neither role substitutes for the other.

The material decision and systemic investigation can progress on different timelines. Record unresolved dependencies explicitly: what remains unknown, which decision it blocks, who owns the next action and what evidence resolves it. Closing a disposition does not demonstrate corrective-action effectiveness; closing CAPA does not confirm that the material disposition was executed.

Treat the MRB record as a decision history, not merely meeting minutes. Use the data-model figure as the field-level reference rather than duplicating its entity list. A suggested record structure connects case identity, affected material and scope, the requirement reference and evidence links to the decision rationale and alternatives considered. Capture the disposition, approving role, conditions, execution references and verification outcome so another reviewer can reconstruct why the action was authorized and what actually happened.

Keep the reviewer’s recommendation, authorized decision and executed action in separate fields, each with its own event time and responsible person. A recommendation to return material is not evidence that return was approved or completed. Link execution to the relevant transaction or work record; record verification against the decision’s conditions rather than using an unexplained closed status.

Preserve prior decision versions, changed scope and reasons for amendment. Maintain parent–child material links through splits or transformations using the lot pedigree. Mark superseded instructions explicitly and identify the currently authorized version at the point of execution. Retain references showing which version governed earlier actions; a later amendment should not silently rewrite their history.

As covered in the authority boundary above, keep disposition evidence distinct from any separate release record, even when both link to the same batch record.

Use locally defined operational measures, not universal performance targets. Anchor timestamps to a consistent process event log.

Before comparing periods, fix reopening and partial-execution rules. A practical convention retains the original hold timestamp, reports reopened cases separately, and uses the latest authorization for their lead time and execution lag. Partial execution leaves the execution clock running.

Track recurrence by a stated defect classification within a defined material population, such as affected lots divided by reviewed lots in the same material family. Report unresolved quantity in a consistent unit; do not total unlike products or units. Pair speed with unresolved evidence, repeat defects and decision amendments: rapid closure alone is not a quality outcome.

Use this suggested internal review to test whether written MRB controls match actual records and material status.

• Establish the authority matrix, including delegated authority and unavailable approvers.
• Define case-entry and evidence-readiness gates.
• Map status transitions against physical segregation and the electronic hold tag.
• Assign exception owners for stalled or conflicting actions.
• Define record relationships between the observation, affected material, decision and transactions.
• Test execution reconciliation across quantities, locations and statuses.
• Assign periodic review ownership and a route into management review.

Walk a representative case from the original observation to current material location, authorized decision, executed transaction and verification evidence. Include a deferred decision and a partially executed disposition in process testing; check that neither appears complete while actions remain outstanding.

Ask whether an independent reviewer can reconstruct why the action was selected, which material it covered, who authorized it and whether it happened as intended. Assign each discovered weakness to a named action owner.

Review prompt: decision, material, authority, execution—do they agree?