A clean AS9100 or ISO 9001 certificate tells you a company has a documented quality system. It does not tell you whether that system reflects how the floor actually operates on a Tuesday afternoon when the schedule is behind and the shift lead is improvising.
That gap — between what's certified and what's actually happening — is one of the more common surprises PE sponsors encounter in the first 100 days post-close. It's rarely fraud. It's more often a documented process that was accurate when it was written and has quietly drifted since, while the certification itself never expires on that basis alone.
Why certifications don't close the gap
Quality certifications audit against a documented standard, on a schedule, using a sample. They're a legitimate signal of process maturity, but they weren't designed to answer the questions that matter most in the first 100 days of ownership:
- Is the documented operating cadence actually followed, or is it a formality maintained for audit season?
- Where is the real constraint in the plant right now, and does leadership actually know it — or are they managing to a metric that looks fine while a different bottleneck quietly caps throughput?
- How much of "on-time delivery" is structural capability versus expediting, overtime, and heroics that won't scale post-acquisition?
None of these show up in a certificate. They show up in a walk-through, a review of actual schedule adherence data against the documented process, and direct conversations with supervisors who weren't in the room for the diligence presentation.
What a post-close operational review should actually check
A useful 100-day diligence pass, beyond the paper trail, typically covers:
- Schedule reality versus schedule fiction. Compare what the ERP says should happen against what actually happened on the floor for the last several completed jobs — not the best-case examples used in the deal deck.
- Where the true constraint sits today. Capacity claims in diligence materials are often based on a snapshot. Confirm the current binding constraint directly, rather than trusting a number that may already be stale.
- Supervisor-level operating cadence. Ask what actually happens when a job falls behind. A documented escalation process that nobody follows is a bigger risk than an undocumented one people genuinely use.
- Working capital tied up in the gap between certified process and actual process. Inventory buffers, expediting costs, and rework often exist specifically to compensate for a process that isn't running the way the certification implies it runs.
The payoff for doing this early
Sponsors who run this kind of review in the first weeks — rather than discovering the gap when the first quarter's numbers come in soft — get to make deliberate decisions about where to invest stabilization effort, instead of reacting to a surprise six months in. The certification isn't the problem. Treating it as a substitute for direct operational verification is.