Free AS/NZS 3760 test and tag register template
A ready-to-use spreadsheet for logging electrical safety tests on portable tools and equipment — the fields an inspector expects to see, already laid out. Download it, or skip the spreadsheet entirely and let SiteWarden keep the register for you automatically.
What's in the template
Each row is one test event for one item of equipment. The columns:
- Asset ID / description — a unique code and a plain description (e.g. KP-014, "Makita angle grinder").
- Location / site — where the item is normally used or stored.
- Test date and next due date.
- Visual inspection (pass/fail) and electrical test result (pass/fail).
- RCD tested (Y/N) — for equipment used with a safety switch.
- Tester name and notes (e.g. reason for a failure).
Open the CSV in Excel, Google Sheets, or Numbers — it's plain text, no macros, nothing to trust.
How to fill it out
- List every tool. Every item of portable electrical equipment on site gets a row and a unique asset ID.
- Test and record the result. A competent person visually inspects and electrically tests each item, then the date, result, and tester name go in.
- Set the next due date. Calculate it from the interval that applies to your environment — see the intervals guide.
- Remove failed items from service immediately and record the failure.
- Keep it available for audit — an inspector can ask to see it on the spot.
Frequently asked questions
What fields does a test and tag register need?
At minimum: an asset ID or description, the location or site, the test date, the result (pass/fail), the tester’s name, and the next test due date. Many registers also record the RCD (safety switch) test result and any visual inspection notes. The template on this page includes all of these as columns.
How often do tools need to be retested?
It depends on the environment, not a single fixed number. See our full breakdown in the test and tag intervals guide — construction sites are hostile environments and typically need 3-monthly testing, while lower-risk environments can go much longer.
What happens if a tool fails its test?
A failed tool should be tagged out of service, removed from use immediately, and either repaired and retested or discarded. Your register should record the failure and the date, so there’s a clear paper trail if an inspector asks what happened to it.
Do I need a licensed tester?
The person testing and tagging equipment needs to be a "competent person" as defined by the standard — in practice, someone trained in test-and-tag procedures, which may or may not require an electrical licence depending on your state/territory rules. Many companies use a specialist test-and-tag contractor rather than training staff in-house.
Can I just use this spreadsheet template, or do I need software?
The template works fine for a handful of tools. It gets harder to keep true as your tool count grows or tools move between sites — someone has to remember to open it and type in every test result. SiteWarden keeps the same fields automatically: log a test once against a tool, and the due date, status, and audit trail update themselves from then on. Use the template if you’re just getting started; move to software when the spreadsheet starts lying to you.
Get the register done for you
Leave your email and we'll send you the template plus a short guide to keeping your register audit-ready — and a free trial link if you'd rather it kept itself.
✓ Got it — check your inbox soon. No spam, ever.
That email didn't look right — give it another go.
More free resources
- What Is Test and Tag? A Complete AU/NZ GuideWhat test and tag means, who has to do it, and what the WHS Regulations actually require.
- Test and Tag Intervals by Environment (AU/NZ)How often tools need retesting on a construction site vs a factory vs an office.
- Free Tool Register & Sign-Out Sheet Template (CSV)Track who has every tool, on which site, without electrical test dates in the way.
When the spreadsheet stops being enough
A template works while one person maintains it and the tool count is small. It starts breaking down the same way every spreadsheet does: rows go stale, someone forgets to update the due date, and nobody notices a tool has failed until an inspector asks. SiteWarden keeps the same fields — test date, result, next due date — but writes them automatically from the same tap a worker already uses to take or return a tool, and prints an inspector-ready audit report in one click.