RCD Test Record

Upload your logo if you want it on the finished PDF. It lands top right on the downloaded record.

Your trading name as the client and site file should recognise it. Use ABN lookup to fill the business name and ABN together when you have either value.

Optional trading number. ABN lookup fills the matching business name when you enter a valid ABN.

The person who did the testing. This is the name the declaration can mirror later with Same as tester above.

Fill when the client, principal contractor, or site procedure wants a licence or competency reference on the record. Leave blank rather than inventing a number.

Contact number for follow-up or retest bookings. Useful when the site will call you about a fail or a next-due visit.

The business or person you tested for. On construction sites this is often the principal contractor or the site manager who keeps the electrical file.

Your work order, purchase order, or site job number. It also appears in the PDF register summary, so use the same reference you put on photos and other records for this visit.

Use address search for the site address. It fills the street line, suburb, state, and postcode for Australia-wide sites. Confirm the result against the site entry or job sheet when the postal address differs from the worksite name.

Make, model, and serial of the RCD tester used, for example Metrel MI 3152, SN 21054411. Take it from the instrument label or your calibration sheet so the next person can see which kit produced the readings.

Last calibration or verification check for that instrument. The form will not accept a future date. It also appears in the PDF register summary when filled.

The date this record covers. Use Today or Yesterday on site. No future date is accepted. This is the register date on the finished PDF header, separate from each row's test date when you retest over more than one day.

The standard or site procedure used for the work. Common picks are AS/NZS 3760:2022, AS/NZS 3760:2022 + site procedure, or workplace and electrical safety regulations. You can type a site-specific basis. State the basis that matches the checks you actually did so the next tester does not treat a push-button visit as a full trip-time round.

Suggests the next-due date when you add a new register row: 6 months, 12 months, or 2 years. Push-button tests are often more frequent than trip time tests. Treat the suggested next-due date as a helper and check it against this visit type and environment before download.

The register itself is optional if you open the form and download with no RCDs, but every row you add has its own required fields. Leave unused rows out rather than adding blanks.

What one row is. One RCD or circuit you tested on this visit: fixed board RCD, socket RCD, or portable RCD on a lead set.

RCD ID / Circuit and Location - required on each row. Use a label the next person can walk to, including the board name on multi-board jobs. MSB RCD 2, circuits 5-8 at Main switchboard beats kitchen RCD when the site has three kitchens.

Description - optional detail about what the RCD protects, for example Main switchboard RCD or Portable RCD on extension set.

RCD Type and Rating - required. Type is Fixed RCD, Socket RCD, or Portable RCD (or a custom value). Rating is the residual current in mA from the device face, such as 30. Type and milliamps matter when someone later judges a trip result against the right limit.

Push-Button Test - required. Mechanical trip on the test button: Pass or Fail.

Trip Time - optional in milliseconds at rated current, such as 24. Leave it blank for a push-button-only check. Enter >300 when the instrument reports that the device did not trip inside its measurement window. Do not invent a trip time from memory or from a photo of the screen later.

Result - required Pass or Fail for the overall outcome of this row. Mark Fail when push-button, trip time, or both failed against the basis you are using.

Test Date - required. Defaults to today on new rows and can carry forward from the previous row. Use Today while you are still at the board.

Next Due - required when Result is Pass. Suggested from the default retest interval and the test date. Edit it so it matches the interval for this visit type and environment. A pass with no next-due date leaves the site guessing when the device is up again.

Action taken and failure details - required when Result is Fail. Action options include Isolated and tagged out, RCD replaced, Scheduled for repair, and Client notified. Put what failed and what you did in the note, for example that trip time exceeded the applicable limit and the unit was isolated pending replacement. Optional fail photos are available when you want supporting evidence.

Duplicate copies description, type, rating, and location. It clears the RCD ID, result, test readings, dates, actions, and notes so you do not reuse another device's outcome by accident. New rows can also carry the previous location and test date.

The PDF shows each RCD as a stacked record rather than a wide table: identity and result on the first line, button and trip readings with dates on the second, action and notes on the third. Long registers continue across pages with one footer and page count.

Anything the client or site file should see at record level, such as RCDs replaced on site or a portable unit isolated and tagged out. Keep per-device detail on the row; notes are for the visit summary. The PDF notes field is limited to about 220 characters, so put long failure narratives on the row that failed.

Who is signing the record. Use Same as tester above when the signatory is the tester named in Business.

Copies Tester Name into Name and locks the name field while it is on. Turn it off if someone else is signing.

The date you sign. Today and Yesterday shortcuts are available. No future date is accepted.

Sign on screen, upload an image, or use your saved signature. Add it after the register is complete so you are not signing a half-finished fail list.