A recall log is the diary of a recall: one row for everything that happens, as it happens. Each row has the date and time, what was found or done, who did it, the lots involved, the quantity, and where the proof is kept (the email, the photo, the report). It's kept by one person, the recall coordinator, from the first complaint to the day the last store confirms. Afterwards it's the record you show a regulator, an insurer or a buyer, and the thing you read before your next mock recall to see where the time went. Below is a template with an eight-row example.
The short version
- Start the log the moment a problem is suspected, before you know it's a recall.
- One row for each event or action. Time matters: write it.
- Lots and quantities in their own columns, so they can be added up.
- Name the proof and where it's filed.
- TaroStack timestamps the hold, the notices and the answers for you. More below.
An example: one lot of trail mix
A made-up snack maker's recall of lot TM-1104 for undeclared cashews:
| Date | Time | What happened or was done | By | Quantity |
|---|---|---|---|---|
| Nov 12 | 9:40 AM | Customer email: reaction after eating trail mix; says she is allergic to cashews | SP | |
| Nov 12 | 10:15 AM | Retained sample opened: cashew pieces found. Supplier's invoice for the peanut lot shows a mixed-nut substitution | MR | |
| Nov 12 | 10:40 AM | Decision to recall. Remaining stock put on hold | JO | 84 bags held |
| Nov 12 | 11:05 AM | Trace run: 564 bags made, 84 here, 420 to 9 stores, 60 sold at two markets | MR | 564 |
| Nov 12 | 11:30 AM | FDA recall coordinator phoned; strategy sent | JO | |
| Nov 12 | 1:00 to 4:30 PM | All 9 stores phoned; written notice emailed to each | SP | 9 of 9 reached |
| Nov 13 | 9:00 AM | Press release issued; notices posted at both markets | JO | |
| Nov 19 | 3:00 PM | Effectiveness check: 9 of 9 stores confirmed in writing. 371 bags returned or destroyed, 49 sold before the notice | SP | 371 of 420 |
The template has two more columns: the lots on each row, and where the proof is kept.
What a good log shows
The clock. Complaint at 9:40, decision at 10:40, stores being called by 1:00. An hour from complaint to decision is fast, and it was fast because a retained sample was on the shelf and the supplier's invoice was findable. The gap to look at is 11:05 to 1:00: nearly two hours between having the list and starting the calls.
The arithmetic. 564 made. 84 held, 420 to stores, 60 at markets: 564. Of the 420, 371 came back or were destroyed and 49 had sold: 420. Every bag is accounted for or known to be with a shopper. A log whose numbers don't close is a recall that isn't finished.
The proof. "All 9 stores phoned" is a claim. The call sheet and the sent emails are the evidence. Each row says where its evidence lives, so nobody is hunting for it a year later.
Habits that make it work
One keeper. The coordinator, or someone sitting beside them. Two people writing two logs produces two versions of the day.
Write facts, not conclusions. "Cashew pieces found in retained sample" belongs in the log. "Supplier error" is a conclusion for the report at the end.
Don't tidy it. A log with a correction struck through and initialed is more believable than a clean one typed up the next week.
Close it with a short report: cause, quantities, what changed. That report, the log and the customer confirmations are the recall's file.
Get the template
Download the recall log template. The log with the example, and a read-me. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. The plan for the recall itself is in recall strategy template, who keeps the log in recall team roles, and practice in food mock recall example.
Where this stops working
The person keeping the log is also the person running the recall. By mid-afternoon the rows are being written from memory, and the quantities are whatever the last phone call said. The two-hour gap in the example is a real one: it was spent building the list of who got what.
How TaroStack does it
TaroStack writes much of the log by doing the work.
The trace is instant, and it's the 11:05 row. Open the lot: made, on hand, shipped to whom, in what quantity. The two hours go away.
Starting the recall is recorded. The recall gets a number, and every affected lot in stock is held, with the time and who did it.
Notices and answers are kept on the recall. Each customer's notice goes from your mailbox. The recall shows who was told and when, who has answered, and what they said they had left: your effectiveness check, as it happens.
Returns go back into the lot. What comes back is counted against the lot, so the arithmetic closes without a tally sheet.
The report. It prints, and downloads as one CSV file.
| The log needs | By hand | In TaroStack |
|---|---|---|
| When stock was held | You write the time | Recorded when the recall starts |
| Who got how much | Built from invoices | The lot's trace |
| Who's been told, who's answered | A call sheet | On the recall |
| Quantities that close | A tally | Returns into the lot |
Keep your own log as well: the phone calls and decisions are yours to write. Lots and recalls are on every plan, from $9.99 a month. The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
