Silica dust control pre-start checklist Workflow

What happens if the pre-start checklist result is not safe to start?

The record status is set to Work Stopped and the stonemason is emailed straight away that work must not begin. At the same time, a supervisor is assigned a task, due in one day, to review the issues and record corrective actions plus a fresh safety decision. Nothing progresses to a cleared status until that supervisor review is completed.

What happens if the supervisor still finds the site not safe after reviewing it?

If the supervisor's decision is Not safe, the workflow sends the review task back to the supervisor for another round, up to two additional times. Each time, the supervisor records issues, corrective actions and a new safety decision, which is saved to the record so there's a running history of what was tried.

Can this handle a site where the supervisor still can't confirm it's safe after the re-checks?

The workflow allows for up to two further supervisor review cycles beyond the first one. Every cycle's issues and corrective actions are saved to the record's timeline, so even if the workflow's automatic routing is exhausted, staff have a full written history of what was checked and attempted to inform next steps.

Who is responsible for each task in this workflow?

The stonemason completes the initial public request form with checklist details, and the supervisor is the only assigned task-holder, responsible for reviewing issues, logging corrective actions, and deciding whether it's now safe to start. The workflow itself handles status updates and notification emails between these two points.

What information does the stonemason receive by email?

If the initial result is not safe, the stonemason is emailed immediately that work must not start. If the checklist is safe from the outset, or if the supervisor later confirms it's safe after corrective action, the stonemason is emailed that work is cleared to start, including the corrective actions taken.

Can we customise the questions on the pre-start checklist form?

Yes, the request form fields — such as stone type, tools used, respirator fit-testing, or wash-down area availability — can be adjusted by describing the change in plain English or editing the workflow steps directly in the workflow editor. Earlier versions of the workflow are kept, so changes can be reviewed or reverted if needed.

What gets saved to the record versus staying with a task?

Because the workflow waits for the supervisor's review task, the issues, corrective actions and safety decision entered on it are saved directly to the record. Anything entered on a task the workflow doesn't wait for would instead stay attached to that task in the record's task list rather than on the record itself.

How do we track how many checklists are being stopped versus cleared?

Every checklist becomes a record with its own reference number, status and timeline, and table views and dashboards group these records by status — Submitted, Cleared, or Work Stopped. This makes it straightforward to see patterns across sites or jobs and review corrective action history for compliance purposes, which each business should confirm against its own obligations.

Does the stonemason need an account to submit the checklist?

No, the stonemason submits the pre-start checklist through a public request form and receives status updates by email, without needing to log into anything. This keeps the process simple for stonemasons working across different sites.