I have watched plants where the audit calendar consumed more engineering hours than the improvement plan. Weeks booked solid with customer audits, second-party assessments, certification bodies, layered process audits and internal surveillance — all overlapping, all requesting the same evidence, all pulling the same people off the same production lines. When quality engineers spend their days preparing conference rooms and retrieving documents rather than solving field failures, the audit system has inverted its purpose.
This is not a complaint about auditors. Most do careful, honest work within their brief. The problem is structural: no single customer sees the total audit load, so each adds theirs in good faith. A supplier with thirty major customers might face a dozen full process audits a year, each two to four days, each demanding sample retrievals, line walk-throughs and management interviews. Multiply by preparation time — typically two to three times the audit duration — and you have consumed a full quality department's capacity without producing a single corrective action.
The question I ask plant managers is blunt: what did last year's audits change? If the honest answer is 'we passed them', the organisation has paid a substantial hidden cost for certificates of conformity it already possessed. Measuring that cost is the first step towards consolidating the load and pushing back on duplication.
Counting the True Cost of Being Audited
Most companies track audit findings and closure rates. Almost none track what the audit itself cost them. Start with direct labour: auditor escort time, preparation hours logged by each function, document retrieval, translation, sample pulls, and re-audit preparation when findings appear. Run a time-tracking exercise for three months across every contributing function — production, quality, engineering, HR for training records, purchasing for supplier files. The number that emerges usually shocks management, because nobody had ever assembled it in one place.
Then add the indirect costs, which are larger and harder to see. Line stoppages when supervisors are pulled into interviews. Deferred engineering work — the process change that slipped a quarter because the process engineer was assembling evidence for three customers asking three slightly different questions. Overtime to backfill production roles. Quarantined material pulled as audit samples. Travel and support when audits cascade down to tier-two suppliers facing their first customer assessment.
Finally, count opportunity cost. Every hour a quality engineer spends reconciling two customers' conflicting documentation formats is an hour not spent on a recurring warranty claim. Put a column in the audit log for 'engineering hours diverted' and review it quarterly alongside the findings log. Once that figure is visible, the conversation with customers becomes factual rather than emotional.
Customer Duplication: The Same Questions, Different Forms
Here is what duplication looks like on the ground. Customer A audits your welding process against their proprietary supplier manual. Customer B audits the same welds against a sector process standard. Customer C sends a corporate sustainability team that also walks the weld line and asks about operator qualification records. Each produces findings, and some contradict each other: one wants wet ink signatures on training matrices, another accepts electronic records; one demands annual welder requalification, another accepts biennial. You now maintain two parallel training systems to satisfy both, and neither improves the weld.

