Answering an authority information request: complete, organised and on time

Read the request twice: once for the overall purpose, and once item by item, listing each document or explanation wanted. Note the product and batch scope, the deadline, the format wanted, the contact person, and any reference to quote in the reply. A request misread as a general enquiry, when it actually asks for specific test reports by a specific date, will be answered late and incompletely, and that first impression will colour the case.

Where an item is ambiguous, the seller should ask for clarification early, not guess and hope. A short clarification question, sent promptly, is a normal part of the process and protects the deadline, because the authority can then confirm what is wanted while time remains to produce it.

Assemble the answer against the item list, ticking off each item with the document or explanation that satisfies it. Documents should be the genuine records, not summaries rewritten for the occasion, because rewritten summaries raise questions about what the original said. Where a document is long, a short cover note pointing to the relevant pages helps the reader without replacing the document.

Gaps need honest handling. If a requested document does not exist, say so, explain why, and state what alternative evidence exists or when the genuine document will be produced. A gap admitted with a plan is a problem to solve; a gap hidden behind a vague paragraph is a credibility problem that will surface when the authority asks again.

Structure the reply to mirror the request: quote the reference, then answer item by item in the request's order, with each answer followed by its document. That mirroring lets the authority check completeness at a glance, and it prevents the common failure where a thorough reply buries one requested item in a narrative paragraph the reader misses. A short contents list at the top, mapping items to documents, helps further.

Keep the tone factual and brief. Explain what each document shows, without overstating it, and avoid blaming suppliers or buyers in the reply unless the evidence supports it and it is relevant to the item. The reply is a record that may be read by people beyond the original contact, so it should stand alone without background the reader does not have.

If the deadline cannot be met, tell the authority before it passes, with the reason, the items already ready, and a realistic new date for the remainder. An early, honest extension request is usually received better than a silent miss followed by a late, partial reply. The seller should send what is ready by the original deadline where possible, rather than holding everything until the last item is complete, because partial progress shows good faith.

Internal deadlines should sit ahead of the authority deadline, giving time for review and for the inevitable last item that takes longer than expected. A reply assembled the night before the deadline will contain errors; a reply assembled with a day for review will contain fewer, and the review day is cheap insurance.

A reply should be reviewed by someone other than its author, checking completeness against the item list, accuracy of every factual claim, and consistency with earlier messages to the same authority. That reviewer should also check that no document contradicts another, because contradictory documents, such as two different batch ranges in different files, will generate a second round of questions that a review could have prevented.

The review should also check for overclaiming. A test report that covers one property should not be described as proving overall safety, and a supplier assurance should not be described as a test result. Precise descriptions of what each document proves, and what it does not, build the credibility that makes later stages of a case run smoothly.

After sending, file the request, the reply, and proof of sending together, with the date and the contact. Note any follow up questions that arrive, and answer them in the same item by item style, referencing the original reply. A case file that grows in order, with each exchange filed against the reference, lets any team member pick the case up without reconstructing it from inboxes.

The seller should also treat the request as a diagnostic. If the authority asked for a document the seller struggled to produce, that struggle reveals a file weakness to fix as routine, not merely as a one off for this case. Fixing the routine after the request is what turns an information request from an interruption into an improvement.