Concrete completion and finish acceptance Workflow

How do I get this workflow running for our concreting jobs?

Publish the template in your workspace and it's ready to run immediately — there's no setup project or installation. New jobs start as soon as someone submits the completion request form with the supervisor, customer and job details.

What information do I need before starting a job in this workflow?

You'll need the concreting supervisor's name, customer contact details, site address, the element and area completed, finish and sealer details, foot and vehicle traffic timing, before and after photos, care instructions and the warranty period. All of this comes from the initial request form and flows through to the customer's review and handover emails.

Who is responsible for the walkthrough and rework tasks?

The concreting supervisor is assigned the walkthrough task and records whether the job is ready for handover or needs rework. If rework is needed, the same supervisor gets a rework task showing the rework list, and the workflow loops back to another walkthrough once it's done.

What happens if the customer reports an issue instead of accepting the work?

The job status changes to Customer Issue and the supervisor is assigned a task to fix the problem, with the customer's comments shown on the task. Once the fix is recorded, the workflow returns to the customer review email so the customer can confirm acceptance again.

Does the customer need to create an account to review or accept the work?

No. The customer reviews and accepts the finished work through a form emailed directly to them, and later receives the feedback request the same way. They take part entirely through emailed forms without ever logging in.

Can I change how long the supervisor or customer has to respond?

Yes. Describe the change you want in plain English, or open the workflow editor and adjust the due dates on the walkthrough, rework and fix tasks directly. Earlier versions of the workflow are kept, so you can review what changed.

How is the delayed feedback request triggered?

After the job is marked Handed Over and the thank-you email is sent, the workflow waits two days before automatically emailing the customer a feedback form asking for a 1-5 rating and comments. No one needs to trigger this step manually.

Where can I see the status of jobs going through sign-off?

Each job is a record with a reference number, current status (such as Final Check, Rework, Customer Review or Handed Over) and a full timeline of what happened. Table views and dashboards let you see all jobs grouped by status, and workspace activity is logged throughout.

What gets saved to the job record versus staying on a task?

Anything the workflow waits on — like the walkthrough result, rework details, customer decision, issue fix, and feedback rating — is saved to the record. This gives you a complete history of the job's sign-off process in one place.

Can we send these emails from our own domain?

Email is built into the workflow by default, and a workspace can optionally send through its own AWS SES account for the customer review, thank-you and feedback emails. Each business should confirm this setup meets its own email deliverability and record-keeping needs.