# RCD log book for safety switch testing records (https://tradieforms.com.au/resources/rcd-log-book-safety-switch-testing)

Why a safety switch or RCD log book still matters, what each entry needs, and how to keep push-button and trip time results in one place the site can use. | Trade: Electrical | Template: national-rcd-test-record



Clients still say "safety switch log" more often than "RCD test record". Facility managers ask for the log book. Strata committees want the safety switch certificate. Site officers want proof the boards were checked. Different words, same job: show which residual current devices were tested, what happened when the button was pressed or the trip time was measured, and when they are due again.

This article is about that client-facing log: the language people search for, why paper books fail, who reads the file later, and how to migrate from cardboard to a durable PDF without losing history. It is not a fill-order walkthrough. For row-by-row completion on site, use the [RCD test record on-site guide](/resources/rcd-test-record-on-site-guide). For handing the finished file to a client, use [RCD test record handover to clients](/resources/rcd-test-record-handover-clients).

<KeyTakeaways>
  * "Safety switch log" and "RCD log book" are client language for the same durable in-service test trail
  * Paper, spreadsheet, and photo-only formats fail in predictable ways; the substance still has to survive the next reader
  * Facility managers, safety officers, and the next tester each need different clarity from the same log
  * Bridging from an old cardboard book to a PDF is a multi-visit change, not a single argument at the board
</KeyTakeaways>

Open the guided [national RCD test record](/forms/national-rcd-test-record) when you need a clean register for this visit. Browse [electrical forms](/electrical), or pair portable gear with the [national test and tag register](/forms/national-test-and-tag-register).

## What is a safety switch log book? [#what-is-a-safety-switch-log-book]

In conversation, people rarely ask for "an AS/NZS 3760 in-service RCD register". They ask for:

* The safety switch log book
* Safety switch test results
* An RCD test certificate
* The trip time report
* Proof the RCDs were done

Those phrases are search language and site language, not separate legal forms. Your job is to meet them with one durable register that answers the questions behind the words:

* Which devices did you test (fixed, socket, portable)?
* Was this a push-button check, a trip time test, or both?
* Which units passed and which failed?
* What happened to any fail before you left?
* When are the passes due again?

A summary email that says "all good" without a device list is not a log book substitute. Neither is a photo of a sticky note on a switchboard cover. The client may use soft words. The file still needs hard rows.

Installation certificates are a different story. A compliance certificate covers new or altered work at the time it is done. An in-service safety switch log covers periodic testing of devices already protecting people. Keep those packs separate so a completion cert is not filed as if it were this year's board check.

## Why the cardboard log book idea still exists [#why-the-cardboard-log-book-idea-still-exists]

Paper log books, wall charts, and board-mounted cards were never stupid. One place listed every device, the last test date, and the next due date. The idea survived. The cardboard often did not: books stuck in the office, missing pages between contractors, unread handwriting, and phone photos nobody can search.

Standards and WHS guidance care about the substance of that log, not the binding. AS/NZS 3760:2022 covers in-service safety inspection and testing of electrical equipment and RCDs, including documentation and tagging. The Safe Work Australia model code of practice on managing electrical risks expects workplaces to manage electrical risks and to keep records that show inspection and testing where that is how risks are controlled. SafeWork NSW points people to AS/NZS 3760 for methods and frequency. WorkSafe Queensland points workplaces back to the Electrical Safety Regulation and, where applicable, AS/NZS 3760.

So the question is not "do we still need a book". It is "can the next person show which safety switches were tested, by whom, with what result, and when they are due again".

## Format failure modes: paper, spreadsheet, photo, digital [#format-failure-modes-paper-spreadsheet-photo-digital]

Every format can work. Every format has a failure mode that looks fine on day one and collapses on day ninety.

**Paper book.** Works when someone fills it on the day and files a copy. Fails when the book never leaves the office or pages vanish between contractors.

**Spreadsheet.** Works when every device has its own row and the file is versioned against the job. Fails when three people edit three copies, or trip times live in a chat thread that never reaches the sheet.

**Photo of a board schedule.** Fine as a temporary reminder. Weak as the primary record: glare, crop, and unread handwriting destroy the trail, and photos do not force fail actions or next due dates.

**Digital register or PDF.** Works when hard fields are completed and the client gets a durable copy. Fails when the only "record" is a half-filled browser tab, or five nearly identical PDFs exist and nobody knows which one was handed over.

<GoodBad
  field="What survives to day ninety"
  badLabel="Collapses"
  goodLabel="Holds up"
  bad="
  <ul>
    <li>A book that never leaves the office</li>
    <li>Three people editing three copies of one spreadsheet</li>
    <li>A photo of a board schedule as the primary record</li>
    <li>Five nearly identical PDFs and no idea which was handed over</li>
  </ul>
"
  good="
  <ul>
    <li>Entries completed while the device is in front of you</li>
    <li>No fail left without an action</li>
    <li>A copy handed over before you leave, and one stored against the job</li>
    <li>The last log brought to the next visit</li>
  </ul>
"
  badNote="Every one of these looks fine on day one."
  goodNote="Habits, not formats. Any format works if these hold."
/>

