In aerospace manufacturing, MRB usually stands for Material Review Board. It refers to the controlled process, and often the cross-functional group, used to review nonconforming material and determine an allowed disposition. An MRB does not simply “approve defects.” Its authority is limited by engineering requirements, customer contracts, quality procedures, regulatory obligations, and any delegated approval rules that apply to the program.
Some organizations say “Materials Review Board,” but Material Review Board is the more common usage. In practice, MRB may mean the board, the formal review meeting, the workflow in the QMS or MES, or the disposition authority. The exact meaning should be confirmed in the site’s quality procedures and customer flow-down requirements.
What an MRB typically does
An MRB is normally involved after a nonconformance has been identified, documented, and contained. The board or authorized reviewers evaluate whether the material can be used, repaired, reworked, scrapped, returned to a supplier, or submitted for customer approval.
Common MRB dispositions include:
- Use as is: Accepting the item without physical correction, when allowed by approved authority and requirements.
- Rework: Bringing the item back into full conformance with existing approved requirements.
- Repair: Restoring acceptable function or fit by a method that may not fully match the original design definition and may require additional approval.
- Scrap: Removing the item from production or service use.
- Return to supplier: Sending the nonconforming item back under supplier quality controls.
- Customer concession or deviation request: Seeking customer approval when internal authority is not sufficient.
Why MRB authority is tightly bounded
In aerospace, MRB decisions are constrained because product configuration, airworthiness, traceability, and contractual requirements matter. A supplier or plant may not have authority to accept every nonconformance, even if the part appears usable. Some dispositions require design engineering approval, customer approval, delegated MRB authority, or use of approved repair data.
A common failure mode is treating MRB as a production recovery mechanism rather than a controlled quality process. That creates risk when records do not show who approved the disposition, what requirement was affected, what engineering basis was used, whether customer approval was required, or how the part’s configuration history was maintained.
How MRB connects to shop-floor systems
In a brownfield aerospace environment, MRB rarely lives in one clean system. The nonconformance may originate in an MES, inspection system, supplier portal, paper traveler, or QMS. Inventory status may need to be controlled in ERP. Design definition and effectivity may sit in PLM. Corrective action may be managed in a CAPA system. Maintenance or MRO work may add another layer of recordkeeping.
For MRB to work reliably, the system landscape must support holds, traceability, disposition approval, revision control, attachment control, electronic signatures where required, and audit trails. If integrations are weak, plants often rely on manual controls, duplicate entry, or reconciliation. Those controls may be necessary, but they must be defined and monitored because they are common sources of escaped defects, inventory errors, and incomplete records.
MRB is not the same as RCCA or CAPA
MRB addresses the disposition of a specific nonconforming item, lot, assembly, or condition. Root cause and corrective action processes, such as RCCA or CAPA, address why the nonconformance occurred and how recurrence will be prevented. The two processes are related, but they are not interchangeable.
A mature program will link MRB records to nonconformance reports, inspection evidence, engineering analysis, supplier records, and corrective actions where appropriate. That linkage depends on process discipline, data quality, and system integration. It should not be assumed just because an organization has an MES, ERP, or QMS in place.