What documentation is required for MRB approval?

MRB approval usually requires enough documented evidence for authorized quality, engineering, and program stakeholders to justify and approve a disposition for a nonconforming item. At minimum, this normally includes the nonconformance record, objective inspection evidence, applicable drawing or specification requirements, affected part or lot traceability, proposed disposition, required technical evaluation, and approval signatures. The exact package depends on the product, contract, customer flowdowns, internal procedures, and regulatory context.

MRB approval is not simply a formality and should not be treated as proof that the part is conforming. It is approval of a controlled disposition for a specific nonconformance under defined authority. In regulated manufacturing, the documentation has to support traceability, accountability, and later review by customers, auditors, or internal quality teams.

Typical documentation in an MRB package

A complete MRB package commonly includes:

• Nonconformance report or NCR: A clear description of the defect, deviation, or process escape, including when and where it was found.
• Part, lot, batch, or serial traceability: Identification of all affected material, assemblies, operations, purchase orders, work orders, and quantities.
• Drawing, specification, and revision references: The exact requirement violated, including drawing zone, characteristic, tolerance, process specification, or customer requirement.
• Inspection and test evidence: Measured results, inspection records, photographs, CMM reports, test data, gage references, sampling details, or other objective evidence.
• Containment record: Evidence that affected material was identified, segregated, and prevented from unintended use while the MRB decision was pending.
• Technical evaluation: Engineering or quality analysis showing the impact on fit, form, function, safety, interchangeability, reliability, downstream processing, and configuration.
• Disposition: The approved decision, such as rework, repair, use-as-is, scrap, return to supplier, or continue processing under defined controls.
• Instructions for execution: Rework or repair instructions, inspection requirements, special handling steps, or limits on future use if applicable.
• Approval records: Signatures, electronic approvals, dates, roles, and delegated authority for quality, engineering, manufacturing, customer, or design authority approval as required.
• Verification of completion: Evidence that the approved disposition was carried out and accepted before release, shipment, or return to service.

When customer or design authority approval is required

Some MRB dispositions require customer, prime contractor, regulatory, or design authority approval before the product can move forward. This is especially common for use-as-is and repair dispositions where the product does not fully meet the original requirement but may still be acceptable under a controlled concession or deviation.

Whether outside approval is required is not universal. It depends on contract language, purchase order flowdowns, delegated MRB authority, product criticality, airworthiness or safety classification, and internal quality procedures. A plant should not assume it has authority to accept a deviation unless that authority is explicitly defined and current.

System records matter, but they rarely live in one place

In brownfield environments, MRB evidence is often spread across QMS, MES, ERP, PLM, inspection software, supplier portals, document control systems, and sometimes controlled spreadsheets. That is common, but it creates risk if links, revisions, and approvals are not controlled.

For example, the NCR may be in the QMS, the work order in the MES or ERP, the released drawing in PLM, inspection data in a metrology system, and supplier communication in a portal or email archive. The MRB package should make those references explicit enough that someone can reconstruct the decision later without relying on tribal knowledge.

Replacing all of those systems just to improve MRB documentation is usually unrealistic in regulated manufacturing. The qualification burden, validation cost, downtime risk, integration complexity, and long equipment lifecycles often make full replacement a poor first move. More practical controls usually involve clear ownership, controlled links, audit trails, integration where justified, and disciplined change control.

Common failure modes

MRB documentation often fails when the record explains the defect but not the decision. A measurement alone is not enough if the approved disposition depends on engineering judgment, customer concession, or risk acceptance.

Other common problems include missing revision references, unclear affected quantity, incomplete containment, undocumented rework instructions, approvals by people without defined authority, and no evidence that the disposition was actually completed. These gaps may not stop production immediately, but they create audit, customer, warranty, and traceability exposure later.

CAPA is related but not always the same record

MRB approval addresses what to do with the affected product. CAPA or RCCA addresses why the nonconformance occurred and how recurrence will be prevented. Not every isolated nonconformance requires a formal CAPA, but recurring, severe, escaped, or customer-impacting issues often do under internal procedures or customer requirements.

The MRB record should make clear whether additional corrective action is required, already opened, or intentionally not required based on defined criteria. Leaving that decision implicit is a common documentation weakness.