Recall management

Food Recall Log: Document Every Step When a Recall Becomes Necessary

A structured recall log for tracking affected batches, customer notifications, quantities recovered, and FSA liaison. The document that proves you acted swiftly and thoroughly.

Why it matters

Why a recall log is the document that protects your business

A food recall is every operator's worst-case scenario, but the difference between a controlled recall and a catastrophic one is documentation. The FSA assesses not just whether you initiated a recall but how quickly and completely you executed it. A properly maintained recall log demonstrates due diligence and can be the deciding factor in whether enforcement action is taken.

Counter-intuitive fact: the most dangerous recalls are not the ones you initiate — they are the ones you delay. Businesses that spend 48 hours trying to "investigate internally" before notifying the FSA face far harsher consequences than those that report immediately and then refine the scope. The FSA expects early notification, even when details are incomplete.

How to use this log

Using this recall log during a product withdrawal or recall incident

Record the triggering event (customer complaint, failed test result, supplier notification), the affected product and batch codes, the date and time recall was initiated, every customer or recipient notified (with contact method and time), quantities dispatched vs quantities recovered, FSA incident reference number, and final disposal method.

Test your recall procedure with a mock recall at least annually. Digital SFBB recall logs provide a pre-built workflow that guides your team through every step, auto-populates batch traceability data, and generates the FSA notification template with all required fields pre-filled — turning a process that typically takes hours into one that takes minutes.

Common mistakes

Recall failures that attract FSA enforcement action

No mock recall testing. The FSA expects evidence that you have tested your recall procedure. A recall log that has never been exercised is a theoretical document, not a proven capability. Run a mock recall annually and document the results — including how long it took to identify all affected product and notify all recipients.

Incomplete contact records. If your dispatch log does not contain accurate contact details for every recipient, your recall log cannot function. See our Dispatch Log and Food Traceability Log for the records that feed into a successful recall.

Prevra · Early access

Prevra is building a digital SFBB app.

The app is not ready yet. See the planned features and contact us about early access.

See planned features

Prevra · In development

Coming soon.

We’re building Prevra to help UK food businesses keep SFBB records. The app is not available to download yet.