Actions
The follow-through module
Inspections and observations raise work. Actions is where that work lives: owned, due-dated, prioritised and visible until it is genuinely done.
How it works
Pick a step. Each screen is a working miniature of the product.
Actions
All sites · this month
Open
24
Overdue
3
Done this week
41
- Overdue
Replace damaged rack guard, aisle 4
Riverside · from inspection WW-0143
- Due today
Absorbent and barrier at loading bay
Riverside · from hazard OB-0318
- Open
Service forklift FL-02 hydraulics
Docklands · raised directly · Maintenance
- Done
Refit guard on bench grinder
Workshop · from inspection WW-0139
Try the filters
What it does
Every source, one hub
Each action keeps a link to the inspection question or observation that raised it, so the context is never lost.
Personal queues
"My work" 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 sit on the action record, including phone photos, which are 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