You renewed the certificate. The system expired years ago.

Five recertification announcements landed in seven days. Sequenex renewed its medical-device quality management system, Korea United Pharmaceutical re-certified for the Ukrainian market, FOMAS Group extended nuclear-grade scope to its MIMETE metal powders. Every release read like a victory lap. Here is an uncomfortable observation: no shop floor is cleaner than the Monday an auditor arrives. Gauges freshly calibrated. Tier boards current. 5S corners you could eat off. The certificate measures that Monday. It says almost nothing about the other 999 days of the cycle.

I learned the difference early. At SNOP I built a QA/QC department from the ground up for a greenfield plant of 900-plus people, and we designed the system to run daily – QRQC at the line, A3 on the wall, escalation that fired within the hour. The certificate became a by-product of that. Leading quality initiatives across a 2,000-plus workforce spread over multiple sites, under IATF 16949 and AS9100/EN 9100, I watched the same three-year cycle from the other side: plants magnificent in audit week, middling in March. Same lesson from both chairs. A certificate samples auditability. A customer samples everything.

What a recertification actually samples

Do the arithmetic. A three-year certificate covers roughly a thousand production days. The recertification audit observes three of them; surveillance visits observe fewer. Within those hours the auditor verifies what records can show: documents current, calibrations closed out, management reviews minuted, CAPAs dated and dispositioned. Records are readable. Habit is not. No auditor can establish whether the night-shift leader stops the line over a burr, whether reaction plans live in muscle memory or in a drawer, whether February's deviation rate bore any resemblance to audit week's. What gets certified is the plant's ability to present itself.

This is also where system certificates stop and process audits start. ISO 9001, IATF 16949, AS9100/EN 9100 certify the management system – the architecture of documents, responsibilities and reviews. VDA 6.3 goes further. It stands at the station, watches the operator, follows one part end to end. That is why I rate a hard-nosed VDA 6.3 report above any wall plaque, and why supplier after supplier fails a process audit while holding an immaculate system certificate. The certificate proves you can document a system. The process audit tests whether the system still runs.

The registrar certifies you can prove it. The customer finds out whether you can do it.

The decay curve between audits

The pattern repeats wherever the three-year cycle governs. Year one, vigilance: findings are fresh and people still fear the registrar. Year two, drift. Calibrations run late, layered checks get backfilled on Friday afternoons, deviations quietly reclassify themselves as known conditions. By year three the plant runs a parallel quality calendar – housekeeping spike before the surveillance visit, trough after it. I saw the numbers at multi-site level: calibration completion and CAPA closure climbed in the fortnight before each visit and sagged within a month of the auditor leaving. Call it the audit-spike. Not dishonesty. A rational plant optimising to the sample it is graded on.

Surveillance visits make it worse, because the sample shrinks. Years two and three narrow to the clauses that produced findings last time, so the plant optimises to the checklist and everything unlisted atrophies. What gets audited gets performed; the rest rots. The money side: a full cycle with surveillance easily runs €25,000 in registrar fees, and it buys three days of observation. The plant spends the other thousand unsupervised. Drift fills the vacuum.

At FOREAST, consulting for clients including ArcelorMittal and AVX Kyocera, I kept meeting the same specimen. Valid certificate in the lobby. Control plan last touched at the previous audit. Reaction plans nobody on the floor recognised. The paperwork described a plant that had stopped existing years earlier; the certificate described the paperwork.

Audit yourself as if the registrar had left

Certification is the entry ticket to automotive and aerospace supply chains, so walking away is not the remedy. The remedy is making the registrar irrelevant to daily behaviour. Layered process audits every shift, findings closed in days rather than quarters. QRQC cadence: containment within the hour, root cause inside 24 hours, countermeasure verified within the week. Once a month, somebody senior walks the control plan against the real station and asks why the two differ. An escalation route that works without an external audience.

At SNOP the department kept one scoreboard that mattered, and it was not the audit result. QRQC and A3 cadence cut defect costs by 70% while customer satisfaction held at 98%, and we ran a full quarter with zero critical customer escalations. No registrar issued that outcome. Customers did – by receiving conforming shipments month after month, on days nobody was auditing. Warranty data and escalation counts are the only recertification body that never leaves.

The honest test of a system is whether it could pass an unannounced audit on a random Tuesday. If the answer depends on which Tuesday you pick, you do not have a quality system. You have a performance timed to the surveillance calendar.

Keep the certificate. It opens markets – the Ukrainian channel for Korea United, nuclear scope for FOMAS, medical for Sequenex – and no contrarian essay rewrites procurement rules. But be honest about the arithmetic. The registrar audits you three days a decade; the customer audits every shipment, every drawing, every warranty claim. Build for the days nobody is watching. The customer never receives the plant the auditor got.