What is MRB responsible for in an NCR workflow?

In an NCR workflow, the MRB is typically responsible for reviewing the documented nonconformance and authorizing a controlled disposition for the affected material or product. That usually means deciding, within its delegated authority, whether the item can be reworked, repaired, used as-is, scrapped, returned to a supplier, or escalated for customer or engineering approval.

MRB usually means Material Review Board in this context. Its role is not to make a defect disappear or bypass normal quality controls. The MRB decision must be traceable, justified, approved by the right functions, and reflected in the systems and records that control production and shipment.

Typical MRB responsibilities

• Review the NCR description, inspection evidence, affected part numbers, serial or lot numbers, quantities, and containment status.
• Confirm whether the nonconformance has been properly segregated or controlled so suspect material is not used unintentionally.
• Assess technical impact with quality, engineering, manufacturing, supplier quality, and sometimes program or customer representatives.
• Select or approve the disposition, such as rework, repair, use-as-is, scrap, return to supplier, or request for concession or deviation.
• Define required actions, instructions, verification steps, and acceptance criteria for the disposition.
• Ensure required approvals are obtained before material is released, especially for use-as-is or repair decisions that may affect design requirements.
• Maintain the decision record, rationale, approvals, and linkage to the affected work order, traveler, inspection record, purchase order, or shipment record.
• Escalate recurring or systemic issues into RCCA, CAPA, supplier corrective action, or process change control when required by the QMS.

What MRB usually does not own

MRB does not normally own the original detection of the nonconformance. That is usually performed by inspection, production, test, receiving, or another process owner. MRB also does not automatically own root cause analysis, although it may trigger or require it.

MRB should not approve dispositions outside its authority. In regulated manufacturing, some decisions require design authority, customer, regulatory, or delegated engineering approval. This is especially important for repair and use-as-is dispositions, where accepting a departure from drawing, specification, or contract requirements may not be within local MRB authority.

Where the responsibility is site-specific

The exact MRB membership and approval rules depend on the company QMS, customer flowdowns, product risk, regulatory context, and contract language. Some organizations have a standing board. Others use an electronic approval workflow with defined roles for quality, manufacturing engineering, design engineering, supplier quality, and program management.

The boundary between MRB, engineering change control, deviation management, and CAPA is often a source of failure. A disposition may solve the immediate material problem but still require a separate corrective action or formal change if the underlying process, tooling, supplier, or design data is wrong.

System and record implications

In brownfield environments, the NCR may live in a QMS while material status is controlled in ERP, production execution is controlled in MES, and product definition is controlled in PLM. MRB responsibility includes making sure the disposition is reflected consistently across those systems or covered by a validated manual control.

Common failure modes include releasing material in ERP before the NCR is closed, rework instructions that are not tied to the traveler, missing engineering approval for repair, poor linkage between serial numbers and NCR records, and CAPA actions that are disconnected from the original nonconformance. Replacing one system rarely fixes these issues by itself; the workflow, authority model, integrations, and data discipline have to be controlled.