What are safe cooking and reheating temperatures?

Safe cooking temperatures are the minimum internal temperatures the FDA Food Code requires before time/temperature control for safety (TCS) food can leave the cook step: 145°F for whole-muscle beef, pork, lamb, and veal, 155°F for ground and mechanically tenderized meats, and 165°F for poultry, stuffed items, and anything reheated for hot holding.

Reheating runs on its own clock. Food must hit 165°F within 2 hours of the reheat starting.

Multi-unit chains that pair line checks with Bluetooth thermometers, Dave's Hot Chicken runs them across walk-ins, hot-holds, and line stations at 321 locations, treat the cook-temp reading as the first data point in the same corrective action chain that catches a bad walk-in temp later in the day.

The stakes behind these numbers are not abstract. The CDC estimates 1 in 6 Americans, about 48 million people, get sick from foodborne illness every year, with 128,000 hospitalized and 3,000 deaths. Cooking is the one control point in the chain designed to bring that risk down to near zero before food ever reaches a guest.

Cooking is the kill step in the food safety chain. Three things separate it from every other control point between receiving and service, and this distinction is the piece a lot of temp-log content skips:

Treating "temp check" as one undifferentiated task loses the distinction a health inspector actually cares about. A cook-temp failure means the food was never safe to begin with. A hold-temp or cool-temp failure means safe food was allowed to become unsafe afterward.

The corrective action is different in each case, and the audit trail a kitchen needs to produce is different too. Thawing, the control point right before cooking, matters here as well. An undercooked reading is sometimes a thawing problem in disguise, a partially frozen center that never reaches the probe's read temperature. See safe food thawing procedures for the control point that sits just upstream of the cook step.

The FDA Food Code, Chapter 3 sets the numbers for cook, hold, cool, and thaw in one place.

Regulatory framework

The cook step is governed by FDA Food Code §3-401.11 (minimum cooking temperatures), the reheat step by §3-403.11 (reheating for hot holding), and both sit inside HACCP Principle 3, Establish Critical Limits, the part of the food safety framework that turns "cook it well" into a measurable, auditable number.

Common mistake worth flagging: the USDA consumer chart tells home cooks to hit 160°F on ground beef, with a rest period noted for whole-muscle roasts. That's consumer guidance.

The FDA Food Code, the standard a restaurant, c-store hot case, or hotel kitchen actually gets inspected against, sets ground meat at 155°F for 15 seconds and whole-muscle roasts at 145°F for 4 minutes. A kitchen manager training staff off the USDA consumer chart alone is training the team to the wrong number for a health inspection.

Minimum internal temperatures by food type, and the 165°F reheating rule

FDA Food Code §3-401.11 sets three temperature and time tiers for cooking, and §3-403.11 sets one fixed rule for reheating: 165°F within 2 hours, no exceptions for previously-cooked TCS food headed back into hot holding.

| Food category | Minimum internal temp | Hold time |
|---|---|---|
| Poultry (whole, ground, parts), stuffing made with fish, meat, or poultry, stuffed meat, seafood, poultry, or pasta | 165°F (74°C) | 15 seconds |
| Food reheated for hot holding (previously cooked and cooled) | 165°F (74°C) | 15 seconds, within 2 hours of starting reheat |
| Ground meat (beef, pork, other), injected or brined meat, mechanically tenderized meat, ratites, ground seafood, shell eggs held for service | 155°F (68°C) | 15 seconds |
| Whole-muscle beef, pork, lamb, veal steaks and chops, seafood, commercially raised game, shell eggs served immediately | 145°F (63°C) | 15 seconds |
| Roasts (whole-muscle beef, pork, lamb, veal) | 145°F (63°C) | 4 minutes |
| Commercially processed, packaged ready-to-eat TCS food (hot holding only, no reheat-to-165 required) | 135°F (57°C) | N/A |

Microwave reheating is its own line item. §3-403.11 requires food reheated in a microwave for hot holding to hit 165°F, get rotated or stirred, stay covered, and stand covered for 2 minutes after heating. The standing time is part of the rule, not a suggestion.

A QSR kitchen manager checking a batch of fried chicken tenders probes the thickest piece in the fryer basket, not the thinnest. The thinnest piece always reads hotter and can mask an undercooked piece elsewhere in the same batch.

A c-store running a roller grill or hot case is usually holding food rather than cooking it fresh on site, but wherever the format does include an on-site cook step, fresh-cooked chicken or breakfast sandwiches, the same 155°F and 165°F thresholds apply before the item goes into the case.

‍NACS's food safety resources list failure to cook to the correct internal temperature as a top health-inspection violation at c-store foodservice counters, the same failure mode as a restaurant kitchen, just under forecourt vocabulary.

How does Xenia handle cooking and reheating temperature checks?

