Receiving Deliveries: The Checks and the Record
The back door is a control point, whether you treat it like one or not. Every food delivery temperature check you skip is a gap in the cold chain you can't prove was safe. Here's what to check, what to send straight back, and the log that keeps an auditor off your back.
The delivery lands at 07:40, in the middle of prep, and the driver is already glancing at his watch because he has eleven more drops before lunch. That is exactly the moment food safety quietly falls over. Someone signs the docket, the crates go into the walk-in, and nobody put a probe near the chicken.
Receiving is the one control point where you can stop a problem before it enters the building. Once that box is on your shelf, its history belongs to you. If the chicken travelled at 9°C for two hours in a van with a dying fridge, you now own that risk — and you have no paper that says otherwise. This piece is about closing the door properly: the checks that take ninety seconds, the reject calls most chefs are too polite to make, and the record that turns "I'm pretty sure it was cold" into something an inspector will accept.
Why the door is a control point
Cook, chill and reheat get all the attention in HACCP plans because they involve fire and thermometers and drama. Receiving gets a shrug. But think about what's actually happening: product that has been out of your control — packed, loaded, driven, sometimes cross-docked — is crossing your threshold. You have no idea what happened between the supplier's chiller and your door unless you check. The whole cold chain up to this instant is a black box, and the receiving check is the only window you get into it.
The US FDA Food Code treats time and temperature control for safety (TCS) foods at receipt as an explicit requirement: refrigerated TCS food must arrive at 41°F (5°C) or below, and the operator has to be able to demonstrate it. You can read the model rule and the reasoning behind it in the US FDA Food Code, which most state and local codes adopt with minor edits. In the UK and Australia the temperatures are framed slightly differently — the UK FSA works to an 8°C legal maximum for chilled storage but good practice targets 5°C, and the same principle holds everywhere: cold food arrives cold, or it doesn't come in.
The checks, in the order you actually do them
You don't have all morning. The trick is a fixed sequence that hits the high-risk stuff first, so if you have to stop after thirty seconds you've already caught the thing most likely to hurt someone.
1. Temperature — chilled and frozen, probed properly
This is the check people fake. A probe laid on top of a shrink-wrapped tray reads the surface, which warms and cools fast and tells you almost nothing. You want the temperature between two packs, or — for an opened case — the core of the product. A clean, sanitised probe, inserted, given three or four seconds to settle.
Frozen product should be hard through and through. Soft edges, a block of what was clearly loose peas now welded into one lump, ice crystals on the inside of the bag — that's a product that thawed and refroze somewhere along the line. It may be at −18°C right now, but it wasn't an hour ago, and refrozen product is both a quality write-off and a safety flag. Reject it.
Between the sanitising wipes, one probe reading per high-risk line, and writing the number down, a proper temperature check on a mixed chilled and frozen delivery runs about ninety seconds to two minutes. That is the entire cost of the most important thing you'll do all morning.
2. Packaging integrity
Torn vacuum packs. A swollen pouch (gas from bacterial growth — this is a hard reject, no discussion). Dented cans, especially seam dents or any dent you can catch a fingernail in. Leaking cartons, weeping trays of raw meat that have dripped onto the produce below them in the same crate. Damaged packaging isn't cosmetic; it's a broken barrier between your food and whatever was in the van.
3. Dates and rotation
Check the use-by and best-before on what's arriving, not just that they exist. A delivery of yoghurt with two days of life left is useless if you use it over a week. This is also where you catch the supplier quietly clearing short-dated stock onto you. If the date won't survive your normal usage cycle, it goes back.
4. Pest signs and general condition
Gnaw marks on cardboard, droppings in the bottom of a crate, a moth in a flour sack, live or dead insects in produce. Rare, but when you see it you reject the whole affected consignment and you tell the supplier in writing — because if it's in your delivery, it's in their store.
5. Vehicle and driver
Glance into the van. Is the refrigeration actually running or is it a dry box with a chill blanket over the pallet? Are raw and ready-to-eat stacked together with raw on top? Is the load bay filthy? You're allowed to note this and, in a bad case, refuse. A driver who props the doors open at every drop is undoing the cold chain one stop at a time.
| What you find | Call |
|---|---|
| Chilled TCS food at 6–8°C | Borderline — reject or use immediately with a noted corrective action; never store as normal |
| Chilled TCS food above 8°C | Reject |
| Frozen soft / refrozen / heavy ice crystals | Reject |
| Swollen pouch or blown can | Reject, isolate, tell supplier |
| Seam-dented can | Reject |
| Short date that won't survive usage | Reject |
| Pest evidence | Reject whole affected consignment, report in writing |
| Raw dripping onto ready-to-eat in the van | Reject the contaminated items |
The 6–8°C row is where judgement lives. A single line at 6°C on a hot day, when the rest of the load is at 4°C, is often a probe-and-pack quirk you can manage by using it first and logging why. A whole chilled load at 7°C is a failed van, and you send the lot back. The difference is pattern: one warm pack is noise, a warm load is a failure.
The receiving log: what goes in it and why an auditor cares
Here is the uncomfortable truth about receiving food safety: if you didn't write it down, you didn't do it. An inspector standing in your kitchen next Tuesday cannot see the probe reading you took last Thursday. The receiving log is the only evidence that the goods in check happened at all, and a log with honest gaps and the odd rejection in it is far more credible than a suspiciously perfect one.
A working receiving log needs these fields:
| Field | Why it's there |
|---|---|
| Date & time | Ties the reading to the delivery and to who was on shift |
| Supplier | Traceability — lets you trace a recall or a repeat offender |
| Delivery / product | What was checked, so a blanket "all fine" can't hide one bad line |
| Temperature read | The actual probe number, chilled and frozen — the core evidence |
| Condition OK? (Y/N) | Packaging, dates, pest, vehicle — the non-temperature checks in one call |
| Accepted / rejected | Proves you act on what you find, not just record it |
| Corrective action / note | What you did when something failed — the field auditors read first |
| Checked by (initials) | Accountability; names a person to the decision |
The field auditors care about most is not the temperature — it's the corrective action. A log full of "42°F, accepted, AK" tells them the readings were taken. A single line reading "chicken 7°C, rejected, driver took back, supplier informed, AK" tells them your system works under stress. That one rejection is worth more to your audit than a hundred clean lines, because it's the only proof that when the process found a problem, a human acted on it. Auditors trust systems that visibly catch failures. They're suspicious of systems that never seem to.
Keep the log for the retention period your local code sets — commonly the shelf life of the product plus a margin, and often a fixed period such as three months or longer for the paperwork itself. When in doubt, keep it longer; the storage is free and the peace of mind isn't.
In ProChefDesk
The HACCP receiving log gives you exactly these fields on a phone at the back door — date, supplier, delivery temperature, a condition-OK toggle and a note box for the corrective action. It runs the temperature against your region's threshold and marks the line pass or fail for you, so a delivery over 5°C flags itself. No clipboard, no transcribing a soggy sheet into a folder at the end of the week.
A workflow that survives a busy back door
The reason receiving checks get skipped is friction. Any system that assumes you have a calm five minutes and a clean pen will fail at 07:40. Design for the real morning instead.
- Probe in your apron, sanitising wipes by the door. If the tool isn't within arm's reach, the check doesn't happen. Keep a dedicated receiving probe so you're not hunting for the one from the sauce station.
- Highest-risk line first. Poultry, raw meat, seafood, dairy — the TCS foods. Probe those before you even look at the dry goods. If the driver has to leave, you've measured what matters.
- Log at the door, not later. "I'll write it up after prep" means it never gets written, or gets written from memory, which is worthless as evidence. Enter the number while the crate is still in front of you.
- Reject at the door too. Once it's on your shelf, sending it back becomes a phone call, a credit note and an argument. At the door it's just a crate that goes back on the van. Make the call before you sign.
- Sign the docket last. Your signature is you accepting the goods in their current condition. Don't sign until you've decided what you're keeping.
One more habit worth building: cross-check the delivery against what you actually ordered before it leaves the van. A short-delivered line or a substituted item you didn't approve is easiest to sort out while the driver is still standing there. It's not strictly a safety check, but it lives in the same ninety seconds and saves the mid-service discovery that you're two cases short.
The honest summary
Receiving is ninety seconds of work that most chefs treat as zero seconds of work, and it's the cheapest food safety win in the building. You cannot fix at the pass what walked in broken at the door. Probe the chilled at 5°C, the frozen at −18°C, look at the packaging and the dates and the van, and reject without apology when something's wrong.
Then write it down. Not because the log makes the food safer — the checking does that — but because the log is the only thing that proves, weeks later, to an inspector or an insurer or your own worried self at 3am, that the cold chain didn't break on your watch. The chef who can put a finger on Thursday's line and say "here, I checked, it was 4°C, I signed" sleeps better than the one who's pretty sure it was fine.
"The delivery I remember best is the one I sent back. Everyone watched me do it. Nobody argued with a temperature check on that dock again."
Make the reject once, in front of your team, and the standard sets itself. That's worth more than any policy on the wall.