How Do You Request an Audit Report From a Supplier?

Most buyers either never ask for an audit report or ask for it in a way that produces a brochure. Both failures have the same root cause: the request is made as a favour rather than as a step in a process, and the answer is therefore shaped by politeness rather than by procedure. The fix is not to ask more forcefully; it is to make the request ordinary, specific and part of the standard document set that accompanies a quotation.

This piece sets out what to ask for, how to ask, what a reasonable production partner will say yes to, what they will legitimately decline, and what to do with each of those answers. It also covers the case that most guides ignore: what to do when there is no report to share, which is a common and perfectly workable situation.

Which Report Should You Ask For, and From Whom?

Name the class, not the concept. "Please send your audit report" invites a first-party self-assessment; "please send the most recent third-party audit report conducted under a named programme, with the evidence annex" invites the document you actually need. Where a programme has a specific scheme in mind, name it, and where it does not, ask what schemes the site is audited against and choose from the list rather than accepting whatever is nearest to hand.

Then name the entity. Ask for the report covering the legal entity and the site address that will produce the order, and say so explicitly in the request. A group report covering several entities is not evidence about the one that will invoice the buyer, and a report for a registered office is not evidence about a production floor. Naming the entity in the request converts a vague document into a specific one and costs one sentence.

How Do You Ask Without Turning It Into an Interrogation?

Say what the report is for. A production partner receiving a bare demand reads it as distrust and answers accordingly; the same partner told that a buyer is building a programme file and needs a dated, third-party document for it will usually send the full report. The difference is not tact, it is context: people comply with procedures and resist accusations.

Put the request in the normal commercial flow, at the point where the quotation is discussed, and treat it as one line in a list of documents rather than as a separate examination. Buyers who make the request routine get better documents than buyers who make it dramatic, and they get them faster, because the report is already indexed and does not have to be assembled under pressure.

What Should the Request Message Actually Contain?

Six lines, in this order: what the buyer is asking for, why, the class and programme, the entity and site, the maximum acceptable age, and how the document will be handled. That is a short message and it removes every ambiguity that produces a useless answer. Add a sentence on what the buyer will do with personal data, because interview logs are routinely redacted and the production partner needs to know that redaction is expected and acceptable.

Do not attach a questionnaire to the request. A questionnaire signals that the buyer does not trust the report and intends to audit the auditor, which pushes the conversation toward the shortest compliant answer. Read the report first and ask questions afterwards; questions asked after reading are specific and get specific answers, and questions asked before reading are generic and get generic ones.

How Recent Does the Report Have to Be?

Recent enough to be inside the cycle set by the programme behind it, and recent enough to cover the scope of the order. The second condition is the one that trips buyers: a report issued inside its cycle can still predate a new building, a new process or a change in the scale of operations, and it therefore says nothing about the part of the operation the buyer is depending on.

State both conditions in the request. Ask for the issue date, ask for the cycle length, and ask whether any change of site, entity or scale has occurred since the visit dates. Those three questions take one line and they convert an expiry check into a scope check, which is the check that actually matters.

Can You Ask for the Full Report Instead of a Summary?

Yes, and it should be the default. A summary removes the method section and the evidence annex, which are exactly the two parts that let a buyer weigh the findings. Asking for the full report is not an escalation; in most established programmes the full report is the standard share and the summary is the exception produced for buyers who did not specify.

What a buyer should expect to receive redacted is personal data: names in interview logs, signatures, and anything identifying an individual. That redaction is normal and should be accepted without argument. What should not be accepted is redaction of the finding text, the clause references, the sampling period or the corrective entries, because those are the substance of the document.

What Do You Do When the Report Is Shared on a Platform?

Accept platform access rather than insisting on a file, because that is how most programmes distribute reports and pushing for an attachment usually means waiting. Ask for read-only access for the named people who need it, confirm whether download is permitted, and record the access route in the programme file so that the document can be found again twelve months later by someone who was not there at the time.

