Formwork pre-pour inspection Workflow

Do I need to set up anything special before using this workflow?

No — the template is ready to use as soon as your workspace publishes it, so you can start submitting pre-pour inspections straight away. There's no installation or setup project involved; the request form and rectification loop work out of the box.

Can my team customise the inspection checklist or the emails that get sent?

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 if you want to compare or roll back. This makes it easy to adjust wording on client emails or add extra fields to the form as your inspection standards evolve.

Who is actually involved in this workflow day-to-day?

The inspector submits the initial pre-pour result and later handles the re-inspection task if rectification is needed. The formwork crew is assigned the rectification task when checks fail, and the builder or client receives email updates on the outcome — none of them need a workspace account, since they interact through the public request form or emailed tasks.

What happens if the formwork fails the first inspection?

The record's status changes to Rectification, and the formwork crew is assigned a task (due in 1 day) to fix the failed checks and record what work was done along with photos. Once that's saved, the inspector gets a re-inspection task, and the result of that determines whether the pour is approved or sent back for another rectification attempt.

How many times can a formwork inspection go through rectification?

The workflow allows the rectification-and-re-inspection loop to repeat up to two times if the re-inspection still comes back as not ready. Each attempt is tracked on the record's timeline, including the rectification work, photos, and re-inspection notes, so there's a clear history of what happened at each round.

Is this suitable for inspections across multiple sites or crews?

Yes — each submission creates its own record with a reference number, status, and timeline, so inspections at different sites or with different crews are tracked separately. Table views and dashboards show all records grouped by status, making it straightforward to see which pours are approved, in rectification, or awaiting re-inspection.

What information gets saved on the inspection record versus staying with a task?

Anything the workflow waits for — like the rectification work and photos, or the re-inspection result and notes — gets saved directly on the record. If a task isn't one the workflow waits for, its answers stay with that task in the record's task list instead. This distinction matters if you're relying on the record itself as your source of truth for reporting.

How does the client find out whether the pour is approved?

The builder or client receives an email automatically once the inspection is approved, whether that happens on the first pass or after a rectification cycle. They don't need to log in or check a dashboard — the email tells them the result, and the full history is visible in the record's timeline if anyone on your team needs to review it later.

Does this workflow help with compliance record-keeping for inspections?

The workflow records each inspection's status changes, the values entered by the inspector and crew, and a full timeline of what happened and when. Each business should confirm its own regulatory or contractual record-keeping obligations, as the workflow supports documentation but doesn't itself determine compliance.