Telling the authorities about a recall: what to send, when, and in what form

A notification written from memory invites follow up questions that slow everything down. Before drafting, gather the product identification, the batch or serial range, the sales period and channels, the fault description, the number of complaints or incidents, and the test or inspection evidence that confirms the fault. A short timeline of discovery helps too, showing when the first report arrived and what checks followed.

Where a fact is still unknown, say so plainly and give the date by which it will be confirmed, rather than filling the gap with a guess. Authorities deal with incomplete pictures routinely; what frustrates them is a confident statement later contradicted by the seller's own records. Illustration: a seller of rechargeable fans lists two confirmed overheating reports, notes a third report still under inspection, and promises the inspection result within a stated week.

Lead with identification, then fault, then risk, then remedy. That order lets the reader grasp the scope before the detail. Identification means product name, model, batch codes and a photograph or drawing if one helps distinguish affected units. Fault means the mechanism in plain terms, such as a seam that splits under load, not a code from an internal system.

Risk follows from the fault: who could be harmed, in what use, and how seriously. Remedy closes the notice: what buyers are asked to do, what the seller offers, and the timetable. Contact details for a named person, not just a general inbox, belong at the end, because a named contact speeds every later exchange.

Factual, specific and unhurried beats defensive or dramatic. Avoid blaming a supplier in the first notice unless the evidence proves it, because blame written early can harden positions before the facts are settled. Avoid minimising language as well: describing a fire risk as a minor warming issue will be read against the complaint evidence and will damage credibility.

Numbers need care. Report only counts the seller can support from records, and label any estimate as an estimate with its basis, such as units shipped in the affected batch. Where complaint counts differ between systems, reconcile them before sending, and explain the reconciliation briefly. A notification that corrects itself within days looks worse than one that waited a day to get the figures right.

The route depends on where the product was sold and which authority arrangements apply, and the seller's responsible person in the EU is normally part of this step. Some situations use a portal, others a direct contact, and marketplace sales may add a platform notification in parallel. The practical rule is to use the route the relevant authority publishes for safety notifications, and to keep proof of submission with the date and reference.

Timing should reflect the risk to continuing users. A risk that could injure someone today justifies same day notification, even if some detail is still outstanding. A slower moving risk, such as a part that degrades over months, still deserves prompt notice, but the seller can use the extra time to confirm the batch range. Delay for commercial reasons, such as waiting for a sales event to pass, is never a defensible reason.

The first notice is rarely the last message. Updates should follow when the batch range widens or narrows, when the remedy changes, when response numbers pass a useful point, or when a new incident arrives. Each update should reference the original notification so the authority can file it against the same case, and should state clearly what changed since the previous message.

A regular rhythm helps even when little changed: a short note confirming the tally and the next step keeps the case alive without burying the authority in detail. The seller should also tell the authority when the action closes, with the final tally and the preventive change made, so the file ends with an outcome rather than trailing off mid conversation.

The most common weakness is a vague product identification that leaves the authority unsure which units are affected. A model name shared across safe and faulty versions, with no batch distinction, forces the authority to ask for the very detail the seller should have supplied. Photographs of labels and packaging, and the exact wording of batch codes, remove that ambiguity.

A second weakness is a remedy described in slogans rather than actions. Saying buyers will be looked after means nothing; saying buyers will receive a prepaid return label and a refund within a stated process means something. A third weakness is silence after the first notice, which authorities read as drift. A short update on schedule costs little and preserves the credibility the first notice built.