Key takeaways
- Notification duties are triggered by the type and severity of the outcome rather than by whether anyone was actually hurt, so a near miss involving a serious mechanism can still be notifiable.
- Your immediate duties — making the area safe, preserving the scene and helping injured people — sit alongside the notification, not after it, and delay in either direction creates exposure.
- Preserving the scene does not mean freezing the site; it means not disturbing anything before the regulator or an inspector has had the opportunity to attend, except to make the site safe or assist an injured person.
- The person conducting the business or undertaking holds the primary notification duty, and a principal contractor on a residential site is usually that person for the works they control.
- Getting the notification decision wrong is expensive in both directions: a failure to notify can attract enforcement action, and repeated speculative notifications erode credibility with the regulator.
Most builders will only think about notification in the ten minutes after something goes wrong, when the answer matters and the facts are still moving. That is the wrong time to be reading guidance for the first time. The decision itself is not complicated, but it has to be made while you are also controlling the scene, getting an injured person care and keeping the rest of the crew out of the way.
This article deals only with the notification decision and the immediate duties that sit around it. It does not cover workers compensation, income protection, contractual claims or insurance — those are separate processes with separate timelines, and they start after the scene is stable.
The organising idea is simple: notification turns on what happened to a person or a structure, not on how dramatic it looked at the time. Two incidents can look identical from the far end of the site and be treated completely differently once you classify the outcome.
Why the duty exists before you think about whether to call
The work health and safety framework in NSW puts the primary duty on the person conducting the business or undertaking. On a residential site that is usually the builder, and where a principal contractor has been appointed, the principal contractor carries duties for the matters over which it has management or control. The point of the notification requirement is not record-keeping for its own sake. It exists because a serious outcome on one site is evidence of a hazard that probably exists on others, and the regulator cannot respond to a pattern it never hears about.
That is why the trigger is framed around the severity and type of outcome rather than around fault. A builder who did everything reasonably practicable still has to notify if the outcome falls into a notifiable category. The obligation is not an admission, and treating it as one is the most common reason notifications get delayed.
The duty is also not discharged by telling your insurer, your client or your head office. Those notifications are separate obligations serving separate purposes. If you are unsure how the duty sits alongside your other site obligations, the material on ladder safety on site sets out where management and control actually sit.
The notification decision, in order
- 1Attend to the personFirst aid, ambulance, making the immediate area safe. Nothing about notification changes this sequence.
- 2Classify the outcomeWork out what actually happened to the person or the structure, not what it looked like at the moment of the event.
- 3Check the triggerCompare the outcome against the categories the regulator treats as notifiable, using the current published guidance rather than memory.
- 4Notify if triggeredContact SafeWork NSW by the method it publishes for notifications, and record the time, the person you spoke to and the reference.
- 5Preserve and recordSecure the scene, take photographs and measurements, and record who was present before memories and conditions change.
What makes an incident notifiable in practice
The categories the regulator treats as notifiable are published and are updated from time to time, so the reliable habit is to check the current guidance rather than to work from a remembered list. What you are checking for is the outcome: whether a person has died, whether a person has sustained a serious injury or illness of a kind the guidance describes, or whether there has been a dangerous incident involving a substance, plant, structure or electrical event.
The dangerous incident category is the one builders most often miss. It captures events where nobody was hurt but something happened that could have killed or seriously injured someone — a structure or plant collapsing, an uncontrolled escape of a substance, an electrical event, or an incident that exposes a person to a serious risk. A pallet of bricks that lets go above a walkway, a suspended slab prop that fails under load, or a near miss with an energised cable all sit in territory that needs a proper assessment against the published categories.
Electrical events are worth treating carefully because the mechanism is often invisible after the fact. The guidance on electrical safety makes the point that contact with live parts and arc events can leave little physical evidence, which means the outcome to the person is often the only reliable trigger you have. If someone reports a shock, a flash or an unexplained trip on a temporary supply, get it assessed rather than filing it as a nuisance fault.
Exposure-driven illness is the other category that catches builders out, because it does not present on the day. Where workers are cutting, grinding or dry-sweeping crystalline silica-containing material, the relevant duties are set out in the guidance on WHS duties for silica, and a single overexposure event may or may not be notifiable depending on the outcome and the circumstances. The safe approach is to treat any event where exposure control has clearly failed as one to assess against the published categories rather than to decide on the spot.
The immediate scene duties that run alongside notification
Notification is not the first thing you do and it is not the only thing you do. Three duties run at the same time, and the order between them is dictated by risk, not by paperwork.
First, you make the area safe. That means eliminating the immediate danger of a further event — isolating plant, de-energising a circuit, propping or barricading a partially collapsed element, and keeping people out. Second, you provide assistance to any injured person, which in practice means first aid, calling an ambulance and, where a person is transported, recording where they have gone. Third, you preserve the scene so that the incident can be investigated properly.
Preserving the scene is the duty most often misunderstood. It does not mean the site stops. It means you do not disturb anything before the regulator or an inspector has had the opportunity to attend, except to the extent necessary to make the site safe, assist an injured person, or do something covered by a direction from an inspector. Photograph the conditions as found, note the position of plant and materials, and record who was on site and where they were standing. Once conditions change, that information is gone.
The mistake that costs the most. Tidying up before the scene is recorded. Clearing debris, moving plant or finishing a pour because the concrete truck is already on site destroys the evidence an inspector needs, and it looks like something other than housekeeping. Do the minimum to make the site safe, then stop disturbing things.
How to make the notification call itself
The notification is made to SafeWork NSW using the method the regulator publishes for that purpose. Do not rely on a phone number written on the back of an old site diary; check the current published method on the day. When you make the call, have the facts in front of you: what happened, where on the site, who was involved, what the outcome was, what you have done to make the area safe, and who the site contact is.
Keep it factual. You are not required to have completed an investigation before you notify, and you should not speculate about cause. What you are required to do is to give an accurate picture of the event as it is known at that moment. If facts change later, you update the regulator; that is a normal part of the process, not an admission that the first call was wrong.
Record what you did. The time of the notification, the method used, the reference number if one is given, and the name of the person you dealt with should all go into the site file the same day. This record is what demonstrates that you met the duty, and it is the first thing anyone reviewing the event will ask for.
If you are a subcontractor on someone else’s site, notify your own PCBU as well as the principal contractor. The principal contractor may hold the notification duty for the site, but your own duty to report internally is not extinguished by theirs. The verification habits described in the article on subcontractor WHS verification before start are worth applying here too: know who is responsible for what before the event, not after.
What an inspector will expect to see when they arrive
- The scene is secure and no further person can be exposed to the same hazard.
- Injured people have been treated and, where relevant, transported.
- Nothing has been moved except what was necessary to make the site safe or assist a person.
- Photographs and notes record the conditions as found, including the position of plant, materials and access.
- Witness details are recorded while those people are still on site.
- Plant, equipment and materials involved are identified and, where possible, isolated.
- The notification reference and the time it was made are recorded in the site file.
Worked example: a fall from a first-floor deck
A builder in western Sydney is running a two-storey addition. A carpenter is working on the first-floor deck, which has a temporary edge protection system installed and a fall arrest anchor point in use. Late in the afternoon, the carpenter loses footing near the edge, the edge protection catches him, and he ends up suspended briefly before being recovered by two other workers. He is shaken, has a graze on his forearm, and is walked to the site shed. He does not want an ambulance.
The supervisor on site makes a quick assessment. Nobody has been seriously injured, the harness did its job, and the edge protection is still standing. The instinct is to record it as a near miss in the site diary, have a chat about footing and move on. That instinct is half right and half dangerous.
What actually matters is the mechanism. A person fell from height and was arrested by a system rather than by the ground. The hazard that produced the fall is still present unless something changes, and the outcome to the person is not the only thing the regulator is interested in. The correct sequence is to secure the area, get the carpenter assessed by a medical practitioner rather than by the supervisor, photograph the edge protection and anchor point as found, and then check the current published categories to determine whether the event is notifiable. If it is, notify. If it is not, record the assessment and the reasoning in the site file so that the decision is documented.
Now change one fact. The same carpenter falls the same distance, the edge protection catches him, but he lands awkwardly and fractures his wrist. The outcome to the person has changed, and the event has moved into a category the regulator expects to hear about. The notification duty attaches at that point, and the scene duties — making safe, assisting the person, preserving the scene — apply with more force, not less, because the outcome is more serious.
Change another fact. The brick pallet on the scaffold above the walkway collapses and falls. Nobody is underneath. No person is injured, but plant or a structure has failed in circumstances that could have killed someone. That is the classic dangerous incident, and it is the one most often missed because the site diary entry says “no injuries” and everyone moves on.
The commercial reality of getting this wrong runs in two directions. A failure to notify an event that should have been notified surfaces later, usually when a worker’s condition worsens, when a claim is made, or when an inspector arrives for an unrelated reason and asks to see the records. At that point the absence of a notification is read as evidence of a culture, not as a one-off oversight. In the other direction, a builder who notifies everything indiscriminately — every graze, every dropped tool — trains the regulator to treat their calls as noise, which is not the position you want to be in when you have a genuine event to report.
Two incidents that look similar and are treated differently
| What happened | Why the treatment differs |
|---|---|
| A subbie steps off the edge of a first-floor deck and is caught by the fall arrest system | The mechanism is the same as a fall that injures someone, but what matters is the outcome to the person and whether the hazard is now controlled |
| The same subbie falls the same distance and fractures a wrist | The outcome is a serious injury to a person, which moves the event into the category the regulator expects to hear about |
| A brick pallet collapses on a scaffold with nobody underneath | No person was injured, but the collapse of plant or a structure can itself be notifiable depending on what it was and how it failed |
| Scaffold planks are found loose at the end of the day and nothing has fallen | This is a defect to fix and record, not a notification, unless something has actually collapsed or a person has been harmed |
What happens after the call
An inspector may attend, depending on the nature of the event. If they do, they will want to see the scene as it was, the records that support your account, and evidence that the notification was made promptly. They may issue directions, notices or requirements on the spot. Those directions are not optional and are not negotiable on the day; if you disagree, the mechanism to challenge them is separate from your obligation to comply.
If an inspector does not attend, your obligations do not end. You still need to preserve what you can, complete an investigation into the cause, and act on the findings. The investigation is where the value is: an event that is notified but never investigated will repeat, and the second time it may not be a near miss.
The investigation should also feed back into your safe work method statements. If the fall arrest system was being used but the footing was the issue, the SWMS probably needs to say something different about housekeeping on the deck. The article on SWMS templates for residential builders in NSW explains how to keep those documents live rather than filed, and an incident is the strongest prompt you will ever get to review one.
Where notification sits in your broader obligations
Notification is one obligation among several that attach to the same event, and confusing them is where builders get into trouble. Your duty to notify the regulator is separate from your duty to notify your insurer, separate from your duty to notify the principal or the client under the contract, and separate from your duty to report to your own board or head office. Different triggers, different timelines, different consequences for getting them wrong.
There is also a record-keeping obligation that runs underneath all of them. Site diaries, incident registers, training records and verification documents are what allow you to reconstruct what happened months later when a claim or a dispute is running. Builders who maintain those records well find the notification decision easier, because they have a habit of writing down what actually happened rather than what they wished had happened.
Keeping current with these obligations is part of staying licensed. The guide to how NSW builder CPD works explains how the annual requirements are structured, and the PointCPD course catalogue includes safety and compliance content that covers incident response in more depth than an article can. If you are new to the platform, the PointCPD home page is the place to start.
The habits that make the decision easy
Builders who handle incidents well tend to do the same few things before anything goes wrong. They know who on site is authorised to make the notification call, and they know who makes it when that person is off site. They keep the current published notification method somewhere the supervisor can find it without a phone signal. They have a blank incident record template on site that prompts for the facts an inspector will ask for. And they treat every near miss as an assessment against the notifiable categories, not as a note in the diary.
The decision itself will always be made under pressure, with partial information, while other things are demanding attention. What you can control is whether the people on site know the sequence, know where to find the current requirements, and know that tidying up before the scene is recorded is the one thing that will cost the most. Everything else follows from that.
Questions builders ask
What is a notifiable incident in NSW?
It is an event that falls into one of the categories the regulator treats as notifiable — typically a death, a serious injury or illness of a kind described in the published guidance, or a dangerous incident involving plant, a substance, a structure or electricity. The categories are published and updated, so check the current guidance rather than relying on memory. The test turns on the outcome, not on whether anyone was at fault.
Do I have to notify SafeWork NSW if nobody was injured?
Yes, in some cases. The dangerous incident category captures events where nobody was hurt but something happened that could have killed or seriously injured someone, such as a structure or plant collapsing or an uncontrolled electrical event. If nobody was injured, you still need to assess the event against the published categories. If it falls within one, notify.
How quickly do I have to notify?
The requirement is to notify promptly once you become aware that an event is notifiable, and the practical constraint is that you should not delay notification while you complete an investigation. Make the call as soon as you have the basic facts, then update the regulator if the picture changes. Check the current published guidance for the specific timing expectation.
Can I clean up the site before notifying?
Only to the extent necessary to make the area safe, assist an injured person, or comply with a direction from an inspector. Beyond that, you must preserve the scene so it can be investigated. Clearing debris or moving plant because a delivery is due destroys the evidence and looks like something worse than housekeeping.
What if I am not sure whether the incident is notifiable?
Assess it against the current published categories, and if you are still genuinely uncertain, notify and record your reasoning. The cost of notifying an event that turns out not to be notifiable is a conversation. The cost of failing to notify an event that was is enforcement action, and it surfaces at the worst possible time.
Does the principal contractor notify, or do I?
The person conducting the business or undertaking holds the primary notification duty, and on a residential site that is usually the builder. Where a principal contractor has been appointed, they carry duties for matters over which they have management or control. A subcontractor should also report internally to their own PCBU, because one party notifying does not extinguish the other’s duty.
Sources
- Rising fuel costs: what trades need to know about contracts, insurance and compliance · Building Commission NSW · 2026-04-28
- Electrical safety · Safe Work Australia
- Pools and pool safety · NSW Government
- WHS duties for silica · Safe Work Australia
Published 9 August 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.
