29 June 2026 · 2 min read

Spreadsheets, WhatsApp and email, the hidden cost of coordinating a recall by hand

Short answer: Roughly half of food and drink suppliers still coordinate incidents with a spreadsheet, a WhatsApp group and a chain of emails. It works fine in steady state, which is exactly why it survives. Then a real recall hits, and the cracks that were invisible on a normal Tuesday become the reason the response is slow and hard to prove afterwards. The cost is real, it’s just hidden until the worst possible moment.

What it costs when a recall hits

The record fragments across a dozen phones and inboxes, so when legal or your insurer asks what happened and when, someone spends days reconstructing it from memory. Ownership goes fuzzy, since a group chat has no concept of who owns what, and a message read by eight people gets actioned by none. Escalation becomes a scramble when out-of-hours numbers live in someone’s phone rather than somewhere reliable, and version control breaks the moment two people edit the tracker at once. Anyone joining the response late has no clean state of play to inherit, so they either operate half-informed or pull people off the response to brief them. And the line between private speculation and external communication disappears, so a hypothesis meant for the team ends up quoted to a retailer.

The tell

You don’t pay this cost on the ninety-nine normal days. You pay it all at once, on the one day it matters, when the pressure is highest and your capacity to absorb it is lowest.

What good looks like instead

It doesn’t require abandoning the tools your team likes day to day. It requires one place that holds the response together when an incident is live. A timestamped record built as it happens, clear ownership on every action, escalation contacts kept current and reachable in seconds, and a clean line between working conversation and anything external.

Frequently asked questions

Can you manage a food recall with spreadsheets and WhatsApp?

You can, and many brands do. It works in steady state and fails under load, usually through a fragmented record and unclear ownership at the worst possible moment.

Do we need to replace our existing systems?

No. What’s usually missing is a coordination layer for the live incident itself, sitting alongside what you already use day to day.

Friday4:30 is the coordination layer for the food and drink business, from product incidents to business and industry issues, first alert to closed-out review.

This article is general guidance, not legal or regulatory advice. Always confirm your specific obligations with your regulatory authorities and legal advisors.