A critical limit is the line at a critical control point between safe and not safe: a number you can measure, with a pass on one side and a fail on the other. "Cook chicken to 165°F" is a critical limit. "Cook thoroughly" isn't, because nobody can check it. For a restaurant or retail kitchen in the United States, most limits don't have to be invented. They're in the FDA Food Code: 165°F for poultry, 155°F for ground meat, 145°F for fish and whole cuts, 135°F hot, 41°F cold, two hours and six hours for cooling. Below is the full table with the section each number comes from, what makes a limit a good one, and a file.
The short version
- A critical limit is measurable: a temperature, a time, a pH, a date.
- It has a source: a code section, a regulation, or a validation of your own process.
- Cooking: 145°F, 155°F or 165°F, by food.
- Holding: 135°F or above, or 41°F or below.
- Cooling: 135°F to 70°F in 2 hours; to 41°F in 6 in all.
- Your own limit can be stricter than the code's. It can't be looser.
- TaroStack holds each batch's readings on its record. More below.
The table
| Control point | Critical limit | Food Code 2026 |
|---|---|---|
| Cooking: fish, whole cuts of meat, eggs for immediate service | 145°F or above for 15 seconds | 3-401.11(A)(1) |
| Cooking: ground and other non-intact meats, eggs to be held | 155°F for 17 seconds, or 158°F instantaneous | 3-401.11(A)(2) |
| Cooking: poultry, stuffed foods, stuffing with meat | 165°F or above, instantaneous | 3-401.11(A)(3) |
| Hot holding | 135°F or above | 3-501.16 |
| Cold holding | 41°F or below | 3-501.16 |
| Cooling cooked food | 135°F to 70°F within 2 hours; to 41°F or below within 6 hours in all | 3-501.14 |
| Reheating for hot holding | 165°F for 15 seconds | 3-403.11 |
| Receiving refrigerated food | 41°F or below | 3-202.11 |
| Ready-to-eat food held more than 24 hours | Date marked; 7 days at most at 41°F or below, the day made counted as day 1 | 3-501.17 |
| Time used in place of temperature | 4 hours from leaving temperature control, marked, under written procedures | 3-501.19 |
| Vacuum-packed food, no variance | 41°F or below with a second barrier; 30 days at most from packing | 3-502.12 |
| Sous vide and cook-chill bags | 7 days at 41°F, or 30 days at 34°F | 3-502.12(D) |
| Fish served raw: freezing for parasites | -4°F or below for 7 days, or -31°F until solid and held 15 hours | 3-402.11 |
| Acidified sushi rice held without refrigeration | pH 4.2 or below | Annex 6 |
One from outside the Food Code, for makers of packaged acidified foods such as pickles and salsa: a finished equilibrium pH of 4.6 or lower, under 21 CFR 114.80.
Whole roasts have their own chart of lower temperatures held for longer times, in 3-401.11(B), and the code has exceptions this table leaves out. Read the section before you rely on a row.
What makes a good critical limit
| A good limit | Example | Not this |
|---|---|---|
| Is a number | 165°F | "Cooked through" |
| Can be measured on the spot | A probe reading | A lab test that comes back in three days |
| Says which side is safe | "41°F or below" | "Around 40°F" |
| Has a source | Food Code 3-501.14 | "What we've always done" |
| Includes time where time matters | "Within 2 hours" | "Cool quickly" |
Critical limit and operating limit
Kitchens that never miss usually aim past the limit. The code says 165°F for chicken, and the cook pulls it at 170°F. The 165°F is the critical limit: miss it and the corrective action in the plan applies. The 170°F is an operating limit: miss it and you adjust, with nothing to throw away. Write both down, and be clear which is which. If the plan itself says 170°F is the critical limit, then 168°F is a deviation you have to act on and record.
When no rule gives the number
Plenty of control points have no number in any code: the roast on cocoa beans, the sensitivity of a metal detector, the pH of a final rinse, the salt in a ferment. There the limit comes from your own process, and it has to be shown to work. That's validation, and a record for it is in HACCP validation template.
A limit needs three things beside it
A limit on its own controls nothing. In the plan, each one sits in a row with:
Monitoring. Who measures, with what, how often. "Cook probes the center of each batch."
A corrective action. What happens when it's missed. "Keep cooking." "Reheat once to 165°F and cool again, or discard."
A record. The reading itself, written down, with the time and initials.
Worked rows are in HACCP plan template for a restaurant, and the cooling limit, with what to do on a miss, in critical limits for cooling.
Your state or county may use an older edition of the Food Code or its own figures; FDA's adoption page showed 14 states on the 2022 edition when I read it. This is general information, not legal advice. Your health department has the last word.
Get the table
Download the critical limits table. The fifteen rows above with their sources, a column for your own limit where it's stricter, and a read-me. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. Print it for the wall by the pass.
Where this stops working
A table on the wall says 41°F. It doesn't know that the reach-in read 44°F at two o'clock, or which batches were in it. Limits are only as good as the readings taken against them, and readings on a clipboard don't follow the food.
How TaroStack does it
TaroStack puts the readings on the batch they describe.
Each thing you make is a batch. Record it and it has a lot code, a date and a use-by.
Your readings are fields on the batch. Cooking temperature, the two cooling readings, pH, initials: you choose the fields, and each recipe's batch-record form prints with its own.
On hold until it passes. A batch on hold is kept out of what's available until someone releases it.
Dates count themselves. Each lot carries its use-by, the oldest is used first, and an alert flags lots close to their date.
| The job | Wall chart and clipboard | In TaroStack |
|---|---|---|
| The reading for this batch | On a sheet, somewhere | On the batch record |
| A batch that hasn't been checked | Looks like any other | On hold |
| Seven days | Tape and a marker | A use-by on the lot |
| Which batches were in that cooler | Guess | Stock by lot and place |
TaroStack doesn't set a critical limit or take a temperature. 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.
