Module: Operations
Incidents and investigations
Something happened, and what you do in the next hour matters. Capture it from any device, decide how serious it is, investigate it properly, and close it on evidence rather than on a tick.
What it does
Reported in a minute
The report form asks one short question per screen, so a person holding a phone can say what happened, when, where and how serious it was, and attach photos. Where you want it, the same form opens from a scanned code with no login at all.
Hazards as well as events
A hazard is something someone noticed before anybody was hurt, so it has its own register and a lighter form. When a hazard turns out to matter, it is promoted into the risk register and keeps its history.
Triage that does not stall
Every record follows a workflow: acknowledged, investigated where it warrants it, corrective action, verification, closed. The next step sits on the record and the person who owns it is told.
The investigation method that suits the event
A minor event gets a short review. A serious one gets five whys, ICAM, a reconstructed timeline, or a diagram you build on screen such as a bow tie, fishbone, fault tree or event tree. Contributing factors, root causes and lessons are recorded against the incident.
Notifiable incidents, prepared and checked
An incident is tested against the notification thresholds for your jurisdiction and a notification is drafted for a person to approve or reject. Obliwise never contacts a regulator for you. You record when and how you notified, the deadline is tracked, and the whole trail stays on the incident.
Anonymous reporting, with a reply
People can report without giving a name and still be answered. The reporter keeps a tracking code and can hold a two way conversation with the handler, who never sees who they are. The queue shows at a glance which reporters are waiting on an answer.
One event, one record
When the same event is reported twice, the likely duplicate is flagged and the two records can be merged into one. Nothing is deleted, the record that was merged away stays readable, and the merge can be undone.
How it fits with the rest
Incident reporting draws on the people, locations, contractors and equipment already held in the platform, so a reporter picks from a list instead of typing a name and the record can be read by location, by business unit, by contractor or by project from the first day.
Corrective actions raised during triage or investigation are ordinary actions: they appear in the Actions register with everything else, with an owner, a due date and a verification step, so nothing is tracked in a spreadsheet beside the system. When a person is hurt, the injury record and any claim are created from the incident and held under their own access rules, so clinical detail is not open to everyone who can read the incident. A hazard promotes into the risk register. Lessons reach the people who need them, and earlier events that look like this one are surfaced while the investigation is open.
The follow up runs by itself. Owners are notified, overdue work is escalated to the person accountable for it, and the record closes only when the workflow's conditions are met and a person approves it.
Ready-made content
Incident reporting installs with a ready-made pack: the guided report form, the lifecycle workflow from report through investigation and verification to close, an incident report document you can print or send, and the lists behind the fields such as how a person was hurt and what was involved. A matching observation pack covers near misses, good catches and unsafe conditions, and a corrective action pack covers the follow up work.
Notifiable incident thresholds are supplied for every Australian state and territory, the Commonwealth and New Zealand, each rule written in plain words so the person reviewing it can see exactly what it tests. Your workspace starts on the jurisdiction you nominate, and the rules can be edited or added to.
Change it if you need to
Every module comes ready to use. If your organisation records something differently, your own team can adjust the forms, fields and workflow, or ask us to do it with you. Nothing here requires a development project.
Works alongside
See incidents and investigations running on your own processes.
Bring one of your own forms or procedures to the demonstration. We set the module up the way you work and show it end to end.