Skip to main content
Help Centre Support Contact
Partners
Create Free Account
Create Free Account Book a Demo

Incident Management

The Incident Lands on a Record That Already Knows Them.

Most incident systems start with a blank form and ask who the person was. In ComplyFlow the Worker involved already carries their employer, their induction, their licences, and the time they signed in, because it is the same record you prequalified and let through the gate.

Book a Demo See What It Covers
  • Safety & HSE
  • Site Supervisors
  • Legal & Insurance
  • Operations
One process for staff and contractors, on one record

What the Incident Module Does.

The ComplyFlow incident module records incidents, near misses, hazards, and injuries against the same record that holds the Worker’s employer, induction, licences, and sign-in. Every corrective action carries an owner, a due date, and a status, and the incident cannot close until they do.

  • Your incident types and your questions. Near miss, hazard, injury, environmental, property damage, and whatever else your business records, with your own form behind each.
  • Potentially notifiable incidents are contained. Flagged on submission, and their records are seen only by the security group you name until unrestricted. You must still notify the regulator immediately; ComplyFlow does not lodge the notice.
  • Actions are owned and dated, or they are not actions. Owner, due date, activity, files, and a status from Open to Closed, with the incident status moving as they close.
  • The same process for staff and contractors. An employee’s injury and a subcontractor’s near miss are handled the same way, on one record.

What It Covers

From the First Report to the Closed Action.

Everything below is in the product today and documented in the Help Centre.

Reporting It

Containing It

Closing It & Learning From It

Every item links to the Help Centre article that documents it.

How It Works

Three Screens From the Report to the Close.

Follow one near miss involving a subcontractor’s Worker.

The Supervisor Records the Facts, Not the Paperwork.

Description, shift time, date and time, and site, auto-saved as they type, so a supervisor interrupted halfway through has not lost it. The Worker involved is picked from the record, which means their employer, their induction, their licences, and the time they signed in are already attached without anybody typing them.

  • Auto-saved from the first field
  • The Worker’s employer and induction already known
  • Notification groups told before it is finished

Adding an Incident

Potentially Notifiable Means Restricted, Immediately.

Where an incident is flagged as potentially notifiable under the WHS Act, its record is visible only to the security group you name until it is unrestricted. That restriction is on the record, not on your notice to the regulator: you must still notify the regulator immediately after you become aware, and ComplyFlow does not lodge the notice. Your legal and insurance people get the reporter’s name and phone number, not a ticket in a queue. An insurer or external consultant can be given access to that one incident and nothing else. The Fortstone rollout put incidents on one record, and after a reportable fall from height the team reported that WorkSafe was satisfied with the system, forms, and steps taken.

  • Restricted on submission, not after review
  • Reporter’s name and phone in the alert
  • External users scoped to one incident

Notifiable Incidents, Legal

It Does Not Close Until the Actions Do.

Every corrective action carries an owner, a due date, an activity, and a status. The incident sits at Pending Actions until each one closes or is marked not required, then moves to Ready-to-Close. When somebody leaves, their open actions are transferred in bulk rather than going quiet in a departed user’s list.

  • Owner, due date, and status on every action
  • Status advances as the actions close
  • Open actions transferred in bulk when people move

Corrective Actions

What You Get

What Changes When the Incident Knows the Person.

The difference between an incident system and a contractor incident system is everything you do not have to establish after the fact.

No Investigation Starts From Zero

Who they work for, whether they were inducted, which licences they hold, and what time they signed in are all on the record already, because it is the record you prequalified.

Sensitive Incidents Stay Contained

A potentially notifiable incident is restricted to the security group that should see it, from submission. Containment after somebody has already forwarded it is not containment.

Actions That Cannot Quietly Lapse

An owner, a due date, and a status, with the incident held at Pending Actions until they close. An action list with no owner is a list of intentions.

One Process for Staff and Contractors

An employee’s injury and a subcontractor’s near miss are handled the same way. Two systems is how a contractor incident ends up outside the numbers.

Your Insurer Sees One Incident

External users are scoped to a single incident, so a broker or consultant can be brought in without being given the site.

Numbers You Can Take to the Board

Charts by type, tag, or question over a date preset, exported as PNG, PDF, or SVG, with the underlying data available through REST.

Questions

Questions About the Incident Module.

What makes a contractor incident different?

Everything you would otherwise have to establish afterwards is already on the record: who the Worker is, who employs them, whether their induction was current, which licences they held, and what time they signed in. In a standalone incident system all of that is typed in after the fact, by somebody working from memory.

How are potentially notifiable incidents handled?

An incident flagged as potentially notifiable under the WHS Act is restricted on submission, and its record is visible only to the security group you name until it is unrestricted. That restriction is on the record, not on your notice to the regulator: you must still notify the regulator immediately after you become aware, and ComplyFlow does not lodge the notice. The people in that group are emailed at once with the reporter’s name and phone number so they can act, not queue.

Can an insurer or an external consultant be given access?

Yes, to one incident only. External users are added per incident, so a broker, Client, or consultant can see what they need without being given access to the site or to anything else.

Can an incident be closed with actions still open?

No. The status sits at Pending Actions until every corrective action is closed or marked not required, then moves to Ready-to-Close. That is what stops an incident being filed while the thing that caused it is still there.

What happens to open actions when somebody leaves?

They are transferred in bulk to a new owner. Open actions belonging to a departed user are one of the standard ways a corrective action goes quiet, so moving them is a first-class operation rather than a workaround.

Do staff and contractors go through the same process?

Yes, and it is deliberate. An employee’s injury and a subcontractor’s near miss are recorded the same way on the same record. Running two systems is how contractor incidents end up outside the numbers the board sees.

Can we get the data out?

Yes. Charts export as PNG, PDF, or SVG, the corrective action list exports to CSV, and incident and injury data is available through the REST API into Power BI or your own reporting.

More Features

Three More Things ComplyFlow Does That Nobody Asks About in a Demo.

All WHS features

Walk One of Your Own Incidents Through It.

A 30-minute demo on an incident type you record today: your questions, your notification groups, who sees a potentially notifiable one, and how the corrective actions close it.

Book a Demo See Incident Management
  • ISO 27001
  • Hosted on AWS
  • Microsoft & Okta SSO
  • API & MCP
  • Data in Australia

Compliance you can prove, instantly.