A fire alarm fault at 2am, a sprinkler leak in a shopping centre or a failed pump before an inspection: emergency callouts are where a fire contractor earns trust, or loses a contract. More facility managers now write response times into maintenance contracts, and ask for the figures at review time.
Callout software replaces the phone, the whiteboard and memory with a clock that starts when the call comes in. This guide covers how to set targets, what to record, and how to close a callout out properly.
Priorities and targets
Most contracts use four priority levels, each with three targets: how fast you respond, how fast you are on site, and how fast the job is closed out. As an example, traqR’s defaults are:
| Priority | Respond | On site | Close out |
|---|---|---|---|
| P1 (emergency) | 15 minutes | 4 hours | 24 hours |
| P2 (urgent) | 1 business hour | Next business day | 48 hours |
| P3 (routine fault) | 4 business hours | 24 hours | 72 hours |
| P4 (minor) | 1 business day | 3 business days | 5 business days |
Your targets should match what you can actually deliver and what each contract says. Software should let you set company defaults and override them per contract.
Stamping every step
Response times are only credible if they are recorded as they happen: when the call was reported, when a technician accepted it, when they set off, when they arrived and when the job was closed out. Each stamp should come from the action itself, not be typed in afterwards. When work has to pause for a genuine reason, such as waiting on parts or access, the clock should pause with it, and the reason should be recorded.
Logging the callout fast
Callouts arrive by phone, email and the client portal. Each should become a logged callout with its priority straight away. Clients raising a request through a portal can set the priority themselves, and an alarm email from a known building can be logged automatically. A technician rostered on callout duty for a contract should be notified the moment it is logged.
Warnings before a miss
The point of tracking is to act before a target is missed, not to report on it afterwards. Software should flag callouts at risk while there is still time to reassign them, and alert the right people immediately when an emergency target is missed.
Closing it out
A callout is finished with a close-out report: what the call was, the fault found, what was done, the hours and materials, and the outcome. If it is not finished, the technician should say why and book the return. One callout should produce one invoice, however many trips it took, raised at close-out from the callout fee and labour.
Reporting to the client
At contract review, facility managers want to see how many callouts were logged and how many met their targets. Software should produce those figures per contract, on the report and in the client portal, where the client has agreed to see them.
What to look for in fire callout software
- P1 to P4 priorities with respond, on site and close out targets, set per company and per contract.
- Timestamps taken from the technician’s own actions.
- A paused clock for genuine waits, with the reason recorded.
- Callouts logged from the portal and email, with on-duty technicians notified.
- At-risk warnings and miss alerts.
- A close-out report that invoices the callout or books the return visit.
- Response time figures per contract for the client.
Frequently asked questions
What is a callout SLA?
A service level agreement for reactive work: the response, attendance and close-out times a contractor commits to for each priority of callout.
What counts as a response?
Contracts define it differently. In traqR, a callout is responded to when a technician accepts it, which is a recorded action rather than a phone call nobody logged.
Should the clock stop while waiting for parts?
Usually, if the contract allows it and the reason is recorded. Waiting for parts, another trade, access or the client’s request are common reasons; running out of time is not.
Can clients log callouts themselves?
Yes, through the client portal, choosing the priority. The callout is logged straight away and the technician on duty for that contract is notified.