Incident reporting that does not stall in an inbox
Most incident systems fail at the same point. The report comes in, and then a person has to remember to act on it. Certify takes that remembering off the human.
The usual problem
A near miss gets scribbled on a paper form that sits in a ute for a week. Or it gets emailed to a supervisor who is on leave. By the time anyone acts, the detail is fuzzy and the trail is thin. When the auditor asks how you closed it out, the honest answer is a shrug.
The reporting was never really the issue. The follow-through was.
One incident, minute by minute
- Minute 0
A worker reports a slip on the wet dock. They open the public link on a phone, add two photos, and submit.
- Minute 0
The HSE manager gets an email and a Teams ping. The record is already in the SharePoint list.
- Same day
A corrective action is raised and linked to the incident. An owner is assigned.
- Day 3
The action is still open. The owner gets a reminder. Their manager is copied.
- Day 5
The fix is done, approved, and the action closes. The incident is marked resolved.
- Audit day
The assessor asks about that slip. You open one record and the whole story is there.
Why it holds up
Nobody had to chase the action. The workflow did, on a schedule, and it escalated when the clock ran out. Every move was written down as it happened, so the record is not reconstructed after the fact. It is just what occurred.
The form, the photos, the action, the approval, the close. One thread, in your tenant.
"Every incident system I have watched fail did the reporting fine. It died at the follow-up. So that is the part we made automatic."