V5 runs the MRB: nonconforming material tagged and segregated at the moment of detection, quorum board convened with role gating, disposition (use-as-is, rework, regrade, RTV, scrap) e-signed and traceable back to the affected lots — with cost of poor quality auto-calculated.
Waiting for the next MRB meeting — which is Thursday, and it's Monday, and the customer is waiting.
No linkage to the deviation, the CAPA or the customer notification obligation — auditor pulls the string and it comes out short.
Scrap value, rework hours, expedited freight — never rolled up per supplier, per product family, per root cause.
Receiving or in-process nonconformity tags the specific lot/serial, freezes it in the warehouse system, and opens the MRB record — no paper travellers.
QA, engineering, operations and (where required) regulatory sign the disposition; missing roles block closure. Async or scheduled sessions, both e-signed.
Use-as-is (with deviation and customer-notification link), rework (with revised routing and re-inspection), regrade (with new spec), return-to-vendor (with SCAR), scrap (with write-off).
Recurring nonconformity auto-links to the parent CAPA and updates the supplier scorecard — the MRB record isn't a dead end.
Scrap value + rework labour + expedited freight aggregated per supplier, product family and root cause — reported to management review without a spreadsheet.
MRB fails when nonconforming material sits in a queue and CoPQ isn't measured. Criteria below expose it.
What it tests: Are quarantine locations tied to record status?
Why it matters: Nonconforming material moving unnoticed is the incident.
V5: Material status and warehouse location interlocked.
What it tests: Are Use-As-Is / Rework / Return / Scrap / UAI-with-concession dispositions distinct with evidence?
Why it matters: Undifferentiated disposition is auditor bait.
V5: Each disposition a distinct workflow with required evidence.
What it tests: Is Cost of Poor Quality captured per event?
Why it matters: Otherwise the business doesn't see the loss.
V5: CoPQ captured with financial linkage; trended per supplier / product / process.
What it tests: Do supplier NCs flow to supplier scorecards?
Why it matters: Otherwise supplier performance decays silently.
V5: Supplier NC hits scorecard automatically.
What it tests: Are concessions time-limited, quantity-limited and re-evaluated?
Why it matters: Concession creep is a documented failure mode.
V5: Concessions bounded and re-evaluated on expiry.
MRB approaches.
| Capability | Spreadsheet | Legacy QMS | V5 Ultimate |
|---|---|---|---|
| Physical link | None | Cross-system | Interlocked |
| Disposition distinct | One field | Sometimes | Distinct workflows |
| CoPQ | Not captured | Optional | Native |
| Supplier scorecard | None | Cross-tool | Live |
MRB clauses.
Each manufacturer shall establish and maintain procedures to control product that does not conform to specified requirements...
V5: Distinct procedures per disposition with evidence.
The organization shall document procedures... for control of nonconforming product.
V5: Same platform serves 13485 §8.3.
The organization shall ensure that outputs that do not conform to their requirements are identified and controlled...
V5: Identification and control interlocked with warehouse.
MRB in V5.
Receiving, in-process or supplier NC opens record.
Status change moves material to quarantine location.
Named disposition with required evidence.
Rework/return/scrap executed with evidence.
Scorecard, CAPA linkage and CoPQ recorded.
MRB ROI is measured in CoPQ reduction.
Distinct workflows and inventory link.
Native capture.
Scorecard-driven supplier development.
CoPQ visibility usually generates the improvement — you fix what you can see.
Setting
A contract manufacturer with 40 suppliers.
Before
Disposition sat 12 days average; CoPQ not measured.
After
Disposition under 3 days; CoPQ trended per supplier; top-quartile supplier NC rate halved.
Both. Routine dispositions run async with role-gated e-signature; complex or safety-relevant cases can require a scheduled session with attendee capture.
Electronically at the warehouse system level — pick lists, shipments and next-operation moves refuse the lot until the MRB closes. Physical yellow-tag is still a good practice, V5 just doesn't rely on it.
Repeat use-as-is on the same failure mode auto-escalates to CAPA and blocks further use-as-is until a corrective action is open — the pattern surfaces, it doesn't hide.
Free trial, no card. Live in 7 days with guided onboarding.