An AI hardware factory audit should prove that the quoted product can move through a controlled process at the exact site you are evaluating. Do not begin with a generic scorecard. Begin with one product revision, one process route, one planned volume, and one traceability test.
During the audit, follow that product from incoming material to final release. At every step, ask for the current method and a recent record created by that method. Record anything you only heard as declared, not verified. A certificate, a showroom, or an idle machine can support a review, but none of them alone proves the factory can build your configuration consistently.
Write the audit scope before the visit
A useful audit has boundaries. Send the scope to the supplier before the visit so the right records, owners, and production areas are available. If the factory changes the site, product, line, shift, or subcontractor, note the change rather than silently expanding the conclusion.
| Scope field | What to record | Why it matters |
|---|---|---|
| Legal entity and site | Registered company, physical address, and the entity on the quotation | Prevents a trading office or sister site from being mistaken for the audited factory |
| Product baseline | Model, hardware revision, firmware state, BOM revision, and accessories | Keeps evidence tied to the configuration you may buy |
| Process route | Incoming, assembly, programming, test, pack, and release steps | Shows where controls and handoffs must exist |
| In-house and outsourced work | Which party performs each process and where | Makes hidden subcontracting and missing audit scope visible |
| Demand assumption | Pilot quantity, production quantity, shift pattern, and target period | Turns a capacity claim into a reviewable calculation |
| Audit sample | Lines, records, lots, dates, and people sampled | Stops a limited visit from being reported as universal proof |
Use four evidence states
Do not force every answer into pass or fail during the walkthrough. Use four states so the team can see what was actually supported.
- Declared: a person described a capability, process, or result.
- Observed: the auditor saw the place, equipment, label, or activity.
- Recorded: a controlled document or recent record supports the claim.
- Verified: the record, product, process, and scope agree, with no unresolved contradiction.
For example, seeing an automated optical inspection machine proves that the machine exists. A recent inspection record tied to the sampled assembly, current program, operator, result, and disposition is stronger evidence that the control was used for that product.
Buyer rule: ask twice at every critical control: “Show the current method” and “show a recent record produced by that method.” A procedure without records, or records with no controlled method, needs follow-up.
The 10-stop factory walkthrough
1. Confirm the entity, site, and audit boundaries
Match the legal entity, address, quotation, quality documents, and people hosting the audit. Ask which product and processes belong to this site. Record any other facility, affiliate, or subcontractor that participates in engineering, assembly, testing, packaging, or shipping.
2. Map the real process route
Ask the team to draw the route from material receipt to dispatch. Then walk it. Compare the route with work instructions, floor layout, WIP labels, and the quoted scope. If the product leaves the site, identify the handoff, the external provider, the acceptance step on return, and the change-notification rule.
3. Trace incoming material
Select one meaningful component or assembly. Check its supplier identity, specification, receiving status, lot or batch link, storage condition, segregation, and issue record. The audit does not need to prove every part, but the sample should reveal whether the system can preserve identity and status.
4. Check engineering release and change control
Compare the released drawing, BOM, firmware or programming instruction, test limits, work instruction, tooling, and packaging specification. Ask who can approve a component, firmware, process, or test change. Then inspect one recent engineering change: request, review, affected stock, implementation date, and verification.
5. Observe production controls
Choose a live or recent production step. Look for the correct instruction and revision, material identity, operator qualification where required, equipment or tooling status, first-off approval, in-process checks, and WIP status. Do not infer volume capability from the number of machines. Tie capacity to cycle time, yield, staffing, maintenance, setup, bottlenecks, current loading, and the quoted shift plan.
6. Test inspection and measurement discipline
Pick one important product characteristic. Identify the test method, equipment, calibration status, sample rule, limit, result, and reviewer. Follow one failed result to its containment and disposition. An inspection report is useful only when it can be connected to the correct product revision, lot, method, and equipment.
7. Follow a nonconforming unit
Ask how a failed unit is identified and separated. Review one recent case from detection through review, disposition, rework instruction, retest, root-cause action, and effectiveness check. If material can return to production, the record should show who authorized it and how the unit was re-verified.
8. Run a two-way traceability test
Choose a finished unit or finished-goods lot and trace backward to the relevant material, process, test, and release records. Then choose a component lot and trace forward to affected work in process and finished goods. IPC-1782B describes risk-based manufacturing and supply-chain traceability for electronic products; your required depth should still match the product, market, and business risk.
9. Challenge capacity and continuity assumptions
Request the calculation behind the proposed output, including working days, shifts, cycle time, yield, changeover, planned downtime, rework, and the bottleneck process. Compare it with recent records and current loading. Ask how critical equipment, people, suppliers, test fixtures, software, and data are backed up. Treat future equipment or hiring as an open action, not current capacity.
10. Close at final release and dispatch
Inspect the final release record, quantity reconciliation, pack specification, labels, accessory checks, storage status, and shipment traceability. Confirm who has release authority and how blocked product is prevented from shipping. If product identity changes at packaging or branding, make sure the approved configuration remains traceable.
Certification is a starting point, not the whole audit
ISO explains that a supplier can support confidence through its own declaration, a customer assessment, or third-party certification. If a factory presents an ISO 9001 certificate, verify the organization, site, scope, standard edition, certification body, validity, and whether the quoted work falls inside that scope. A management-system certificate does not certify your product.
ISO 19011:2026 provides guidance on audit principles, audit programs, conducting audits, and auditor competence. It also emphasizes evidence-based and risk-based approaches. Use those principles to plan the audit, but define product-specific criteria with your quality, engineering, regulatory, security, and legal owners.
Remote audits need tighter evidence rules
A live video audit can help with an early screen or follow-up, especially when travel is impractical. Ask for continuous navigation between agreed areas, live views of labels and records, and dated exports of selected evidence. Record anything the camera cannot show, any area the host declines to enter, and any record supplied only after the call.
Remote access can confirm useful facts, but it can also narrow the sample. Do not present a remote audit as proof of every shift, line, subcontractor, or future order. Use it to decide which gaps require an on-site visit, third-party assessment, sample validation, or contract control.
End with an issue log, not one reassuring score
A single percentage can hide an important unresolved gap. Close the audit with an issue log that preserves evidence and ownership.
| Field | Example entry |
|---|---|
| Requirement | Finished unit must link to component lot and final test record |
| Evidence state | Recorded, not yet verified |
| Evidence sampled | Lot A2409, unit 0187, test record TR-91 |
| Gap or contradiction | Packaging label uses a different revision identifier |
| Owner and due date | Supplier quality owner, dated response required |
| Closure evidence | Corrected label rule plus one verified production record |
Classify issues by consequence and scope, not by how confidently someone answered. A missing calibration record, undisclosed subcontractor, unapproved substitution route, or untraceable lot may require a different decision from a housekeeping observation. Keep open items visible until the agreed evidence is reviewed.
What one factory audit cannot prove
- Performance on every line, shift, product revision, subcontractor, or future order.
- Product compliance, cybersecurity, privacy, or legal suitability for a target market.
- Future capacity based only on planned equipment, hiring, or supplier promises.
- Ongoing control after components, firmware, tooling, ownership, or sites change.
NIST describes supplier due diligence as research that supports informed acquisition decisions. For connected recording hardware, combine the factory audit with product testing, commercial review, security and privacy review where applicable, and a controlled change process. The audit is a dated evidence record, not permanent supplier approval.
Before arranging a visit, use the 15-question AI hardware supplier RFQ checklist to confirm scope. If you are still choosing a partner type, read manufacturer vs solution provider. The AI voice recorder manufacturer scorecard and AI Hardware Customization hub cover the wider sourcing process.
Official references
- ISO 19011:2026 — Guidelines for auditing management systems
- ISO — How can you have confidence that your supplier meets ISO 9001?
- ISO 9001 Auditing Practices Group — External providers
- U.S. DLA ASSIST — IPC-1782B traceability standard record
- NIST SP 1326 — C-SCRM Due Diligence Assessment Quick-Start Guide
Your next step
Choose one product revision and complete the scope card before booking the audit. Then send the factory the process route and evidence list you expect to sample. You will arrive with a testable plan instead of a tour agenda.
Planning an AI recording hardware project? WhatsApp Recolx at +85251718843 or email sale@recolx.ai.
