Roofing safety checklist: hand over changed conditions between shifts

What should a roofing shift handover include?

A roofing shift handover should tell the incoming supervisor where work ended, what conditions changed, which observations remain open and who owns the next decision. Pair that handover with the current roofing pre-start review. Yesterday's completed checklist is useful history, not proof that today's conditions are unchanged.

The most helpful note often answers a small question: which roof area does this update concern? A general message such as roof checked does not tell the next team about a relocated access point, a newly occupied work area or an unresolved observation around an opening.

This article is a records and coordination guide for roofing contractors. It does not teach fall-protection selection, anchor design, rescue procedures or weather thresholds. Those decisions belong to your site-specific procedures and appropriately qualified people. Do not use a checklist or this article as authorization to start or resume work.

• View the roofing pre-start checklist

Keep the work-area reference consistent

Give each handover a project, date, shift, author and work-area reference. Describe the roof zone in terms the incoming team can find, using the project plan or agreed location labels. North roof is not enough if there are several buildings or levels.

Record the task and its current stage as well as the place. Preparing a membrane area, receiving materials and completing flashing may share a location but need different coordination. Say what is complete, what is unfinished and where the supporting work plan can be found.

Use the same location reference in photographs, observations and assigned follow-up. If the team changes the reference, explain the mapping rather than leaving two names that appear to describe different areas. The aim is to remove the small ambiguities that become bigger during a busy shift change.

Separate current observations from yesterday's decisions

The roof-edge template is intended for the start of a roof shift and following weather or changes to edge protection. It includes prompts concerning edges and openings, anchor points, access, surface conditions and rescue-plan readiness. Treat these as questions for the appropriate review, not as technical criteria this article can certify.

In the handover, distinguish an observed change from a reviewer's decision. Write that a particular access arrangement changed and name the person asked to assess its implications. Do not infer that a control is suitable because it was photographed or mentioned in the previous shift's note.

If you carry an open observation forward, include its original reference. The new shift can add what it has observed without erasing what the earlier team recorded. Where an item has been resolved, reference the actual review or evidence rather than saying someone dealt with it.

• View the roof edge protection checklist

Build a handover around the next decisions

Keep the record brief enough to use, but complete enough to act on. A paragraph of general reassurance is less useful than three specific items with owners. Start with the work area and state which questions the incoming supervisor needs answered before making their own plan.

For each open item, include the observed condition, the person responsible for follow-up and the next review point. Record communication status separately: sent, acknowledged and reviewed are not the same. If the responsible reviewer is unavailable, follow the escalation route in your project process rather than assuming silence means acceptance.

• Work remaining: exact task and location, with the current assignment reference.
• Changed conditions: what was observed, when, and where.
• Open observations: original reference, current owner and response still needed.
• Current decisions: reviewer, time, scope and supporting record.
• Incoming review: who will reassess the affected work under the site process.
• Communication: who received the handover and which questions they raised.

A worked example: two roof areas, one incomplete handover

Here is an illustrative scenario. A roofing contractor has finished preparation in zone A and planned to continue in zone B. Between shifts, a delivery occupies part of the previously agreed access area. A separate roof-edge observation in zone B is still awaiting the responsible reviewer's response.

The outgoing note reads: Zone A preparation recorded against task R-21; zone B work remains unstarted. Access-area change observed at 16:10, location shown on marked plan. Site coordinator asked to confirm the next access arrangement. Observation RE-08 remains open with the designated reviewer. Do not treat zone A's completed record as a review of zone B.

The incoming supervisor reads the handover, checks the latest responses and arranges the required current review under the project process. Operations receives the constraints before assigning a team to the next visit. The note does not decide whether the roof is safe; it makes the outstanding decisions visible to the people responsible.

This is the practical difference between a useful handover and a message saying roofing delayed. It explains the affected work and preserves the next action without attributing fault or inventing a technical conclusion.

Handle weather and protection changes without guessing

When weather or a protection arrangement changes, record the factual change and ask the responsible reviewer which parts of the plan and checks need revisiting. Avoid copying a generic wind limit or weather rule into the handover unless it comes from the applicable approved procedure and is correctly interpreted by the responsible person.

A forecast, a site observation and a work decision are different records. Note the observation time and affected area, then reference the actual decision when it is made. If the plan is adjusted, communicate the revised scope to the people who schedule work and the people who carry it out.

The same principle applies if access, openings or shared work areas change. Do not ask the incoming team to reconstruct the history from a group chat. Give them the latest record plus the reference to the earlier decision that changed.

Review the handover before you reuse the checklist

Ask the incoming supervisor to explain the open items back in practical terms: which area is affected, which work is waiting and whose response is needed? That short conversation can expose a missing location or unclear responsibility. It is not a test of competence or a replacement for required training.

Use a fresh review for the current shift as your process requires, with references to unresolved findings. Copy stable project identifiers if helpful, but do not copy yesterday's answers as though they were current observations. The value of the record comes from what was actually checked and understood.

After the shift, look for recurring handover gaps. If people repeatedly cannot find the affected area, improve the location convention. If items lack a next reviewer, improve responsibility assignment. Those are process improvements you can make without pretending that a higher checklist completion rate establishes safer conditions.

Choose the templates that match the roofing task

Use the roofing pre-start and roof-edge templates as starting points for the current review. For task planning, choose the JHA that matches the work, such as low-slope roofing, rather than treating all roof work as one activity. Adapt and review the material with the people responsible for your actual project.

The templates are publicly viewable; operational use follows the library's demo request. A template is not a site-specific fall-protection plan. Keep the task plan, specialist decisions and follow-up references connected to the handover so the incoming team knows where to find them.

• View the low-slope roofing JHA
• Hand over open safety concerns without losing context
• Verify corrective-action closure with supporting evidence