MRB needs engineering approval when the disposition of a nonconformance could affect design intent, product definition, fit, form, function, performance, interchangeability, safety, reliability, qualification status, or customer and regulatory requirements. It is not normally required for every MRB record. Routine scrap decisions, segregation, or rework back to an already-approved drawing, specification, or work instruction may be handled by quality or production authority if the site’s quality system allows it.
Common cases where engineering approval is required
Engineering approval is commonly required when MRB proposes a disposition such as:
- Use-as-is where the part does not fully meet drawing, specification, or process requirements.
- Repair that is not already defined in approved technical data, a standard repair, or an approved work instruction.
- Rework that changes the method, sequence, material condition, or inspection basis beyond approved planning.
- Deviation or waiver from product requirements, process requirements, or customer flow-downs.
- Substitution of material, hardware, tooling, process parameters, inspection method, or acceptance criteria.
- Impact to special processes, critical characteristics, key characteristics, serialized parts, life-limited parts, or configuration-controlled items.
- Potential effect on qualification, certification basis, first article status, or previously accepted configuration.
Cases where engineering may not be needed
Engineering approval may not be needed when the disposition is limited to actions already authorized by controlled documentation. Examples include scrapping a part, returning material to supplier under an approved process, or reworking a feature exactly to drawing using an approved operation and inspection plan.
That boundary depends on the organization’s QMS, customer contracts, delegated MRB authority, part criticality, and applicable regulatory obligations. Some programs require engineering or customer approval for dispositions that another program would allow internally.
MRB authority is not the same everywhere
In regulated manufacturing, MRB authority should be defined in procedures, approval matrices, customer agreements, and role qualifications. Engineering may be a standing member of MRB, an approver for specific disposition types, or the owner of technical evaluation only. Customer or design authority approval may also be required, especially where the manufacturer does not own the design authority.
A common failure mode is treating MRB as a generic quality workflow. That creates risk when a quality user approves a disposition that actually changes technical acceptability. The opposite failure mode is routing every minor issue to engineering, which slows production and hides which decisions genuinely need technical judgment.
System workflow matters
In brownfield environments, the MRB trigger may live across MES, QMS, ERP, PLM, inspection systems, and supplier portals. The system can help route records based on part number, defect code, characteristic criticality, program, contract, and disposition type, but only if master data and approval rules are maintained.
Poor integration can create weak points: an NCR may be opened in MES, dispositioned in QMS, updated in ERP inventory, and linked to drawing authority in PLM. If those links are incomplete, engineering approval can be missed or recorded outside the traceable quality record. Replacing all systems to fix this is usually unrealistic in aerospace-grade and similarly regulated environments because of validation cost, qualification burden, downtime risk, integration complexity, and long equipment lifecycles. Most sites need controlled workflow integration and clear approval rules, not a blanket system replacement.
Practical rule
If the disposition changes or accepts a departure from the approved technical requirement, involve engineering or the appropriate design authority. If the action simply restores the item to approved requirements using approved instructions, engineering may not be required unless the procedure, customer, or program says otherwise.