"Wiring issue" is not a defect note. It does not tell the customer what to fix, does not tell the office what to quote, and does not tell the next electrician where to look. Six months later it does not tell anyone what you actually saw.
This guide covers how to classify a defect, how to word it, and what evidence to keep with it. For the conversation side of the same job, see how to explain a CCEW to your customer.
Document defects in your job record while you are still on site. The NSW CCEW process covers how a defect sits alongside the certificate, which you complete in the BCNSW eCert portal. Read more in the NSW CCEW guides.
Immediate danger
Make safe before certifying. Work stops.
Non-compliant
No immediate danger, but departs from current standards. Rectify before completion.
Note for later
Functional and safe, worth recording for the next upgrade.
How should you classify a defect?
Classify by the action the defect forces, not by how alarming the words sound. Three bands cover almost every finding, and each one has a different consequence for the certificate.
Immediate danger means someone could be hurt before the issue is fixed - exposed live parts, missing or ineffective earthing, a failed safety switch on a circuit in service. Work stops and the installation is made safe before you certify anything as compliant.
Non-compliant, no immediate danger covers departures from current standards that are not going to hurt anyone today. Older wiring methods that were acceptable when installed, undersized or inappropriate protection, poor terminations that are still mechanically sound. These get recorded, explained, and scheduled.
Note for later is the band people skip, and it is the one that protects you. A functional installation with poor labelling, no working space at the board, or an undocumented modification is worth a written line even though nothing needs to happen this week.
The band matters more than the label. Whatever vocabulary your business uses, be consistent across your certificates so an office reviewer can sort a defect list without ringing you.
Where the defects actually are
Run the same route every time and the misses drop. Start at the main switchboard and work outward.
At the board, check labelling, whether protective devices suit the connected loads, and whether anyone has been in there without documenting it. Signs of overheating, corrosion, and physical damage are all visible before you connect a tester. Missing barriers and inadequate working space belong in your notes even when the installation is functioning.
Through the installation, follow cable routes to junction points and terminations. Penetrations through structural elements are the classic damage location, along with anywhere a cable has been pulled hard or supported badly. Check that cable types actually suit the application rather than what was on the van that day.
At outlets and switches, verify earthing connections, polarity, and mounting. Overheating marks and loose connections at accessories are common and easy to photograph.
On the earthing system, check the electrode connection, main earthing conductors, and equipotential bonding. Corrosion at the electrode connection is a recurring find on older properties and a genuine safety issue rather than a paperwork one.
Writing a defect note that still makes sense in six months
The note has to survive being read by someone who was not there. Four elements do that work.
The component. Name it and identify it. "Circuit 3 RCD" beats "a safety switch".
The location. Precise enough that another electrician walks straight to it. Room name, circuit number, equipment identifier, distances where they help. "Plant room" is not a location on a multi-building site.
The observed condition. What you actually saw or measured, in technical but plain terms. "Main earthing conductor shows corrosion at the connection to the earth electrode" is a fact. "Earthing not up to standard" is an opinion with no content.
The required action. Specific and quotable. "Replace the damaged cable section with appropriate cable, ensuring support and protection through the wall penetration" tells the customer what they are paying for. "Repair required" does not.
On standards references: a correct, current clause reference makes a note harder to argue with, and a half-remembered one makes it easier. If you have the current standard open, cite it. If you are working from memory, describe the condition instead. An accurate description of what you observed is always defensible; a wrong clause number invites someone to dismiss the whole finding.
What testing tells you before you write anything
Suspected defects become recorded defects once a test backs them up. Note the equipment used, the conditions, and anything that limited the result.
Insulation resistance testing surfaces cable damage, moisture ingress, and deteriorating insulation. Record the test voltage alongside the reading - a result without its voltage is not much use to the next person.
Earth continuity and fault loop impedance testing verifies the protective earthing path. High readings point at loose connections, corroded joints, or conductors that were never adequate.
RCD testing has to cover operation and timing, not just whether it clicks. Record any device that fails to operate or operates outside acceptable parameters, and remember a failed test may be telling you about the connected circuit rather than the device.
Polarity testing catches reversed connections that indicate either poor workmanship or an undocumented modification upstream. For the wider picture on safety switch testing, see electrical safety switches and CCEW testing.
Where a limitation stopped you from testing something - an occupied tenancy, a load that could not be dropped, an inaccessible section - write the limitation down. An untested circuit recorded as untested is honest. An untested circuit left blank looks like it passed.
Can you issue the certificate when you have found defects?
It depends on whether the defect sits inside the work you are certifying and whether it is an immediate danger. Those two questions decide it, and the answer is not the same for every finding on the list.
An immediate danger inside your scope stops certification until the installation is made safe. That is not a paperwork judgement. Non-compliant items inside your scope generally need rectification before the work is complete, and the certificate should reflect the finished state rather than the state you found. Pre-existing issues outside the work description are usually recorded and reported to the customer rather than treated as blockers on your certificate - you did not create them and you are not certifying them, but you did see them.
The failure mode to avoid is silently widening or narrowing your scope to make the paperwork easier. Certify the work you described, report what else you found, and keep the two clearly separated on the record.
Prioritising remediation for the customer
Customers make better decisions when the list is ranked rather than dumped. Sort findings into must fix now, fix soon, and note for later, and explain the consequence attached to each band rather than the standard behind it.
Where a list is long or the budget is tight, stage the work in a sequence that puts safety first and avoids doing the same access twice. Point out where addressing several items in one visit is cheaper than three separate call-outs - that is a genuine saving, not a sales pitch.
Give the customer the findings in writing, not only verbally at the board. If they choose to defer non-critical items, note that decision in the job file. That record is what protects you if the deferred item causes a problem later.
Schedule the re-inspection where remediation was required, and make sure the certificate documentation reflects the work as completed rather than the state before the fix.
Keeping the evidence with the job
Photos, test results, and defect notes are only useful if they stay together and stay findable. Capture them on site rather than reconstructing them in the van.
Take photos while the board is open, with enough context to show where the component sits. Attach them to the job record rather than leaving them in the camera roll where they get lost in a month of site photos. Enter test results while the tester is still connected, then check the eCert details before submission.
The records supporting a certificate can be requested long after the job. Systematic storage against the job reference is the difference between answering a query in two minutes and spending an afternoon in a photo library. The CCEW record keeping and workflow guide covers how to structure that at a business level.
Keep defect notes, photos and test results with the same job record as the eCert confirmation so you can trace what was found at the board.
Next steps
Before you issue the certificate, check every defect note names the component, the location, the observed condition, and the required action. Pair each one with the photo or test result that explains it.
Open the BCNSW eCert portal or browse other Australian trade forms. See common CCEW mistakes for the errors that send certificates back.
Official references
Check NSW electrical compliance requirements, the BCNSW eCert portal, Service NSW submit a CCEW, SafeWork NSW electrical inspection and testing, and the Standards Australia Wiring Rules for current requirements before relying on this guide for a live job.
