The 90-Minute Problem Nobody Has a Real Answer For
A guard calls off at 5:45 a.m. Shift starts at 7:00 a.m. You have one dispatcher, three group chats, a spreadsheet of availability that has not been touched since December, and a client who will notice if that post goes unmanned.
This is not an edge case. If you run more than 40 active guards, this happens multiple times a week. The question is not whether you will face it. The question is whether your operation has a repeatable system for resolving it quickly, or whether you are relying on whoever is awake and willing to make calls until something sticks.
Most security firms operate in reactive mode. A call-off triggers a scramble. The scramble depends entirely on who is working dispatch that morning, what they remember about who is available, and whether anyone picks up the phone. There is no playbook. There is institutional knowledge living in one person's head, and when that person is off, coverage response degrades.
This article is about building the dispatch playbook that removes the scramble. Not in theory. In operational detail.
Why Most Call-Off Workflows Break Down
Before building the fix, it is worth diagnosing the failure modes clearly.
Availability data is stale. Most teams track officer availability in a shared spreadsheet or inside a scheduling tool that nobody updates in real time. The dispatcher calls someone marked available and gets voicemail. Calls the next person. Same result. By the time they reach someone willing to take the shift, 40 minutes are gone.
Escalation paths are undefined. Who gets called first? What qualifies an officer to cover a specific post? If it is a credentialed site, does the covering officer have the right license? Most teams have no documented answer to these questions. The dispatcher makes judgment calls under pressure, and those calls are inconsistent.
The shift decision and the notification are separate manual steps. Once someone agrees to cover, a dispatcher still has to update the schedule, notify the client if required, confirm check-in instructions, and make sure the officer has access to the post order. That chain of steps introduces more delay and more surface area for error.
There is no time pressure built into the workflow. Without a defined response SLA, a call-off can sit in a group chat for 25 minutes while everyone assumes someone else is handling it. Urgency is implied but never enforced.
The 15-Minute Dispatch Framework
Fifteen minutes is achievable. It requires three things working in sequence: a defined qualification filter, a tiered contact sequence, and automated confirmation handoffs. Here is how to build each one.
Step 1: Define the Post Profile Before You Need It
Every post in your system should have a qualification profile attached to it. At minimum, that profile should specify the license type required, any site-specific training or access credentials, whether the officer needs a vehicle, and the physical location relative to officer home addresses or last known locations.
This is setup work, not dispatch work. If you are doing qualification filtering during a 5:45 a.m. call-off, you have already lost time. The profile should exist before the schedule is ever built.
With a post profile in place, your dispatcher does not need to think about eligibility. They pull the list of officers who qualify for that post. That list is the only list they work from.
Step 2: Build a Tiered Contact Sequence
Not all available officers should be contacted with equal priority. A tiered sequence gives your dispatcher a structured order to work through instead of calling whoever comes to mind first.
Tier one: officers who are scheduled off and have confirmed standing availability, have previously covered that post, and are within a reasonable commute distance.
Tier two: officers currently on a shift that ends within two hours of the open shift start, who could extend or transfer without creating a fatigue or overtime violation.
Tier three: officers flagged as available but who have not covered that specific post before and may require a brief orientation or post order review.
This tiering does two things. It increases first-contact success rates because you are leading with the highest-probability options. And it protects the operation from eligibility mistakes that cause compliance exposure.
Document the tiers. Put them in writing. Make sure every dispatcher works from the same sequence.
Step 3: Set a 7-Minute Contact Deadline Per Tier
This is the part most playbooks skip, and it is the part that actually enforces the 15-minute target.
If tier one contacts have not produced a confirmed coverage commitment within 7 minutes, the dispatcher moves to tier two. No exceptions, no waiting to see if someone calls back. The clock is the rule.
This forces action and prevents the dispatcher from spending the entire available window on one or two preferred officers. It also makes performance measurable. If tier one consistently fails to produce coverage, that is a data point about your availability pool, not a dispatch failure.
Step 4: Separate Confirmation from Commitment
When an officer verbally agrees to cover, that is a commitment. Confirmation is different. Confirmation means the schedule has been updated, the officer has received the post address and check-in instructions, the post order has been sent to their device, and if client notification is required, that notification has gone out.
If confirmation depends on a dispatcher manually completing all of those steps after the call, you will lose another 10 to 15 minutes and introduce error. The confirmation workflow should be automated as much as possible. When an officer is assigned to the shift, the system should push the post order, trigger a client notification if that is part of the service agreement, and log the assignment with a timestamp.
The dispatcher's job ends at confirmed assignment. The system handles the rest.
What This Looks Like in Practice
A regional security firm running 85 guards across commercial, residential, and retail sites rebuilt their call-off workflow using this framework last year. Before the rebuild, their average time from call-off to confirmed coverage was 38 minutes. Roughly one in five call-offs resulted in a late start or uncovered post.
After implementing the post profile system, tiered contact sequences, and automated confirmation steps, average coverage time dropped to under 14 minutes. Late starts dropped by over 60 percent in the first quarter.
The change was not technology-driven. They did not buy a new platform. They documented a workflow that had always existed informally and made it repeatable. The technology supported the process. The process was the work.
The Compliance Dimension Nobody Talks About
Call-off coverage decisions carry compliance risk that rarely gets discussed in dispatching guides.
If an officer covers a post that requires a specific state license or site credential they do not hold, that is not just an operational problem. It is a liability exposure for the company, and potentially a regulatory violation depending on your jurisdiction. When dispatch is moving fast and under pressure, these checks get skipped.
Building eligibility into the post profile and the contact list means those checks happen before the call, not during it. The dispatcher is not responsible for knowing every officer's license status. The system filters the list. The dispatcher works the list.
This is where modern workforce operations platforms add real value. Arcova OS handles post qualification filtering, officer eligibility checks against active license and certification records, and shift assignment confirmations in the same workflow. Dispatchers work from a filtered, compliance-aware contact list rather than relying on memory or manual checks during high-pressure moments.
Turning the Playbook Into a Standard Operating Procedure
A playbook only works if it is used consistently. That means documenting it formally and training every dispatcher against it, not just the senior ones.
Your dispatch SOP should include the trigger conditions that activate the protocol, the tiered contact sequence with time gates, the eligibility filters by post type, the confirmation steps and who owns each one, and the escalation path if coverage cannot be confirmed within the window.
Test the SOP in low-stakes scenarios before you need it in a crisis. Run tabletop exercises. Time your dispatchers. Identify where the process breaks down under real conditions and fix it before those conditions are a 5:45 a.m. call-off at a client site with a notification requirement.
Coverage Is a System Problem, Not a Hustle Problem
The instinct in most security operations is to solve coverage problems by working harder. Call more people. Move faster. Put in the hours.
That approach does not scale, and it burns out good dispatchers. Coverage reliability is a system design problem. It gets solved with documented workflows, qualified contact lists, time-gated escalation, and automated confirmation steps.
When your dispatch process is repeatable, coverage response becomes predictable. Clients notice. Retention follows. And your dispatchers can do the job without carrying the entire operation in their heads.
The 15-minute target is not aspirational. It is the result of removing the parts of your workflow that depend on memory, luck, and whoever happens to be awake.