A capacity audit is only as good as the records it verifies, so preparation matters more than presentation: headcount, lines, hours, and output must reconcile before the auditor arrives. This guide explains how buyers read capacity claims, which cross-checks expose exaggeration, and how to scope the audit so the conclusion reflects real output rather than staged readiness. Use it to turn the audit from a formality into a planning input.
Key takeawaysCheck overtime patterns for sustainability rather than celebrating them, because peak output borrowed from rest days is not real capacity, a context shaped by technical barriers to trade rules, which expect technical requirements to stay transparent and non-discriminatory[1]. · Verify the bottleneck operation separately, since overall capacity can never exceed what the slowest necessary step delivers, a caution supported by acceptance sampling theory, which ties conclusions to defined plans rather than single specimens[2]. · Put seasonal workforce swings in writing with the factory, because the crew that exists in peak season may not exist in yours, a context shaped by technical barriers to trade rules, which expect technical requirements to stay transparent and non-discriminatory[1]. · Decompose every capacity claim into headcount, lines, hours, and yield before believing the headline monthly figure, a caution supported by acceptance sampling theory, which ties conclusions to defined plans rather than single specimens[2]. · Reconcile attendance, payroll, and production records against each other, because a single self-reported number proves nothing, a context shaped by technical barriers to trade rules, which expect technical requirements to stay transparent and non-discriminatory[1].
Capacity audits answer a deceptively simple question: can this factory deliver the quantity on time without degrading quality or breaking labor rules. Simple questions need careful methods, because the answer depends on headcount, equipment, working hours, yields, and subcontracting all holding at once. This guide breaks the question into verifiable parts.
The standard failure mode is a headline number that nobody decomposed: a monthly figure quoted from experience, accepted without checking the arithmetic underneath. Auditors who reconcile independent records often find the real sustainable output sitting well below the quoted figure. The gap usually hides in overtime assumptions, uncounted rework, or outsourced steps nobody mentioned.
The sections below follow the order of a well-run audit: scoping the work, verifying the records, walking the floor with specific checks, and closing findings on time. Each section includes the buyer-side actions, since audits go wrong as often from vague buyer instructions as from factory opacity.
What a monthly capacity number really contains
Every monthly capacity claim hides an equation: workstations multiplied by hours multiplied by throughput multiplied by yield, with changeovers and rework subtracted along the way. Technical barriers to trade rules add the market-access angle: technical requirements should remain transparent and non-discriminatory across supplying countries.[1] Asking the factory to show that equation turns a negotiation about trust into a review of arithmetic. The parts that cannot be shown are usually the parts that were guessed.
Nameplate output deserves particular skepticism, since it describes ideal conditions that production weeks rarely reproduce for long. Experienced buyers book production capacity audit once the trigger is confirmed, so the work answers the question the order depends on. Replacing it with demonstrated output from comparable past months grounds the discussion in evidence both sides can accept.
Subcontracted steps need their own lines in the equation rather than a footnote, because outside capacity follows someone else's schedule. Acceptance sampling literature makes the same point from the other side: without a defined sampling plan, one result cannot carry the whole lot.[2] When the factory names each subcontractor and shows their recent delivery performance, the capacity picture becomes plannable. When it cannot, the buyer should treat that step as the schedule risk it is.
Reading capacity claims with healthy skepticism
| Audit area | What auditors review | Common gap | Buyer response |
|---|---|---|---|
| Seasonal staffing | Hiring and attrition across the year | Peak-season crew assumed year-round | Get seasonal staffing in writing |
| Maintenance downtime | Stoppage logs and service records | Zero-downtime planning assumptions | Insert a downtime allowance |
| Headcount reality | Time-clock and payroll across months | Quoted crew larger than attendance shows | Base plans on verified attendance |
| Working hours | Shifts, overtime, and rest-day patterns | Sustainable output assumed from peak weeks | Discount peak-week figures explicitly |
| Bottleneck operation | Throughput of the slowest necessary step | Bottleneck never measured separately | Require a bottleneck-specific assessment |
Use the matrix as a scope checklist: any row without corroborating records becomes explicit audit scope rather than background trust.
From scope letter to verified conclusion
- State the planning questionDefine the quantity, mix, and ship date the capacity must support before scoping any audit work. Audits scoped to abstract capacity produce abstract conclusions; audits scoped to a real order produce usable answers.
- Decompose the headline figureAsk the factory to show the arithmetic behind its monthly claim across stations, hours, throughput, and yield. Parts that cannot be shown were guessed, and guessed parts are where schedules go to fail.
- Triangulate the recordsReconcile attendance, payroll, material intake, production tickets, and shipment logs for the same weeks. Consistent stories across independent sources earn trust; single-source totals earn verification visits.
- Walk the full flowFollow the material path including night shifts, rework rooms, and subcontracted steps that the paperwork minimized. Each discovered step gets its own record requests and observation time.
- Name the bottleneckMeasure the slowest necessary operation separately and cap the plan at what it can deliver. System output obeys the constraint regardless of how impressive the other stations look.
Why delivery plans built on quotes collapse
Audit fatigue is real on both sides of the table, and tired people produce thin evidence and thinner conclusions. Technical barriers to trade rules add the market-access angle: technical requirements should remain transparent and non-discriminatory across supplying countries.[1] Buyers can reduce fatigue by consolidating overlapping audits, sharing recent reports across customers where appropriate, and scoping each visit to genuine open questions. Fewer, better audits beat a calendar crowded with ritual visits.
Corrective closure is where fatigue does its costliest damage, as follow-up visits get postponed and promises age into ambiguity. Acceptance sampling literature makes the same point from the other side: without a defined sampling plan, one result cannot carry the whole lot.[2] Fixed closure dates agreed at the closing meeting, with named owners on both sides, resist the drift that kills improvement. Each overdue week should trigger a written update rather than silent extension.
Verification visits earn their cost by checking that fixes survived contact with peak production rather than with audit-week conditions. Technical barriers to trade rules add the market-access angle: technical requirements should remain transparent and non-discriminatory across supplying countries.[1] Scheduling the verification during a normal busy period, not a staged quiet week, tests the corrective action honestly. Fixes that hold under load are assets; fixes that hold only under observation are liabilities.
A reminder before you commit the order
Before trusting any capacity figure, ask for the equation behind it and one month of corroborating records. Factories with real capacity show their math gladly; factories with aspirational capacity change the subject.
Sources
- WTO: Agreement on Technical Barriers to Trade —— WTO portal for the TBT Agreement covering technical regulations, standards and conformity assessment.
- Wikipedia: Acceptance sampling —— Overview of acceptance sampling including AQL concepts used in product inspection.
Frequently asked questions
When should overtime figures raise concern rather than confidence?
When high overtime is structural rather than seasonal, since it means quoted output already borrows from rest time. Trend the overtime across months instead of admiring a single compliant one. A factory living on overtime has no reserve left for rush orders.
How should audit findings be closed credibly?
With dated commitments, named owners, and evidence of implementation such as logs, photos, and retraining records rather than plans. Schedule verification during normal busy production. Fixes that hold under load count; fixes visible only under observation do not.
How often should capacity be re-verified?
Re-verify when headcount, equipment, product mix, or subcontracting changes materially, and on a lighter periodic cycle otherwise. One audit is a snapshot; capacity is a moving picture. Written triggers keep re-verification consistent across team changes.
What belongs in the audit scope letter?
The planning question with quantities and dates, the full material flow including off-site steps and night shifts, the bottleneck operation for deep review, and the record lists for each area. Specificity in the letter raises the quality of everything that follows.