Workflow Template
RCD / safety switch test record Workflow
Captures RCD/safety switch test results submitted by an electrician, notifies the client of a Pass, or manages the Fail path with a repair-and-retest task (looping up to 2 times) before notifying the client of the final outcome.
Electrical contracting businesses and facilities teams responsible for periodic RCD/safety switch testing need a consistent, auditable way to capture results across multiple sites and technicians. This workflow captures test data submitted by an electrician through a request form, records a Pass or routes a Fail into a repair-and-retest cycle involving the electrician for up to two additional attempts, and keeps the client informed at each key outcome. Admins and members within the workspace can monitor every record's status and timeline as it moves from Submitted through to a final Passed or Failed outcome.
Business Outcomes
- Reduces manual chasing of test results and client notifications through automated emails at each outcome
- Improves visibility of failed RCDs and their repair status through consistent record statuses and timelines
- Supports faster turnaround on repairs with a time-bound retest task assigned directly to the electrician
- Helps standardise the data captured for every RCD test, including trip times, ratings and protected circuits
- Makes it easier for teams to track outstanding retests and final outcomes across multiple sites from one workspace
Workflow Steps
Steps
- 1Create RCD Test Recordcreate record
Registers the submitted RCD test as a record.
- 2Set Status to Submittedupdate record
Marks the record status as Submitted immediately after creation.
- 3Route on Test Result
Branches the workflow based on whether the RCD test passed or failed.
test_result: "Pass"→Set Status to Passedtest_result: "Fail"→Set Status to FailedDefault→End - 4Set Status to Passedupdate record
Marks the record status as Passed after a successful test.
- 5Email Client Pass Resultsend email
Emails the client the test result and the next test due date.
- 6Set Status to Failedupdate record
Marks the record status as Failed after an unsuccessful test.
- 7Email Client Fail Noticesend email
Emails the client that an RCD failed its test and the circuits it protects may be unprotected until replaced.
- 8Repair and Retest Taskcreate task
Assigns the electrician a task due in 5 days to record the repair made and the retest result.
- 9Save Retest Resultupdate record
Persists the repair notes and retest result to the record.
- 10Route on Retest Result
Branches based on whether the retest passed or still failed.
retest_result: "Pass"→Set Status to Passed After Repairretest_result: "Fail"→Loop Back to ElectricianDefault→End - 11Loop Back to Electricianrestart from step
Sends the record back to the electrician for further repair if the retest still fails, up to 2 times.
- 12Set Status to Passed After Repairupdate record
Marks the record status as Passed after the retest succeeds.
- 13Email Client Repaired Pass Resultsend email
Emails the client that the RCD was repaired and passed its retest, with the next test due date.
Fields
- Electrician Name*
- Client Name*
- Client Email*
- Site Address*
- Switchboard Location*
- Number of RCDs Tested*
- +11 more fields
Forms
RCD & Safety Switch Test Form
14 fields
Data Views
RCD Test Records
client_name, site_address, switchboard_location, num_rcds_tested +3 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
What does this workflow record for each RCD test?
Each submission creates a record with a reference number, a status, and a timeline capturing every step taken. The initial form data — electrician, client, site, switchboard location, RCD ratings, trip times, circuits protected, photos, next test due date and result — is saved to the record, along with the repair notes and retest result entered later by the electrician.
Who is involved in the RCD test and repair process?
An electrician submits the initial test result through the request form, and is also assigned the repair-and-retest task if the result is a Fail. The client receives email notifications at each key outcome — Pass, Fail, or Passed After Repair — without needing an account. Workspace members and admins can view record status and progress at any point.
What happens when an RCD test fails?
When the Result is Fail, the record status is set to Failed and the client is emailed a notice that the RCD failed and the circuits it protects may be unprotected until replaced. The electrician is then assigned a Repair and Retest task, due in 5 days, to record the repair made and the retest result.
How does the repair-and-retest loop work?
After the electrician submits repair notes and a retest result, the workflow routes on that result: a Pass sets the record status to Passed After Repair and triggers a client email with the next test due date. A continued Fail sends the record back to the electrician for further repair, and this loop can repeat up to 2 times before the process reaches its final outcome.
How do we change this workflow to suit our own testing process?
A workflow can be adjusted by describing the change in plain English or by editing its steps directly in the workflow editor, and earlier versions are kept for reference. This makes it possible to adjust task deadlines, notification wording, or the number of retest loops without a development project.
Can we track outstanding and overdue retests?
Table views and dashboards show records grouped by status, so records currently at Failed or awaiting a repair task are easy to identify. Since the Repair and Retest task carries a 5-day due date, teams can monitor which records are approaching or past that deadline.
Does the client need to create an account to receive results?
No — clients receive their test result and any relevant next steps by email at each key stage of the process. They take part entirely through emailed notifications without needing to log in or hold an account.
How quickly can this workflow be put into use?
As a ready-to-use template, a workspace can publish it and start running live RCD test submissions within minutes. There is no installation or development project required before the process is operational.
Ready to use this workflow?
Create a free account and customise this workflow for your business.