Incident Report App: What One Has to Do on Site

The incident apps I have watched fail did not fail on features. They failed because the person who saw the thing happen did not use them. The report came in two days later, typed by someone else, out of a conversation in a car park.

That is the standard to buy against. Not the length of the feature list, but whether the report gets made by the right person, at the right moment, in a form that is still useful in two years. Safe Work Australia’s figures released on 16 October 2025 put 188 traumatic injury deaths in 2024 alongside 146,700 serious workers compensation claims for 2023-24, more than 400 a day.⁴ Every one of them started as something a person saw.

This post is about what the app has to do. What belongs inside the document is covered in how to write an incident report that holds up, and which incidents the law says you must notify is covered in recordable versus reportable.

The Report Gets Made Where the Incident Happened.

The biggest quality difference between two incident records is how far the reporter walked before writing one.

At the scene, a person can pace out a distance, read the asset number off the machine, ask the bloke who saw it what he saw, and photograph the guard that was missing. Back at the site office an hour later, all of that is memory. Two days later it is a reconstruction, built in good faith out of what everybody has since been told.

So the app runs on the phone already in the pocket, and the first screen is short enough to finish standing up. ComplyFlow opens an incident with a short description, the shift time, the incident date and time, the date reported, the site, and one or more incident types such as hazard, near miss, injury or illness, property damage, environmental damage, or security.⁵ The detail sections come after the record exists, and the form saves as you work through them.⁵

The other half of the same problem is signal. Basements, lift shafts, tunnels, plant rooms, and anywhere past the last tower will drop a connection mid-form, and an app that throws away a half-written report when the bars go is worse than a paper pad, because at least the pad is still in your hand. ComplyFlow’s inspection app works to a complete and sync model for exactly this reason: the work is done on the device, then pushed up.¹¹

Photographs Belong to the Incident, Not to a Phone.

Photographs are the part of an incident record that ages best and gets handled worst.

Section 39 of the model WHS Act requires the person with management or control of the workplace to preserve the site, so far as is reasonably practicable, until an inspector releases it, along with the evidence of the occurrence, including electronic records and witness details.¹ SafeWork NSW puts the same duty plainly: do not disturb the scene until an inspector arrives or gives a direction, though you may still help an injured person and make the site safe.²

Preservation ends. Once the site is released, the scene goes back to being a workplace, and what survives of it is the set of photographs somebody took in the first hour. Whether they are any use depends entirely on where they were stored. A photograph in a supervisor’s camera roll leaves the business when he does.

The requirement, then, is that the camera sits inside the form rather than beside it. Each image attaches to the incident, carries the time it was taken, and can be pulled back up by a person who was not there, two years later, without asking anyone for their phone.

The Notification Question Goes to the Person on Site.

This is the feature that separates a reporting app from a filing cabinet with a login.

Under the model WHS Act a notifiable incident is the death of a person, a serious injury or illness, a dangerous incident, or, in the December 2025 model version, a violent incident.¹ Notice goes to the regulator immediately after becoming aware, by the fastest possible means, by telephone or in writing.¹ SafeWork NSW gives 13 10 50 for that call, staffed around the clock, and states the maximum penalty for failing to notify as AU$50,000 for a body corporate and AU$10,000 for an individual.²

The decision is made by whoever is standing there, usually a supervisor, often at night. A policy document does not reach that moment. A question on the screen does.

In ComplyFlow’s incident module, the potentially notifiable workflow asks the user whether the incident may be notifiable immediately after the record is created. Answer yes and the incident is restricted to the security group configured for it, that group is notified, and the user is shown the instructions your own business wrote, including who to ring, with a field for the number they can be reached on straight away.⁶

Two things stop going wrong at once. Nobody is guessing at a statutory definition in the dark, and the record stops being editable by everyone while the decision is still being made.

Everyone on Site Has to Be Able to Report.

An app that only the safety team can open collects only the incidents the safety team already knows about. That is not an incident data set; it is a record of what reached the office.

