Ask most kitchens which check they’re least confident about, and cooling comes up more than any other. Not because anyone’s careless with it — because it’s the one check that has to survive the busiest, most distracted part of service.
Why it slips
Cooking has a moment: you probe it, you record it, you’re done. Cooling doesn’t have a moment — it has a window. Something comes off the stove, gets covered, gets put aside “to cool down,” and the clock that matters starts the second it’s covered, not whenever someone next has a spare minute to think about it. On a busy night, that spare minute can be an hour and a half away, by which point the window’s already gone.
What the window actually is
Cooked food needs to pass through the temperature danger zone quickly — the accepted standard is getting it down within 90 minutes of cooking, with a single 30-minute extension if you’re genuinely still working on it, not routinely used to paper over a slow night. If it’s still not safely cool after that, it isn’t a technicality — it’s food that shouldn’t be kept.
Making it automatic
The reason cooling gets missed isn’t a knowledge gap — everyone knows the rule. It’s that nothing physically reminds you the clock is running. Rated5 starts a real timer the moment you log that something’s cooling, tracks the 90 minutes plus the one allowed extension, and if it’s still not safe when time’s up, it opens a proper record rather than letting the moment just quietly pass. The check stops depending on someone remembering to look at a clock mid-service.
The habit that actually works
Start the timer the second the pan comes off the heat, not after it’s already been sitting out. It costs nothing in the moment and it’s the difference between a check you can stand behind and one you’re guessing about after the fact.