Actions
The follow-through module
Inspections, incidents, observations and fire checks all raise work. Actions is where that work lives: owned, due-dated, prioritised and visible until it is genuinely done.
Included free — like the rest of the platform.
How it works
- 1
Raise from anywhere
Actions come from a failed inspection response, an approved incident finding, a hazard report, a failed fire check — or stand alone. Each one keeps the link to whatever raised it.
- 2
Assign and prioritise
An owner, a due date, a priority and a type — corrective, preventive, improvement and maintenance out of the box, extendable with your own catalogue and categories.
- 3
Work the queue
The register carries the filters people actually use — mine, overdue, by site, by source — and every person sees the actions they owe in their own "For me" queue, next to the signatures and acknowledgements waiting on them.
- 4
Close with evidence
Attach photos and files to show what was done. The record links back to its source, so the audit trail reads in both directions.
What it does
Every source, one hub
Actions carry their origin — the inspection question, the incident finding, the observation — so context is never lost.
Personal queues
"For me" merges the actions you owe with the acknowledgements, signatures and drafts waiting on you. One list, no hunting.
Types and categories
Four sensible defaults, plus your own action types and categories for how your organisation splits the work.
Evidence attachments
Photos and files on the action record — including phone photos, converted automatically when needed.
Overdue visibility
Needs-attention counts sit in the navigation itself, so the red is one click away rather than buried in a report.
Exports
The register exports to CSV when someone upstairs asks for the numbers.
The golden thread
Every module feeds this one, which is what makes the platform more than a stack of registers.
- A finding becomes an action exactly once — recurring checks never duplicate it
- The action links back to the finding, and the finding to its record
- "What did we do about it?" is a click, not an archaeology project
Works with
Inspections & audits
Build a checklist once, run it on any device, and turn every failed answer into a tracked action.
Incidents & RIDDOR
Record what happened, screen it against RIDDOR with deadlines that watch themselves, and investigate properly.
Hazards & observations
Anyone can report what they see — from a QR code, no login — and it lands somewhere it gets dealt with.