Workflow Template
Waterproofing substrate readiness inspection Workflow
Captures a waterproofing substrate readiness inspection, acknowledges the submission, and either confirms the substrate is ready for membrane or routes failed checks through a rectification and re-inspection loop (up to 2 cycles) before notifying the builder/client of the final result.
Without a structured process, a failed substrate check means phone calls to the site team, a manual re-inspection reminder, and a builder left wondering whether membrane can go ahead. This workflow captures the inspection on submission, routes passed substrates straight to a Ready for Membrane status, and sends failed checks through a rectification and re-inspection loop of up to two cycles before the builder or client is notified. The team ends up with a record that always shows the current status and a timeline of who did what, without anyone needing to chase updates.
Business Outcomes
- Reduces time spent manually tracking which inspections are pending, in rectification, or ready for membrane
- Cuts down on missed handoffs between inspector and site team during rectification cycles
- Speeds up builder/client notification once a substrate passes, whether on first pass or after rectification
- Supports consistent capture of moisture readings and photos across every inspection
- Makes it easier to see rectification history and re-inspection results for a given job reference
Workflow Steps
Steps
- 1Create Inspection Recordcreate record
Registers the submitted inspection as a record.
- 2Set Status to Submittedupdate record
Marks the inspection record status as Submitted.
- 3Email Acknowledgementsend email
Sends the inspector an acknowledgement email with the job reference.
- 4Route on Overall Result
Routes the workflow depending on whether the substrate is ready for membrane or requires rectification.
overall_result: "Ready for membrane"→Set Status to Ready for Membraneoverall_result: "Not ready"→Set Status to RectificationDefault→End - 5Set Status to Ready for Membraneupdate record
Marks the inspection record status as Ready for Membrane.
- 6Email Builder/Client - Passedsend email
Notifies the builder or client that the substrate passed the readiness inspection.
- 7Set Status to Rectificationupdate record
Marks the inspection record status as Rectification.
- 8Site Team: Rectify Failed Checkscreate task
Assigns the site team a task to rectify failed checks, due in 2 days, recording work done and photos.
- 9Save Rectification Detailsupdate record
Persists the rectification work done and photos to the inspection record.
- 10Inspector: Re-inspect Substratecreate task
Assigns the inspector a task due in 1 day to re-inspect and record the result and notes.
- 11Save Re-inspection Resultupdate record
Persists the re-inspection result and notes to the inspection record.
- 12Route on Re-inspection Result
Routes to Ready for Membrane if the re-inspection passed, otherwise loops back to the site team for further rectification.
reinspection_result: "Ready for membrane"→Set Status to Ready for Membrane (After Rectification)reinspection_result: "Not ready"→Loop Back to Site TeamDefault→End - 13Loop Back to Site Teamrestart from step
Sends the record back to the site team for further rectification, up to 2 cycles.
- 14Set Status to Ready for Membrane (After Rectification)update record
Marks the inspection record status as Ready for Membrane following successful rectification.
- 15Email Builder/Client - Rectified and Passedsend email
Notifies the builder or client that the substrate was rectified and passed the readiness inspection.
Fields
- Inspector Name*
- Inspector Email*
- Builder/Client Name*
- Builder/Client Email*
- Site Address*
- Job Reference*
- +17 more fields
Forms
Substrate Readiness Inspection
18 fields
Data Views
Substrate Readiness Inspections
site_address, job_reference, area, overall_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
What happens if the substrate fails inspection twice in a row?
The workflow allows up to two rectification and re-inspection cycles. If the substrate still isn't ready after the second cycle, the record stays in Rectification status with the site team's work and photos and the inspector's notes saved on the record, so the team can see the full history and decide next steps.
Can this handle a re-inspection that comes back as 'otherwise' rather than a clear pass or fail?
Yes, the routing step after re-inspection has three paths: Ready for membrane, Not ready, and an otherwise path for any other result entered. This keeps the record moving through a defined status rather than getting stuck if the inspector enters something unexpected.
Who is responsible for each step in the process?
The inspector submits the initial readiness form and later carries out any re-inspection task, while the site team is assigned the rectification task when checks fail. The builder or client isn't assigned tasks but receives email notifications at the point the substrate is confirmed ready, either on first pass or after rectification.
What if the site team doesn't complete the rectification task within 2 days?
The rectification task is due in 2 days, and the workflow waits for it to be completed before moving forward, so the record simply stays in Rectification status until the site team records the work done and uploads photos. This keeps an accurate timeline of how long rectification took for each job.
Can we customise the inspection checklist or add more fields?
Yes, the request form fields, such as the specific readiness checks or the substrate moisture reading, can be adjusted by describing the change in plain English or editing the steps directly in the workflow editor. Earlier versions of the workflow are kept, so changes can be reviewed or reverted if needed.
What information does the builder or client actually see?
The builder or client receives an email notification confirming either that the substrate passed on first inspection or that it was rectified and passed after the rectification loop. They take part through emailed forms and don't need an account to receive these updates.
What gets recorded on the inspection record versus staying with a task?
Because the rectification and re-inspection tasks are steps the workflow waits for, the rectification work done, rectification photos, re-inspection result, and notes are all saved directly onto the inspection record. This means anyone viewing the record later can see the full readiness history, not just the current status.
How do we track where a specific job is in the process?
Each inspection is a record with a reference number, a status such as Submitted, Rectification, or Ready for Membrane, and a timeline of what happened. Table views and dashboards show records grouped by status, making it easy to see which jobs are waiting on rectification or re-inspection at a glance.
Does the workflow send SMS updates instead of email?
The workflow as described uses email for the acknowledgement and builder/client notifications, though a workspace can send messages through its own connected email or SMS account. Adding SMS notifications to specific steps would need to be configured as a change to the workflow.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
