How to Write an Incident Report
When something goes wrong on site, the report you write in the next few hours is the record everyone relies on months later — the insurer, the regulator, and whoever's arguing about what happened.
Nobody writes an incident report while things are calm. It gets written after a near miss with a ladder, a cut that needed stitches, or a reversing ute meeting a client's fence — which is exactly why the format matters. A good report is written the same day, sticks to what happened rather than who's to blame, and captures the detail nobody will remember in six months. This guide covers what belongs in one, what to record and what to leave out, what happens after you file it, and which incidents you can't just file and forget.
Doing this job for a living? See job management in ServiceYak.
Why the report matters more than it feels like it does
In the moment, an incident report feels like paperwork about something that's already over. Its value shows up later, and by then it's too late to write a better one.
- Insurance. A claim made months after the event is assessed on the record made at the time. No record, weaker claim.
- Regulators. If a WHS inspector ever looks at your business, what they want to see is that incidents were recorded and something changed as a result.
- Disputes. Damage to a client's property, an injured subbie, a disagreement about what was said — the contemporaneous note beats everyone's memory.
- Patterns. Three near misses on the same task isn't three unrelated events. You only see that if all three were written down.
- Your people. A crew that sees near misses recorded and acted on reports the next one. A crew that sees nothing happen stops bothering.
Record near misses, not just injuries. They're free information about a failure that hasn't happened yet, and they're the cheapest safety data a small business will ever get. If your report book only contains injuries, it's telling you what already went wrong instead of what's about to.
What belongs in an incident report
| Section | What goes in it |
|---|---|
| Who reported it | Name, role and contact, plus the date and time the report was written |
| When and where | Date, time, site address and the specific location — "second floor, north stairwell", not "the job" |
| Who was involved | Everyone present: employees, subbies, the client, other trades, members of the public |
| Witnesses | Names and contact details, taken on the day while people are still on site |
| What happened | A plain factual sequence from before the event to after it |
| Injury or damage | What harm was done, to whom or to what, and what treatment was given |
| Immediate action | What was done straight away — first aid, isolating power, making the area safe, who was called |
| Conditions | Weather, lighting, surface, noise, time pressure, who else was working nearby |
| Equipment involved | Make, model, ID, its condition and when it was last checked or serviced |
| Evidence | Photos, the job record, delivery dockets, service history, CCTV if there is any |
| Contributing factors | What made it possible — a fact-finding section, not a blame section |
| Corrective actions | What changes, who owns it, and by when |
How to write it
- Make people safe first. First aid, emergency services, isolate the hazard, secure the area. The report comes after that, always.
- Take photos before anything is cleaned up. Wide shots for context, close shots for detail. This is the part that can't be recreated, and cleanup happens fast.
- Write it the same day. Within a few hours if you can. Detail degrades quickly, and a report written a week later reads like a reconstruction — because it is one.
- Stick to what happened. "The ladder moved and Sam fell approximately 1.5 metres onto the concrete" — not "Sam wasn't being careful". Facts survive scrutiny; opinions get pulled apart.
- Separate what you saw from what you were told. Attribute it: "the client stated that…". Mixing observation and hearsay is what makes a report unusable later.
- Get statements while people are there. A few lines in the witness's own words, signed and dated, is worth far more than your summary of what they said.
- Finish with actions, not conclusions. What will change, who's doing it, by when. That's the part that makes the report worth writing.
Leave speculation about cause and any admission of fault out of the report. Record what happened and what conditions existed; the assessment of why comes from the investigation, and your insurer will have views about anyone conceding liability in writing on the day.
What to report, and what can't just be filed
The safe default is that anything that hurt someone, could have hurt someone, or damaged property gets a report. In practice that covers:
- Injuries and illnesses, including the ones treated with a plaster from the ute.
- Near misses — the falling tool that missed, the trench that slumped after everyone was out.
- Hazardous conditions found — live wiring not on the drawings, unexpected asbestos, an unsafe access route.
- Equipment and vehicle incidents, including damage with no injury.
- Damage to a client's property or a third party's, however minor it looks at the time.
- Aggression, threats or theft on site — reported to police as well where it warrants it.
Some incidents are notifiable, meaning you have to tell your state or territory WHS regulator immediately and preserve the site until they say otherwise. Serious injuries, deaths and certain dangerous incidents fall into this category, and the exact list and the process are set by the regulator in your state. Find that list now and keep the notification number in your phone — the moment you need it is not the moment to start researching it.
Workers compensation reporting runs on its own timeframes and its own forms, and both differ by state. If someone is injured at work, contact your insurer and your state's workers compensation authority promptly rather than waiting to see whether a claim gets made.
What happens after it's filed
A report that goes in a folder and changes nothing is worse than no report, because it proves you knew. The follow-through is short:
- Work out what actually caused it. Keep asking why past the first answer. "He wasn't wearing gloves" is a symptom; "the gloves are in the other van and nobody restocks them" is the cause you can fix.
- Decide on the change. A different tool, a changed sequence, a physical barrier, restocking a consumable. Changes to equipment and process outlast changes to how careful people intend to be.
- Assign it and date it. One name, one deadline. Actions owned by "the team" are actions owned by nobody.
- Tell the crew at the next toolbox meeting. What happened, what's changing, no names attached. This is what makes the next near miss get reported instead of quietly cleaned up.
- Close it out and keep it. Record that the action was done, and keep the report. Insurers and regulators can ask about incidents long after everyone's forgotten them.
ServiceYak keeps job records, site photos and notes on the job they belong to, so when an incident report needs the context around it — who was on site, what was being done, what the job history was — it's still there months later instead of scattered across phones.
Frequently asked questions
How soon should an incident report be written?
The same day, ideally within a few hours of the site being made safe. Detail fades fast and photos become impossible once the area is cleaned up. If you can only manage rough notes and photos on the day, do that and write it up properly that evening — the notes made at the time are what the report is built from.
Do I need to report near misses if nobody was hurt?
Yes, and they're arguably the more valuable records. A near miss is a failure that happened to have a lucky outcome, and it tells you where the next injury is coming from. Businesses that only record injuries are working from a much smaller and much later dataset than businesses that record both.
Who has to be told about a workplace incident?
It depends on how serious it is and which state you're in. Serious injuries and certain dangerous incidents are notifiable to your state or territory WHS regulator immediately, with the site preserved until you're told otherwise. Injuries also trigger workers compensation obligations with their own forms and timeframes. Check the requirements for your state and keep the contact details somewhere you can find them in a hurry.
Should sole traders bother with incident reports?
Yes, for a different reason. As a sole trader the report is mainly for your insurer, your client and your own income protection claim — a documented account of what happened on site, written the same day, is far more useful than your recollection when a claim is assessed six months later.