The use-as-is decision that cost $12 million.
Raw material arrived with endotoxin at 0.35 EU/mL. Spec said NMT 0.25 EU/mL. Friday afternoon, upstream campaign scheduled Monday. Engineering said the downstream purification step would clear it. Decision: use as is. Three months later, a clinical hold after an unexpected immune response. Root cause traced back to residual endotoxin. Eighteen months of clinical material destroyed.
This was the sixth endotoxin exceedance from that supplier in eighteen months. Nobody had connected the dots.
Every organization has a nonconformance culture. Most can't see theirs.
Clear failures are easy. Media arrives contaminated. Reject it. A bioreactor crashes mid-run. Scrap the batch. Nobody argues. The hard decisions are the marginal ones. Endotoxin at 0.35 EU/mL when the spec says 0.25. Titer at 1.8 g/L when acceptance is 2.0. Aggregation at the edge of the distribution.
These decisions reveal who you actually are. One use-as-is is reasonable. Twenty for the same specification is normalizing deviation. But most quality systems can't show you which one you're doing, because each NCMR lives in its own record. The pattern is invisible. Not because the data doesn't exist, but because nothing connects it.
The FDA sees it differently. They don't audit individual NCMRs. They audit the aggregate. They ask for your concession rates by supplier, by material, over time. They want to see whether you're improving or drifting. If you can't produce that picture in minutes, you've already given them the answer.
Seal treats every disposition decision. Use as is, rework, scrap, return. As a data point in a trajectory. When the MRB convenes for the sixth endotoxin exceedance, they see it's the sixth. Not because someone remembered, but because the system connects every decision about the same failure mode, the same supplier, the same specification. The question changes from "is this batch acceptable?" to "what is the pattern of our decisions telling us?"
Your MRB makes good individual decisions. That's not the problem.
Your cross-functional review process works. Engineers assess technical risk. QA checks compliance. Manufacturing flags handling concerns. Each decision is defensible in isolation.
The problem is that each MRB sees one event. The board that reviewed the sixth endotoxin exceedance didn't know it was the sixth. Because their QMS showed them a single NCMR, not a trajectory. They made a reasonable decision with incomplete information.
Seal puts the pattern in front of the MRB before they deliberate. When reviewers open NCMR-2024-047, they see every prior NCMR for that supplier, that material, that specification. The trend line is right there. The concession rate over the last twelve months is right there. The discussion changes. Not because the people are different, but because the information is.
This is what a connected platform makes possible. Your current QMS captures MRB decisions. Seal connects them to supplier history from incoming inspection, to batch outcomes from MES, to stability data from LIMS. The MRB doesn't just know about this event. They know what happened last time they accepted the same deviation.
The trace that takes your team days takes Seal seconds
The $12 million recall didn't happen because someone made a bad decision. It happened because nobody could see that six people had made the same decision, independently, over eighteen months. And when stability data finally revealed the problem, it took weeks to determine which batches were affected.
That's because in a standalone QMS, the NCMR is a document. It references lot numbers, but those lot numbers don't link to batch records in your MES, which don't link to distribution records in your ERP. The forward trace is a manual investigation across disconnected systems.
In Seal, the NCMR, the batch record, and the distribution record are on the same platform. The moment an NCMR is opened, automatic inventory holds block the material from being issued to any batch. Not a tag that can fall off, but a system-level lock that a barcode scan can't override. When the NCMR is dispositioned, the links are already there. The trace from "NCMR-2024-001, raw material lot RM-2024-0847" to "all affected drug substance batches and clinical shipments" is a single query.
When the FDA asks "which products were affected?"—you show them in minutes, not days. That speed isn't a feature of the QMS module. It's a consequence of the QMS, MES, and inventory living on one platform.
The question you should be asking in management review
Most management reviews look at NCMR counts. Open vs. closed. Aging. Maybe a Pareto chart of root causes. This tells you almost nothing about whether your quality is improving.
The questions that matter: Are concession rates increasing? Which suppliers are generating the most nonconformances, and is it getting better or worse? Are the same specifications failing repeatedly. And if so, is the specification wrong or is the process drifting? When a CAPA closes, do the nonconformance rates for that failure mode actually decrease?
Seal surfaces these patterns in real time. When a supplier's rejection rate crosses a threshold you define, the system flags it before the next MRB. When the same specification fails for the third time in six months, it's visible to everyone reviewing the NCMR. Not buried in a filing cabinet. When a CAPA claims to have fixed a problem, the nonconformance data shows whether it actually did.
The sixth endotoxin exceedance shouldn't have been a surprise. With connected data, it would have been an expected escalation. Flagged after the third, investigated after the fourth, resolved before it became a $12 million recall.