Masonry pre-start / footing readiness check Workflow

Why should we automate the masonry pre-start inspection instead of doing it on paper or in emails?

Manual pre-start checks are easy to lose track of, especially when a site fails and needs rectification and a follow-up visit. This workflow captures the inspection once, automatically notifies the builder or client of the result, and routes failed checks to the site team with a due date, so nothing depends on someone remembering to chase it up. Every step is logged on the record's timeline, giving a clear history of what happened and when.

What is the return on investment of using this workflow?

The workflow reduces the administrative effort of manually notifying builders, tracking rectification tasks, and chasing re-inspections, which can otherwise consume significant coordinator time on every failed check. Faster rectification loops help crews get onto ready sites sooner, reducing costly downtime. Because the template is ready to use immediately, a workspace can start realizing these efficiencies without a development project.

How does this compare to handling pre-start checks and rectification manually?

Handling this manually typically means separate phone calls, emails and spreadsheets to track inspection results, rectification status and re-inspection outcomes. This workflow keeps all of that on a single record with a status and timeline, and automatically emails the builder or client when the site passes or is rectified and passed. It also assigns rectification and re-inspection tasks with due dates, reducing the chance of a step being missed or delayed.

Who is involved in the inspection and rectification process?

An inspector submits the initial pre-start inspection via the request form, and receives an acknowledgement email with the reference number. If the site fails, a task is assigned to the site team to rectify the failed checks within 2 days, after which the inspector is assigned a re-inspection task due in 1 day. The builder or client is kept informed by email at each key outcome, without needing an account.

What happens if the site fails the initial pre-start inspection?

When the overall result is 'Not ready', the workflow generates a short AI summary of which checks failed and saves it to the record, then sets the status to Rectification. The site team is assigned a task due in 2 days to fix the failed checks and record what was done, including rectification photos, and this information is saved to the record before the inspector is assigned a re-inspection task.

What happens if the re-inspection still fails after rectification?

If the re-inspection result comes back as 'Not ready', the workflow returns to the site team rectification task, closing the current iteration and restarting the rectification and re-inspection cycle. This loop continues until the re-inspection result is 'Ready to start', at which point the record is marked Ready to Start and the builder or client is emailed that the site was rectified and passed.

Can we customise the checklist items on the pre-start inspection form?

Yes, the request form fields and workflow steps can be adjusted by describing the change in plain English or editing the steps directly in the workflow editor. This makes it straightforward to add, remove or reword checklist items such as wall type, damp-proof course materials, or services penetrations as site requirements change. Earlier versions of the workflow are kept, so changes can be made with confidence.

How are photos and rectification details captured and stored?

Photos submitted with the original request form, along with rectification photos and notes entered on the site team's task, are saved to the inspection record since the workflow waits for that task before continuing. This means the record's timeline holds a documented history of the failed checks, what rectification work was done, and the supporting photos. The same applies to the re-inspection result and notes, which are saved to the record after the inspector completes their task.

How do builders or clients stay informed without needing to log in anywhere?

Builders and clients receive email notifications at key points in the process — when the site passes the initial pre-start check, or when it is rectified and passes re-inspection — without ever needing to create an account. This keeps them informed of progress while the inspection, rectification and re-inspection work happens through tasks assigned to the inspector and site team.

What visibility does a workspace have into the status of multiple inspections?

Each pre-start inspection is created as its own record with a reference number, a status such as Submitted, Ready to Start or Rectification, and a timeline of everything that has happened on it. Table views and dashboards show these records grouped by status, making it easier to see at a glance which sites are ready, which are in rectification, and which are awaiting re-inspection.