Xenia pairs a Bluetooth-enabled probe thermometer to a digital audit or daily-ops checklist so the cook or reheat reading logs automatically with a timestamp. An out-of-range reading triggers a follow-up question, a required photo, and a corrective task, instead of a number written on a clipboard that nobody checks until the health inspector asks for it.

A cook-temp check is a point-in-time verification, not a continuous monitor. The line cook or kitchen manager inserts the probe into the thickest part of the batch, and the app captures that single reading the moment it's taken, with a timestamp the person taking it can't edit after the fact.

That's a different workflow than a walk-in cooler probe, which reads at fixed intervals whether anyone is standing there or not. Xenia's Bluetooth thermometer integration supports both patterns, but they stay separate.

A cook check is one reading per batch, taken by a person, at the moment of cooking. A hold check is a logged interval reading from a probe that stays in place. Line checks, walk-in temps, and hot-hold monitoring all roll into the same compliance-ready trail instead of a binder that gets filled in after the fact.

What happens when a cook temp reads under the minimum:

One guardrail worth stating plainly: the probe reading is a person-taken measurement that Xenia logs and timestamps. The platform doesn't verify doneness itself, doesn't interpret the photo evidence attached to a corrective action, and doesn't stream temperatures continuously. Dave's Hot Chicken's walk-in and hot-hold probes log at 15-minute intervals, not continuously.

A cook-temp check is even more discrete, a single reading captured at the moment the cook or line lead takes it. Bluetooth integration also works with supported probe hardware. It isn't universal across every thermometer brand on the market, so confirm compatibility before the rollout.

Weighted audit scoring plays into this too.

A missed cook temp is a critical food safety item, not a cosmetic one. The weighted audit scoring approach that separates a 10-point temp failure from a 1-point cosmetic issue is what let Dave's Hot Chicken finally see which locations needed a DM visit and which didn't, after switching from RizePoint, where a temperature failure and a missing patio chair landed as the same point deduction.

|  | Clipboard / manual log | Bluetooth-paired probe (Xenia) |
|---|---|---|
| Who enters the number | Line cook writes it by hand | Probe reading auto-logs with a timestamp |
| Editable after the fact | Yes, numbers get pencil-whipped to pass | No, the logged reading is the reading the probe took |
| Out-of-range response | Depends on whether anyone reviews the sheet | Automatic follow-up question, required photo, and corrective task |
| Escalation if uncorrected | Manual, if it happens at all | Automatic escalation to the DM on a missed deadline |
| Audit trail for a health inspector | A binder, if it wasn't lost or filled in later | Timestamped digital record tied to the corrective action |

Where do operators see results?

Cook and reheat temperature results surface on the location dashboard as open corrective actions and flagged items, not as a completion percentage. A multi-unit ops director's morning view is "what's failing right now," not "did yesterday's checklist get done."

This is the same "issues view, not completion view" pattern that shows up across Xenia's multi-unit restaurant task management customers. Operators running 50-plus locations care less about a compliance percentage on a dashboard and more about what's about to become a problem.

A cook-temp failure that auto-creates a task and escalates on a missed deadline is exactly that kind of forward-looking signal.

Dave's Hot Chicken is the clearest example at scale. The chain runs Bluetooth thermometers across walk-ins, hot-holds, and line stations at 321 locations, after leaving RizePoint, where audit scoring couldn't tell a temperature failure from a cosmetic issue.

Out-of-range readings now trigger a follow-up question and a photo requirement, and the corrective action workflow assigns a task with a deadline that escalates to the DM if it isn't closed. For a deeper look at how the temp data rolls into a single compliance record, see HACCP-aligned temperature logs and the food safety operations hub for the rest of the receive-to-reheat chain.

How to set up cook-and-reheat temperature checks in Xenia

Setting up a cook-and-reheat temperature check in Xenia means pairing a Bluetooth probe, adding the cook-temp question to the relevant audit or daily-ops checklist, and configuring the out-of-range follow-up and corrective action rule. It's a one-time setup per station.

1. Pair the Bluetooth probe thermometer to the Xenia app on the kitchen tablet, per station or per line, depending on kitchen layout.
2. Add the cook-temp or reheat-temp question to the relevant checklist, line check, opening or closing audit, or a standalone temp-log form, and set the minimum threshold: 145°F, 155°F, or 165°F depending on the food category.
3. Set the follow-up question and required photo to trigger automatically when a reading logs below threshold: what did you find, and what corrective action did you take, plus a photo of the corrective action taken.
4. Assign the corrective task to the kitchen manager or shift lead, with a deadline. Dave's Hot Chicken uses a 24-hour window on its Bluetooth-triggered corrective tasks.
5. Set the DM escalation rule so an unresolved corrective task automatically routes up if the deadline passes.
6. Test on one station or one location before rolling the same checklist template out chain-wide.

The same checklist template that captures cook temps can capture reheat temps at a different station too. There's no need for a separate app or a separate template for each control point in the chain.