Dispatch note · 19 Nov 2026

Supplier audits: what a remote review can prove, and what only a site visit can

A remote audit is a reading of documents and a phone call. A site visit is a reading of a factory. The two answer different questions, and confusing them is expensive.


A remote audit is a reading of documents and a phone call. A site visit is a reading of
A remote audit is a reading of documents and a phone call. A site visit is a reading of a factory. The two answer different questions, and confusing them is expensive.

The four questions an audit has to answer

Any audit, remote or on site, is trying to answer four questions: can this factory make the product, can it make it consistently, is it telling the truth about what it does, and will it still be doing it next year.

The first two are technical and can be partly answered by documents. The third and fourth are behavioural and are answered by observation and by time.

A remote audit is strong on the first two and weak on the last two. A site visit is strong on all four, at a cost that is worth paying for a first order and usually not worth paying for a repeat.

The audit's purpose should decide its form. A brand that runs a remote audit to save money and then treats the result as a site visit is buying confidence it has not earned.

What documents can prove

A business licence, an export licence and a tax registration prove that the entity exists and can legally trade; they do not prove that it makes the product.

Certificates - ISO 9001, BSCI, a product certification - prove that a third party audited something at some point. The brand should read the certificate's scope and its date, because a scope that excludes the product line is a certificate that does not apply.

Test reports prove that a sample passed a test at a laboratory. They do not prove the production line makes the same thing, which is what the brand is actually buying.

The document set is a filter, not a verdict. It removes the obvious frauds and leaves the rest unresolved.

What a video call adds, and what it cannot

A video walk-through with a live camera shows the machines, the lines, the warehouse and the people, and it shows them at a moment the factory has chosen.

It can prove that a line exists and is running. It cannot prove the line's output, the defect rate, the working conditions or the factory's behaviour when the camera is off.

A staged walk-through is easy to detect if the questions are specific: ask the operator to read a gauge, show the maintenance log's last entry, point the camera at the scrap bin.

The call is a good tool for a repeat supplier and a weak tool for a first order. The brand should treat it as a check on a known relationship, not as a discovery.

What only a site visit reveals

A site visit reveals how the factory behaves when it is not being watched: the state of the toilets, the age of the fire equipment, whether the scrap bin is full of parts that look like the product.

It reveals the capacity's real shape: how many lines, how many shifts, how many people, and whether the space for expansion exists or is a promise.

It reveals the management: whether the owner is present, whether the quality manager can answer a technical question without fetching someone, and whether the workers look at the visitor or through them.

None of that fits in a checklist, and all of it changes the price and the risk. The checklist's job is to make the observation systematic, not to replace it.

Sampling the production, not just the sample

The most useful part of a site visit is the unannounced look at a production run, not the golden sample that was prepared for the visitor.

The auditor should ask to see the last three production records, the last three defect reports and the last shipment's inspection sheet, and should compare them with each other.

A factory that cannot produce the records in five minutes does not maintain them, whatever the folder in the meeting room shows.

The records' consistency is the evidence of a system; a single polished document is the evidence of a presentation.

Remote audits that are worth running

A remote audit is worth running when the factory is known, the product is simple and the order is small. Its value is in the discipline it imposes, not in the assurance it provides.

It should be structured: a fixed document list, a scheduled call with named participants, specific questions with specific evidence requests, and a scoring sheet with red, amber and green thresholds.

The brand should require the factory to send the evidence as files, not as photos in a chat, because the files can be checked for metadata and the photos cannot.

A remote audit should end with a list of what remains unverified and what the brand will verify on the first shipment. That list is the honest output.

Auditing the auditor

Third-party audit firms vary as much as factories. The brand should ask for the auditor's name, the days spent on site, the sample size and the report's scope before accepting a certificate.

A report that is three pages for a factory of two hundred people is a report that sampled nothing. A report with photographs of every line, the timestamps and the names is a report that was done.

The firm's accreditation matters for regulated products and matters less for a general capability audit, but the report's method always matters.

A brand that pays for an audit and does not read the report has paid for a certificate, not for information.

The audit as a decision gate

The audit should sit at a gate with a defined outcome: proceed, proceed with conditions, or stop. A gate that produces a report and no decision is a cost with no benefit.

The conditions should be specific and time-bound: a machine to be installed, a quality manager to be hired, a second line to be validated, each with a date and a verification method.

The gate should apply to the first order and to any change of site, ownership or product line, because those are the moments when the earlier audit stops describing the factory.

A brand that audits once and then assumes the factory is unchanged is trusting a snapshot to describe a moving object.

The audit report that a factory will actually use

A report written as a verdict is filed; a report written as a list of findings with owners and dates is used.

The findings should be ranked by consequence rather than by category, and the top three should be the ones that could stop the order.

The factory's corrective actions should be verified at the next visit rather than accepted as promises, because an unverified action is a sentence in a document.

A report that the factory's own quality manager keeps on the wall is a report that changed something.

The second-source question the audit should answer

An audit is also a check on whether a second source is needed, because a factory that is the only source of a critical component is a single point of failure.

The auditor should ask what the factory would do if its main machine failed, and whether the answer is a spare machine, a subcontractor or a delay.

A factory with a subcontractor should declare it, and the brand should audit the subcontractor too, because the certificate belongs to the site and not to the supply chain.

The single-source answer belongs in the file next to the audit report, because it is the risk the audit could not remove.

The short version

A remote audit proves documents and existence; a site visit proves behaviour, capacity and the state of the scrap bin.

Use the remote form for known suppliers and small orders, and list what remains unverified so that the first shipment can close the gap.

Put the audit at a gate with an outcome, verify the corrective actions on the next visit, and record the single-source answer beside the report.

Two final numbers

Track the share of audit findings closed on time, and the share of first orders that passed inspection without a critical defect.

A factory whose findings close on time is a factory whose next audit can be remote without much risk.

A partner that will say which items remain unverified after a remote review is the sourcing and procurement desk, and that honesty is worth more than a certificate.

What to check

  • Audit purpose matched to form (remote vs on-site)
  • Certificate scope and date checked against the product line
  • Video call questions that require live evidence
  • Site visit includes an unannounced look at a live run
  • Last three production and defect records compared
  • Remaining unverified items listed after a remote audit
  • Gate outcome (proceed / conditions / stop) recorded