The deep failure mode is audit-scope drift. Customer audit programmes expand because each new quality manager at the customer adds a clause to their checklist, and nobody ever removes a question. Checklists grow monotonically, like sediment. I have seen supplier questionnaires running to hundreds of line items, of which perhaps a third genuinely drive the customer's decision to buy from you. The rest is inherited bureaucracy, copied forward year after year.
Value assessment means going clause by clause through each customer's audit requirements and asking one question: does this relate to a failure mode that has actually occurred in this product family? If a customer audits your calibration system for a process that uses no measuring equipment on their part, that is a finding with no value stream behind it. Build a simple matrix — customer requirements on one axis, your actual processes on the other — and mark where they intersect. The empty rows are your negotiation targets.
Practical Consolidation Tactics
Consolidation starts internally. Map every audit hitting your site over a rolling twelve months — certification, customer, regulatory, internal, layered process, financial — onto one calendar with owner, duration, scope and preparation effort. Assign someone senior to manage that calendar as a portfolio, with authority to negotiate timing. Clustering audits into defined windows protects the rest of the year; scattering them across fifty weeks guarantees permanent disruption. Where two customers want to visit within a month of each other, propose a joint visit or a mutual recognition arrangement.
Audit consolidation sequence
- 01Map the loadTwelve-month calendar of all audits with owner, scope and preparation effort.
- 02Cost itTrack direct, indirect and diverted engineering hours for one quarter.
- 03Standardise evidenceOne master file organised by process, not by customer.
- 04Build the duplication matrixCustomer requirements against actual processes; empty rows are negotiation targets.
- 05NegotiatePresent third-party results and cost data to the supplier quality engineer.
Second, standardise your evidence once and serve everyone from it. Build a master evidence file organised by process — not by customer — so that when three auditors ask about supplier approval, you retrieve one controlled document set rather than three bespoke packs. This cuts preparation labour dramatically and prevents the credibility damage that comes when auditors notice your story differs slightly between packs. One version of the truth, indexed by process element, updated on a fixed cycle.
Third, use existing audit results as currency. When a new customer proposes a full process audit, present your most recent third-party assessment report and the closure evidence for its findings. Many will accept it, particularly if you offer a shortened confirmation visit instead. Some will refuse, and you accept that for strategic accounts. But you would be surprised how many audit programmes persist simply because nobody ever offered an alternative.
What to Measure: An Audit Load Dashboard
I recommend a small set of metrics, reviewed monthly. Audit days per site per quarter, broken down by type. Total preparation hours per audit day — a ratio that reveals whether your evidence organisation is improving. Duplicated scope coverage: how many separate audits this quarter covered the same process element. Diverted engineering hours. And findings per audit day, which tells you whether the audits are finding anything worth the disruption. A pattern of near-zero findings across high-effort audits is not success; it is waste wearing a badge of honour.
Track repeat findings across customers. When three different customers flag the same weakness — say, incomplete retention of deviation approvals — that is a genuine signal worth fixing at the root. When each customer finds something different and trivial, the audits are sampling noise. The ratio of value-carrying findings to administrative findings is the single best indicator of whether an audit programme deserves its cost. I have closed audits where every finding was about a form field, and others where one observation prevented a serious escape. Only the second type earns its keep.
Finally, measure closure durability. If a customer finding recurs eighteen months later, the audit consumed resources twice for the same defect. Root-cause discipline on findings — real corrective action rather than evidence supplementation — separates organisations that improve through auditing from organisations that merely survive it. Watch for the tell-tale sign of fatigue: findings closed by creating new documents rather than changing the process. That compounds, because every new document becomes evidence to prepare next time.
Audit load ratios worth tracking
Pushing Back Without Losing the Business
Negotiating audit load with customers requires evidence and tact in equal measure. Arm yourself with the duplication matrix and the cost data. Then approach the supplier quality engineer, not their manager, and frame it commercially: 'You audit our injection moulding annually; so do two other customers using an equivalent scope. We propose you accept the shared third-party assessment plus a half-day focused review of the items specific to your programme.' Most SQA engineers, themselves drowning in audit schedules, will engage with that framing. Some have targets to reduce their own audit days and will welcome a supplier who makes it easy.
The distinction between 'we will show you everything' and 'we question whether you need to see it four separate times' is the whole game.
Escalate carefully. For strategic accounts with contractual audit rights you will not eliminate the audit, but you can often shape it: narrower scope, shorter duration, off-cycle scheduling, remote evidence review for documentation elements with on-site time reserved for the process walk. Reserve executive escalation for genuine absurdity — the fourth full audit of the same process in one year, the questionnaire demanding data your customer already receives in monthly quality reports. Make the business case to your commercial counterpart, who shares your interest in a profitable account.
One caution from experience: never let pushback read as evasion. The moment a customer suspects you are hiding something, every audit becomes longer and more forensic. Offer transparency relentlessly while questioning duplication specifically. Transparency about content and firmness about repetition are not in tension; conflating them is how suppliers lose both the argument and the goodwill.
Designing the Audit Programme You Want to Live Under
Long term, the answer is to engineer your audit exposure the way you engineer a process. Tier your customers by risk and revenue: accept full audits for the top tier, deploy mutual recognition and third-party reliance for the rest. Negotiate audit clauses at contract stage — frequency, scope, notice period, acceptance of existing certifications — because once the contract is signed, the customer's standard terms apply and renegotiation is ten times harder. Suppliers who treat audit clauses as seriously as payment terms are right to do so.
Internally, audit yourself hard enough that external audits become confirmations rather than excavations. A rigorous internal process review cycle, run by people trained to find real failure modes rather than paperwork gaps, reduces both preparation effort and findings. Paradoxically, the plants most comfortable under audit are the ones that audit themselves most severely — they have nothing to assemble in a panic, because the evidence lives in the process, not in a binder prepared the week before.
The goal is not fewer audits for their own sake. It is audits that pay their way: each one either verifies a risk that matters to a real customer, or finds something that makes the product better. Everything else — the ritual visits, the inherited checklists, the fourth identical walk-through of the same line — is a tax paid in engineering hours. Measure that tax, publish it internally, and use it to drive consolidation. Being audited should be an occasional verification that you are doing the work, not the work itself.
