In the hypothetical scenario below, a dispatcher spends 91 minutes calling 23 guards from memory at 2:14 AM. The replacement arrives unarmed. The client's 24-hour audit catches it. The contract goes on 30-day probation. This is what every contract guard operator is one bad night away from.
Below is an illustrative dispatch log of that night — minute-by-minute, timestamp by timestamp. Then we show you the same 24 hours with XShift running the dispatch. The contrast is the point.
21-day free trial · Credit card required to start · Cancel anytime in the trial
Everything below is a hypothetical, illustrative scenario. The operator (24 sites, 180 officers, $14M revenue), the client (“BankCorp HQ”), the officer names (Marcus, David), the timestamps, the $820,000 contract value, and every dollar figure are fictional illustrative composites based on typical mid-size contract-security-operator economics. They are not measured XShift customer outcomes and are not drawn from any real customer's data. We're using a concrete scenario to show what the product does — not to describe any real event.
An $820K contract is ~5.9% of total revenue and ~73% of an entire year's profit margin. Losing it ends bonuses. Losing two ends careers. One empty post can do it.
Every entry below is a hypothetical CAD-style dispatch log for an illustrative 24-site, 180-officer security operator. The timestamps, names, and dollar amounts are fictional — but the failure mode is the one that lands on real operators when there's no system between the call-off and the call list.
One day. $820K contract on probation. $1,680 in week OT. $210 in dispatcher OT. Owner trust shaken. Multiply by 250 working days/year and you're looking at $420K/year of preventable OT and 22,000 minutes of dispatcher phone-tree time — not counting the contract impact. The phone tree isn't a scheduling problem. It's a margin problem. It's a retention problem. It's an existential problem.
Same call-offs. Same guards. Same client sites. Different log.
Same hypothetical 24 hours. Same two call-offs. Same illustrative operator. The Autopilot is on. Manager Approval is on. The day threshold is 0.5 days, so anything inside 12 hours uses Messages mode. Watch what happens.
The dispatcher had a quiet day. The operator preserved an $820K contract. The OT bleed went from $1,680/week to $240/week — a $74,000/year line-item recovery. The owner didn't have to call. The clients didn't have to call. And nothing happened. Which is exactly the point.
Not a starter tier. Not an “upgrade to unlock.” Every feature listed below runs in the standard XShift account, from the first guard you onboard.
The phone tree, deleted
The second a guard calls out, the Autopilot runs the qualification filter across all 180 officers in your org — location, role clearance, availability, weekly hours, PTO, conflicts, and rest. You set the day threshold; calls-offs at or beyond it auto-assign, calls-offs under it send one-tap accept messages to a qualified short list. Manager Approval toggle lets you stay in the loop or let it run.
One command. The whole week.
Type: “Generate next week's schedule.” The Copilot validates every single constraint across all 24 sites and 180 officers in under a minute: availability, OT exposure aggregated org-wide, role clearance, time-off, hour caps, preferences, pairing rules, minimum rest.
Catch OT before it crosses 40
Scheduled scan, or run-now. Finds every officer approaching the weekly overtime threshold, surfaces qualified non-OT replacements for the shifts that would push them over, with the dollar math attached. One tap to approve. Never auto-swaps.
No more cross-client invisibility
Every officer's hours are aggregated across your whole organization, not per client site. The 22-hour officer at BankCorp shows up in every other site's candidate list. The 38-hour officer at the warehouse falls to the bottom.
11+ hrs between shifts. Enforced.
Tell XShift: “Every officer needs at least 11 hours between when one shift ends and the next starts.” The Autopilot and the schedule grid both honor it. The closer-to-opener back-to-back never lands on the schedule.
Your operation, your rules
Pairing constraints (officers who can't work together), daily and weekly labor caps per site, per-day-of-week caps, OT-block rules. Each rule fires at assignment time, not at payroll time. Hard mode blocks the save; soft mode lets you force-save with a reason.
Retention is a feature
Each officer configures preferred days, unavailable days, preferred start/end times, and a maximum hours per week. The AI Copilot honors them during schedule generation. Officers who feel scheduled-with, not scheduled-at, stay longer.
Live same day · no implementation
The AI Copilot walks you through setup in natural-language chat. Configure your sites (locations) and posts (roles), bulk-import officers from a CSV, ask the Copilot to generate your first schedule. No 6-month implementation. No IT review.
You can keep running dispatch on memorized phone trees, hoping that tonight's 2:14 AM call-off doesn't land on a $820K contract.
You can keep paying $74,000 a year in overtime that didn't need to be paid, because cross-site hours never aggregated and the under-40-hour officer at your other site never surfaced.
You can keep losing dispatchers to burnout because 90-minute phone trees at 3 AM are the second job they didn't sign up for — and watch the cost cascade every time one quits.
Or you can give your dispatcher a system that runs the qualification filter in seconds, sends the one-tap accept message to only the qualified short list, aggregates hours org-wide, surfaces OT swaps with the dollar math attached, and lets your dispatcher have a quiet day.
$208/month to make your dispatcher's log boring. The math doesn't need a calculator.
Tonight your dispatcher will be on the desk at 23:47. You decide which log she writes.
XShift's Autopilot and AI Copilot enforce the rules you configure — minimum rest hours between shifts, weekly hour caps, daily and weekly labor caps, pairing constraints, officer preferences, and per-role staffing minimums. The operations manager and dispatch supervisors remain in control of every decision and can override or reverse Autopilot at any time. Schedules are reviewed before they go live. XShift is a workforce-operations tool, not a compliance product — your operation, your management team, your attorneys, and the relevant regulators (state guard licensing, wage-and-hour, union contracts where applicable) determine whether your configured rules satisfy applicable law. XShift does not track state guard card or other certification expirations; certification currency is managed in your HR system, and the role assignments in XShift reflect what the manager has set.
The 24-hour dispatch log on this page is an illustrative composite based on typical mid-size contract security operator economics (24 client sites, 180 officers, $14M annual revenue, 8% margin). The timestamps, names, contract values, and dollar figures are illustrative — they are not measured XShift customer outcomes and are not drawn from any single customer's data. Actual results depend on your operation, wage structure, client SLAs, regulatory environment, and how you configure XShift.