The FDA Food Code sets two critical limits for cooling cooked food that needs temperature control. It must go from 135°F to 70°F within two hours, and from 135°F to 41°F or less within a total of six hours. The first stage is the tight one, because bacteria grow fastest between 135°F and 70°F. Food made from room-temperature ingredients, like tuna salad from canned tuna, has four hours to reach 41°F. A cooling log records the time the food hit 135°F, its temperature at two hours and at six, and what you did if it missed. Here are the limits, a log with a failure in it, and the file.
The short version
- Stage one: 135°F to 70°F within 2 hours.
- Total: 135°F to 41°F or less within 6 hours.
- Start the clock when the food reaches 135°F, not when it leaves the stove.
- Pots don't cool in a walk-in. Use shallow pans, ice baths, ice wands, smaller batches.
- TaroStack holds the two readings on the batch record and dates the batch. More below.
The limits
| Food Code limit (3-501.14) | |
|---|---|
| Cooked food, stage one | 135°F to 70°F within 2 hours |
| Cooked food, in all | 135°F to 41°F or less within 6 hours |
| Food made from ambient-temperature ingredients | To 41°F or less within 4 hours |
If the food reaches 70°F in one hour, it still has until the six-hour mark to reach 41°F. The total is what counts.
A log with a miss
| Food | Method | Start (135°F) | At 2 hours | Check | At 6 hours | Check |
|---|---|---|---|---|---|---|
| Chicken chili, in bags | Ice bath | 10:40 AM | 66°F | OK | 39°F | OK |
| Rice, two hotel pans | 2-inch pans, walk-in | 1:15 PM | 68°F | OK | 40°F | OK |
| Beef stock, 5 gallons | Stockpot in the walk-in | 2:00 PM | 96°F | REHEAT OR DISCARD | ||
| Beef stock, restarted | 2-inch pans over ice | 4:10 PM | 61°F | OK | 38°F | OK |
The stock is the classic failure. Five gallons in a pot, lid on, in the walk-in: two hours later the center is 96°F. The cook reheated it to 165°F, split it into three shallow pans over ice, and started a new row. The restart made its numbers easily.
What to do when a batch misses
The code sets the limits. It doesn't spell out a corrective action in this section, so your own procedure has to, and your health department may have a view. A common one, used in the log above:
| Missed | This kitchen's rule |
|---|---|
| The 2-hour mark | Reheat to 165°F once, then cool again by a faster method. If it misses again, discard |
| The 6-hour mark | Discard |
| Unknown times (nobody logged it) | Discard |
Reheating once is a second chance, not a routine. A food that keeps missing needs a different method.
Methods that work
| Method | Why it works |
|---|---|
| Shallow pans, 2 inches deep | Heat leaves from the surface; depth is the enemy |
| Ice bath, stirred | Water pulls heat far faster than air |
| Ice wand, or ice as an ingredient | Cools from the inside; make the soup thick and finish with ice |
| Smaller containers | Five 1-gallon bags cool; one 5-gallon bucket doesn't |
| Blast chiller | If you cool large amounts daily |
| Leave it uncovered or loosely covered until cold | A tight lid holds the heat in |
A walk-in is built to keep cold food cold, not to pull heat out of 40 pounds of stock. Putting a hot pot in it mostly warms everything else.
Cooling is a critical control point in any plan with a cook-chill step: see HACCP plan template for a restaurant and HACCP plan for catering. Holding temperatures are in hot and cold holding temperatures. 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 log
Download the cooling log. One row a batch; the two checks work themselves out and say OK, REHEAT OR DISCARD, or DISCARD. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The two-hour reading falls in the middle of service. The cook who started the batch has gone home by the six-hour mark. The log has a start time and two blanks, and nobody can say whether the stock in the walk-in made it.
How TaroStack does it
TaroStack keeps the batch out of use until its readings are in.
Each batch you cool is a batch on record. Soup, stock, rice, braises: a recipe each. Record it and it has a lot, a date and a use-by.
The cooling checks are fields on the batch. Start time, two-hour and six-hour temperatures, initials: fields of your own, on the batch-record form.
On hold until it passes. Put a new batch on hold. It's out of what's available until someone enters the six-hour reading and releases it. A batch nobody checked stays held.
Discards have a reason. Throwing a batch away is an adjustment with a reason, so cooling failures show up in the waste report, in dollars.
| The job | Clipboard | In TaroStack |
|---|---|---|
| The two readings | Blanks, on a busy day | Fields on the batch record |
| A batch not yet checked | Looks like any other | On hold |
| How long it's good for | A date on tape | A use-by on the lot |
| What failed cooling cost | Unknown | Waste by reason |
TaroStack doesn't take the temperatures or set your procedures. 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.
