Use-as-is in an MRB disposition means a specific nonconforming part, assembly, material lot, or record condition is accepted without physical rework or repair. The decision must be documented and justified by authorized functions, usually quality and engineering, and sometimes the customer. It does not mean the nonconformance was irrelevant, permanently acceptable, or approved for future production.
In practical terms, the MRB is saying that the item can proceed in its current condition because the evaluated nonconformance is judged not to prevent its intended use under the applicable requirements. That judgment is site-specific and contract-specific. It depends on the characteristic involved, product criticality, design authority rules, customer flowdowns, regulatory obligations, and the approval authority defined in the quality system.
What use-as-is does and does not mean
A use-as-is disposition applies to a defined nonconformance and a defined population, such as a serial number, lot, work order, or quantity. It should be traceable to the nonconformance record and to the evidence used to support the decision.
It does not revise the engineering definition. If the drawing, specification, bill of material, work instruction, or inspection plan remains unchanged, future parts are still expected to meet the original requirement. Repeated use-as-is dispositions for the same condition are often a signal that the process, requirement, supplier performance, or design documentation needs review through formal change control or corrective action.
It also does not automatically avoid customer involvement. In aerospace, defense, medical device, pharmaceutical, and other regulated or customer-controlled environments, some use-as-is decisions require customer concession, design authority approval, source inspection acceptance, or other contract-defined authorization. Plants should not assume internal MRB authority is sufficient unless that authority is clearly established.
Typical basis for the decision
A credible use-as-is decision normally considers whether the nonconformance affects form, fit, function, interchangeability, performance, durability, safety-related requirements, regulatory commitments, or customer acceptance criteria. The analysis may involve engineering review, quality history, inspection data, test results, stress or tolerance assessment, supplier documentation, or prior approved dispositions.
The level of analysis should match the risk. A minor cosmetic condition on a non-critical surface is not the same as a dimensional miss on a key characteristic, a material certification gap, a process parameter excursion, or a condition affecting an interface controlled by the customer or design authority.
Controls that matter
Use-as-is should be controlled through the nonconformance and MRB process, not handled informally on the shop floor. Common controls include:
- clear identification of the affected item, quantity, serial number, lot, or work order;
- documented description of the nonconformance and the requirement not met;
- technical rationale for accepting the condition as found;
- approval by the required quality, engineering, MRB, customer, or design authority roles;
- updates to inspection status, inventory status, traveler records, and as-built records where applicable;
- retention of evidence and approvals under the site’s recordkeeping rules;
- review for recurrence, supplier action, CAPA, or process change when patterns appear.
Where brownfield systems create risk
In many plants, MRB activity spans QMS, MES, ERP, PLM, inspection systems, supplier portals, and sometimes paper travelers. That creates real failure modes. A part may be accepted in the QMS but still blocked in ERP inventory. A traveler may show the disposition, while the inspection plan does not. A customer concession may exist in a document repository but not be linked to the serial number or shipment record.
These gaps matter because use-as-is depends on traceability. The decision has to remain visible to production, quality, shipping, receiving, and downstream users. Full system replacement is usually unrealistic in regulated brownfield environments because of validation cost, qualification burden, downtime risk, integration complexity, and long equipment lifecycles. More commonly, companies improve interfaces, status controls, document links, and approval workflows around the existing stack.
Main failure modes
The most common failure is treating use-as-is as a convenience disposition rather than a controlled technical decision. Other failures include weak engineering rationale, unclear approval authority, missing customer notification, poor linkage to serial or lot records, and repeated acceptance of the same defect without corrective action.
Another common problem is confusing use-as-is with rework or repair. Rework brings the item back into full conformance with the original requirement. Repair makes the item usable through an approved method but may not restore original conformance. Use-as-is accepts the item in its nonconforming condition. Those distinctions affect records, approvals, cost accounting, customer communication, and future quality analysis.
The safest interpretation is narrow: use-as-is is a documented, bounded acceptance of a specific nonconforming condition by authorized parties. It is not a shortcut around specifications, customer requirements, validation, or change control.