18 September 2026 · 5 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 the same way: a spreadsheet for tracking, a WhatsApp group for talking, and a chain of emails for everything else. It works well enough 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, unclear and hard to prove afterwards. The cost is real. It is just hidden until the worst possible moment.

This is an honest look at what coordinating a recall by hand actually costs.

Why the manual stack survives

Nobody chose the spreadsheet-and-group-chat stack on purpose. It accreted. The spreadsheet started as a complaint tracker. The WhatsApp group started because it was faster than email. The email chain is just how work has always moved. Each tool is familiar, free, and already open on everyone's phone. In normal operations they are genuinely fine.

The trap is that steady state is not the test. The test is the incident, and the incident behaves nothing like a normal Tuesday.

What it costs when a recall hits

The record fragments across a dozen phones

The single most expensive failure. During an incident, decisions and messages scatter across a group chat, several inboxes, a spreadsheet and a few phone calls nobody wrote down. There is no single timeline. When legal or your insurer asks what happened and when, someone spends two days reconstructing it from screenshots and memory. A reconstructed record is weaker evidence than one built as it happened, and it is a poor way to spend the days after a recall.

Ownership goes fuzzy

A group chat has no concept of who owns what. A message asking "can someone quarantine the affected stock" is read by eight people and actioned by none, because everyone assumes someone else has it. Tasks fall between people precisely when nothing can afford to be dropped.

Escalation is a scramble

The out-of-hours numbers live in a spreadsheet tab, or in one person's phone, or in the plan nobody opened. Reaching the right people becomes a hunt, and you discover mid-incident that the retailer contact left last year and the number on file is dead.

Version control breaks

Two people edit the tracker at once. Someone works from a copy that is an hour out of date. A decision gets made on stale information. In a fast-moving recall, the spreadsheet that is supposed to be the source of truth becomes a source of confusion.

The new person is lost

Anyone who joins the response an hour in, a senior manager pulled in, an external advisor, has to scroll back through hundreds of chat messages to understand what is going on. There is no clean state of play to hand them. So they either operate half-informed or pull three people off the response to brief them.

Silence and speculation both leak

Group chats blur the line between a private working conversation and a communication. Someone speculates about the cause, and that hypothesis, meant for the team, ends up quoted to a retailer or screenshotted onto social. The tools were never built to hold a disciplined line between internal thinking and external messaging.

The tell: you only feel the cost once

Here is what makes this cost so easy to ignore. You do not pay it 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. That is the worst possible risk profile: an invisible cost that lands in full exactly when you can least afford it.

What good looks like instead

Coordinating a recall well does not require abandoning the tools your team likes for day-to-day work. It requires one place that holds the response together when an incident is live. In practice that means:

One live record, timestamped, built as the response happens, exportable for legal and insurers.
Clear ownership, with each action assigned to a named person and a due time, so nothing sits unowned.
Instant escalation, with the contact matrix held current and reachable in seconds, not scrolled for.
One current state of play, so anyone joining the response sees where things stand without reading the whole history.
A clean line between working conversation and external communication, so speculation does not leak.

This is not about adding process for its own sake. It is about making sure that on the one day the manual stack fails, something is holding the response together instead.

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. The cost shows up as a fragmented record, unclear ownership, slow escalation and version-control problems, all at the worst possible moment.

What is the biggest risk of coordinating an incident by hand? The record fragmenting across phones and inboxes. When you cannot produce a single, timestamped account of what you did and when, you are weaker with the regulator, the retailer and the insurer, and reconstructing it afterwards costs days.

Do we need to replace our existing systems? Not your quality system or your day-to-day tools. What is usually missing is a coordination layer for the live incident, the thing that holds the response, the ownership and the record together when something goes wrong. That sits alongside what you already have.

How do we know if our manual approach is a risk? Run a mock recall that starts the way a real one would and watch the first hour. If ownership is unclear, the escalation is a scramble, or you cannot easily produce a clean timeline afterwards, you have found the cost before it found you.

Friday4:30 is the coordination layer for food and drink incidents. It gives you the one live place that holds the response together when a recall hits, without replacing the systems your team already relies on. If the manual stack is your current recall plan, that is worth a conversation.