Workflow Template
Fire protection maintenance service report Workflow
Captures a fire protection technician's service report, routes follow-up actions based on defect priority (none, minor, critical), manages quote approval for minor defects, tracks repairs to completion, and keeps clients informed at each stage.
Fire protection service providers need a consistent, auditable way to capture technician findings and follow through on any defects identified during routine servicing, particularly where organisations must demonstrate ongoing oversight of building fire safety systems. This workflow captures the technician's service report and automatically routes follow-up action based on the reported defect priority, whether no defects, minor defects requiring a priced quote, or critical defects requiring urgent notification and repair. Technicians, office staff, and clients are each brought into the process at the appropriate stage, with the record's status and timeline reflecting progress throughout.
Business Outcomes
- Helps standardise how service reports and defect follow-up are captured across technicians and sites
- Supports faster client notification of critical fire safety impairments through combined email and SMS alerts
- Reduces manual chasing of quote approvals by routing minor defect quotes to clients through a tracked approval form
- Makes it easier to see repair status and history for each site through record statuses and timelines
- Helps ensure repair and quote details are recorded against the record rather than lost in separate communications
Workflow Steps
Steps
- 1Create Service Report Recordcreate record
Registers the submitted service report as a record.
- 2Set Status to Submittedupdate record
Marks the record status as Submitted immediately after creation.
- 3Route on Defect Priority
Branches the workflow based on the technician's reported defect priority.
defect_priority: "No defects"→Set Status to Completedefect_priority: "Critical defects"→Set Status to Critical Defectdefect_priority: "Minor defects"→Office: Price the RepairsDefault→End - 4Set Status to Completeupdate record
Marks the record complete because no defects were found.
- 5Email Client Service Summarysend email
Sends the client the service summary and next service due date.
- 6Set Status to Critical Defectupdate record
Marks the record as having a critical defect requiring urgent action.
- 7Email and Text Client - Urgent Impairmentsend email
Notifies the client by email and SMS that a fire safety system is impaired and needs urgent repair.
- 8SMS Client - Urgent Impairmentsend sms
Sends an SMS alert to the client about the critical fire safety impairment.
- 9Technician: Record Critical Repairscreate task
Technician completes a task within 1 day recording repairs or interim measures and photos for the critical defect.
- 10Save Critical Repair Details to Recordupdate record
Persists the technician's repair notes and photos to the record.
- 11Set Status to Completeupdate record
Marks the record complete after the critical defect repairs are recorded.
- 12Email Client - Repairs Madesend email
Informs the client that the repairs to the critical defect have been made.
- 13Office: Price the Repairscreate task
Office team completes a task within 3 days to price the minor defect repairs and record the quote amount.
- 14Save Quote Amount to Recordupdate record
Persists the office's quote amount to the record.
- 15Set Status to Quote Sentupdate record
Marks the record status as Quote Sent.
- 16Send Quote to Client for Approvalrequest external input
Emails the client a form showing the defects and quote amount, and waits for their approve or decline decision.
- 17Route on Quote Decision
Branches the workflow based on the client's approval or decline of the repair quote.
quote_decision: "Approve"→Technician: Record Minor Repairsquote_decision: "Decline"→Set Status to Repairs DeclinedDefault→End - 18Technician: Record Minor Repairscreate task
Technician completes a task recording the minor defect repairs made and photos, no due date set.
- 19Save Minor Repair Details to Recordupdate record
Persists the technician's minor repair notes and photos to the record.
- 20Set Status to Completeupdate record
Marks the record complete after the minor defect repairs are recorded.
- 21Email Client - Repairs Madesend email
Informs the client that the approved minor defect repairs have been made.
- 22Set Status to Repairs Declinedupdate record
Marks the record status as Repairs Declined.
- 23Email Client - Defects Remainsend email
Informs the client that the defects remain unrepaired and are noted for the next service.
Fields
- Technician Name*
- Client Name*
- Client Email*
- Client Phone
- Site Address*
- Service Date*
- +14 more fields
Forms
Fire Protection Service Report
12 fields
Data Views
Service Reports
client_name, site_address, service_date, defect_priority +3 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send SMS in the workflow
Twilio
AWS SNS
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
What does this workflow record for each service visit?
Each submitted service report becomes a record with a reference number, capturing the technician's details, systems serviced, checks performed, defects found, photos, and next service due date. As the record progresses, the workflow adds status changes such as Submitted, Critical Defect, Quote Sent, or Complete, along with a timeline of what happened. Task outputs the workflow waits for, such as repair notes and photos, are also saved directly to the record.
Who is involved in handling a critical defect?
When a technician reports critical defects, the client is notified urgently by both email and SMS about the impairment. A technician is then assigned a task, due within one day, to record the repairs or interim measures taken along with photos, which the workflow waits for before marking the record complete. The client receives a further email once these repairs are confirmed.
Who is involved when minor defects are found?
For minor defects, a member of the office team is assigned a task, due within three days, to price the repairs and record the quote amount on the record. The client is then emailed a form showing the defects and quote for their approval or decline decision. Depending on their response, a technician records the completed repairs, or the record is marked as Repairs Declined.
What happens if the client declines the repair quote?
If the client declines the quote, the record status is set to Repairs Declined and the client receives an email confirming that the defects remain unrepaired. The workflow notes that these defects are flagged for the next scheduled service. The decline decision and any comments the client provides are recorded on the record.
How do we change this workflow to suit our own service process?
A workflow can be adjusted by describing the desired change in plain English or by editing its steps directly in the workflow editor. This could include changing task deadlines, adjusting the wording of client messages, or adding further routing conditions. Earlier versions of the workflow are kept, so changes can be reviewed over time.
Do clients need an account to respond to quotes or service updates?
No. Clients take part entirely through emailed forms and messages sent to them, such as the quote approval form, without needing to create or log into an account. Their responses, including quote decisions and comments, are captured directly on the record.
Who can see the status and history of a service report record?
Workspace admins and members can view records through table views and dashboards that show records grouped by status, such as Submitted, Quote Sent, or Complete. Each record's timeline reflects the actions taken, and workspace activity is logged. Tasks and approvals are assigned to specific team members as they arise in the workflow.
How are technicians and office staff notified of their tasks?
Tasks such as recording critical or minor repairs, or pricing a quote, are assigned to team members within the workspace as the workflow reaches those steps. Some tasks, like recording critical repairs, have a set due date, while others, such as recording minor repairs, do not. The workflow waits for these tasks to be completed before moving the record forward, and the information entered is saved to the record.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
