assess.one – AI-powered business operations platform

Workflow Template

Roof safety / fall protection pre-start Workflow

Captures a roofer's pre-start fall protection checklist, records the safety result, and either clears the job to start or stops work and routes unsafe conditions to a supervisor for corrective action and re-check (up to 2 loops) before final clearance.

A roofer arrives on site, works through the fall protection checklist on their phone, and hits submit before climbing up. The workflow instantly records the result, clears the job to start if everything checks out, or stops work and sends the issue straight to a supervisor for corrective action and a re-check, looping up to twice until it's genuinely safe to proceed. Supervisors and roofers both get clear notifications at each stage, so nobody has to chase paperwork or guess whether a job is cleared.

Business Outcomes

  • Faster turnaround between checklist submission and go/no-go decision
  • Fewer unsafe starts thanks to automatic stop-work routing
  • Clearer accountability with corrective actions and outcomes logged on each record
  • Less manual chasing of paper checklists and supervisor sign-off
  • Easier visibility into which jobs are cleared, stopped, or under review at any time

Workflow Steps

Steps

  1. 1
    Create pre-start recordcreate record

    Registers the submitted pre-start checklist as a record.

  2. 2
    Set status to Submittedupdate record

    Marks the pre-start record as Submitted on creation.

  3. 3
    Route on pre-start result

    Branches based on whether the pre-start check result is safe or not safe.

    result: "Safe to start"→Set status to Cleared
    result: "Not safe - stop work"→Set status to Work Stopped
    Default→End
  4. 4
    Set status to Clearedupdate record

    Marks the record as Cleared because the pre-start result was safe to start.

  5. 5
    Email roofer: cleared to startsend email

    Notifies the roofer that the job is cleared to start work.

  6. 6
    Set status to Work Stoppedupdate record

    Marks the record as Work Stopped because the pre-start result was not safe.

  7. 7
    Email roofer: stop worksend email

    Notifies the roofer that work must not start until the safety issue is resolved.

  8. 8
    Supervisor: review issues and corrective actionscreate task

    Assigns the supervisor a task to record the issues, corrective actions and whether it is now safe to start.

  9. 9
    Save supervisor findings to recordupdate record

    Persists the supervisor's issues and corrective actions notes to the record.

  10. 10
    Route on supervisor re-check outcome

    Branches based on whether the supervisor found the site now safe to start.

    safety_recheck: "Safe to start"→Set status to Cleared
    safety_recheck: "Not safe"→Send back to supervisor for further review
    Default→End
  11. 11
    Send back to supervisor for further reviewrestart from step

    Restarts the supervisor review task because the site is still not safe, up to 2 times.

  12. 12
    Set status to Clearedupdate record

    Marks the record as Cleared after the supervisor confirmed it is now safe to start.

  13. 13
    Email roofer: cleared to start after corrective actionssend email

    Notifies the roofer that the job is now cleared to start, including the corrective actions taken.

Fields

  • Roofer Name*
  • Roofer Email*
  • Site Address*
  • Date*
  • Job Reference*
  • Roof Type*
  • +18 more fields

Forms

Roof Safety Pre-Start Checklist

20 fields

Data Views

Pre-Start Checks

site_address, prestart_date, job_reference, fall_protection_used +2 more

Dashboard Widgets

Pre-Starts by Status

Recommended integrations

Setup the following integrations to extend workflow capability.

  • Send email in the workflow

    AWS SES logoAWS SES
roof safety / fall protection pre-startroofing and roof plumbingpre-startsafetytradetrades

Similar Workflows

Similar Categories

FAQs

Do I need to set this up for every site or can one template handle all roofing jobs?

One published template runs the live pre-start process for every job — there's no separate setup needed per site. Roofers fill in the same request form each time with the site address, job reference and checklist details, and each submission becomes its own tracked record.

Can my team change the checklist questions or add extra fields later?

Yes, a workspace admin can update the workflow by describing the change in plain English or editing the steps directly in the workflow editor. Earlier versions are kept, so you can review what changed and when.

What happens if a roofer marks the site as not safe to start?

The record status changes to Work Stopped, the roofer gets an email saying work must not start, and a task is assigned to the supervisor to record the issues found, the corrective actions taken, and whether it's now safe to proceed. The workflow waits on that task before moving forward.

How many times can the supervisor re-check a site before it's cleared?

The workflow allows up to two further review loops if the supervisor still finds the site unsafe. Once the supervisor confirms it is now safe to start, the record status changes to Cleared and the roofer is emailed with the corrective actions included.

Is this suitable for roofing businesses with more than one supervisor?

Yes — supervisor review tasks are assigned to a team member in the workspace, and any admin or member can be set up to receive them. Every action taken, including issues recorded and corrective actions, is saved to the record's timeline for full visibility.

Do roofers need to log into anything to submit the checklist?

No account is required. Roofers complete the public request form or a form emailed to them, and their answers are saved straight to the record.

Can my team see the status of all jobs at a glance?

Yes, table views and dashboards show every pre-start record by its current status — Submitted, Cleared, or Work Stopped — so you can quickly see which jobs are ready to go and which need attention.

What gets recorded if photos are attached to the checklist?

Photos submitted on the request form are saved to the record along with all the other checklist answers, so they're available in the record's history alongside the result and any supervisor notes. Each business should confirm what photo evidence it needs to keep for its own record-keeping obligations.

Does clearing a job mean the business is compliant with safety regulations?

The workflow records the checklist answers, the result, supervisor findings and corrective actions in the record's timeline, giving a clear audit trail of what was checked and decided. Each business should confirm its own compliance obligations, as the workflow supports documentation but doesn't determine legal compliance.

Ready to use this workflow?

Create a free account and customise this workflow for your business.

Roof safety / fall protection pre-start Workflow | assess.one