On a site running six subcontractors, the people most likely to see a near miss are not on your payroll. In ComplyFlow a contractor reports directly from their own account, choosing the client and site they are assigned to and entering the same details your staff would, and on finishing, the site contact for that site is notified automatically, or the notification manager where a group is triggered.⁷ The potentially notifiable prompt appears for them too.⁷

One limit is worth naming. Reporting from a contractor account needs an account, so a visitor or a delivery driver with no login still reports through whoever is running the gate. What the system can do for people outside it is keep them informed: external users can be added to notification groups and receive the email alert without any system access, and up to ten further addresses can be added to a single notification.⁸

Triage, Investigation, and Actions With an Owner and a Date.

Most incidents need somebody to look at them within the hour and decide how far this goes. A good app makes that state visible rather than leaving it in an inbox.

ComplyFlow tracks an incident through draft, draft and notified, submitted, pending actions, awaiting sign-off, ready to close, and closed. An incident carrying an open corrective action or an open investigation sits in pending actions until it is dealt with, and hovering over that status shows exactly what is outstanding.⁹

Corrective actions are where the loop closes, or quietly does not. An action with no owner and no date is a sentence in a document. In ComplyFlow each one is assigned to a named staff member who receives email and dashboard notifications, and it moves through open, in progress, partial, closed, or not required, with the activity undertaken and the date of that activity recorded on closure.¹⁰ An action nobody has touched for six weeks is visible rather than buried.

The Record Has to Survive Five Years and Still Be Producible.

Section 38 of the model WHS Act requires a record of each notifiable occurrence to be kept for at least 5 years from the day notice was given to the regulator.¹ That is a floor, not a filing plan.

The practical test is retrieval on demand. An insurer assessing a claim, a solicitor acting for an injured worker, or an inspector following up will ask for one incident, by date, and expect the whole thing: the sequence, the photographs, the investigation, the actions, and who was notified and when.

Look for export that produces the record rather than a screenshot of it. ComplyFlow can attach the incident report PDF to the initial notification and to any forward of it, so the version that went out at the time is itself part of the record.¹² Ask in the demo how notification history is stored, because who knew what, and when, is usually the contested part.

Near Misses Are the Part That Pays for the App.

Everything above is about the incidents you must record. The value sits in the ones you do not have to.

Safe Work Australia’s measuring and reporting report describes two ways a business learns about its hazards: proactively, from the risk register, from inspections and audits, and from industry experience, or reactively, the hard way, only after a costly injury.³ It defines a high potential incident as a near miss or lesser injury that had the potential to cause a permanently disabling one, and makes the point that analysing those uncovers what went right as well as what went wrong: quick thinking, a control that held, or sheer luck.³

That only works if near misses are actually entered, which comes straight back to who can report and how long the form takes. Once they are in, the pattern matters more than any single record. ComplyFlow charts incident data by incident type, tag, or question over a chosen period.¹³ Three strikes against the same reversing truck in one month is a control problem you can still fix cheaply, and catching it is what a safety manager is there for.

What to Ask For in the Demo.

Six requests, in the order I would make them. Have the vendor do each one on the screen rather than describe it.

1. Report an incident on a phone in flight mode, then reconnect and show me the record.
2. Take three photographs inside the form and show them attached to the incident, with their times.
3. Show me the notifiable prompt, who gets notified, and where our own instructions and phone numbers go.
4. Have a subcontractor, not a staff member, report an incident, and show me who is notified.
5. Raise a corrective action, assign it, and show me the report of everything open past its date.
6. Produce the full record of an incident from two years ago, exactly as an insurer would receive it.

Where the answer to any of them is a roadmap, you have your answer on that item.

The App Is Judged by the Report Nobody Wanted to Write.

Picture the record you actually want, then ask whether the app in front of you would ever produce it. A ladder slips while nobody is on it. An apprentice, on his own phone, standing where it happened, files four minutes’ worth: what he saw, two photographs, and the ladder’s asset number. Nobody is hurt, so nothing compels the report. It gets written because the form is short, it is on the thing in his pocket, and he is allowed to file one.

That is the test. Not whether the app can capture a fatality, which any of them can, but whether it captures the near miss nobody had to report. The serious incidents reach you regardless. The ones that tell you something while there is still time are the ones an app either makes easy or quietly loses.