Your thermometer is telling you the wrong number

Here is the small, maddening thing about roasting. A thermometer can tell you both whether the roast has reached a safety minimum and how much farther it may climb while resting. Those are different jobs. USDA consumer guidance lists 165°F for poultry; 145°F plus at least a 3-minute rest for whole beef, pork, veal and lamb cuts; 160°F for ground beef, pork, veal and lamb; and 145°F for fish. A 130°F medium-rare rib roast is a culinary preference below that whole-cut minimum, and 140°F reheating applies only to certain fully cooked hams. Carryover matters, but it should not blur those distinctions.

Meat does not stop cooking when it leaves the oven. The outside of a roast is very much hotter than the middle, and heat moves from hot to cold until it runs out of gradient. So for the first stretch on the counter, the middle keeps climbing — and it is that climb, not the oven, that decides whether the thing you carve is pink or gray.

The useful number is not always a simple pull temperature. For a safety minimum, the thermometer should reach that minimum before the food leaves the heat. Carryover is then a forecast of likely overshoot. For culinary doneness preferences that are already above the applicable safety floor, carryover can help you decide how early to start checking, but it is never a fixed subtraction.

Carryover is not a fixed number

You will read “five to ten degrees” everywhere, which is true in the way that “a journey takes between ten minutes and four hours” is true. Carryover scales with two things, and once you know which two it stops being a mystery.

Mass. A big roast has more stored heat and a longer road to the middle, so it climbs further and for longer. A three-pound tenderloin has almost no reserve; a twenty-pound turkey has an enormous one.

How hot the oven was. A hot oven builds a steep gradient — a scorching outside and a cold center — and steep gradients keep driving heat inward after the door opens. A low oven builds a shallow one, so there is less left to move.

Put those together and you get a useful planning pattern, not a universal table. On this site’s current models, a three-pound beef tenderloin from a 425°F oven is estimated around a five-degree rise; a four-pound chicken roughly the same; a fourteen-pound turkey around seven; and an eight-pound rib roast from a 250°F oven around five. Those are house planning estimates, not validated constants. Actual carryover changes with shape, starting temperature, oven behavior, probe location and rest conditions.

Which is the actual argument for low-roasting

The case for cooking a rib roast at 250°F usually gets made on evenness — less gray band under the crust, more of the roast at the temperature you asked for. That is true and it is not the whole reason.

The rest of the reason is predictability. A low oven makes a shallow gradient, a shallow gradient makes small carryover, and small carryover means the number on the thermometer when you pull it is very close to the number you get. Roast the same cut at 425°F and it will climb ten or twelve degrees on the counter — which is fine if you predicted it exactly and a disaster if you were two minutes late reading the probe.

Low and slow is not a fussier technique. It is a more forgiving one, and it buys the forgiveness with time you were going to spend anyway.

The other thing nobody schedules

Resting gets treated as dead time. Stand around, make the gravy, wait. It is in fact the largest block of empty, hot, uninterrupted oven you will have all day, and it lands at precisely the moment when the potatoes want color, the rolls want fifteen minutes and the gratin wants a top.

Thirty-five minutes at 325°F and falling, free, arriving exactly on cue — and almost nobody plans anything into it, because the rest is filed mentally under waiting rather than under oven.

With one exception, and it is a cruel one. A rib roast cooked low wants the oven back at 500°F for ten minutes at the end of its rest to build the crust. So on the one night you have the most sides to finish, the window is not free at all — it is booked, at a temperature nothing else can share. That collision is why a rib-roast dinner runs late so reliably, and it is entirely predictable a week in advance.

So we built the clock

The Roast Clock does the scheduling arithmetic. Pick the roast, give it a weight and the moment you want it carved, and it works backwards: out of the fridge, oven on, in, thermometer target, rest, blast if it needs one, carve. The safety-controlled meats now reach the applicable minimum before removal; the carryover estimate is shown separately so you can anticipate texture and overshoot. It covers whole and spatchcocked turkey, a beef rib roast, tenderloin, roast chicken, a glazed ham and a whole side of salmon.

It is free and there is no sign-in. If the roast in question is a frozen turkey, the Thanksgiving Clock runs the days-long version of the same problem: buy by, thaw, salt, roast.

And when the roast is not the only thing in the oven — it never is — the Oven Traffic Calculator takes the whole menu, works backwards from the serve time and names the dish that is not going to make it.

One thermometer, checked early and read in the right place. Reach the applicable safety minimum before removal, then use carryover to predict how much farther the roast may travel while it rests. That is less dramatic than pulling by nerve, but considerably more defensible.

Part of Kitchen Systems.