Workflow Template
Concrete slab pre-pour checklist Workflow
Captures a pre-pour inspection for a concrete slab, notifies the builder/client of the outcome, and — if not ready — routes rectification work to the concreting crew and a re-inspection by the inspector (looping up to twice) before confirming the slab is ready to pour.
Pre-pour slab inspections often stall when a failed checklist item gets buried in texts and phone calls, leaving the crew unsure what to fix and the builder waiting for a straight answer. This workflow captures the inspection as a record, notifies the builder or client of the outcome, and automatically routes any failed items to the concreting crew for rectification and back to the inspector for re-inspection, looping up to twice. The result is a clear timeline of what failed, what was fixed, and when the slab was confirmed ready to pour.
Business Outcomes
- Reduces time lost tracking down inspection outcomes and rectification status
- Speeds up the handoff between inspector, crew and builder when rework is needed
- Cuts back-and-forth by summarising failed checks for the crew automatically
- Improves visibility into pour readiness with a single record and timeline per job
- Supports faster resolution of failed checks with due dates on rectification and re-inspection tasks
Workflow Steps
Steps
- 1Create slab inspection recordcreate record
Registers the submitted pre-pour inspection as a record.
- 2Set status to Submittedupdate record
Marks the inspection record status as Submitted.
- 3Email inspector acknowledgementsend email
Sends the inspector an acknowledgement email with the job reference number.
- 4Route on overall inspection result
Branches based on whether the slab is ready to pour or needs rectification.
overall_result: "Ready to pour"→Set status to Ready to Pouroverall_result: "Not ready"→Set status to RectificationDefault→End - 5Set status to Ready to Pourupdate record
Marks the inspection record status as Ready to Pour.
- 6Email builder/client - slab passedsend email
Notifies the builder or client that the slab passed the pre-pour check.
- 7Set status to Rectificationupdate record
Marks the inspection record status as Rectification.
- 8Summarise failed checksai summarise
Uses AI to summarise which checklist items failed for the crew task.
- 9Save failed checks summaryupdate record
Persists the AI-generated failed checks summary to the record.
- 10Concreting crew: rectify failed checkscreate task
Assigns the concreting crew a task to fix the failed items, due in 1 day, and blocks until they record completion.
- 11Save rectification detailsupdate record
Persists the rectification notes and photos to the record.
- 12Inspector: re-inspect slabcreate task
Assigns the inspector a task to re-inspect the slab, due in 1 day, and blocks until the result is recorded.
- 13Save re-inspection detailsupdate record
Persists the re-inspection result and notes to the record.
- 14Route on re-inspection result
Branches based on whether the re-inspection passed or still fails.
reinspection_result: "Ready to pour"→Set status to Ready to Pourreinspection_result: "Not ready"→Send back to concreting crewDefault→End - 15Send back to concreting crewrestart from step
Restarts the rectification cycle from the crew task since the re-inspection still failed.
- 16Set status to Ready to Pourupdate record
Marks the inspection record status as Ready to Pour after successful rectification.
- 17Email builder/client - rectified and passedsend email
Notifies the builder or client that the slab was rectified and passed the pre-pour check.
Fields
- Inspector Name*
- Inspector Email*
- Builder/Client Name*
- Builder/Client Email*
- Site Address*
- Job Reference*
- +20 more fields
Forms
Concrete Slab Pre-Pour Inspection
20 fields
Data Views
Slab Pre-Pour Inspections
site_address, job_reference, slab_type, planned_pour_date +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 slab fails inspection twice?
The workflow loops the rectification and re-inspection cycle up to twice, sending the job back to the concreting crew each time the re-inspection result is Not ready. If it still fails after the second loop, the record's timeline shows the full history of failed checks, rectification notes and re-inspection results, giving the team a clear record to review and decide next steps.
Can this handle a slab that passes on the first inspection?
Yes. When the Overall Result is Ready to pour, the workflow sets the record status to Ready to Pour and emails the builder or client directly, skipping the rectification and re-inspection steps entirely. This keeps straightforward passes moving quickly without any unnecessary tasks.
Who is assigned the rectification and re-inspection tasks?
The concreting crew is assigned the rectification task, due in one day, and must record Rectification Done and Rectification Photos before the workflow continues. The inspector is then assigned a re-inspection task, also due in one day, and records the Re-inspection Result and Re-inspection Notes, which the workflow waits for before routing further.
What if the builder or client needs to see photos or check details?
Photos and checklist answers submitted on the initial request form, along with rectification and re-inspection details, are saved to the record and visible in its timeline. The builder or client is notified by email at the key outcomes — pass, or rectified and passed — so they stay informed without needing to log in anywhere.
How is the crew told what specifically failed?
The workflow uses AI to summarise which checklist items failed straight after the Overall Result is marked Not ready, and saves that summary to the record before assigning the crew's rectification task. This gives the crew a clear, specific list of what needs fixing rather than a generic failed status.
Can the checklist items or due dates be customised?
Yes. A workspace can edit the workflow's steps in the workflow editor, or describe the change in plain English, to adjust checklist fields, task due dates, or notification wording. Earlier versions of the workflow are kept, so changes can be reviewed or reverted if needed.
What if the same job reference gets a duplicate submission?
Each submission through the public request form creates its own record with a reference number and status, so a duplicate submission would appear as a separate record. Table views and dashboards let the team see all records by status, making it easier to spot and manage duplicates for the same job.
Does the inspector need an account to complete their tasks?
No — the inspector and the concreting crew are workspace members or admins who receive their assigned tasks directly, while the builder or client takes part through emailed notifications without needing an account. Task assignees record their results directly against the relevant task, which the workflow then saves to the record.
What gets recorded if the concrete volume ordered changes after submission?
The Concrete Volume Ordered and other order details captured on the initial request form are saved to the record at submission. If details change later, the workspace can update the workflow to add a step for capturing revised figures, and any change would be reflected in the record's timeline of activity.
Ready to use this workflow?
Create a free account and customise this workflow for your business.