Catering adds two things to a restaurant's risks: time and distance. Food is cooked hours ahead, sometimes cooled and reheated, driven across town and held on a buffet. A catering HACCP plan follows the food through that journey and puts a control at each point where temperature can slip: cooking, cooling, reheating, and transport and holding. The limits are the FDA Food Code's: cook to the temperature for the food, cool from 135°F to 70°F in two hours and to 41°F in six, reheat to 165°F, and hold hot food at 135°F or above and cold food at 41°F or below. Here's a plan, an event's log and a worksheet.
The short version
- Four control points: cooking, cooling, reheating, and transport and holding.
- Take temperatures when food is loaded, when it arrives, and every two hours of service.
- Decide in advance what happens when a pan reads low. Write it in the plan.
- Label the buffet for allergens.
- TaroStack keeps each event's batches with their readings, and the lots that went into them. More below.
The limits
| Step | Food Code limit |
|---|---|
| Cooking | Poultry and stuffed foods 165°F; ground meats 155°F for 17 seconds; fish and whole cuts of meat 145°F for 15 seconds |
| Cooling | 135°F to 70°F within 2 hours, and to 41°F or less within a total of 6 hours |
| Reheating for hot holding | 165°F for 15 seconds |
| Hot holding | 135°F or above |
| Cold holding | 41°F or less |
A caterer generally doesn't need an approved HACCP plan for these ordinary steps. Venues, corporate clients and insurers ask for one anyway, and writing it is how you find the weak leg of the journey. If you vacuum pack, sous vide or cure, that part does need a plan filed with your health department: see HACCP plan template for a restaurant.
The plan
| CCP | Critical limit | Monitoring | If it's missed |
|---|---|---|---|
| 1. Cooking | The code's temperature for the food | Probe the center of two pans, each batch | Keep cooking |
| 2. Cooling (made ahead) | 70°F at 2 hours; 41°F at 6 hours in all | Probe at 2 and 6 hours | Reheat once and re-cool, or discard |
| 3. Reheating | 165°F for 15 seconds | Probe each pan | Keep heating |
| 4. Transport and holding | Hot 135°F or above; cold 41°F or below | Probe when loaded, on arrival, every 2 hours of service | This caterer's rule: hot food under 135°F for less than 4 hours is reheated to 165°F; otherwise discarded |
The corrective action in the last row is the example caterer's own procedure. Some codes also allow time alone as the control for a limited period, with the food marked and discarded at the end; that has its own rules, in time as a public health control.
An event's log
A made-up caterer, a 120-guest buffet, 40 minutes' drive:
| Time | Step | Reading | Limit | OK? | Action |
|---|---|---|---|---|---|
| 11:10 | Chicken cooked | 171°F | 165°F or above | Yes | |
| 3:20 | Loaded in the carrier | 158°F | 135°F or above | Yes | |
| 4:05 | Arrival | 149°F | 135°F or above | Yes | |
| 6:10 | Buffet, 2 hours in | 131°F | 135°F or above | No | Chafer fuel was out. Pan back to the warmer: 166°F in 12 minutes |
The food lost 9°F in the van, which is what a good insulated carrier does. It lost another 18°F on the buffet because a chafer ran dry. The log caught it at the two-hour check. Without the check, that pan sits at 120°F until the last guest leaves.
Your state's edition of the code may differ. This is general information, not legal advice; your health department has the last word.
Get the worksheet
Download the catering HACCP plan worksheet. Four sheets: the hazard analysis, the plan with a place to sign, a monitoring log that checks each reading against its limits, and a read-me. It's a worksheet to organize your own plan, not a plan to copy. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. What to pack is in catering inventory checklist.
Where this stops working
The log lives on a clipboard that goes to the event and often doesn't come back. Three events on a Saturday means three clipboards, three leads, and nobody at the kitchen who can say on Monday what the chicken read at the second venue.
How TaroStack does it
TaroStack keeps each event's food as batches with their own records.
Each dish for an event is a batch. Record it and the ingredients come off stock, with the lots noted automatically. If a supplier recalls a case of chicken, you know which events it went to.
Readings are fields on the batch. Cook temperature, load, arrival and service checks, with initials. The form prints for the clipboard, and what's entered stays with the batch.
The order holds the event. A sales order carries the client, the date and what was promised, and one picking list gathers everything going in the van.
The phone works in the venue's basement. Record on a phone with no signal; it sends itself later.
| The job | Clipboards | In TaroStack |
|---|---|---|
| Readings for an event | Paper, if it comes back | Fields on the batch record |
| Which chicken went where | Memory | Lots on each batch |
| What goes in the van | A list | A picking list |
| Proof for a venue | Find the sheet | The event's records |
TaroStack doesn't write your plan or take the temperatures. Recipes, batches and lots are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). 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.
