Waterproofing flood test / inspection Workflow

What happens if the flood test finds a leak?

The record status is set to Rectification and a task is assigned to the waterproofer, due in 2 days, to fix the failed checks and record the rectification work and photos. Once that's submitted, the inspector gets a re-inspection task, and the result of both steps is saved to the record's timeline.

Can this handle a leak that's found again after rectification?

Yes. If the re-inspection finds another leak, the workflow loops back to the rectification task, and this can repeat up to 2 times. Each cycle's rectification work, photos, re-inspection result and notes are saved to the record so the full history is visible.

What if the re-inspection result is something other than watertight or leak found?

The workflow includes an otherwise path at the re-inspection routing step, so an unexpected or missing result doesn't stall the process silently. A workspace can customise what happens on that branch by editing the workflow's steps.

Who is responsible for each task in the process?

The waterproofer is assigned the rectification task, and the inspector is assigned the re-inspection task, both as tasks the workflow waits for before moving on. The builder/client isn't assigned tasks — they're kept informed by email at the pass and rectified-and-pass stages, using the email address given on the request form.

What if the inspector or waterproofer misses their task deadline?

The rectification task is due in 2 days and the re-inspection task in 1 day, and the workflow waits for each to be completed before continuing. Because the record's status and timeline are visible in table views and dashboards, a workspace can see overdue tasks and follow up with the assigned team member.

Can we change what the request form asks for or add extra checks?

Yes. A workspace can edit the request form fields, such as adding extra checks or changing which fields are required, either by describing the change in plain English or by editing the workflow's steps directly. Earlier versions of the workflow are kept, so changes can be reviewed later.

What gets recorded if the flood test passes on the first attempt?

The record status is set to Watertight and the builder/client is emailed confirming the waterproofing passed the flood test, with no rectification steps triggered. All the original check values, photos, and water level readings entered on the request form are saved on the record.

Does the builder or client need an account to receive updates?

No. The builder/client is emailed directly at the address given on the request form, both when the test passes and when it's rectified and passed, without needing to log into anything. Customers only ever interact through the public request form or emailed forms.

What if we run this for multiple sites or job references at once?

Each submission creates its own inspection record with a unique reference number, status, and timeline, so simultaneous flood tests across different sites don't get mixed up. Table views and dashboards let a workspace see all records by status, whether Submitted, Rectification, or Watertight.

How do we know what compliance documentation this provides?

The workflow records the checks entered on the form, the overall result, rectification and re-inspection notes, photos, and status changes in the record's timeline. Each business should confirm its own record-keeping and compliance obligations, as this workflow is not a substitute for that assessment.