What a JSA is (and how it differs from a permit or SDS)
A JSA is task-level: it takes one job — "set steel on the second floor," "saw-cut the slab," "trench for the new service line" — and walks it step by step. That is different from a safety data sheet (SDS), which describes one chemical, and from a permit (hot work, confined space), which authorizes one high-risk activity. The JSA is the connective tissue: it is where you decide that this task, on this site, today, needs fall protection at the leading edge and a spotter for the equipment.
OSHA does not mandate a specific JSA format, but it does expect documented hazard assessment with controls specified, PPE identified, and evidence the crew was made aware. A JSA is the standard way contractors produce that evidence.
Break the job into steps — not too coarse, not too fine
The first and most-skipped move is decomposing the task into sequential steps. Most crews go too coarse ("install the roof") which hides every real hazard, or too fine ("pick up a shingle") which buries the analysis in noise. The right grain is a handful of steps a foreman would naturally call out: stage materials, set up fall protection, tear off the old roof, dry in, install.
A good test: each step should have at least one hazard worth naming. If a step has none, it is probably too granular to be its own line.
Name the hazard, then assign a real control
For each step, ask what could hurt someone and rank it honestly — a slip on debris is not a fall from a leading edge. Then assign a control that actually removes or reduces the hazard, following the hierarchy of controls: eliminate it, substitute it, engineer it out (guardrails), use administrative controls (sequencing, training), and only last rely on PPE.
The most common JSA failure is jumping straight to "wear PPE" for everything. PPE is the last line, not the first answer. If the honest control for a leading-edge fall is a guardrail or a personal fall-arrest system anchored to a rated point, write that — not just "hard hat, safety glasses."
- Fall protection — guardrails, PFAS with rated anchor, or a controlled-access zone for leading-edge work above the trigger height.
- Lockout/tagout — for any energized electrical, hydraulic, or pneumatic source before service.
- Silica/dust — wet-cutting or on-tool extraction for concrete and masonry, per the respirable-crystalline-silica standard.
- Trenching — protective system (slope, shore, or shield) for excavations at depth, plus a competent-person daily inspection.
- Heavy equipment — spotters, swing-radius control, and ground-worker separation.
In Vexor
Vexor ships JSA templates for these common contractor hazards — fall protection (roofing), lockout/tagout (electrical), silica (concrete), confined space (plumbing crawl-space), heavy-equipment LOTO, and trenching — so you start from a real hazard set instead of a blank page, then edit per job. You can also save your own templates per trade.
Get crew sign-off — and make it mean something
A JSA the crew never read is worse than none, because it implies a briefing that did not happen. The acknowledgement step is the point: each worker reads the analysis, has the chance to flag a hazard you missed, and signs that they understand it before the task starts. That signature is also your documentation that the briefing occurred.
Capture the sign-off where the work is — on a phone at the jobsite — not on a clipboard that gets back to the office three days later. A signature with a name, timestamp, and location attached is contemporaneous evidence; a scanned sheet signed in the truck is not.
In Vexor
Crews sign on the phone before work starts; each signature captures the signer's name, timestamp, device, and GPS location, and works offline (it uploads with the original timestamp when the device reconnects). Every JSA event — created, assigned, viewed, signed, edited — is logged and exports as a PDF for OSHA, insurance, or a dispute.
Reuse and re-brief on long jobs
On a multi-day job the hazards usually persist — the leading edge is still there on day four. The mistake is writing the JSA once on day one and never re-briefing. Either re-deliver the same JSA each shift so new or rotating crew acknowledge it, or update it when conditions change (weather, a new trade on site, a phase change). The discipline of a daily re-brief is what keeps the JSA from becoming wallpaper.
In Vexor
Vexor can schedule a JSA to deliver daily, weekly, or before each shift, so the same hazards get re-acknowledged by whoever is on the crew that day without anyone re-typing it.
Step by step
- 1
Pick the task and the date
Name the specific task, crew, and day. A JSA is for one task on one site — not a generic "safety policy."
- 2
Break it into steps
List the handful of sequential steps a foreman would call out. Each step should carry at least one real hazard.
- 3
Identify hazards per step
For each step, name what could cause injury and rank the severity honestly.
- 4
Assign controls by hierarchy
Eliminate, substitute, engineer, administrate, then PPE — in that order. Avoid defaulting to PPE for everything.
- 5
Specify PPE and permits
List required PPE and flag any task needing a permit (hot work, confined space) or a competent-person inspection.
- 6
Brief and collect sign-off
Walk the crew through it on site, invite missed-hazard callouts, and capture each worker's acknowledgement before work starts.
- 7
Re-brief as conditions change
Re-deliver or update the JSA each shift on long jobs, or whenever weather, phase, or trades on site change.