Then check the version. Platforms hold multiple reports for the same site across cycles, and it is easy to be granted access to the wrong one. Confirm the issue date and the cycle on the document actually opened, not on the link description. Where a report has been superseded, the platform usually shows the earlier one as archived; read the current one and note the earlier one as history.

How Do You Handle a Report That Names Another Buyer?

Reports are frequently commissioned by one buyer and shared onward, and the document may carry that buyer name in the commissioning field. That is normal and is not a problem. What matters is whether the scope covers the processes the second buyer needs; the identity of the commissioning party has no bearing on the findings.

The one thing to check is confidentiality. Some reports are shared under a condition that limits onward distribution or requires the recipient to be named. Where that is the case, honour it, record the condition in the programme file, and do not circulate the document internally beyond the people covered by it. A buyer who mishandles a shared report will find the next request declined.

What If There Is No Report to Share?

There are three legitimate reasons and one bad one. The legitimate reasons: the site has never been audited under a third-party programme; a report exists but the cycle has lapsed and a new audit is scheduled; or the site is audited under a scheme the buyer does not recognise and cannot map. The bad reason is a refusal to say which of the three applies.

For the first, the workable path is a first-party self-assessment now and a third-party audit before or during the pilot, with the pilot used as the practical evidence in the meantime. For the second, ask for the scheduled date and treat the pilot as the interim evidence. For the third, ask for the clause set the scheme covers and compare topic by topic. None of those is a disqualification; all three are common and manageable.

How Should the Report Be Filed Once It Arrives?

Filed where the commercial decisions are made, not in a compliance folder nobody opens. The practical test is whether the person who places the next order can find the report and its expiry without asking anyone. That means one index entry with the entity, the site, the programme, the issue date, the expiry, the scope and the file location, and it means the expiry sits on the same calendar as the production schedule.

Two further entries are worth making at filing time: a note of what the programme looked like on the day of the audit, and a note of which processes the report does not cover. Both are dull and both are the entries that matter in an argument eighteen months later, because the gap between what was audited and what is being bought is the gap every dispute eventually falls into.

What Does a Good Answer Look Like, and How Quickly?

A good answer arrives within a few business days, contains the full report with the annex, and includes a line on the cycle and the next scheduled audit. A production partner with an indexed file can produce that quickly; one that has to assemble it will take longer, and the delay itself is information about how the document set is managed.

Where the answer is slow, do not read hostility into it. Ask once, specifically, and then judge on the document rather than on the timing. Where the answer never arrives, record the request and the non-response in the programme file and treat due diligence on that point as incomplete. That is not a verdict on the site; it is an accurate statement about the buyer file, which is the only thing the buyer controls.

One further practice is worth adopting: ask for the document set at quotation stage rather than at order stage. A buyer who asks early gets the report as part of a normal exchange and can read it before committing; a buyer who asks after placing the order is asking under time pressure and will accept a summary rather than hold up a schedule. The same document, requested two weeks earlier, is a far better instrument.

The commercial frame is unaffected by the document flow: MOQ 500 pcs per style and colourway, sampling 6-10 working days from a signed-off tech pack, bulk production 35-50 days from written sample approval, inspection at AQL 2.5 under ISO 2859-1 General Inspection Level II, T/T 30/70, quoted FOB Xiamen. A request for an audit report adds no time to any of those windows, and a programme that treats it as routine loses nothing by making it.

One practical detail decides whether the document is usable a year later: keep the request and the answer together. A report filed without the request it answered leaves the reader unable to tell what was asked for, and therefore unable to tell whether what arrived was responsive. One folder with the request message, the reply and the report is a complete record; a report alone is not.

The same applies to a refusal. Where a production partner declines a specific part of the request — the annex, for example, or the full report rather than a summary — record the reason given alongside the partial document. Reasons given at the time are usually precise and reasonable, and a note made twelve months later from memory will not be.

Frequently Asked Questions

People Also Ask