Apeiron CAD is security guard management and computer-aided dispatch software that connects the people running a security operation with the officers working in the field. It brings dispatch, guard status, patrol rounds, incident handling, scheduling, timekeeping and client reporting into one system. Built for private security companies, it gives owners and supervisors a clearer view of operations while giving guards practical tools for the work in front of them.
The dispatch board combines an on-shift roster, active calls, guard statuses and a live map. Dispatchers can see assigned responders, call priorities and recent activity alongside the people handling the work. Statuses such as Available, On Patrol, En Route, On Scene and Break make the operational picture easier to understand. Location freshness matters too: the board distinguishes current information from older updates so a last-known position can be interpreted in context.
Incident dispatch keeps the call and its response in one place. Staff can create an incident, record its site or address, set its priority, assign responders and follow its progress. The incident history records updates as the response develops, giving the next dispatcher or supervisor context for a handoff. Responders can be attached to the same incident, and staff can review who is assigned and what has already happened. This helps teams coordinate suspicious-person calls, alarms, access concerns, property issues and other everyday security events.
The updated guard app organizes work around Home, Schedule and More. Home brings together clock-in and clock-out, the status shared with dispatch, patrol rounds, daily activity entries and incidents. Smaller shortcuts open the map and daily activity history. Schedule keeps upcoming shifts and shift history together, while More provides access to additional tools such as BOLOs, team information, reports and post orders.
Patrol rounds turn a site's instructions into a sequence of actionable checks. A configured route can include ordered points, instructions, QR requirements and required notes. During a round, the guard sees the current point and progress through the route. A point may require a matching QR scan or allow a manual check, depending on its configuration. Required observations are recorded with the point result. If a guard cannot complete a check, an explained exception records the problem so the operation can distinguish a successful visit from a point that could not be checked.
Each round has its own progress and outcome. Completed checks, exceptions and remaining points stay distinct, helping supervisors understand what the guard actually did. An unfinished round can remain incomplete when the shift ends, preserving the work already recorded. Corrections add context without silently replacing the original result or visit time. These details matter when a gate is inaccessible, a required area is unsafe to enter or a client asks why a particular part of a round was not completed.
The native app supports full offline rounds using routes downloaded while connected. Guards can work through a saved route and retain checks, notes and progress through an app restart. Queued work uploads when connectivity returns, with the original action times preserved. Dispatch sees the progress it has received, including when it was last received. This is useful on sites where service varies between buildings or disappears in a basement or parking structure. Downloaded routes and saved evidence help field work continue through those gaps.
Daily activity reporting gives routine work a place alongside incidents. Guards can record observations as they happen, including site conditions, checks and other activity that does not need a separate dispatched call. Shift records can bring together clock-in and clock-out, status changes, checkpoint activity, round evidence and officer notes. A Daily Activity Report presents that information in a readable document under the security company's branding. Instead of reconstructing a shift from scattered messages, supervisors can work from a record built during the shift itself.
Formal incident reports provide a separate workflow for events that need a fuller account. Guards can draft the narrative, attach supporting photos and submit the report for supervisory review. The review process supports a clearer distinction between an active operational call and the finished account of that event. Dispatch activity explains how the response unfolded; the formal report captures the details the organization needs to retain or share. Keeping those workflows connected helps the team move from response to documentation without losing the incident's context.
Field incident tools let guards create new incidents and open their assigned work from the app. Incident details can include the reference, priority, status, reported time, location, description and immediate safety information. A new incident can identify an existing company site or an off-site address and include initial actions taken or relevant contact details. Guards can review the latest update and use the actions available to their role. The unresolved incident count on Home helps draw attention to assigned work that still needs a response.
BOLO alerts keep important descriptions available across the operation. Staff can publish be-on-the-lookout information about a person or vehicle and include photos to make identification clearer. Guards can review active BOLOs and explicitly acknowledge them. The app separates reviewing later from acknowledging an alert, so postponing the prompt does not imply the information has been read. Active alerts remain accessible for reference. This gives the team a shared place for information that otherwise might disappear into a radio conversation or group message.
Broadcasts and notices support communication beyond individual calls. Dispatch can send a message to the team or a particular site and track acknowledgments. Notices give guards a place to review relevant changes and follow through to the associated information. Supported delivery channels include in-app notices, email and push notifications according to the event, configuration and recipient's preferences. A persistent inbox helps important changes remain available after a notification has disappeared from the lock screen, while explicit acknowledgments make the next action clearer.
Guard safety is visible in the operational workflow. The hold-for-SOS control gives an on-duty guard a direct way to raise an emergency alert. Dispatch can see the alert, locate the guard using available position information, acknowledge it and manage the response. The board also gives staff information about guard status and update freshness that can support welfare checks. Optional Zello integration brings radio presence and supported radio emergency information into dispatch, helping staff connect field communication with the people and incidents already on the board.
Location sharing follows the guard's duty state. The app makes it clear when sharing is active and when the guard is off duty. Off-clock status sharing is separate from collecting a new location: a status can be communicated while location sharing remains off. Clock-out stops duty tracking, and the permission experience explains location use to the guard. This distinction helps companies coordinate their teams while giving officers a clear understanding of what is shared. Native background location depends on the device permissions and operating-system behavior.
Scheduling and timekeeping connect planned coverage with the shift record. Staff can prepare schedules before publishing them, assign guards to posts and review who has actually clocked in. Guards can see upcoming shifts and request time off through the app. Shift history gives them a place to review past work and relevant corrections. Authorized staff can correct timeclock records or close a shift when needed, with a history of the change. The operational record remains important alongside payable time, so reviewing hours does not require treating every timestamp as interchangeable.
Site information and post orders keep instructions close to the work. A guard can refer to the site's guidance while on assignment, and supervisors can maintain the information their teams need. Clients, sites, posts and personnel are managed within the company's workspace. License and certification tracking helps staff identify expiring or expired credentials, while scheduling and coverage tools support day-to-day planning. Bringing these details together helps an owner or supervisor answer practical questions about who is assigned, what they need to know and what requires attention.
The client portal extends visibility beyond the security company's internal team. Companies can provide clients with access to the site information and reports they are permitted to see, using the security company's branding. Daily activity report publishing is configurable, allowing the company to decide when that reporting is shared. A portal gives clients a consistent destination for their service information and helps account managers respond with the same records used by operations. It can support a more concrete conversation about patrol activity, incidents and the work performed during a shift.
Apeiron CAD supports several working environments: the browser-based dispatch console, a vehicle-oriented browser workspace and native guard apps for iPhone and Android. Each surface serves a different role in the same operation. Dispatch focuses on coordination, field tools focus on the next action, and reporting focuses on the evidence left behind. Company settings and role-based access govern which tools and records are available. The result is a connected workflow for private security teams that want clear dispatch, usable field tools and a reliable account of the service they provide.
Who Is the Company Behind Apeiron CAD?
