Workflow Template
Job Safety Analysis Workflow
Captures a Job Safety Analysis (JSA) submitted by a preparer detailing a task's work steps, hazards, and controls. Routes the analysis to a supervisor for review and decision (Approved / Changes Required / Unsafe to Proceed). Approved JSAs trigger a worker acknowledgement request before work starts; changes required routes back to the preparer for revision and resubmission; unsafe determinations stop work and escalate to the safety manager. Preparer and supervisor are notified of every decision.
Organisations operating under health and safety regulatory frameworks require a defensible, consistent process for reviewing Job Safety Analyses before work commences, particularly where unsafe determinations must trigger immediate escalation. This workflow governs the full lifecycle of a JSA submission — from preparer input through supervisor review, decisioning (Approved, Changes Required, or Unsafe to Proceed), and worker acknowledgement — ensuring frontline workers, supervisors, and safety managers operate from a single, auditable record. It is designed for field operations, HSE, and site supervision teams that need structured accountability without introducing administrative burden into pre-work safety checks.
Business Outcomes
- Supports faster supervisor turnaround on JSA reviews through structured routing and notifications
- Helps reduce work started without proper hazard review or worker acknowledgement
- Improves traceability of safety decisions for audit and incident investigation purposes
- Reduces administrative delay in escalating unsafe conditions to safety management
- Makes it easier to demonstrate consistent JSA governance across sites and teams
Workflow Steps
Steps
- 1Create JSA Recordcreate record
Registers the submitted job safety analysis as a record.
- 2Set Status to Draftupdate record
Marks the JSA as drafted and awaiting review.
- 3Assign to Supervisorassign user
Routes the JSA to the supervisor for review.
- 4Set Status to Under Reviewupdate record
Marks the JSA as under supervisor review.
- 5Review Job Safety Analysiscreate task
Supervisor reviews the task steps, hazards and controls and records a decision.
- 6Persist Supervisor Decisionupdate record
Writes the supervisor's decision and comments to the record.
- 7Route on Supervisor Decision
Branches the workflow based on the supervisor's decision.
supervisor_decision: "Approved"→Set Status to Approvedsupervisor_decision: "Changes Required"→Set Status to Changes Requiredsupervisor_decision: "Unsafe to Proceed"→Set Status to Unsafe - EscalatedDefault→End - 8Set Status to Approvedupdate record
Marks the JSA as approved by the supervisor.
- 9Notify Preparer - Approvedsend email
Informs the preparer that the JSA was approved.
- 10Notify Supervisor - Approvedsend email
Confirms to the supervisor that their approval was recorded.
- 11Request Worker Acknowledgementrequest external input
Sends workers the approved safe work method for acknowledgement before starting the task.
- 12Set Status to Changes Requiredupdate record
Marks the JSA as requiring changes from the preparer.
- 13Notify Preparer - Changes Requiredsend email
Tells the preparer to revise the JSA based on supervisor feedback.
- 14Notify Supervisor - Changes Requiredsend email
Confirms to the supervisor that the JSA was sent back for revision.
- 15Revise Job Safety Analysiscreate task
Preparer revises the work steps, hazards and controls based on supervisor feedback.
- 16Persist Revised JSA Detailsupdate record
Saves the preparer's revised work steps, hazards and controls to the record.
- 17Resubmit for Supervisor Reviewrestart from step
Restarts the workflow from supervisor review with the revised JSA.
- 18Set Status to Unsafe - Escalatedupdate record
Marks the JSA as unsafe to proceed and escalated to the safety manager.
- 19Notify Preparer - Unsafe to Proceedsend email
Informs the preparer that the task was deemed unsafe and work is stopped.
- 20Notify Supervisor - Unsafe to Proceedsend email
Confirms to the supervisor that the unsafe determination was recorded and escalated.
- 21Escalation: Unsafe Task Reviewcreate task
Safety manager reviews the unsafe determination and decides on next steps before any new JSA can be submitted.
- 22Set Status to Unsafe - Closedupdate record
Marks the JSA task cycle as closed following safety manager escalation review.
Fields
- Preparer Name*
- Preparer Email*
- Supervisor Name*
- Supervisor Email*
- Task Description*
- Location*
- +12 more fields
Forms
Job Safety Analysis Submission
12 fields
Data Views
Job Safety Analyses
task_name, task_location, preparer_name, supervisor_name +3 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
How is this workflow audited?
Every status change — draft, under review, approved, changes required, or unsafe-escalated — is recorded against the JSA record along with the associated supervisor decision and timestamp. This creates a chronological, retrievable audit trail that supports internal safety audits, regulatory inspections, and post-incident reviews. Because the record persists within assess.one, historical decisions and revisions remain accessible without relying on email threads or paper files.
Who has access to JSA records and decisions at each stage?
Access is configured by role within assess.one, typically limiting edit rights to the preparer during drafting and revision, and decision rights to the assigned supervisor during review. Safety managers can be granted visibility into escalated unsafe determinations without needing access to every routine approval. Administrators can adjust these permissions directly in the platform as organisational structure or site requirements change.
How does this integrate with existing notification tools like email or Slack?
Notifications to preparers and supervisors — for approvals, changes required, or unsafe determinations — are configured within assess.one and can be directed to email, Slack, or other supported channels. No separate integration project or external development work is required; these connections are set up as part of workflow configuration. This keeps stakeholders informed in real time without manual follow-up.
How long does implementation take?
The JSA Review Workflow is a ready-to-use template that can be published and made live within minutes. Once published, preparers and supervisors can begin submitting and reviewing JSAs immediately, with no weeks-long rollout or IT project required. Teams can refine steps and roles after go-live based on real usage rather than waiting for a lengthy pre-launch configuration phase.
What happens when a supervisor marks a JSA as Unsafe to Proceed?
The workflow immediately sets the record status to Unsafe - Escalated, halting progression toward worker acknowledgement or work start. Both the preparer and supervisor are notified of the determination, and the record is escalated to the safety manager for further review or intervention. This ensures unsafe conditions receive prompt attention rather than being buried in a general review queue.
Can the approval and escalation logic be customised?
Yes, the decision routing, approval criteria, and escalation paths are configured directly within assess.one and can be adjusted to reflect site-specific safety policies or organisational hierarchy. Teams can add additional review steps, change notification recipients, or introduce further approval tiers without requiring developer involvement. Changes take effect on republishing the workflow.
How is worker acknowledgement handled after approval?
Once a JSA is approved, the workflow automatically triggers a worker acknowledgement request before work is permitted to start. This step is designed to confirm that workers performing the task have reviewed the identified hazards and controls prior to commencing work. Acknowledgement activity is recorded against the JSA, supporting downstream audit and compliance reporting.
What happens if a supervisor requests changes to a submitted JSA?
The record status is set to Changes Required, and both the preparer and supervisor receive notification of the decision. The JSA routes back to the preparer for revision, allowing updates to work steps, hazards, or controls before resubmission. Once revised, the JSA is automatically routed back into the supervisor review queue, maintaining a continuous and traceable review cycle.
Who typically needs access to this workflow within an organisation?
Typical participants include field or task preparers responsible for drafting JSAs, supervisors accountable for review and decisioning, and safety managers who handle unsafe escalations. Depending on organisational structure, HSE administrators may also require visibility to monitor trends or generate compliance reporting. Role assignments are managed within assess.one and can be scaled across multiple sites or teams.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
