Workflow Template
Ceiling insulation pre-start safety check Workflow
Captures an installer's pre-start safety check before ceiling insulation work begins, automatically clears the job if safe, or stops work and routes unsafe findings to a supervisor for corrective action and re-check (up to 2 loops) before clearing the job to start.
Ceiling insulation crews can turn up to a site with hazards like exposed wiring, extreme roof space heat or suspected asbestos, and without a consistent pre-start check those risks can go unnoticed until work is underway. This workflow captures the installer's pre-start safety check, clears the job automatically when the site is safe to start, and stops work while routing unsafe findings to a supervisor for corrective action and a re-check, looping up to twice before the job is cleared. Installers complete the check from the field and supervisors handle any corrective action tasks, with every step logged on the record.
Business Outcomes
- Helps reduce the chance of ceiling insulation work starting on an unsafe site
- Speeds up clearance for jobs that pass the pre-start check, with no manual sign-off needed
- Gives supervisors a clear, time-bound task to record issues and corrective actions
- Keeps a timeline of every check, decision and corrective action on the job record
- Cuts back-and-forth by capping supervisor re-checks at two loops before escalation is visible in status
Workflow Steps
Steps
- 1Create pre-start check recordcreate record
Registers the submitted pre-start safety check as a record.
- 2Set status to Submittedupdate record
Marks the pre-start check as Submitted on creation.
- 3Route on pre-start result
Branches based on whether the site was found safe to start or not.
result: "Safe to start"→Set status to Clearedresult: "Not safe - stop work"→Set status to Work StoppedDefault→End - 4Set status to Clearedupdate record
Marks the record as Cleared since the site was found safe to start.
- 5Set status to Work Stoppedupdate record
Marks the record as Work Stopped since the site was found unsafe.
- 6Email installer: work must not startsend email
Notifies the installer that work must not start due to unsafe conditions.
- 7Supervisor: review issues and corrective actionscreate task
Assigns the supervisor a task due in 1 day to record issues, corrective actions taken, and whether the site is now safe to start.
- 8Route on supervisor decision
Branches based on whether the supervisor confirms the site is now safe to start.
supervisor_safe_decision: "Safe to start"→Save corrective actions to recordsupervisor_safe_decision: "Not safe"→Send back to supervisorDefault→End - 9Send back to supervisorrestart from step
Restarts the supervisor review since the site is still not safe, up to 2 times.
- 10Save corrective actions to recordupdate record
Persists the supervisor's recorded issues and corrective actions to the record and sets status to Cleared.
- 11Email installer: cleared to startsend email
Notifies the installer that the job is now cleared to start, including the corrective actions taken.
Fields
- Installer Name*
- Installer Email*
- Site Address*
- Date*
- Job Reference*
- Roof Space Access*
- +13 more fields
Forms
Ceiling Insulation Pre-Start Safety Check
18 fields
Data Views
Pre-Start Checks
site_address, check_date, job_reference, roof_space_access +2 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
How do I set up this workflow for my team?
Publish the template in your workspace and it runs live straight away, no development or installation needed. The public request form is ready for installers to use, and you assign the supervisor task to whichever team member handles corrective actions on site.
What do installers need to use this in the field?
Installers don't need an account. They fill in the pre-start check request form on their phone or tablet before starting work, covering roof space access, wiring, hazards and PPE, then submit the Result field to trigger the workflow.
What happens if the installer marks the site as not safe to start?
The record status changes to Work Stopped and the installer is emailed to confirm work must not start. A supervisor is then assigned a task, due in one day, to record the issues found, the corrective actions taken and whether the site is now safe.
What happens after the supervisor reviews the issues?
If the supervisor confirms the site is now safe to start, the corrective actions are saved to the record, the status is set to Cleared, and the installer is emailed with the corrective actions included. If the supervisor still finds it unsafe, the review task is sent back to the supervisor, up to two times, before the job can be cleared.
Who is responsible for each step in this process?
Installers submit the initial pre-start check through the public form. Supervisors, added as workspace team members, are assigned the corrective action review task and record their findings directly on it, which the workflow waits for before moving on.
Can I change the questions on the pre-start check form?
Yes, you can edit the workflow's steps in the workflow editor or describe the change you want in plain English. Earlier versions of the workflow are kept, so you can review what changed over time.
How long does it take to get a workspace running with this workflow?
The template is ready to use as soon as it's published, so a workspace can be running live pre-start checks within minutes. There's no separate development project or setup delay.
What information is kept on the job record?
Each pre-start check becomes a record with a reference number, a status such as Submitted, Cleared or Work Stopped, and a timeline of what happened. Fields the workflow waits on, like the supervisor's issues and corrective actions, are saved to the record, and workspace activity on the job is logged.
Does this workflow notify anyone by SMS as well as email?
Email is used in this workflow to notify the installer when work must stop and when the job is cleared to start. SMS is built into the platform and can be added to a workflow if your workspace wants that notification channel.
What if the supervisor still can't clear the site after two re-checks?
The workflow allows up to two send-backs to the supervisor for further corrective action and re-check. Each loop and the supervisor's recorded findings are visible in the record's timeline, so your team should confirm its own process for handling a job that still isn't safe after those checks.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
