The regulators caught up. Your audit didn't.

TeamLease RegTech published findings this week framing compliance as a test of operational readiness rather than paperwork. I read it and thought: finally. Anyone who has run a proper VDA 6.3 process audit has known this since the standard was first drafted. The regulatory world is arriving where quality practitioners have lived for two decades. A binder full of evidence proves you own a printer. It says nothing about whether your process works.

Why the binder audit survives

The documentation audit persists because it is comfortable. Cheap to prepare. It creates a satisfying sense of order—tabs, indices, colour-coded sections, every clause mapped to a procedure somebody wrote once and nobody has read since. I have walked into audit openings where the quality manager presented a six-inch binder with visible pride. I have watched auditors nod approvingly. The binder is a shared fiction. Both parties understand the document is a negotiation, not a mirror.

The binder defends itself in meetings. When a customer escalation lands, the first instinct is to produce the control plan and point to the clause where the controls are described. The floor was doing something else. The operator followed a work instruction that contradicted the control plan. The gauge was calibrated on schedule but used outside its effective range. The PFMEA listed a severity rating of 8 for a failure mode the team had never actually seen—and the one that escaped was nowhere in the document.

Paperwork audits survive because they create accountability without responsibility. You can pass one without your process being capable. You can pass one while your customer is quietly building a containment team.

What readiness verification looks like on the floor

When I built the greenfield QA/QC department at SNOP for over 900 employees, I inherited nothing. No procedures, no legacy systems, no cultural muscle memory. A greenfield site is a rare gift—no inherited habits to unlearn. We achieved a 70% defect-cost reduction and zero critical customer escalations within the first quarter. We did it by refusing to treat audit readiness as binder assembly.

VDA 6.3 and IATF 16949 lived on the shop floor. QRQC was triggered by capability data, not by a customer phone call. When drift was detected, the reaction was immediate, structured, documented in real time at the line—not retroactively in a conference room three days later. PFMEA was a living instrument that predicted escapes before they happened, because the cross-functional team had walked the process, observed the failure modes, and rated them with the operator standing there. Risk priority numbers were debated, not copied from a template. Control plans were checked against actual process behaviour weekly. If the control plan said the operator inspects every 50th part but the cycle time made that physically impossible, the control plan was wrong—not the operator.

A process that can only pass an audit is a process that cannot survive a customer.

This is the operational readiness the TeamLease report describes. It is what the standards intended. The gap was never in the requirements—it was in how comfortably organisations misread them as a filing exercise.

The audit that tests capability, not paper

The audit that matters starts at the line, not the desk. Pick a part at random and trace the deviation chain backward: where it was stamped, who signed off, what gauge was used. Check whether that gauge is in calibration and within its effective range for this specific measurement. Look at the last capability study on that station—what did Cpk actually show? Then ask the harder question: when a deviation was detected, did the system respond before the customer found it or after?

I have run audits where the documentation was immaculate and the floor was a catastrophe waiting for a date. I have also run audits where the documentation was rough—handwritten logs, a PFMEA overdue for review, a work instruction corrected in pen—and the floor was disciplined, responsive, capable. The gap between paper and practice was narrow and actively closing. The second plant will survive. The first is one escalation away from a crisis it does not see coming.

The regulatory environment is now asking the question customers have been asking for years. Bangladesh garment exporters feel it in labour compliance. Chinese firms feel it in data processing rules. The bar is moving from can you show evidence to can you demonstrate capability under real conditions. TeamLease's headline landed in the Indian MSME context. The observation underneath is universal.

The regulators are coming around. Your next customer escalation will not wait for them.