Supplier verification through production capacity audit: scope and limits: part 2
A production capacity audit tells you what a factory could produce under the conditions observed on the audit day, not what it will deliver six months later under peak-season pressure. That distinction is the whole subject of this second installment: mapping where the scope ends so buyers stop treating the report as a promise. Standard coverage includes lines, equipment, staffing, and planning records, while subcontracting chains, seasonal labor swings, and shared-line contention sit at or beyond the boundary unless explicitly added. Define those edges in writing before the visit, and the report becomes a decision tool instead of a misunderstanding.
Key takeawaysTreat the audit as a dated snapshot of observable capacity, not a forecast of future output or delivery reliability. · Quality management practice treats workshops, equipment, and working conditions as controlled inputs, which is why auditors examine maintenance and calibration records rather than taking machinery at face value. [2] · Read sample-based checks on headcount or output with sampling logic in mind: a small observed sample bounds the risk but never eliminates it. [1] · Put subcontracting, second sites, and seasonal labor inside the written scope when they matter to your order, because default visits focus on the main site. · Use the findings to set order caps and follow-up monitoring instead of treating the report as approval for unlimited future volumes.
The first installment in this series covered the basic purpose of a production capacity audit: verifying that a supplier genuinely has the lines, people, and organization to make your order. This second part deals with the harder half of the topic, which is understanding where that verification stops. Every audit has edges, and buyers who cannot see them tend to read more into reports than the evidence supports.
The most expensive misunderstandings in supplier verification rarely come from dishonest auditors. They come from scope gaps that nobody discussed in advance. The buyer assumed subcontractors were checked, the auditor never visited them, and the resulting shortage surprised everyone except the factory. Each of these failures was preventable with a written scope statement agreed before the visit.
This article maps the standard coverage of a capacity audit, the boundary zones around subcontracting and seasonal labor, and the practical steps for pinning the scope down in writing. It continues the series without repeating the introductory material, so readers new to the topic benefit from reading part one first.
What a scope statement should contain
A scope statement is the short written agreement that says what the auditor will and will not examine. At minimum it names the site address, the product categories concerned, the lines and workshops to be observed, the shift pattern in operation, and the records to be reviewed. It should also state the audit date explicitly, because capacity findings expire as staffing and order books change.
The statement earns its keep in the boundary clauses. Good ones name subcontracted processes, second sites, warehouses outside the main gate, and any lines shared with other customers. Each named item gets a verification method: visited in person, checked through records, or excluded by agreement. Items nobody names tend to receive no attention, and that silence later gets misread as approval.
Buyers sometimes worry that a detailed scope looks distrustful. In practice factories prefer it, because it tells them which documents to prepare and which managers should be present. A supplier that resists putting the scope in writing is itself informative, and that reluctance belongs in your supplier evaluation alongside the audit findings.
Standard coverage against its boundaries
| Area | What auditors usually observe | Typical evidence | Where the boundary lies |
|---|---|---|---|
| Production lines | Line layout, workstations, and bottlenecks for your product type | Photos, line counts, cycle-time observation | Shared lines and night shifts need explicit inclusion |
| Workforce | Headcount present, skill mix, and supervision ratios | Attendance records, payroll cross-checks | Seasonal and agency workers fluctuate across months |
| Equipment and upkeep | Machine condition, calibration stickers, and maintenance logs | Maintenance records, calibration certificates | Idle or broken machines may be excluded from capacity math |
| Planning and records | Order books, production plans, and material stock | Planning sheets, warehouse observation | Forward plans show intent, not guaranteed execution |
| Subcontracting | Usually the main site only unless agreed otherwise | Subcontractor lists where provided | Off-site processes stay unverified by default |
Why subcontracting sits at the edge
Most capacity disputes trace back to work the auditor never saw. A factory with tidy in-house lines may send dyeing, electroplating, embroidery, or final packing to workshops across town, and those workshops hold the real bottleneck. When the scope statement is silent on subcontracting, the report describes only the presentable half of the operation.
See the inspection scope before you confirm the audit date, and verify that subcontracted processes, second sites, and shared lines are named in it with a verification method for each. This single check prevents the most common form of scope failure, because it forces an explicit conversation about the parts of production the supplier would rather keep offstage.
Where a subcontractor cannot be visited, ask for the next best evidence: incoming inspection records for subcontracted parts, delivery notes showing volumes, and the criteria the factory uses to qualify those workshops. Partial evidence honestly labeled as partial beats a confident-sounding report built on half the process.
Set the boundaries before the visit
- Map your product flowList the processes your product actually passes through, from raw material to packed carton, and mark which ones might sit off-site.
- Write the scope explicitlyName each site, shift, and shared line in the scope statement with the verification method for every entry.
- Probe seasonal staffingAsk which months run at full staffing and how the factory copes when orders exceed in-house capacity.
- Demand upkeep evidenceRequest maintenance logs and calibration evidence for the machines your product depends on, not just a machine count.
- Fix the reporting formatAgree how findings will be expressed, such as demonstrated daily output under observed conditions with stated assumptions.
A capacity report is a photograph, not a weather forecast. It shows staffing, lines, and organization on one specific day, and every conclusion beyond that day is inference. Keep the photograph labeled with its date and its frame, and it will serve you well. Mistake it for a prediction, and peak season will correct the error at your expense.
Sources
- Wikipedia: Acceptance sampling —— Overview of acceptance sampling including AQL concepts used in product inspection.
- Wikipedia: ISO 9000 —— Overview of the ISO 9000 family of quality management standards.
Frequently asked questions
What should I check first when I receive the audit report?
Ask whether the visit covered subcontractors, second sites, night shifts, and shared lines, and what records supported each headcount and output figure. A scope that names these items explicitly is far more useful than a general statement that the factory looked capable. If an item you care about is missing, treat it as unverified rather than assuming it was fine.
Can the audit confirm the factory will meet my peak-season volumes?
It can, but only within the conditions observed on the day. Auditors measure demonstrated output under current staffing and line configuration, sometimes supplemented by planning records. They cannot verify how the factory behaves when half the workforce leaves after a holiday or when your order shares lines with three larger customers. Use the figure as a baseline for order caps, not as a promise.
Should subcontracting be inside the audit scope?
Yes, and for many product categories it is the most important boundary to set. Default visits concentrate on the main site that the supplier presents, while plating, printing, stitching, or final assembly may happen elsewhere. Name each subcontracted process in the scope statement and ask how the auditor will verify it, whether by visit, records, or incoming inspection evidence.
How do I handle seasonal swings the audit day might miss?
Seasonality affects both headcount and output, so a single visit can mislead in either direction. Ask the auditor to record how current staffing compares with peak staffing, which months run at full shifts, and what the factory does when orders exceed in-house capacity. Pair the snapshot with personnel records across several months to see whether the observed day was typical, strong, or weak.
Reserve Your Numbered Edition.
Each Gremir release is capped at 500 units. 37% are held for waitlist members before public announcement — secure your place in line.