How to log high-heat procedures
What to record when the temperature hits 95 F, and what an inspector reads back out of it.
High-heat procedures are the easiest thing to skip on a busy roof and the hardest to prove after the fact. A useful log entry shows the reading and where it came from, that shade and water were in place, that the pre-shift meeting happened, that the required rest actually occurred, who was observing for symptoms, and a supervisor signature. Anything less is a temperature with no procedures attached to it.
Takeaways
- Write a high-heat entry that answers the questions an inspector asks.
- Record the reading with its source and time rather than a number alone.
- Capture rest that happened rather than rest that was available.
- Know which industries and states trigger high-heat procedures at all.
Who gets high-heat procedures
The seven things a high-heat entry should contain
Record the source, not just the number
Rest that happened, not rest that was available
Naming the person who was watching
What a good entry looks like
Frequently asked questions
- Do I need a log for every day or only hot days? RestShade defaults to action days: file when heat, smoke, or cold crosses thresholds an inspector would ask about. A mild workday stays all clear. Choose daily mode in Settings if you want a log every scheduled workday.
- Can the crew sign instead of the supervisor? Crew acknowledgment is valuable, but the supervisor signature is what attests that the procedures were run. Many operations capture both.
- What if the temperature crossed 95 F only briefly? Record it. High-heat procedures attach to conditions at the worksite, and a brief crossing is easier to explain in a log than to reconstruct from memory a year later.
- Should I record the forecast or the actual reading? Both, when they differ. Some rules attach to a forecast, and recording both shows why preparation happened before the heat arrived.