Steam Table Well Water Level and Hot Hold Temperature Log
Log hourly steam table well water levels and hot-hold temperatures for TCS foods. Use it to catch unsafe wells fast, document verification, and keep service moving.
Trusted by frontline teams 15 years of frontline software
Built for: Restaurants · Cafeterias · Catering · Hotels · Commissary Kitchens
Overview
This template is an hourly log for steam table wells that hold TCS foods hot. It combines two checks that need to happen together in service: verify the water level in each well and verify the food is being held at or above the hot-hold threshold. That makes it useful when you need a simple, repeatable record for line cooks, shift leads, or managers who are responsible for active service.
Use it during any meal period where food sits in a steam table for extended service, especially when multiple wells are running at once. It helps catch low water, uneven heating, empty wells that were left on, and food that drifts below the safe holding range. The log is also useful when a health inspector asks how the team monitors hot holding in real time.
Do not use this template as a cooking, cooling, or receiving log. It is also not the right fit for cold-holding equipment or for one-off temperature checks that are not tied to a recurring service cadence. If your operation does not use steam tables, or if your local procedure requires a different hot-hold limit, customize the threshold and the checklist items before rollout. The goal is a short, verifiable record that shows each well was checked, the result was clear, and any problem was corrected immediately.
Standards & compliance context
- This template aligns with FDA Food Code hot-holding expectations for TCS foods held at or above 135 °F.
- It supports HACCP-style verification by creating a time-stamped record of control checks and corrective actions.
- If local health rules require a different hot-hold limit or documentation cadence, update the threshold and recurrence to match the stricter rule.
- A completed log can help show due diligence during inspections, but it does not replace thermometer calibration or equipment maintenance records.
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. List each steam table well as its own checklist item so the person running the log can verify water level and hot-hold temperature one well at a time.
- 2. Set the recurrence to match service, such as hourly during lunch or dinner, and assign a DRI who can make immediate corrections during the shift.
- 3. During each check, verify the water level, measure the food temperature, and record whether the well is holding TCS food at or above the required threshold.
- 4. If a well is low on water or below temperature, mark it as blocking, correct the condition, and repeat the verification step before service continues.
- 5. Review the completed log at the end of the shift to confirm every required check was completed and to identify wells that need maintenance, retraining, or process changes.
Best practices
- Measure the food temperature in the product, not just the air above the pan, so the log reflects the actual holding condition.
- Verify the water level in every active well before you record the temperature, because low water can create false confidence in a warm-looking pan.
- Keep each checklist item atomic by naming one well per item and one verification step per entry.
- Use the same thermometer and the same probe method across shifts so readings stay consistent and easy to compare.
- Mark empty or intentionally unused wells as N/A instead of leaving them blank, so the record shows the station was checked.
- Escalate any below-threshold reading immediately and document the corrective action, not just the failure.
- Review repeated failures by well or by shift to spot equipment issues, training gaps, or staffing problems.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this template cover?
This template covers hourly verification of each steam table well’s water level and the hot-hold temperature of TCS foods held in that well. It is designed for line checks during service, not for cooking, cooling, or receiving. Each entry records a clear yes/no-style inspection result, the measured temperature, and any corrective action taken when a well falls out of range.
How often should this log be completed?
Use it on the recurrence you set for service, typically hourly during active hot holding. If the operation is busy, the DRI should still complete each check at the planned interval rather than batching entries later. If a well is empty, out of use, or temporarily blocked, record that status instead of leaving the row blank.
Who should run this checklist?
A line cook, shift lead, or other assigned DRI who can verify the wells in real time should run it. The person completing the log should be able to take immediate action if a temperature is below the hot-hold threshold or if the water level is low. For larger kitchens, the manager can review the log at shift end as a verification step.
Is this only for FDA-regulated food service operations?
No, but it is built around FDA Food Code hot-holding expectations for TCS foods. It is a good fit for restaurants, cafeterias, commissaries, and catering operations that use steam tables to keep food at or above 135 °F. If your local health department uses a stricter limit or a different documentation format, customize the threshold and notes fields accordingly.
What are the most common mistakes with steam table logs?
The biggest mistake is logging the temperature without checking the water level, since low water can cause uneven heat and false confidence. Another common issue is writing down a number without confirming which well was checked, which makes the record hard to act on. Teams also sometimes mark everything as normal even when a well is empty, uncovered, or not holding temperature.
Can I customize this template for my kitchen layout?
Yes. You can rename wells by station, add columns for pan position or menu item, and set the recurrence to match your service pattern. If you use multiple steam tables, duplicate the task by line or station so each well is independently verifiable. Keep the checklist item wording atomic so each check still has one clear answer.
How does this compare with ad-hoc temperature checks?
Ad-hoc checks are easy to miss during a rush and often leave no audit trail when a problem appears later. A structured log creates a repeatable cadence, makes ownership clear, and helps supervisors spot patterns like one well running cold or losing water repeatedly. It also reduces the chance that a single missed check becomes a food-safety issue.
Does this integrate with other kitchen logs?
Yes. It pairs well with receiving logs, cooling logs, and end-of-shift sanitation checklists because it sits in the same food-safety workflow. Many teams link it to a daily opening checklist or a shift handoff so the next DRI can see whether a well was already flagged. If your operation uses digital task management, map each well to a separate checklist item for cleaner reporting.
What should I do if a well is below temperature or low on water?
Treat it as a blocking issue for that well until the condition is corrected and reverified. Refill the water, restore heat, and recheck the food temperature before continuing service. If food has been in the unsafe range too long or cannot be corrected promptly, follow your food-safety policy for holding, discarding, or replacing the product.
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.
