Electrical Test and Verification Workflow

How do I set up this workflow for my team?

Publish the template in your workspace and it's ready to use straight away, no installation or development project needed. The request form and email steps already match the fields listed, so electricians can start submitting test records right away. You can assign the repair task to your electricians as workspace members before you go live.

What information does the electrician need to submit for each test?

The request form captures details like electrician name, client name and email, site address, job reference, circuits tested, test date, and all the key test readings such as earth continuity, insulation resistance, polarity and RCD trip times. It also captures the test instrument used, its calibration date, photos, the next test due date and the overall test result. This becomes the record the rest of the workflow runs on.

What happens when a test passes on the first attempt?

The record status is set to Passed, and the client is automatically emailed the test result along with the next test due date. No repair task is created, so the record moves straight to a completed state.

What happens when a test fails?

The record status is set to Failed and the client is emailed to let them know the installation failed and won't be energised until it's fixed. The electrician is then assigned a Repair and Retest task, due in 2 days, to record the repair made and the retest result.

How does the repair-and-retest loop work?

Once the electrician submits the repair made and retest result, that information is saved to the record and the workflow checks whether the retest passed or failed. If it fails again, the workflow can send it back to the electrician for further repair, repeating up to 2 times before the loop ends.

What does the client see if the installation passes after a repair?

The record status is set to Passed After Repair, and the client is emailed to confirm the installation was repaired and passed its retest, including the next test due date. This gives the client a clear final outcome even though the first test failed.

Can I change what the request form or emails ask for?

Yes. You can describe the change you want in plain English, or edit the steps directly in the workflow editor, and earlier versions of the workflow are kept. This makes it straightforward to adjust fields, wording or routing as your process evolves.

Do clients need an account to receive updates?

No. Clients take part through emailed messages and forms sent directly to them, so they never need to log in or create an account. All the Pass/Fail and repair notifications in this workflow are sent straight to the client's email address on record.

Where can I see the status of test records across my team?

Each request becomes a record with its own reference number, status and timeline of what happened, and table views and dashboards group records by status like Submitted, Failed or Passed. Workspace activity is also logged, so you can see how each record progressed through the repair loop.

What if the installation keeps failing after the maximum repair attempts?

The workflow allows up to 2 further repair attempts after an initial failed retest. Each attempt's repair and retest details are saved to the record, so staff can review the full history and decide on next steps for records that don't reach a pass within those attempts.