Verifying overtime records (batch 2 guide 3)

By admin
The short answer

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 takeaways

  1. Verify the bottleneck operation separately, since overall capacity can never exceed what the slowest necessary step delivers, a step that matters because restricted substance rules limit specific materials in electrical and electronic products[1].
  2. Put seasonal workforce swings in writing with the factory, because the crew that exists in peak season may not exist in yours, a logic familiar from acceptance testing practice, where agreed criteria decide pass or fail before shipment[2].
  3. Decompose every capacity claim into headcount, lines, hours, and yield before believing the headline monthly figure, a step that matters because restricted substance rules limit specific materials in electrical and electronic products[1].
  4. Reconcile attendance, payroll, and production records against each other, because a single self-reported number proves nothing, a logic familiar from acceptance testing practice, where agreed criteria decide pass or fail before shipment[2].
  5. Walk the subcontracted processes in person or include them explicitly in scope, since hidden outsourcing is the classic capacity trap, a step that matters because restricted substance rules limit specific materials in electrical and electronic products[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. Restricted substance rules explain why buyers test at all: certain materials are limited in electrical and electronic products, so composition evidence belongs in the file.[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. The engineers at UTS Inspection compare headcount and line records against the declared capacity before confirming the audit agenda. 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 testing practice follows the same logic: agree the criteria first, test against them, and let the result decide whether the goods move forward.[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.

The classic capacity illusions, compared

Audit areaWhat auditors reviewCommon gapBuyer response
Yield and reworkFirst-pass yield and repair loop sizeNameplate output used as net outputApply demonstrated yield to the math
Order mix effectsChangeover burden from product varietySingle-product rates applied to mixed ordersAsk for mix-adjusted estimates
Seasonal staffingHiring and attrition across the yearPeak-season crew assumed year-roundGet seasonal staffing in writing
Maintenance downtimeStoppage logs and service recordsZero-downtime planning assumptionsInsert a downtime allowance
Headcount realityTime-clock and payroll across monthsQuoted crew larger than attendance showsBase plans on verified attendance

Use the matrix as a scope checklist: any row without corroborating records becomes explicit audit scope rather than background trust.

Illustration: The classic capacity illusions, Decorative illustration for the section "The classic capacity illusions,"; visual only, carries no data.

From scope letter to verified conclusion

  1. 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.
  2. 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.
  3. Agree corrective actionsConvert findings into dated commitments with named owners at the closing meeting while attention is focused. Vague improvement intentions age into the next audit repeat findings.
  4. Verify under loadSchedule the follow-up during normal busy production rather than a staged quiet week. Fixes that hold under load are assets; fixes visible only under observation are liabilities.
  5. 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.

Recurring gaps in capacity evidence

Audit fatigue is real on both sides of the table, and tired people produce thin evidence and thinner conclusions. Restricted substance rules explain why buyers test at all: certain materials are limited in electrical and electronic products, so composition evidence belongs in the file.[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.

Illustration: Recurring gaps in capacity Decorative illustration for the section "Recurring gaps in capacity"; visual only, carries no data.

Corrective closure is where fatigue does its costliest damage, as follow-up visits get postponed and promises age into ambiguity. Acceptance testing practice follows the same logic: agree the criteria first, test against them, and let the result decide whether the goods move forward.[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. Restricted substance rules explain why buyers test at all: certain materials are limited in electrical and electronic products, so composition evidence belongs in the file.[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

A practical rule: plan against demonstrated output, not nameplate output, and keep a visible reserve for the rush orders that always arrive. Schedules built on peak-week assumptions fail exactly when failure costs most.

Sources

  1. Wikipedia: Restriction of Hazardous Substances Directive —— Overview of the RoHS directive restricting hazardous substances in electrical and electronic equipment.
  2. Wikipedia: Factory acceptance test —— Overview of factory acceptance testing performed before shipment or installation.

Frequently asked questions

What records best verify a capacity claim?

Independent, mutually constraining records: time-clock and payroll data for labor, material intake for possible output, production tickets for actual output, and shipment logs for what left. Consistency across these sources earns confidence that no single spreadsheet can provide. Ask for the same weeks across all sources so the triangulation is exact.

How should subcontracted steps be audited?

Name each external step in the scope letter, visit the subcontractor or review their recent delivery performance, and confirm inspection rights and rejection records mirror the main factory. Undisclosed outsourcing follows someone else's schedule during crunch weeks. Backup options for critical external steps belong in the contingency plan.

What is the most common capacity illusion?

Nameplate output presented as available output, ignoring changeovers, rework, maintenance, and mix effects. Demonstrated output from comparable past months is the honest baseline. The gap between the two is where delivery promises go to fail.

How can buyers handle seasonal workforce swings?

Get the seasonal staffing pattern in writing with hiring and attrition data, then schedule critical production inside reliably staffed windows. Factories with stable crews deserve more scheduling trust. Avoid assuming the peak-season crew exists year-round without evidence.