Safety Walks — Overview
Ad-hoc site walks built around severity-rated observations that can be promoted to safety issues or escalated straight to incidents.
A safety walk is a quick, ad-hoc site inspection. Rather than a fixed checklist, it's built around observations — anything you see worth recording, from a hazard to a piece of good practice — each rated by severity.
Safety is in beta
Safety walks are part of the Safety module, which is in beta — in production and usable, but not yet part of a versioned release of its own.
Starting a Walk
From Safety → Safety Walks, click Start walk, give it a name (e.g. "Morning walk — Tower A levels 5–7") and start. The walk opens in progress, ready for observations.
Logging Observations
As you move around the site, tap Log observation for each thing you see:
- Severity — good, low, medium, high, or critical
- Note — describe the hazard, condition, or good practice
- Photo — capture evidence at the point of observation
- Location — optionally capture GPS coordinates
Promote and Escalate
Observations don't sit in isolation. From an observation you can:
- Raise issue — promote it to a safety issue in the Issues register, so it's tracked to resolution. An owner and a due date are set there, on the issue
- Escalate to incident — turn a serious finding straight into an incident with a full investigation
Once promoted or escalated, the observation shows an "Issue raised" or "Escalated" badge so you don't double-log it.
One tap, no re-typing
Promoting an observation carries the note, the photos and the severity across — you don't re-enter the description. Your policy can even auto-create an issue for every observation above good practice, or auto-escalate anything at or above a chosen severity.
Completing a Walk
When you're finished, tap Complete walk. The walk moves to completed and shows a summary — total observations, issues raised, and incidents escalated. Walks you haven't finished stay in progress.
| Status | Meaning |
|---|---|
| In progress | Active — you're still logging observations |
| Completed | Finished, with a summary of what came out of it |
Tips
- Log good practice too — a "good" observation is a great way to credit crews
- Capture location on serious findings so the exact spot is on record
- Escalate early — if something looks like an incident, escalate rather than just noting it
Next Steps
- Incidents — where escalated observations land
- Safety Policies — auto-create issues and set the escalation threshold
Questions
Why did my observation raise an issue or an incident on its own?
By default every observation above good practice raises a safety issue, and a High or Critical one also opens an incident. Change this in Admin → Safety → Policies with Auto-Create Safety Issues and Escalate to Incident at Severity.
Can I add or change observations after completing the walk?
No. Observations can only be logged or edited while the walk is in progress, and a completed walk can't be reopened. Start a new walk for anything you missed.
Can someone else log observations on my walk?
Yes. Anyone whose role can update Safety records can log observations on any walk that's still in progress.
Not a user yet? The Safety Walks feature page shows the module in context, and where to book a demo.