Accident and incident reporting duties: what to report, to whom, and how quickly, in general terms

A reportable incident, in general terms, is an event where a product causes, or may cause, serious harm to a person, or where a product failure creates a serious risk that should be brought to the attention of authorities and others in the chain. This guide gives general educational information only and does not give legal advice for a specific incident, since reporting duties depend on the product, the market, the severity and the applicable rules, and a seller facing a serious incident should seek prompt advice from a knowledgeable adviser or the relevant authority. The general principle, however, is consistent: serious harm and serious risk should be reported promptly, not held until an investigation is complete.

Incident reporting typically involves several audiences, in an order that protects people first: the customer affected, with care and practical help; the supplier and others in the supply chain, so they can check other products; and the relevant market surveillance authority, through the route that authority provides. Retailers and marketplaces that sold the product should also be informed where they can help reach other owners. The exact authority and route depend on the market and the product, and sellers should identify their relevant authority and reporting route in advance, as part of monitoring preparation, rather than searching for it during a crisis.

Internal reporting matters too: the incident should be logged in the safety register, escalated to the product safety decision maker the same day, and grouped with other reports for that product and batch. An incident reported externally but not logged internally will be forgotten internally, while an incident logged internally but not reported externally may fail a duty. Both routes should happen, promptly, and both should be recorded, so the incident history is complete whichever audience later asks.

Reporting should happen promptly, on the facts known at the time, rather than waiting for a complete investigation, since delay leaves other owners exposed and authorities uninformed while a cause is still being established. A first report should contain the product identification, the batch where known, a factual account of what happened, the harm or risk observed, the number of similar reports known, and the immediate steps taken, such as pausing sales of a batch. It should avoid speculation about cause, blame or legal conclusions, since those may change as investigation proceeds, and a speculative first report can mislead more than it helps.

While a report is being prepared, the seller should take precautionary steps proportionate to the risk: preserve the product and its details, pause sales of the affected batch where the risk suggests it, warn other owners where a warning can prevent further harm, and contact the supplier for batch and component information. Those steps should not wait for the report to be finalised, since their purpose is protection, not paperwork. Record each precautionary step with its date and reason, so the report, when sent, can show what was done immediately, not only what was planned.

Illustration: a seller learning of a heater that overheated preserved the heater, paused that batch, and sent a first report with the known facts the same day, updating it a week later when testing identified a faulty thermostat batch. The seller story is illustrative, and the lesson is that prompt precaution and prompt reporting, followed by honest updating, is a stronger position than delayed perfection, since protection and credibility both favour early action on known facts.

Reporting readiness should be prepared before an incident: identify the relevant authority and reporting route, name the internal decision maker and deputy, keep a first report template with product identification fields, and train handlers to escalate serious reports the same day. That preparation, done in calm conditions, turns a crisis response from a search for contacts and templates into a prompt, factual report. A seller who prepares reporting readiness will report faster and more accurately, and will be judged, by authorities and customers alike, as a seller who takes serious incidents seriously.

After reporting, investigation should proceed, corrective action should be decided through the signal decision process, and the lesson should be applied to design, supplier, testing or instructions, so the incident does not repeat. The reporting file should be closed with a summary: what happened, what was reported and when, what was found, what was done, and what changed. That closed file, kept with the monitoring log, turns a painful incident into a durable improvement and a record that a future team can learn from, rather than a file that is closed because the incident is over.