Mobile Patrol & Alarm Response Software for UK Security

An alarm trips at 2am. Your mobile officer is fifteen minutes out, does the lock-and-unlock, and by the time they're back in the van the only record of any of it is a text to the office and a memory of what time they think they arrived.

What most firms do today

A logbook in the van, a phone call to confirm arrival, and an invoice at the end of the month built from whoever remembered to write the callout down. Alarm response in particular tends to run on trust: the client assumes someone showed up inside the contracted time, and the only way to check is to ask the officer.

How TacDesk handles mobile response

A roving shift, not a site shift. An officer clocks onto Mobile Duty, a shift with no fixed site or geofence, rather than clocking in at one client like a static guard does.

Every stop is a visit. Arriving at a site starts a visit tagged as a patrol, lock/unlock, alarm response, inspection or keyholding call, with GPS captured at the moment of arrival. Leaving closes it out, with GPS captured again at departure, and either queues a report or marks the visit as needing no report. If the officer's phone has no signal, the arrival or departure is recorded locally and syncs automatically once it's back online, without creating a duplicate visit when it does.

Alarm callouts run on a clock. A callout raised on the callouts board carries an SLA target in minutes set per client. Officers record their own status as they go, en route, on site, then cleared, and if a callout runs past its target before someone marks it resolved, TacDesk flags it as breached automatically rather than waiting for someone to notice.

It plugs into dispatch. A new callout or incident can auto-attach the nearest available mobile officers within a set radius, provided your account also has Dispatcher Mode switched on; officers already tied up on another visit or callout are skipped, and the ones who get sent are notified on their phone the moment they're attached.

Rounds give structure to the roving shift. Management can build a mobile round, a defined sequence of site visits, and assign it to an officer, with the officer's live progress against that round visible while the shift is on.

Billing follows the visit, not an estimate. Each visit can be marked billable or not, and invoicing can charge per visit at a rate set for that client, drawing on the visits that were actually completed and submitted rather than a flat monthly guess.

Why it matters

A client asking "were we alarm-checked last Tuesday" gets a timestamped answer. Arrival and departure times, GPS position and the officer who attended are on the visit record, not in someone's memory.

SLA breaches show up on their own. Nobody has to audit callout times by hand; a callout that ran over is already flagged.

Invoicing matches what happened on the ground. Per-visit billing is built from the visit log itself, so the invoice and the record it's based on are the same data.

Where it sits

Mobile Response is included on every paid plan, TacStarter, TacPro and TacCommand. It isn't part of TacFree, so roving patrols and alarm response aren't available on the free tier.

Pairing it with Dispatcher Mode is what lets new incidents auto-attach your roving officers rather than just your on-site guards; Dispatcher Mode is included from TacPro up, or available as an add-on on TacStarter (check the pricing page for the current price). Reports filed on a mobile visit are ordinary incident reports, and vehicles used on mobile patrol are tracked under fleet management if you're on a plan that includes it.

Start free to try the core app, then book a demo to see Mobile Response running against a real callout.