How it works
One record, followed from the first report to the closed file
The sequence below is an incident, because most people know that one. An inspection, a permit, a contractor review or anything your team builds runs the same way.
Everything about it in one place
A record shows where it has reached, what has to happen next, and the one action open to the person looking at it. The investigation, the notifications, the actions raised and what was learned are all held against the record itself.
Nobody has to hold the thread together in a spreadsheet or a mailbox, because the record is the thread.
Start to finish
Seven steps. The first and the last involve a person, and most of what happens in between is the workflow doing what your organisation decided it should.
1. It is reported from a phone
A worker opens the incident form on their phone where the event happened, describes it, adds photographs and captures the location. If there is no connection the report is held on the device and sent as soon as there is one.
2. Severity and type are set
Whoever picks the report up confirms what happened and sets its severity and type. That answer decides what follows, because the workflow is built around it.
3. The workflow opens the investigation
For a serious event the record moves into investigation and the investigation is assigned. The immediate corrective actions are raised with owners and due dates, and the people who need to know are notified. Nobody has to remember the procedure, because the procedure is the workflow.
4. A notification to the regulator is recorded where one is required
Where the event is notifiable, the notification is recorded against the incident with what was reported, when, and by whom. What was sent stays attached to the record.
5. Actions are tracked and escalated
Each action sits in its owner list with a due date. Work that falls behind is escalated to the person accountable for it. You can require that every action is completed and verified before the incident may be closed.
6. The record closes on evidence
Closing asks for what your workflow says it must: the investigation findings, the actions verified as effective, the documents generated, and the approval of whoever your organisation decides must give it.
7. The history is there when it is asked for
Every change, and who made it and when, is kept with the record. When an auditor, a regulator or the board asks what happened and what was done about it, the answer is already assembled.
The rules that raise the duties along the way are yours to turn on and change.See how the obligation engine works.
Why holding it in one system matters
Keeping a record of the past is straightforward. Knowing what has to happen next, and proving that it did, is where separate tools come apart.
Entered once, used everywhere
The incident, the risk it relates to, the action it raised and the people involved are the same records across the platform. Nothing is re-keyed into a second system, and nothing drifts apart between them.
The follow-up does not rely on memory
Actions, reviews, notifications and escalations are driven by the rules you set. They happen whether or not the person who would have remembered them is in that day.
The evidence is a by-product
Because each step is recorded as it happens, the answer to what was required, when you knew and what you did is assembled already. It is not a project you run when somebody asks.
The same shape runs for every module, and for the ones your team builds.See the platform.
See Obliwise working on your own processes.
Bring one of your forms or checklists to the demo. We rebuild it in the platform with you, connect the workflow, and show the follow-up happening.