Anyone reports it in a minute. Every follow-up is chased to the end.

Incidents, hazards, near misses and good catches come in from a phone, a code on the wall, an email or an anonymous link. Investigations use the method that suits the event, notification deadlines are tracked on the record, and every action is closed on proof.

Works on its ownIncident management works on its own, so if it is all you need it is all you buy, and every other part of Obliwise stays optional.

What incident management includes

Everything below comes with it, ready on the first day and yours to change. 37 capabilities

  • Quick report from a phone

    Anyone reports an incident in a minute, one short question per screen, with photos and location.

  • Investigation methods

    Investigations use five whys, ICAM or a reconstructed timeline, sized to the event.

  • Regulator notifications

    When you decide to notify, a draft is prepared for a person to approve, and the deadline and trail stay on the incident.

  • Actions closed on proof

    An action closes only once the fix is checked by someone.

  • Incident types with their own details

    Each type of event collects the details that matter for it, and one event can carry several types.

  • Hazards

    Hazards are logged before anyone is hurt and promoted into the risk register with their history.

  • Observations and good catches

    Near misses, good catches and unsafe conditions are captured and followed up like any other report.

  • Incident workflow

    Every record moves through clear steps with the next step and its owner shown on the record.

  • People on the incident

    The owner, manager, reporter, investigator and everyone notified are shown together and changed in place.

  • Investigation diagrams

    Bow ties, fishbones, fault trees, event trees and HFACS are drawn on screen and kept with the incident.

  • Witness statements

    Witnesses give their account through a guided link in their own words and language, and it is kept with the incident.

  • Weather and site context

    Weather and site conditions at the time of the event are pulled in automatically.

  • Similar earlier events

    While an investigation is open you see earlier events that look similar.

  • Lessons shared

    Lessons reach the people who need them and resurface when similar work is planned.

  • Notification thresholds

    Each incident is checked against notification thresholds written for your jurisdiction, each citing its source.

  • Automatic threshold checks

    Thresholds are checked the moment an incident is reported or changed, so nothing waits on someone opening the right tab.

  • Notifiable incident wizard

    A guided set of questions works out whether an event is notifiable and starts the clock if it is.

  • Regulator interactions

    Inspector visits, notices and correspondence with regulators are tracked to closure.

  • Anonymous reporting

    People report without giving their name, keep a tracking code and talk back and forth with the handler.

  • Report by email

    Emails sent to your own reporting address become draft reports for someone to check.

  • Duplicate reports merged

    Likely duplicates are flagged and merged into one record that can be undone, with everyone involved told where it went.

  • Tell the assistant what happened

    People describe an event in their own words and the report is filled in for them to check.

  • Actions register

    Every corrective action from every module lives in one register with an owner and a due date.

  • Due dates moved by request

    Owners ask for more time and the right person approves or declines it.

  • Recurring work

    Regular tasks are set up once and raised on schedule.

  • Many actions at once

    Assign, reassign or close many actions in one step, with a preview first.

  • Late work escalated

    Overdue work goes to the person accountable for it automatically.

  • Calendar of what's due

    A calendar shows what is due across teams and sites.

  • Evidence required to close

    You choose which actions need evidence attached before they can close.

  • Effectiveness review

    Important fixes are re-checked after a set time to confirm they still work.

  • Witness audio transcribed as a draft

    A recorded account is transcribed as a clearly labelled draft that a person corrects and the witness signs.

  • Lesson bulletins drafted for you

    A lesson bulletin is drafted from the investigation for a person to review and approve.

  • Lessons shared beyond your workspace

    You choose to publish de-identified lessons to other workspaces or your industry, reviewed before release and switched on separately.

  • One report split into two

    A report that covers two events is split into two records, with its history kept on both.

  • Records converted between types

    A report becomes a hazard, an incident or another record type without anyone typing it again.

  • Notifiable events beyond workplace safety

    Notification checks also cover environmental, dangerous goods and care-sector regimes.

  • Clinical incident management

    Healthcare providers record and investigate clinical incidents with the datasets their sector requires.

Where it works

In the browser on any computer, and in these places too.

  • On the phone

    In the iOS and Android apps, with or without signal.

    • Quick report from a phone
    • Actions closed on proof
    • Incident types with their own details
    • Hazards
    • Observations and good catches
    • Incident workflow
    • Lessons shared
    • Duplicate reports merged
    • Tell the assistant what happened
    • Actions register
    • Late work escalated
    • Evidence required to close
    • Witness audio transcribed as a draft
    • Clinical incident management
  • Without an account

    Through a link or a code that anyone can open.

    • Quick report from a phone
    • Witness statements
    • Anonymous reporting

Worked example: a forklift clips a racking upright

Nobody is hurt, but the racking is damaged in a busy aisle.

  1. Step 1: Reported from the floor

    The operator reports it on their phone with two photos and the location. It takes under a minute.

  2. Step 2: The right people hear about it

    The warehouse manager is told straight away. The event is checked against your notification thresholds and the result is shown on the record.

  3. Step 3: Investigated to the right depth

    The investigator runs a five whys, adds a short timeline and sees two earlier events in the same aisle.

  4. Step 4: Actions closed on proof

    New racking guards and a change to the traffic plan are raised as actions. Each one closes only when the photo evidence is attached and checked.

Start with incident management on its own.

Tell us how many people and locations you have. We will set it up with you, using your own forms and terms, and you add anything else only if you want it.