Steam Table Well Water Level and Hot Hold Temperature Log
Hourly steam table well log for checking water level, hot-hold temperature, corrective actions, and equipment condition for TCS food held at 135 °F or above.
Trusted by frontline teams 15 years of frontline software
Built for: Restaurants · Catering · Hospitality · Healthcare Food Service · Education Food Service
Overview
This template is a hourly log for steam table wells holding TCS food at or above 135 °F. It captures the specific checks that matter in practice: whether each well has enough water, whether the food temperature was verified with a calibrated probe, whether the equipment is functioning correctly, and what corrective action was taken if a reading falls out of range.
Use it when food stays in a steam table during service and you need a repeatable record for each well, not just a general shift note. It is especially useful for soup lines, sauces, gravies, vegetables, and other hot-held items that can drift below safe temperature if water runs low or the unit is not maintained. The log also helps the team separate blocking issues, such as a failed heating element or empty water pan, from non-blocking observations that still need attention.
Do not use this as a substitute for cooling, reheating, or cold-hold records. It is also not the right template for dry holding, buffet items outside a steam table, or one-time opening checks. If your operation does not hold food for an extended period, a simpler opening inspection may be enough. The value of this template is that it turns a routine food-safety expectation into a clear, well-by-well record that supports action during service and review after the shift.
Standards & compliance context
- This template supports hot-holding verification aligned with FDA Food Code § 3-501.16(A)(1) for TCS food held at or above 135 °F.
- A calibrated probe reading and documented corrective action help demonstrate active control during health inspections and internal audits.
- If local health rules require a different temperature threshold or more frequent checks, update the target and recurrence before use.
- The log should be retained according to your food-safety recordkeeping policy so it can support traceability during investigations or inspections.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Create one log for each steam table or holding station and name every well so the recorder can check them one by one.
- Assign a DRI for the shift and make sure the person completing the log has a calibrated probe thermometer and knows the target hot-hold threshold.
- At each hourly recurrence, verify the water level, measure the food temperature in each active well, and record the equipment condition for that station.
- If any reading is out of range, document the corrective action immediately, such as adding water, adjusting heat, moving product, or discarding unsafe food.
- Review the completed log at the end of the shift to confirm every required check was done and to identify repeat failures that need maintenance or retraining.
Best practices
- Check each well separately so one good reading does not hide a problem in another pan.
- Use a calibrated probe thermometer for every temperature entry and record the actual reading, not a rounded estimate.
- Record the water level before the temperature check so you can see whether a low pan may have caused the drift.
- Treat a failed hot-hold reading as a blocking issue until the food is corrected, moved, reheated, or discarded per policy.
- Write the corrective action in the same log entry so the record shows both the problem and the response.
- Keep the recurrence aligned to the actual service period, especially during long banquet lines or extended cafeteria service.
- Note equipment defects such as warped pans, weak heat, or missing lids so maintenance can address the root cause.
- Train staff to complete the log in real time during service, not from memory after the station closes.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this steam table log cover?
This template covers hourly verification for each steam table well holding TCS food, including water level, hot-hold temperature, equipment condition, and any corrective action taken. It is designed to capture a clear yes/no/N/A record for each well so the shift team can see whether the hold stayed within range. It also leaves room for a calibrated probe reading and a DRI if follow-up is needed.
How often should this log be completed?
Use it hourly while food is held in the steam table, or more often if your operation requires tighter internal controls. The recurrence should match the actual holding period, not just the shift schedule. If a well is emptied, refilled, or moved out of service, record that change immediately rather than waiting for the next hourly check.
Who should run this checklist?
A trained line cook, shift lead, or food-safety DRI can complete the log, as long as they know how to read the probe thermometer and recognize an out-of-range hot hold. The person doing the check should be the one who can act on the result, such as adding water, adjusting heat, moving food, or escalating to a manager. Keep assignment clear so the log does not become a shared task with no owner.
What temperature standard does this template support?
This log supports hot holding of TCS food at or above 135 °F, which aligns with common FDA Food Code hot-hold expectations. The template is built around verification steps, not guesswork, so the reading should come from a calibrated probe thermometer. If your local code or internal policy requires a higher threshold, customize the target field before rollout.
What are the most common mistakes with steam table logs?
The most common mistakes are recording a single temperature for the whole unit instead of each well, skipping the water level check, and writing down a reading without taking action when it is out of range. Another common issue is using a non-calibrated thermometer or logging after the fact from memory. This template helps prevent those gaps by separating the checklist item, the reading, and the corrective action.
Can this template be customized for different menu items or stations?
Yes. You can rename wells, add station-specific food items, or include a field for product rotation if one well changes from soup to sauce during the shift. If your operation uses multiple steam tables, duplicate the template by station so each log stays tied to one physical unit. That makes review easier and reduces confusion during audits.
How does this compare with an ad-hoc paper sign-off sheet?
An ad-hoc sheet often records only that someone looked at the steam table, which leaves gaps in temperature evidence and corrective action tracking. This template is structured so each checklist item is independently verifiable and tied to a specific well, reading, and response. That makes it easier to spot repeat failures, assign follow-up, and show consistent control during inspections.
Does this integrate with other food-safety records?
Yes, it pairs well with probe thermometer calibration logs, cooling logs, and opening or closing checklists. Many teams link it to a broader HACCP or food-safety workflow so a failed hot-hold reading can trigger a separate corrective task. It also works well alongside shift handoff notes when the steam table stays active across multiple meal periods.
Related templates
Ready to use this template?
Get started with MangoApps and use Steam Table Well Water Level and Hot Hold Temperature Log with your team — pricing built for small business.