Common slips: [common RCD test record mistakes](/resources/common-rcd-test-record-mistakes). Interval choices: [RCD test intervals and records](/resources/rcd-test-intervals-and-records).

## Who reads the log after you drive away? [#who-reads-the-log-after-you-drive-away]

Write for the next three readers, not only the person who signed the purchase order.

**The site or facility manager** wants to know the building is not running unprotected circuits and when the next visit is due. They often speak "safety switch" language. They need a short walkthrough of fails first, then next due dates, not a lecture on milliamps.

**The principal contractor or safety officer** wants a register that matches board labels and any tags if they audit the electrical file. Vague rows that say "kitchen RCD" when there are three kitchens fail this reader even if every trip time is neat.

**The next competent person** wants enough identity and history to retest the same devices without starting from a blank board schedule. Circuit IDs, board names, and fail history matter more to them than polished marketing wording on the cover page.

If any of those readers cannot match a row to a real safety switch, the log has failed its job. Specific locations and circuit IDs are not pedantry. They are how the log stays useful after you leave.

## What the log must still carry (without becoming a fill guide) [#what-the-log-must-still-carry-without-becoming-a-fill-guide]

You do not need a diary. You need a register that identifies each device, records whether this visit was push-button or trip time (or both), shows pass or fail with a real action on fails, and supports the next visit with testing basis and next due dates.

How those fields sit on each row, and the order to fill them while the tester is still in your hand, lives in the [RCD test record on-site guide](/resources/rcd-test-record-on-site-guide). Keep safety switch logs separate from portable appliance registers so a failed lead does not get lost inside a board RCD list. Appliance-side background: [test and tag register and AS/NZS 3760](/resources/test-and-tag-register-as-nzs-3760).

## Migrating from paper to PDF without a fight [#migrating-from-paper-to-pdf-without-a-fight]

Many workplaces still have an old log book in a cupboard. Bridging it carefully beats overnight replacement.

1. **This visit:** complete a clean PDF for the devices you actually tested. Hand that over as the current record for this visit.
2. **Leave the old book** with the client for history if they want it.
3. **Say it plainly:** "This PDF is today's safety switch log. The old book stays with you for earlier years."
4. **Next visit:** bring last visit's PDF as the start list. Add new devices. Retest due items. Update fails that were replaced.
5. **Over a few cycles:** the PDF trail becomes the working system. The cardboard book becomes archive.

What not to do: call their book illegal when the real issue is missing due dates; photograph the entire old book and call that the new system; overwrite fail history; invent trip times for button-only visits.

If they want a paper page in the plant room as well, that can sit beside the PDF. The durable copy still needs a place the business and the next contractor can find.

## Handover language that matches how clients search [#handover-language-that-matches-how-clients-search]

Lead with their words, then show the rows: "Here is the safety switch log for this visit." Walk fails first, then next due dates. Method and instrument detail only if they ask. More handover detail sits in [RCD test record handover to clients](/resources/rcd-test-record-handover-clients).

Keep each site's log separate even when the same portable RCDs move between buildings. A three-month construction tag is not an office cycle because the unit slept in the van. Filing rule: one site, one current log, clear ownership of shared gear. Cadence detail: [RCD test intervals and records](/resources/rcd-test-intervals-and-records) and [construction site test and tag every three months](/resources/construction-site-test-and-tag-three-months).

## What a durable safety switch log looks like in practice [#what-a-durable-safety-switch-log-looks-like-in-practice]

A client-ready log arrives as a named PDF or a printed register that matches it, not as a chat screenshot. Header shows who tested, where, and on what basis. Body lists devices one by one. End shows a signed declaration and notes about anything still open.

Tradie Forms can download that style of register from the [national RCD test record](/forms/national-rcd-test-record) so you hand over a clean PDF instead of a photo of cardboard. The competent person still owns the testing, the pass or fail judgment, and isolation decisions. The form is not a government document and is not affiliated with regulators.

For the fill path rather than the client-language and migration story, go to the [RCD test record on-site guide](/resources/rcd-test-record-on-site-guide).

<ResourceCta />

Start the [national RCD test record](/forms/national-rcd-test-record), browse [electrical forms](/electrical), or open the [handover guide](/resources/rcd-test-record-handover-clients) when the visit is done and the client needs the file explained.

## Official references [#official-references]

Check the [Standards Australia spotlight on AS/NZS 3760:2022](https://www.standards.org.au/blog/spotlight-on-in-service-safety-inspection-and-testing-of-electrical-equipment-and-rcds) for the scope of in-service testing of equipment and RCDs, the [Safe Work Australia model Code of Practice: Managing electrical risks in the workplace](https://www.safeworkaustralia.gov.au/doc/model-code-practice-managing-electrical-risks-workplace) for workplace electrical risk and record expectations, [WorkSafe Queensland testing and tagging of electrical equipment](https://www.worksafe.qld.gov.au/safety-and-prevention/hazards/electricity/electrical-products-and-equipment/testing-and-tagging-electrical-equipment) for state guidance that points to regulation and AS/NZS 3760, and [SafeWork NSW electrical inspection and testing](https://www.safework.nsw.gov.au/hazards-a-z/electrical-and-power/electrical-inspection-and-testing) for how NSW frames inspection and testing. Confirm how your state or territory applies these duties before you treat any log format as done.