Steam Table Well Water Level and Hot Hold Temperature Log
Use this steam table log to record hourly well-by-well water levels and hot-hold temperatures for TCS food held at or above 135 °F. It gives kitchen staff a simple, auditable way to catch unsafe hot-holding conditions before food falls out of compliance.
Trusted by frontline teams 15 years of frontline software
Built for: Restaurants · Cafeterias · Hotels · Catering · Healthcare Food Service
Overview
This template is a hot-holding verification log for steam table wells used to keep TCS food at or above 135 °F. It is built for hourly checks of two things that matter together: the food temperature and the water level that keeps the well producing heat. Each well should be treated as its own checklist item so the record shows exactly which station was checked, when it was checked, and whether any corrective action was needed.
Use this template when you need a repeatable record for buffet lines, cafeteria service, banquet setups, or any station where food sits in a steam table for extended periods. It is especially useful when multiple wells hold different menu items and one problem can affect only part of the line. The log helps the team catch low water, drifting temperatures, or a missing verification before the issue becomes a food-safety problem.
Do not use this as a substitute for cooling logs, cooking logs, or reheat logs. It is also not the right template for cold holding or for equipment that does not rely on water-assisted heat. If the station is empty, out of service, or holding non-TCS items only, record that status rather than forcing a temperature entry. The value of this template is in clear, independent verification of each active well and a fast handoff to corrective action when a reading is out of range.
Standards & compliance context
- This template supports FDA Food Code hot-holding expectations by documenting that TCS food is maintained at or above 135 °F.
- Independent well-by-well verification helps demonstrate that the operation is monitoring the actual control point, not just the overall station.
- Clear records of out-of-range temperatures and corrective action can support local health department inspections and internal food-safety audits.
- If your jurisdiction or brand standard requires a different temperature threshold or check frequency, customize the template to match that rule set.
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
- 1. Set up one checklist item for each steam table well and label it with the station name, well number, and the food being held.
- 2. Assign the task to the shift lead or station DRI and configure the recurrence for hourly checks during active hot holding.
- 3. At each interval, verify the water level in the well, measure the food temperature with a sanitized probe, and record both results immediately.
- 4. If any reading is below the hot-hold threshold or the water level is insufficient, mark the item as blocking and start the corrective action required by your kitchen procedure.
- 5. Review the completed log at shift change or manager closeout, then note any repeated failures, equipment issues, or retraining needs.
Best practices
- Check each well separately instead of writing one temperature for the entire steam table.
- Use a sanitized probe thermometer for every verification step and record the reading right away.
- Mark low water as a separate issue even when the food temperature still looks acceptable, because the equipment condition can fail next.
- Keep the recurrence aligned to active service hours so the log is not skipped during rush periods.
- Record corrective action in the same task when a reading falls out of range, including reheating, replacing product, or refilling the well.
- Treat empty or unused wells as N/A rather than leaving them blank, so the log stays auditable.
- Avoid priority inflation by reserving critical only for food-safety or compliance-impacting failures.
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 actually cover?
This template is for hourly verification of each steam table well’s water level and the hot-hold temperature of TCS food held in that well. It is designed to document whether food is staying at or above the required hot-holding threshold. The log is useful when you need a simple record that can be reviewed during shift handoff, manager checks, or an inspection.
How often should this log be completed?
Use it at the recurrence configured for the operation, typically hourly during active hot holding. The point is to create a repeatable verification step, not an end-of-shift memory exercise. If a well is idle, empty, or out of service, record that status clearly rather than leaving the item blank.
Who should run this task?
A line cook, prep cook, or shift lead can complete the log as long as they are trained to read the thermometer, check the water level, and escalate problems. The DRI should be the person responsible for the station during that shift, with a manager reviewing exceptions or repeated misses. Keep the assignment clear so the task does not become blocking when the station gets busy.
Is this only for FDA inspections?
No. While it supports FDA Food Code hot-holding expectations, it is also useful for internal QA, franchise standards, and local health department readiness. The log helps show that the team is actively monitoring both the food temperature and the steam table condition. It is a practical control, not just a compliance artifact.
What are the most common mistakes with this kind of log?
The biggest mistake is logging a single temperature for the whole line instead of checking each well independently. Another common issue is recording a number without confirming the water level, which misses the root cause of heat loss. Teams also sometimes wait until the end of the shift to fill it out, which defeats the purpose of the verification step.
Can I customize this for different menu items or stations?
Yes. You can rename wells, add station identifiers, or include notes for specific menu items that are especially sensitive to temperature drift. If your operation uses multiple steam tables, keep each well as a separate checklist item so the log stays independently verifiable. That makes it easier to spot patterns by station or by shift.
How does this compare with a general temperature log?
A general temperature log usually tracks food temperatures only, while this template also captures the steam table water level that supports hot holding. That extra check matters because a food item can drift out of range even when the station looks active. This template is better when the equipment condition itself is part of the control.
Can this be used with thermometers or kitchen systems?
Yes. The log can be paired with probe thermometer readings, Bluetooth thermometers, or a kitchen operations system if your workflow supports it. The important part is that each checklist item remains clear and verifiable, whether the data is entered manually or captured through an integration. If you automate, keep the human verification step for water level and corrective action.
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.
