Workflow Template
Service disconnection verification before demolition Workflow
Verifies that all utility services at a demolition site are disconnected before demolition can proceed. Captures a verification form, checks the result, and if services remain connected, loops between an office follow-up with utility providers and an on-site supervisor re-verification until all services are confirmed disconnected or the loop cap is reached.
Demolition crews risk serious safety incidents and project delays when a site's utilities aren't fully disconnected before work begins. This workflow captures a verification form covering electricity, gas, water, sewer, stormwater, telecoms and solar/battery status, then routes the record based on the result. If services remain connected, it loops between an office task to follow up with utility providers and a supervisor task to re-verify on site, repeating up to 3 times until every service is confirmed disconnected or the loop cap is reached.
Business Outcomes
- Helps reduce the risk of starting demolition with live utility connections still in place
- Makes it easier to track which services are still connected and who is following up
- Supports faster resolution of outstanding disconnections through a structured office-to-site loop
- Keeps clients informed automatically when demolition is on hold or ready to proceed
- Gives a clear timeline of verification status changes for each site on record
Workflow Steps
Steps
- 1Create Verification Recordcreate record
Creates the disconnection verification record from the submitted form data.
- 2Set Status to Checkingupdate record
Sets the verification status to Checking after the form is submitted.
- 3Route on Initial Verification Result
Branches based on whether all services are disconnected or some remain connected.
result: "All services disconnected"→Set Status to Verifiedresult: "Services still connected"→Set Status to Awaiting DisconnectionDefault→Set Status to Awaiting Disconnection - 4Set Status to Awaiting Disconnectionupdate record
Sets the verification status to Awaiting Disconnection because services remain connected.
- 5Email Client - Demolition On Holdsend email
Notifies the client that demolition cannot start until all services are disconnected.
- 6Office: Follow Up With Utility Providerscreate task
Assigns the office team a task to follow up with utility providers on services still connected.
- 7Save Follow-up Details to Recordupdate record
Persists the office follow-up details onto the verification record.
- 8Supervisor: Re-verify On Sitecreate task
Assigns the supervisor a task to re-verify service disconnection status on site.
- 9Save Re-verification Result to Recordupdate record
Persists the supervisor's re-verification result onto the record.
- 10Route on Re-verification Result
Branches based on whether the supervisor's re-verification confirms all services disconnected.
reverify_result: "All services disconnected"→Set Status to Verifiedreverify_result: "Services still connected"→Loop Back to Office Follow-upDefault→Loop Back to Office Follow-up - 11Loop Back to Office Follow-uprestart from step
Restarts the workflow from the office follow-up step since services are still connected, up to 3 times.
- 12Set Status to Verifiedupdate record
Sets the verification status to Verified now that all services are confirmed disconnected.
- 13Email Client - Demolition Can Proceedsend email
Notifies the client that all services are confirmed disconnected and demolition can proceed on the planned date.
Fields
- Supervisor Name*
- Supervisor Email*
- Client Name*
- Client Email*
- Site Address*
- Job Reference*
- +17 more fields
Forms
Service Disconnection Verification Form
18 fields
Data Views
Service Disconnection Verifications
site_address, job_reference, planned_demolition_date, result +1 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
How do I set up this workflow for our demolition jobs?
Publish the template in your workspace and it's ready to run — no development project needed. Share the public request form with supervisors or clients, or the workspace can send it out, and each submission creates a verification record with its own reference number.
Who fills in the initial verification form?
Anyone with the link can submit it through the public request form, since customers never need an account. It asks for supervisor and client details, site address, job reference, planned demolition date, and the status of each utility along with disconnection reference numbers, confirmation documents and photos.
What happens if services are still connected after the first check?
The record status is set to Awaiting Disconnection, and the client gets an email that demolition is on hold. The office team then gets a task to follow up with utility providers, capturing which services are still connected, reference numbers, and expected disconnection dates.
Who is responsible for re-checking the site once follow-up is done?
A supervisor is assigned a task to re-verify service disconnection status on site, and the workflow waits until they submit their result. That result is saved to the record before the workflow decides what happens next.
How many times will the workflow retry if services stay connected?
The loop between office follow-up and supervisor re-verification runs up to 3 times. Each pass updates the record with the latest follow-up details and re-verification result, so the full history is visible in the record's timeline.
What happens once all services are confirmed disconnected?
The record status is set to Verified, and the client is emailed to confirm demolition can proceed on the planned date. Anyone checking the record's table view or dashboard can see it's moved to a completed status.
Can we change the fields on the verification form or the loop limit?
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 covers form fields, task assignments, email wording and the loop cap.
Does the client need to log in to receive updates?
No. Clients receive their updates by email — such as the on-hold notice and the demolition-can-proceed confirmation — without needing an account. They interact only through emailed messages and, where used, forms sent to them.
Who can see the status of a verification record?
Workspace admins and members can see each record's status, reference number and timeline through table views and dashboards. Tasks like the office follow-up and supervisor re-verification are assigned to specific team members within the workspace.
What gets recorded if the loop cap is reached before services are disconnected?
Each loop's follow-up details and re-verification result are saved to the record as they happen, so the full sequence of attempts is visible in the timeline. Each business should confirm its own requirements for handling a site that reaches the loop cap without full disconnection.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
