Key takeaways
- A notification and a register entry are two different obligations: notifying a regulator does not satisfy your duty to keep an ongoing record of the incident, the response and any corrective action.
- The register entry that matters is the one written on the day, because memory reconstructs events favourably to the person doing the remembering and a later account reads like it was written for a purpose.
- Near misses and toolbox talks belong in the same system as injuries, because they are the only evidence that a risk was identified and controlled before it produced harm.
- Photographs, inductions, plant and electrical records and training records only work as evidence if they can be tied to a date, a location and an incident or talk in the register.
- Retention should be driven by the longest relevant period, not by how long the job runs, because the claim or the prosecution can surface well after the last subbie has been paid.
Most builders handle the notification reasonably well. When something serious happens, the office gets a call, the regulator is notified within the period the Act requires, and the site is made safe. That part of the system, and the specific categories that trigger it, is covered in our article on notifiable incidents and the notification process. What this article deals with is the part that stays behind after the notification is lodged and the event is effectively over.
The register is the ongoing record. It is the running account of what happened, what was done about it, who did it, and when it was verified as done. It is also the record of the things that did not produce an injury: the near misses, the damaged tool, the load that slipped, the ladder that moved. And it is the record of what you told the crew and when, because a toolbox talk that is not recorded is indistinguishable from a toolbox talk that never happened.
It matters commercially because the register is usually the only thing left standing when a claim, a dispute or a prosecution arrives. By then the job is finished, the subbies have moved on, the supervisor is on another site, and the physical evidence has been carted away. A builder who can produce a dated, consistent, complete register at that point is in a completely different position from one who is trying to remember.
Notification and the register are separate obligations
Builders commonly conflate the two, and the conflation is expensive. Notifying a regulator is an event: it happens once, within a period, in a specified form, about a specified category of incident. Keeping a record is a continuing duty. It applies to every incident, not only the notifiable ones, and it continues after the notification has been acknowledged and the site has reopened.
Under work health and safety law the duty holder must keep records of incidents and of the response to them, and must be able to produce them. The precise retention period and the exact content required are set out in the legislation and the relevant guidance for your jurisdiction, and you should check the current requirement rather than rely on what was in the file on your last job. The practical test is simpler than the legal one: if a regulator asked you for the record of an incident that occurred on this site, could you produce it in a form that stands on its own?
A register that only contains incidents that were notified is a register with a hole in it. The near misses and the minor injuries are the leading indicators. They are the evidence that a risk was visible on the site before it produced harm. On the electrical side, Safe Work Australia’s guidance on electrical safety treats the identification of hazards and the control of risk as an ongoing process, not a one-off assessment, and the register is where that process leaves a trace.
The mistake that costs the most is reconstructing the register later. An entry written weeks after the event, in the neat language of a report, reads as though it was written for the purpose it is now serving, and it will be treated that way. A rough same-day entry with a date and a name is worth more than a polished account compiled after the fact.
What goes into a register entry, and in what order
An entry should be able to stand alone. Someone who was not on site, reading it a year later, should be able to understand what happened, what the conditions were, what was done immediately, what was decided as a corrective action, who owned it, and whether it was completed.
The order matters because it mirrors the sequence of events. Start with the facts of the occurrence: date, time, location on site, the task being performed, and who was involved, including witnesses and who was supervising. Then the response: first aid given, by whom, whether the person was sent for further treatment, whether the site was stopped, and what temporary controls were put in place. Then the corrective action: what was decided, who owns it, the date it is due, and the date it was verified. Then the close-out: a short statement that the action was completed and verified, with the name of the person who verified it.
Two things should be kept out of the entry. The first is conclusions about fault, because an entry that assigns blame will be read as a finding and will be used against you or against a subbie in a way you did not intend. The second is speculation about cause, for the same reason. Record what was observed and what was done. The investigation, if there is one, produces the analysis, and the register records that the analysis happened and what came out of it.
Photographs belong with the entry, not in a separate folder on someone’s phone. A photograph with no date, no location and no link to an incident is close to useless as evidence. If you take photographs of the scene, of the tool or plant involved, of the conditions and of the temporary control, they need to be downloaded, named and referenced in the entry on the same day. Practical completion is not the time to be chasing images off a supervisor’s phone.
Near misses are the part most registers are missing
A near miss is an event that could have caused harm but did not. The load that slipped off the forklift but landed clear. The guard that was missing on a grinder but was noticed before the tool was used. The trench that was left unguarded overnight and was found before anyone walked into it. These events carry the same information as an injury, without the cost, and that is exactly why they are worth recording.
The reason they are missing from most registers is cultural, not administrative. Crews do not report near misses if reporting them produces a lecture, a delay or a blame. The register only works if the person who reports a near miss is treated as having done the site a favour. That is a management behaviour, not a form design issue, and it is the single biggest determinant of whether your register has anything useful in it.
Practically, the near-miss entry does not need to be long. Date, location, what nearly happened, what was done at the time, and whether a control needs to change. If the answer to the last question is yes, it becomes a corrective action with an owner and a date like any other. If the answer is no, the entry still records that the hazard was seen and considered, which is worth having.
There is a direct line between near-miss reporting and the hazard categories that dominate residential work. Silica is a good example: Safe Work Australia’s guidance on the work health and safety duties for silica sets out the duty to identify the hazard, assess the risk and put controls in place. A register that records when dust controls failed, when a shroud was not connected, or when a worker reported visible dust is evidence that the duty was being actively managed rather than assumed.
How a register entry is built up over time
- 1Same-day entryRecord what happened, where, who was involved and what was done immediately, in plain language and without conclusions about fault.
- 2Photographs and physical evidenceCapture the scene, the tool or plant involved, the conditions and any temporary control before the scene is disturbed or cleaned up.
- 3Injury and treatment recordRecord the injury, the treatment given, who provided it and where the person went afterwards, without attempting a diagnosis.
- 4Corrective actionState the control decided on, who owns it, the date it is due and the date it was verified as done.
- 5Close-out entryRecord that the action was completed and verified, who verified it, and what changed in the SWMS or procedure as a result.
- 6Review at the next toolbox talkFeed the lesson back to the crew and record that the review happened, so the register shows a closed loop rather than a file.
Toolbox talks are records, not events
A toolbox talk is a short, regular briefing to the crew on a safety matter relevant to the work in front of them. The talk itself takes a few minutes. The record of the talk is what does the work later, and it should capture the date, the topic, who presented it, who attended, and any issue raised by the crew and what was done about it.
The last item is the one that separates a real record from a tick-and-flick sheet. An attendance sheet with names on it proves that people stood in a circle. An attendance sheet with a note that a worker raised a concern about the edge protection on level two, and that the concern was actioned on a stated date, proves that the site had a functioning feedback loop. That is the difference between a system and a form.
Toolbox talks also serve as the natural point to close the loop on an earlier incident. When a corrective action comes out of an incident or a near miss, the crew should be told about it, and the register should show that they were told. This is what makes the register a system rather than a file: the events feed the talks, and the talks feed back into the record.
Keep the talk records in the same system as the incident register, or at least in a system that can be searched alongside it. If a claim arrives about an exposure that happened over several months, the toolbox talk records are often the best evidence of what the crew was told and when. Scattered across three folders and a site diary, they are much harder to assemble into a coherent account.
What belongs in the register versus what sits beside it
| In the register | Beside the register |
|---|---|
| Date, time, location and a description of what happened | Site induction records and attendance sheets |
| People involved, witnesses and who was supervising the task | SWMS, JSA and procedure versions |
| Immediate response, first aid and whether the person was sent for further treatment | Plant, electrical and scaffold inspection records |
| Corrective action, owner, due date and verification date | Training and competency records for the people named |
| Near-miss entries and toolbox talk topics with date and presenter | Photographs and site diary entries |
The records that sit beside the register
The register does not stand alone, and a register that refers to documents nobody can find is a liability rather than an asset. The supporting records need to be kept in a way that lets you link them to a specific incident or talk.
- Site induction records. Who was inducted, when, by whom, and what they were told. A worker who was not inducted, or whose induction cannot be produced, weakens every other record that names them. Our site induction checklist for residential work covers what the induction itself needs to contain.
- SWMS, JSA and procedure versions. The version in force on the day of the incident, not the version in force at the end of the job. Version control is not bureaucracy; it is what makes the document referable.
- Plant, electrical and scaffold records. Inspection and handover records that can be tied to a date and a location. Our article on scaffold inspection and handover on residential sites sets out what those records need to show.
- Training and competency records. Tickets, licences and evidence of competency for the people named in the entry.
- Photographs and site diary entries. Dated, located and referenced from the register entry.
One category deserves particular attention on residential sites because it is so often handled informally. Asbestos is present in many older homes, and the guidance from the Asbestos and Silica Safety and Eradication Agency makes clear that the presence and condition of asbestos-containing materials must be identified before work disturbs them. If an incident or a near miss involves disturbing suspect material, the register entry should reference the identification and the control that was in place. If the identification was never done, that is the finding, and it is better to record it and fix it than to leave the register silent and hope.
Swimming pools are another residential-specific record that intersects with safety. NSW Government guidance on pools and pool safety sets out the requirements that apply to pool barriers and related safety measures, and where work is being done around a pool, the register should note any incident involving the barrier or the pool area, and any corrective action taken. It is a small detail that becomes significant if a child is involved and the question is what the builder knew and when.
Worked example: the entry that was written on the day
A builder in western Sydney is running a first-floor addition on an occupied home. On a Tuesday afternoon a subbie on the frame crew cuts a finger on a circular saw. The cut is minor, the subbie is taken to a medical centre by the leading hand, and the saw is taken out of service because the guard is not retracting properly. The job continues.
The builder’s supervisor does four things before leaving site that day. He writes a register entry covering the date, the time, the location, the task, the person involved and the supervising leading hand. He records the immediate response, including who took the subbie to the medical centre and that the saw was isolated. He photographs the saw and the area, downloads the images and names them with the date. And he raises a corrective action to have the saw inspected or replaced, with himself as owner and a due date.
Two days later the saw is replaced. The supervisor adds a close-out entry naming who verified the replacement and the date. At the next toolbox talk the following Monday, the incident is discussed with the crew, the saw issue is explained, and the talk record notes the topic, the presenter and the attendees.
Nothing about this sequence is elaborate. It takes perhaps twenty minutes across three sittings. What it produces, if a claim or a question arrives eighteen months later, is a dated account of what happened, a photograph tied to that date, a corrective action that was verified, and evidence that the lesson was passed to the crew. The alternative, a file assembled from memory after the fact, is worth very little and costs a great deal more to produce.
Retention, storage and who can get at it
Retention should be driven by the longest relevant period, not by how long the job runs. Work health and safety records, workers compensation records and contract records can each carry different retention requirements, and the longest one governs how long you keep the whole set together. Check the current requirement for each category rather than assuming a single number covers everything.
Storage needs to survive the job. The most common failure is a register that lives on a supervisor’s device or in a site folder that gets packed up at practical completion. If the records are not in the business system, they are at risk from the day the site is handed over. Cloud storage with a consistent folder structure, applied across every job, is the practical answer for most residential builders.
Access is the other half. The people who need to write in the register are the supervisor and the leading hands on site, and they need to be able to do it from a phone without a login process that discourages them. The people who need to read it are the builder, the office, and eventually a regulator or an insurer. Design the system so that writing is easy and the record is tamper-evident, with entries that show when they were made and by whom. An editable document with no audit trail is not a register; it is a draft.
Making it work across multiple jobs and multiple supervisors
The test of a register system is not whether it works on one job with one supervisor. It is whether it works across the business, when three jobs are running and the person who wrote the entry has moved on. That requires a standard structure, a standard set of fields, and a standard retention rule applied to every job by default.
It also requires that the register is reviewed, not just written. A short monthly review of the entries across all active jobs will tell you which sites are reporting near misses and which are silent, and silence is not the same as safety. A site with no near misses over a long period either has an unusually controlled operation or a reporting culture that has failed, and the second is far more common.
If you want to see where this fits in the broader picture of maintaining your licence and staying current, our guide to how NSW builder CPD works explains the structure and what counts. The PointCPD course catalogue covers the safety and compliance topics that sit alongside this one, and the PointCPD home page is the starting point for NSW builders working through their annual requirements.
The register is not the most interesting part of running a site. It is, however, the part that decides what you can prove. Build the habit of writing it on the day, keep near misses and toolbox talks in the same system, and retain the whole set for the longest period that applies. Everything else is administration.
Questions builders ask
Do I need to record every incident, or only the notifiable ones?
Every incident, and near misses as well. Notification is a separate obligation that applies to a defined category of serious incidents, but the duty to keep records covers all incidents and the response to them. A register that only captures notifiable events will be missing the leading indicators that show how risk was being managed on the site.
How long do I have to keep incident register records?
It depends on which category of record applies, because work health and safety, workers compensation and contract records can each carry different retention requirements. The practical approach is to identify the longest applicable period and retain the whole set together for that period. Check the current requirement for each category rather than assuming a single figure covers everything.
Can I keep the register as a spreadsheet on my laptop?
You can, but a spreadsheet that lives on one device will not survive the job, and it usually has no record of who changed what and when. A register needs to be written from site, by more than one person, and to show when entries were made. Cloud storage with a standard structure across every job is the practical answer for most residential builders.
What should a toolbox talk record actually contain?
The date, the topic, who presented it, who attended, and any issue raised by the crew and what was done about it. The last item is what distinguishes a functioning feedback loop from an attendance sheet. A list of names with no content proves people were present; it does not prove anything was communicated or acted on.
Should I record near misses if nothing was damaged and nobody was hurt?
Yes, and they are often the most useful entries in the register. A near miss carries the same information as an injury without the cost, and it is evidence that a hazard was identified before it produced harm. The main obstacle is cultural: crews stop reporting near misses if reporting them leads to blame or delay.
How do incident records connect to the rest of my safety documentation?
The register entry should refer to the supporting records that apply, including the SWMS version in force on the day, the induction record for the people involved, and any plant, electrical or scaffold inspection records. If those documents cannot be produced and tied to the entry, the register is much weaker as evidence. Keep them in a system that can be searched alongside the register.
Sources
- Electrical safety · Safe Work Australia
- Pools and pool safety · NSW Government
- WHS duties for silica · Safe Work Australia
- Asbestos in the home · Asbestos and Silica Safety and Eradication Agency
Published 16 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.
