Prevention
Roofing JHA: map low-slope installation tasks before the shift
Plan a low-slope roofing JHA around task stages, material and product choices, work-area interfaces and changes, separate from routine shift handover.
By Reldro · · 5 min read
Use a task plan for the work you are actually doing
A roofing JHA should describe the planned installation activity, work area, task stages and reviewed controls. For low-slope roofing, distinguish the material movement, installation method and edge-detail activities instead of writing roofing work as one broad step.
This guide is about building and maintaining the task plan before the shift. The separate roofing handover guide explains how to transfer changed conditions between shifts. They answer different questions: what is the proposed task, and what does the next team need to know about the work left behind?
No fall-protection design, roof loading limits, weather thresholds, adhesive exposure controls or hot-work instructions are provided here. Those decisions belong to the applicable procedures and responsible specialists. A JHA is not permission to begin roof work.
Break the installation into meaningful stages
The low-slope template includes edges and openings, bringing materials up, laying insulation and membrane, heat or adhesive use, and flashing or sealing edges. These are prompts for task planning, not a complete technical specification.
Compare the prompts with today’s assignment. A delivery-only stage is different from membrane installation. A mechanically fixed method is different from a task involving an adhesive or heat. Have the relevant specialists identify which stages apply and which method documents and product records govern them.
State exclusions clearly. If the day’s JHA is for one roof zone or one method, do not imply that it covers another zone, a different product or a later stage. Record the boundary in terms another supervisor can find on the current plan.
Collect the inputs that can change the task
Before the review, identify the current area plan, task method reference, material/product records and interfaces with other trades. Ask who is responsible for each input and how updates will reach the roofing team. A new document in the office is not automatically an understood change in the field.
Use OSHA’s general JHA approach to discuss the task stages and work environment with the people involved. The publication does not give project-specific roofing controls. Treat worker observations as inputs to the responsible reviewers, not as substitutes for specialist decisions.
A short scope record can make the discussion much clearer than a long generic hazards list. Connect each question to the stage it affects, and record the actual response instead of marking the whole form reviewed.
- Roof zone and current plan reference.
- Installation stage and applicable method document.
- Material/product identity and current supporting information.
- Access, delivery and neighboring-trade interfaces for review.
- Specialist decisions outstanding and the affected work stage.
- Version and person responsible for communicating any change.
Worked example: the proposed membrane product changes
Imagine a roofing contractor preparing membrane work in zone R-2. The task discussion references the specified product in the current work package. A substitution is proposed shortly before the shift. This is an illustrative planning example, not an endorsement of any product or method.
The supervisor records the proposed substitution and asks the responsible project and technical reviewers to confirm its status and effect on the method. If different supporting safety information is involved, the appropriate reviewer must assess it through the company process. The article does not infer an equivalent control set from a similar product name.
Keep the task record tied to the decision. A delivery of the substitute product is not evidence that its use was approved. A later technical response should identify the applicable documents and affected stages, after which the task plan can be revised and communicated under your process.
Decide what needs revisiting when the scope changes
A revised area, task method, product or delivery arrangement can affect different parts of the plan. Ask the responsible reviewers which assumptions need reassessment rather than copying the earlier controls into the new record. Preserve both the original plan and the documented update.
For example, changing the roof zone is a location change, while changing the joining or application method is a task change. Both deserve precise descriptions. A generic revised today label does not tell the next reader what was reconsidered or who reviewed it.
Brief the people carrying out the affected work on the current scope and the decisions relevant to them. Record outstanding questions and the next response owner. The aim is not to collect more signatures; it is to avoid the team relying on a plan that describes something else.
Leave a useful handover for the next review
At shift end, connect the completed task stages, remaining areas and current version to the separate handover record. Use the roofing shift-handover guide for that transfer rather than trying to make a task JHA do the whole closeout job.
If work involves skylights or roof openings, the related template may help organize an additional task discussion, but its technical content needs specialist review too. Inspect the public templates first and follow the demo journey if you want to discuss their use. None is presented as a certified roofing method or a free downloadable authorization.
The takeaway
Plan the actual roof zone, installation stages and method, then revisit the affected assumptions when products or work boundaries change. Keep the later shift handover separate.
Sources and further reading
References for this article, published November 9, 2026. Product scope and requirements can change. Confirm details with the provider and your safety team. Guidance from a specific jurisdiction may not apply to your construction project.