Key takeaways
- Page one is the plan: names, cell numbers, and hold authority. Everything else is reference.
- Mock recall twice a year with real lot codes. 100% reconciled in four hours or it's a fail.
- Who calls the brand and who pays gets decided in the contract, not at 2 a.m.
A food recall plan template that only works during business hours isn't a plan — it's audit paperwork. Real recalls start with a Friday 6 p.m. call from a brand, a supplier notice, or an FDA email, and the clock runs whether your QA manager answers or not. Here's what belongs on paper before that call, including the two questions generic templates skip: who calls the brand, and who pays.
Why most recall plans fail at 2 a.m.
Walk into most $2-15M plants and ask for the recall plan. You get a 40-page section of the food safety binder, written for an auditor, last touched at recertification. It names a coordinator who quit in March. The customer contact list lives in a spreadsheet one person can find. That plan passes audits. It doesn't survive contact with an actual event.
The regulatory floor is real. FDA's recall plan requirements live in 21 CFR 117.139: if your hazard analysis identifies a hazard requiring a preventive control — in a co-packing plant, it almost always does — you need a written plan covering consignee notification, public notification when appropriate, effectiveness checks, and disposition of recovered product. And if there's a reasonable probability your product will cause serious health consequences, the Reportable Food Registry gives you 24 hours to file. Not 24 business hours.
So the floor is written down. The gap is operational: nobody assigned the roles, nobody rehearsed, nobody decided the money questions. That's what the rest of this covers.
What a food recall plan template needs on page one
Page one is the whole game. If your team can't run the first four hours from a single laminated sheet, the other 39 pages don't matter. That sheet has five blocks:
- Recall coordinator. A name, a backup, both cell numbers. Not a title — a person. Titles don't answer phones.
- Traceability lead. Whoever pulls lot records, receiving logs, and shipping docs fastest. Usually your QA manager. Name the backup too.
- One voice out. A single person authorized to talk to the brand, FDA, and anyone with a press badge. Everyone else says "I'll connect you with our coordinator" and stops talking.
- Hold authority. Who can stop the line and freeze inventory without asking permission. If that person needs approval first, your plan has a two-hour hole in it.
- The contact block. Your FDA district office, every active brand's recall contact, your insurer, your lawyer, your lab. Verified quarterly — people quit, numbers die.
Print it. Laminate it. Post it in the QA office and the production office. A plan that lives only on the server fails the night the server password changes.
The 4-hour traceability standard
Here's the bar: pick any lot code and, within four hours, produce every ingredient lot that went into it, every supplier those came from, and every case you shipped and to whom — reconciled to 100%. Auditors call it a traceability exercise, and in food manufacturing the passing grade is exactly that: four hours, full reconciliation. BRCGS makes the four hours explicit. SQF auditors expect the same neighborhood. Brands running their own supplier audits will time you with a phone out.
And 99% is a fail. The missing 1% is a pallet — in a distributor's warehouse or already on a shelf. Mass balance means produced equals shipped plus inventory plus waste, down to the case. If the math doesn't close, your trace isn't done. It's just stopped.
One more clock worth knowing: FDA's Food Traceability Rule (FSMA 204) adds recordkeeping requirements for higher-risk foods, with compliance pushed to July 2028. If you run sauces with fresh herbs, cut produce, or soft cheese, it's aimed at you. Build four-hour capability now and 2028 becomes a paperwork exercise instead of a systems rebuild.
Run a mock recall procedure twice a year — with real lot codes
Your certification scheme requires a mock recall at least annually. Do it twice. People leave, products change, and a drill from 11 months ago proves nothing about the team you have now.
A mock recall procedure that means anything uses real lot codes and real records — not a tabletop with invented numbers. Rotate three scenarios:
- Trace back. A supplier flags a suspect ingredient lot. Find every finished lot it touched and where they went.
- Trace forward. A complaint names a lot code on a shelf. Work forward to every consignee.
- After hours. Run the phone tree at 7 a.m. on a Saturday. Time how long until every page-one role answers. This is the drill that finds the dead numbers.
Score every drill the same way: minutes to 100% reconciliation, gaps found, corrective actions with owners and dates. Keep the scoresheets — auditors ask for them, and they're among the first documents pulled in food safety audit prep. A drill without a written score is a fire drill where nobody checks whether the building emptied.
Who calls the brand — the part no template covers
Generic guides are written for brands recalling their own product. You're a co-packer. Your name isn't on the package — theirs is. In the market it's their recall, but the trigger might be your environmental positive, your metal-detector gap, your supplier's notice. That split is where the 2 a.m. chaos lives, and it's the piece a recall plan for co-packers has to add.
The rule: the brand hears it from you first. Never from FDA, never from a retailer, never from a reporter. Even when the picture is incomplete — especially then. The call is short: what we know, what we don't, when you'll hear from us next. Then keep that update schedule like a production schedule.
Notification timing shouldn't be a judgment call made on adrenaline. Hours-to-notify, who notifies, and what triggers notification belong in writing before you run the first lot — they're standard clauses in a well-built co-packing agreement. The 24-hour reportable-food clock doesn't pause while you and the brand argue about who files.
It's also a sales asset. Brands vet recall readiness before they sign — it's one of the questions that comes up constantly in the outbound conversations we run for co-packers at Feed The Line. A one-page plan and two scored drills a year answer it in thirty seconds. "We'd have to check with QA" also answers it, in the wrong direction.
Who pays for what — decided before, not during
The most expensive sentence in a recall is "we'll sort out costs later." Later, everyone has lawyers. Decide the money before the first production run:
| Cost | Who typically pays | Where it's decided |
|---|---|---|
| Replacing recalled product | Whoever caused it — your process failure vs. their formula or label | Co-packing agreement |
| Retrieval, freight, destruction | Fault-based; often shared when the cause is murky | Co-packing agreement |
| Brand's lost sales, retailer fines | Usually capped or excluded for the co-packer | Limitation-of-liability clause |
| Lab testing during the investigation | Whoever orders the test | Agreement — or an email you'll wish existed |
| Your stopped line and idle crew | You, almost always | Nowhere. Plan for it yourself. |
Then check your insurance, because this is where owners get surprised: general liability covers bodily injury caused by your product. It does not cover the cost of pulling product back. Recall coverage is a separate line, and plenty of $2-15M plants don't carry it — what it costs and what it actually pays is covered in our breakdown of co-packer liability insurance.
Direct costs on even a contained Class II event — retrieval, destruction, testing, replacement — can run from tens of thousands into the mid-six figures before anyone's lost sales enter the math. A Class I riding a brand's national distribution goes to seven figures fast. Whether that lands on you, the brand, or an insurer was decided months earlier, in a clause somebody either wrote or didn't.
Build it this month
None of this needs a consultant or new software. It needs about a day. Write the one-page sheet — names, backups, cells, hold authority, contact block. Put a mock recall on the calendar inside 30 days and score it against the 4-hour standard. Then pull your co-packing agreements and read the recall clauses; if notification timing and cost allocation aren't in there, that's your next brand conversation — a far easier one to have now than at 2 a.m. with a lot on hold.
Frequently asked questions
Q-01What does FDA require in a food recall plan?
If your hazard analysis identifies a hazard requiring a preventive control, 21 CFR 117.139 requires a written recall plan covering consignee notification, public notification when appropriate, effectiveness checks, and disposition of recalled product. Separately, the Reportable Food Registry gives you 24 hours to report a product with a reasonable probability of causing serious health consequences.
Q-02How often should a co-packer run a mock recall?
SQF and BRCGS require a traceability exercise at least annually, but twice a year is the practical standard for co-packers because staff and products turn over. Use real lot codes, trace both directions, and score the drill: 100% reconciliation within four hours is a pass, anything less becomes a documented corrective action.
Q-03Who pays for a recall when a co-packer made the product?
It depends on root cause and on what the co-packing agreement says — process failures typically land on the co-packer, formula and label issues on the brand, with lost sales usually capped or excluded. General liability insurance doesn't cover recall retrieval costs; that takes separate product recall coverage. Decide all of it in the contract before production, not during the event.
Written by
Murtaza Udaypurwala
Founder, Feed The Line · Director, DESENO Media Agency
Murtaza runs Feed The Line, the outbound revenue engine that fills co-packer lines with qualified CPG brands. He writes about capacity economics, MOQ math, and pipeline for food & beverage plant owners.
DESENO ↗
