A 2am activation, pieced together later
The alarm receiving centre calls your control room: intruder alarm, zone 3, at a car parts warehouse. The controller logs the call on a spreadsheet, rings the mobile officer and gives him the address and key tag. The officer drives there, walks the perimeter, lets himself in, checks zone 3, finds a pallet had fallen against a sensor, resets the alarm with the ARC, locks up and leaves. He texts the controller: 'all ok false alarm pallet, reset, left 2.55'.
The next morning, the client asks for the attendance report. What time did your officer arrive? Did he check the whole building or only zone 3? Were there signs of entry? Is there a photo of the pallet? The controller's spreadsheet has the call time. The rest is in a text and the officer's memory.
Why alarm response records have gaps
Alarm response happens in stages, each captured by a different person in a different way. Arrival time, time on site and what was checked are often not recorded at all, or recorded after the fact. Clients who pay for response increasingly expect to see exactly what they paid for.
- The activation details come from the ARC by phone or a separate system.
- Dispatch is a phone call with no timestamp in any record.
- Travel and arrival times are estimated afterwards.
- The officer's checks and findings are sent by text, if at all.
- Reports are typed next day from fragments.
What incomplete records cost
Clients query invoices when they cannot see what was done. Response times you promised in your contract cannot be shown, even when you met them. False alarms at the same site recur without anyone spotting the pattern, which wastes callouts and annoys clients. And if a real break-in follows an earlier false alarm, everyone will want to know exactly what your officer checked last time.
Response standards and any obligations under your contracts or the alarm system's policy are for your company and its advisers. We build the record of what happened.
An alarm response log from activation to secure
- The activation is logged in the control room with the ARC's details: client, site, zone, alarm type, ARC reference, time. Where the ARC can send activations electronically, they arrive automatically.
- Dispatch sends the job to the officer's phone with the site, key tag, access notes and any site hazards.
- The officer taps accepted, en route and arrived, which records each time. Phone location can confirm arrival where your policy allows it.
- On site, a checklist for that client guides the officer: perimeter check, entry points, zone checked, internal sweep, alarm reset or set, premises secured.
- Findings are recorded with photos: signs of entry, cause if found, damage.
- The officer marks secured and departed, with times. If police or the keyholder were involved, their details and references are added.
- The attendance report is produced from the log and sent to the client after a controller check, the same night or the next morning as you prefer.
| Stage | Recorded by | Shown in client report |
|---|---|---|
| Activation | Control room or ARC feed | Time, zone, alarm type |
| Dispatch and arrival | Officer's phone | Times and response time |
| Checks carried out | Officer's checklist | What was checked |
| Findings | Officer, with photos | Cause, damage, photos |
| Secured and departed | Officer's phone | Times, alarm status |
The same callout, with the log
The activation arrives at 1.52am. The officer accepts on his phone and is on site at 2.14. His checklist records the perimeter, the entry points and zone 3, with a photo of the fallen pallet and the reset. He marks secured at 2.53. The client gets a one-page report at 8am. When the same zone triggers again a fortnight later, the client's history shows the pattern, and your account manager can suggest the client asks their alarm installer to look at the sensor.
Signs your alarm response records need work
- Callouts are logged on a spreadsheet by the controller.
- Arrival times are estimated afterwards.
- Officers report findings by text.
- Clients ask what was checked and you cannot say.
- Repeat false alarms at a site go unnoticed.