Reheating is the step where food cooked yesterday passes back through the temperatures bacteria like, so the FDA Food Code puts two limits on it: how hot and how fast. Food that was cooked, cooled and is being reheated to hold hot has to reach 165°F for 15 seconds in all parts, and get there within two hours of leaving 41°F. A reheating log records both for each pan: the temperature reached and the minutes it took. It's a short log, and it catches a familiar way for reheating to go wrong: a steam table or a warmer used as a heater. Below are the rules with their sections, a day of a made-up cafe's log, and the file.
The short version
- Cooked, cooled food reheated for hot holding: 165°F for 15 seconds, in all parts.
- No more than two hours from 41°F to that temperature.
- In a microwave: 165°F, stirred or rotated, covered, and left covered two minutes.
- Packaged ready-to-eat food from an inspected plant: 135°F.
- Reheat on the stove or in the oven, then move to the warmer.
- Write the temperature reached and the minutes it took.
- TaroStack records each batch's checks on its own record. More below.
What the Food Code says
| Case | Rule | Section |
|---|---|---|
| Food cooked, cooled and reheated for hot holding | All parts reach at least 165°F for 15 seconds | 3-403.11(A) |
| Reheated in a microwave | At least 165°F in all parts; rotated or stirred, covered, and left to stand covered for two minutes | 3-403.11(B) |
| Ready-to-eat food commercially processed and packaged in an inspected plant | At least 135°F | 3-403.11(C) |
| How fast | Rapidly: no more than two hours between 41°F and the temperature required | 3-403.11(D) |
| After reheating | Held at 135°F or above | 3-501.16 |
The Food Code is a model. Your State or county adopts its own version, and that version has the last word.
The section's title says what it covers: reheating for hot holding, such as the pot of chili going back on the line for service.
A day's log
| Food | Start | Required | Reached | Minutes | OK? |
|---|---|---|---|---|---|
| Beef chili, made Nov 18 | 38°F | 165°F | 171°F | 45 | Yes |
| Pulled pork, made Nov 19 | 40°F | 165°F | 158°F | 130 | NO: act |
| Clam chowder, bought in a sealed bag | 39°F | 135°F | 150°F | 35 | Yes |
| Rice, made that morning | 41°F | 165°F | 168°F | 12 | Yes |
The chili went on the stove, was stirred, and passed 165°F in 45 minutes.
The pulled pork failed both tests. It went into the warmer cold, in a deep pan, and after 130 minutes it was at 158°F. It was discarded. Leaving it another twenty minutes would have reached the temperature and not fixed the time: the two hours had already gone.
The chowder is the case in paragraph (C). It was commercially made, came sealed from an inspected plant, and needs 135°F, not 165°F. A soup made in house needs 165°F.
The rice went through the microwave: stirred, covered, and left covered two minutes before it was probed.
Why the warmer isn't a heater
A steam table or a holding cabinet is built to keep hot food hot. In this cafe's log, a deep pan of cold pork spent 130 minutes in one and still fell short. So the routine in this cafe is: reheat on the stove or in the oven, in shallow pans or stirred pots, probe in two places, write the reading and the minutes, then move the food to the warmer. Probe the thickest part and the middle of the pan, because "all parts" is the rule.
What to do when it fails
- Under temperature with time left: keep heating on proper equipment, and probe again.
- Over two hours: this cafe discards it, and writes that down.
- Either way: write what was done and why it happened. A deep pan and the wrong equipment is a fix for tomorrow.
Reheating is the last of three linked steps. The cook is in critical limits for CCPs, cooling in critical limits for cooling with a cooling log template, and holding in temperature log template. How to write the monitoring into a plan is in HACCP monitoring procedures. This is general information, not legal advice.
Get the log
Download the reheating log. One sheet and a read-me: the food, its batch, the temperature required, the temperature reached and the minutes it took, with a column that marks a reheat that fell short or ran over two hours, and space for what was done. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The log says the pork made on the 19th was thrown away on the 20th. It doesn't say how much, what it cost, or that the same batch was also served on the 19th at dinner. Reheating is the third time that batch was probed, and the cook, the cooling and the reheat are on three clipboards.
How TaroStack does it
TaroStack keeps a batch's checks with the batch.
Each cook is a batch. Record it and its ingredients come off stock, by lot. The batch notes which lots it used, automatically.
Your checks are fields on the batch record: cook temperature, the cooling readings, the reheat.
Every batch is a lot with a date, and an alert comes before a use-by date arrives.
Every adjustment carries a reason. A pan written off as "reheat failed" is a quantity and a cost.
| The question | Three clipboards | In TaroStack |
|---|---|---|
| The cook and cooling readings for that pork | Find the sheets | On the batch record |
| How much was thrown away, and what it cost | Not written | The write-off, at cost |
| What else came from that batch | Unknown | The lot's history |
| What's past its date in the walk-in | Read the labels | An alert |
TaroStack isn't a thermometer, and it doesn't write your HACCP plan. 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.
