Workflow Template
Underground services verification checklist Workflow
Captures a pre-start underground services verification checklist before any excavation, routes based on whether services are verified safe to dig, and manages a corrective-action loop if not verified until the site is cleared or escalated.
When a crew shows up to dig without a clear, documented check on underground services, the risk of hitting a gas line, cable or pipe rides on a paper form that's easy to skip or lose. This workflow captures the pre-start checklist, automatically routes the record to Cleared or Work Stopped based on the verification result, and runs a corrective-action loop with the supervisor until the site is confirmed safe or the issue is escalated. The result is a supervisor who knows exactly what to fix, a timeline that shows why work stopped and restarted, and no excavation starting on an unverified status.
Business Outcomes
- Reduces the chance of excavation starting before services are verified as safe
- Speeds up corrective-action turnaround with a 1-day task deadline and automatic retries
- Gives supervisors a documented trail of issues found, actions taken and clearance decisions
- Cuts back-and-forth communication with automatic email notifications at each status change
- Makes it easier to track site clearance status across multiple jobs from one dashboard
Workflow Steps
Steps
- 1Create Pre-Start Recordcreate record
Registers the submitted pre-start checklist as a record.
- 2Set Status to Submittedupdate record
Marks the pre-start checklist status as Submitted.
- 3Route on Verification Result
Branches based on whether services were verified as safe to dig.
result: "Services verified - safe to dig"→Set Status to Clearedresult: "Not verified - do not dig"→Set Status to Work StoppedDefault→End - 4Set Status to Clearedupdate record
Marks the pre-start checklist as Cleared since services were verified safe to dig.
- 5Set Status to Work Stoppedupdate record
Marks the pre-start checklist as Work Stopped since services were not verified.
- 6Notify Supervisor - Work Must Not Startsend email
Emails the excavation supervisor that work must not start until services are verified.
- 7Corrective Action Taskcreate task
Assigns the excavation supervisor a task due in 1 day to record issues, corrective actions, and whether it is now safe to start.
- 8Save Corrective Action Dataupdate record
Saves the recorded issues and corrective actions to the record.
- 9Route on Now-Safe Outcome
Branches based on whether the supervisor confirmed it is now safe to start.
now_safe: "Safe to start"→Set Status to Clearednow_safe: "Not safe"→Return to Supervisor for Further Corrective ActionDefault→End - 10Return to Supervisor for Further Corrective Actionrestart from step
Restarts the corrective action task for the supervisor since it is not yet safe to start, up to 2 additional times.
- 11Set Status to Clearedupdate record
Marks the pre-start checklist as Cleared now that corrective actions have made the site safe to dig.
- 12Notify Supervisor - Cleared to Startsend email
Emails the excavation supervisor that work is cleared to start, including the corrective actions taken.
Fields
- Excavation Supervisor Name*
- Excavation Supervisor Email*
- Site Address*
- Date*
- Job Reference*
- Dig Area*
- +16 more fields
Forms
Underground Services Pre-Start Checklist
18 fields
Data Views
Pre-Start Checks
site_address, dig_date, job_reference, dig_area +2 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Categories
FAQs
What happens if the supervisor doesn't complete the corrective action task within 1 day?
The corrective action task remains open on the record until the supervisor submits it, since the workflow waits for this step before moving on. The record's status and timeline continue to show Work Stopped until the task is completed, so the site is not marked cleared without that input.
What happens if the corrective actions still aren't enough after multiple attempts?
The workflow returns the task to the supervisor for further corrective action up to 2 additional times if the site is still marked Not Safe. If it still isn't confirmed safe after those attempts, the record moves into the otherwise branch, which a workspace can configure to escalate the record further.
Can this handle a job where services are verified safe on the first submission?
Yes. If the request form's Result field is submitted as 'Services verified - safe to dig', the workflow routes straight to Set Status to Cleared and skips the corrective action steps entirely. The record's timeline shows Submitted followed directly by Cleared with no work stoppage.
What if the excavation supervisor's email address is entered incorrectly on the request form?
Since the notification emails are sent to whatever address is captured in the Excavation Supervisor Email field, an incorrect entry means the supervisor won't receive the Work Must Not Start or Cleared to Start notifications. An admin or member can check the record and its timeline to see the status and follow up directly if the automated email hasn't reached the right person.
Who is responsible for each step in this workflow?
The excavation supervisor named on the request form completes the corrective action task, recording issues found, actions taken and whether the site is now safe. Status changes, routing decisions and notifications happen automatically based on the Result and Is it now safe to start fields, without requiring a separate reviewer or approver.
Can we customise the questions on the pre-start request form?
Yes. A workspace can edit the workflow's form fields, such as adding site-specific hazard categories or additional photo requirements, either by describing the change in plain English or by editing the steps directly in the workflow editor. Earlier versions of the workflow are kept, so changes can be reviewed or reverted.
What if a job has hazards found but the supervisor still marks it safe to dig?
The Hazards Found and Controls in Place field is captured and saved on the record regardless of the Result selected, so it's visible in the record's timeline alongside the final decision. This gives the workspace a documented record of what hazards were noted at the time of the original submission.
Can this workflow support multiple sites or jobs running at the same time?
Yes. Each submitted checklist creates its own record with a unique reference number, status and timeline, so multiple excavation jobs can be tracked independently on the same dashboard. Table views let a workspace filter and see which sites are Submitted, Work Stopped or Cleared at a glance.
What gets recorded if the supervisor needs to submit corrective actions more than once?
Each time the corrective action task is returned to the supervisor, the newly recorded Issues Found, Corrective Actions Taken and Is it now safe to start answers are saved to the record. This builds a running history in the timeline showing every round of corrective action until the site is cleared.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
