Workflow Template
Safety Observation Workflow
Captures safety observations from staff, acknowledges the observer, and routes At Risk observations through severity assessment, corrective action, and review confirmation until closed.
A staff member spots something unsafe on the floor and fills in a quick form on their phone—no account needed. The workflow logs it as a record with a reference number, sends the observer an acknowledgement straight away, and for anything flagged 'At risk' automatically routes it to the safety lead for severity assessment, then to an action owner for corrective action, and on to a reviewer who confirms the fix before the record closes. Day-to-day, this means safety leads and action owners just work through tasks assigned to them, and anyone can check a record's status and timeline instead of chasing emails or spreadsheets.
Business Outcomes
- Faster acknowledgement of safety observations, helping staff feel heard the moment they report something
- Clearer accountability with severity assessment, action ownership, and review confirmation assigned as distinct tasks
- Reduced risk of At Risk observations being forgotten, since the record stays open until the reviewer confirms the fix
- Better visibility into open vs closed observations through record status and dashboards
- Less manual chasing, since inadequate corrective actions are automatically sent back to the action owner for rework
Workflow Steps
Steps
- 1Create Safety Observation Recordcreate record
Creates the safety observation record from the submitted form.
- 2Set Status to Submittedupdate record
Sets the observation status to Submitted.
- 3Email Acknowledgement to Observersend email
Sends the observer an acknowledgement email with their reference number.
- 4Route on Behaviour
Routes the workflow based on whether the observed behaviour was Safe or At risk.
behaviour: "Safe"→Close Safe Observationbehaviour: "At risk"→Safety Lead: Assess SeverityDefault→Safety Lead: Assess Severity - 5Close Safe Observationupdate record
Sets the observation status to Closed for a positive Safe observation.
- 6Thank Observer for Safe Observationsend email
Emails the observer a thank-you recognising their positive safety observation.
- 7Safety Lead: Assess Severitycreate task
Assigns the safety lead a task to assess severity, assign an action owner, and define the corrective action.
- 8Save Severity Assessmentupdate record
Persists the severity, action owner, and corrective action to the record and sets status to Action Assigned.
- 9Action Owner: Take Corrective Actioncreate task
Assigns the action owner a task to carry out and record the corrective action taken.
- 10Save Action Takenupdate record
Persists the action taken to the record.
- 11Safety Reviewer: Confirm Corrective Actioncreate task
Assigns the safety reviewer a task to confirm whether the corrective action was adequate.
- 12Save Review Outcomeupdate record
Persists the reviewer's outcome and notes to the record.
- 13Route on Review Outcome
Routes based on whether the safety reviewer confirmed the corrective action or found it inadequate.
review_outcome: "Confirmed"→Close At-Risk Observationreview_outcome: "Inadequate"→Return to Action Owner for ReworkDefault→Return to Action Owner for Rework - 14Return to Action Owner for Reworkrestart from step
Closes this iteration and restarts from the action owner task since the corrective action was inadequate.
- 15Close At-Risk Observationupdate record
Sets the observation status to Closed once the corrective action is confirmed adequate.
- 16Notify Observer of Closuresend email
Emails the observer that their at-risk observation has been actioned and closed.
Fields
Show all 16 fieldsShow fewer fields
FormSafety Observation Report
- Observer Name*· Text
- Observer Email*· Email
- Location*· Text
- Date of Observation*· Date
- Activity Observed*· Text
- Behaviour*· Choice
- Description*· Long text
- Immediate Intervention Taken· Long text
- Photos· File upload
TaskSafety Lead: Assess Severity
- Severity*· Choice
- Action Owner*· Text
- Corrective Action Required*· Long text
TaskAction Owner: Take Corrective Action
- Action Taken*· Long text
TaskSafety Reviewer: Confirm Corrective Action
- Review Outcome*· Choice
- Review Notes· Long text
Other fields
- Observation Status· Choice
- Observer Name*
- Observer Email*
- Location*
- Date of Observation*
- Activity Observed*
- Behaviour*
Forms
Safety Observation Report
9 fields
Data Views
Safety Observations
location, observation_date, behaviour, severity +1 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Categories
FAQs
Do I need to set up accounts for staff to report safety observations?
No—staff submit observations through a public request form, and they don't need a login or account to do it. The workflow captures observer name, email, location, and details from the form, then creates a tracked record automatically.
Can my team customise what happens when an observation is marked At risk?
Yes, you can edit the workflow steps in the workflow editor or describe the change you want in plain English. For example, you could adjust who gets assigned the severity assessment task or what fields the safety lead records, and earlier versions of the workflow are kept if you want to compare changes.
Who actually handles an At Risk observation once it's submitted?
Three roles are involved in sequence: the safety lead assesses severity and assigns an action owner and corrective action, the action owner carries out and records the fix, and the safety reviewer confirms whether the corrective action was adequate. Each task is assigned to a workspace member and the workflow waits for it to be completed before moving on.
What happens if the safety reviewer decides the corrective action wasn't good enough?
The workflow routes the record back to the action owner for rework rather than closing it. This repeats until the reviewer confirms the corrective action is adequate, at which point the observation is set to Closed.
Is this suitable for tracking both safe and at-risk behaviour observations?
Yes, the workflow routes based on the Behaviour field submitted on the form. Safe observations are closed quickly with a thank-you email to the observer, while At risk observations go through the full severity assessment, corrective action, and review process.
Does the observer get told what happens to their report?
Yes, the observer receives an acknowledgement email with their reference number as soon as they submit the form. Depending on the outcome, they later receive either a thank-you for a Safe observation or a closure notice once an At-risk observation has been actioned.
What information is kept on the record as it moves through the process?
Fields the workflow waits on—like Severity, Action Owner, Corrective Action Required, Action Taken, Review Outcome, and Review Notes—are saved to the record itself. Each record also has a status and a timeline showing what happened and when, which your team can review at any point.
Can we see how many safety observations are open or closed at any time?
Yes, table views and dashboards show records grouped by status, so you can see at a glance which observations are Submitted, Action Assigned, or Closed. This gives a quick overview without needing to dig through individual records.
How quickly can we start using this workflow?
Since it's a ready-to-use template, your workspace can publish it and start capturing real safety observations within minutes—there's no installation or development project involved. You can then adjust steps like task assignments or email wording as you learn what works for your team.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
