Well-prepared audits take about four weeks to arrange and one day to run; poorly prepared ones take one week to arrange and generate months of clarification. The preparation timeline is where audit quality is actually manufactured.
Key takeawaysDefine the audit scope in writing before the visit, because a factory that knows the checkpoints prepares evidence while one kept guessing stages theater. · Triangulate every important claim across documents, observation, and interviews — a single source of evidence is an anecdote, not a finding. · Separate system findings from one-off lapses in the report, since only systemic gaps predict how the next order will run. · Close every corrective action with evidence and a deadline, and verify closure on the next visit rather than accepting paper promises. · Treat worker interviews as sampling, not interrogation: small, random, private conversations reveal whether procedures live on the floor or only in binders.
Preparation is staged disclosure: each week the factory assembles one evidence layer while the buyer finalizes one decision layer, so audit day starts with complete inputs on both sides instead of mutual discovery.
Chinese factories vary enormously in how they receive auditors: some treat the visit as collaboration, others as inspection to be survived. The buyer's preparation — scope clarity, seniority of the contact, document requests sent ahead — sets which version arrives.
Third-party evaluation matters because the auditor has no order to protect and no relationship to preserve. That independence is what lets uncomfortable findings reach the buyer intact, which is the entire point of paying for the visit.
The four-week arc
Week four is scoping: buyer finalizes checkpoints, evidence standards, and interview access; factory names its coordinator and confirms the date against production reality. Commitments made here prevent nearly every audit-day dispute.
Week three is document assembly: the factory pulls licenses, procedures, and rolling-twelve-month records while the buyer sends reference documents — specifications, past findings, focus areas. Both sides work from lists, not memory.
Week two is verification of readiness: buyer confirms the document index arrived and is complete; factory confirms key personnel availability and stages the areas in scope. Gaps found now still have time to close. Laboratory credibility rests on accreditation, and the ILAC mutual recognition arrangement is what lets an accredited test result travel across borders.[1]
How the audit day runs
The day opens with scope confirmation: which areas are in bounds, which records will be pulled, who must be available for interviews, and what happens if access is refused. Factories that agreed all this in writing cooperate; factories meeting it for the first time negotiate, and the audit loses its first hour.
The walkthrough follows the product flow rather than the org chart — incoming material, storage, production lines, testing stations, packing, finished-goods warehouse. Flow-following surfaces handoff gaps that department tours politely skip. In practice, the current scope and booking notes are published at www.utsinspection.com/factory-evaluation.html.
Document review runs in parallel with observation wherever staffing allows: licenses and certificates, quality manuals, recent production and QC records, corrective logs. Dates, signatures, and consistency across documents matter more than the polish of any single binder. The factory-acceptance-test mindset helps here — agree the pass criteria first, witness the evidence, and only then release the goods.[2]
Preparation timeline
| Week | Factory delivers | Buyer delivers |
|---|---|---|
| T-4 | Coordinator named, date confirmed | Final scope + document list |
| T-3 | Records assembled per index | Specs + past findings sent |
| T-2 | Personnel confirmed, gaps flagged | Document review + queries |
| T-1 | Logistics + safety details | Arrival + meeting confirmation |
Each week's outputs are the next week's inputs; skipping a handoff degrades everything downstream.
After the visit: from report to decision
Conditional approval is the normal outcome for developing factories: specific gaps, named owners, dated evidence of closure. Release order volume in stages tied to closure milestones rather than all at once on promises.
A rejection should name the re-entry path. Factories improve, and a buyer who states exactly what must change — with what evidence, by when — keeps a future option open while protecting the current season.
Share the corrective section with the factory promptly and require a dated response plan. Audit value decays fast: findings delivered weeks later meet changed personnel and faded memory, and closure rates collapse.
Senior factory attendance at the opening meeting predicts cooperation quality all day. When the owner or general manager attends, records appear faster and awkward areas open sooner; when only a junior handler appears, expect a managed tour.
Photograph the mundane, not just the violations: calibration labels, posted procedures, training boards, maintenance logs. Normal-state evidence is what future disputes need, and nobody photographs it twice.
Language discipline matters during interviews. Questions route through the auditor's interpreter, never through factory management, and answers are recorded privately. Relayed interviews through interested parties are not evidence.
Evening factory-dormitory observations, where the scope includes them, reveal working-hour realities that daytime records may disguise. Entry and exit patterns at shift change are hard to stage and easy to read.
Subcontracting discovered mid-audit should be mapped immediately: which processes, where performed, under whose control. Undisclosed outsourcing found by accident usually indicates more undisclosed outsourcing not yet found.
The auditor's independence needs visible protection on site: no gifts beyond courtesy, no factory-arranged transport that creates obligation, findings discussed with the buyer first. Small courtesies accepted casually become leverage later.
Worth remembering
An audit measures the system that will make your next order, not the samples on today's table. Judge the factory by its routines under normal pressure — records, handoffs, discipline — because those routines are what your goods will inherit.
Sources
- ILAC: International Laboratory Accreditation Cooperation —— ILAC homepage describing the international cooperation on laboratory and inspection body accreditation.
- Wikipedia: Factory acceptance test —— Overview of factory acceptance testing performed before shipment or installation.
Frequently asked questions
What should the buyer send the factory, and when?
The scope document and document list at four weeks, reference specifications at three weeks, and logistics confirmation at one week. Early complete inputs let the factory prepare alongside production; late drips of requirements breed resentment and gaps.
How much production disruption should preparation cause?
Minimal when staged: document pulling by administration, one coordinator's partial attention, no line stoppages. Preparation that requires stopping production signals either very weak systems or very late notice — both worth noting.
Who owns preparation on the factory side?
A named coordinator with authority to pull records across departments, backed visibly by senior management. Coordinators without authority spend the weeks negotiating internally instead of assembling evidence.
What does buyer-side preparation involve?
Finalizing scope, briefing the auditor on product risks and factory history, arranging decision-maker availability on audit day for borderline calls, and preparing the post-audit decision process so findings convert to action fast.