How do you design a guard dispatch workflow?

This article gives a practical, ordered workflow you can copy into operations to connect written SOPs, dispatch software, guards and monitoring systems. Follow these steps to define boundaries, create a dispatch ticket template, link CCTV and remote monitoring safely, set escalation stop points and test the system before live service.

Step 1: Define objectives, scope and service boundaries

Start by documenting what your dispatch workflow must cover. Include property types, hours of coverage, expected response expectations, whether you use on-site guards, mobile patrol or remote monitoring, and which service areas you expect to serve. If you work with a contractor, record the geographic coverage and services available from that firm so you do not promise unavailable capabilities. For example, Accure Security describes offering licensed on-site guard teams, mobile patrol, event security, construction protection, fire watch and remote monitoring across Ontario regions such as the GTA and KWC areas, which helps set realistic scope when contracting services.

A clear scope prevents automatic job creation for locations or hours where staffing or licensing is not available. Record any short-notice constraints and make them visible to dispatchers in the first intake step.

Step 2: Map the dispatch lifecycle as ordered steps

Draw a single linear flow from alert or call receipt to incident closeout. Use explicit decision points that demand a yes or no answer. A compact lifecycle looks like this:

1. Receive the report or alarm.
2. Triage: verify credibility and severity.
3. Assign a unit or job to a guard or patrol.
4. Guard accepts the job and acknowledges ETA.
5. Respond on site with continuous monitoring or remote support.
6. Closeout: collect evidence, timestamps, and final notes.

When you build this into dispatch software, ensure the system enforces the decision points. Guard-management platforms commonly let back-office users create and manage dispatch tickets and capture details such as call source, caller information, incident description and actions taken, which improves coordination between dispatch and field personnel. See the GuardsPro support article for an example of required ticket fields and workflows.

Key substeps and stop points

• Receive: capture caller, call source and location. If location is unclear, stop and clarify before moving on.
• Triage: ask scripted questions to determine severity. If the incident involves immediate danger to life or property, stop triage and call emergency services.
• Assign: pick the nearest trained unit that has the correct license and equipment for the task. If no appropriate unit is available, record the constraint and escalate to a supervisor.
• Accept: require a positive acknowledgement and ETA from the unit. If no acceptance within the configured window, reassign automatically and notify the supervisor.
• Respond: field personnel must follow site-specific procedures and evidence collection steps. Stop if a scene becomes unsafe and await police.
• Closeout: require photos, witness statements and timestamps before closing the ticket. If evidence is incomplete, mark the ticket as pending and schedule follow-up.

Step 3: Create a dispatch ticket template you can copy

A consistent ticket template removes ambiguity. Use required fields to force minimum information and optional fields for extra context. Guard-management systems show how to create these tickets and which fields are essential to field teams in real time, as illustrated in the GuardsPro guidance.

Required versus optional fields

• Required: incident ID, location/address, call source, caller name and phone, incident description, priority level, assigned unit, dispatch time stamp.
• Optional: CCTV clip ID, access control event ID, building contact, photos attached, weather or crowd notes.
• Mark attachments and multimedia as time-stamped evidence to support later reporting.

Step 4: Write SOPs and decision rules that link to dispatch actions

Turn the lifecycle into short SOPs that dispatchers can follow without interpretation. Each SOP should have a one-line trigger, a short triage checklist and the exact dispatch action. Modern SOP workflow tools can dispatch a guard directly from the workflow and automatically create a job, showing the job acceptance status back in the SOP. That pattern helps tie procedural steps to dispatch actions but it requires platform integration or subscriptions in some products, as explained in the CONXTD SOPs documentation.

Include acceptance criteria for jobs, such as minimum location detail and caller confirmation. Also define stop points: for example, when the caller reports violence in progress, call 911 immediately and do not dispatch a guard unless the police request private security assistance.

SOP checklist you can copy

• Trigger: what starts this SOP (CCTV motion alert, alarm panel, telephone report).
• Confirm caller identity and location.
• Classify severity: low, medium or high.
• If high severity, call emergency services and notify supervisor.
• If medium severity, assign nearest qualified unit and require job acceptance within X minutes.
• Record CCTV or access-control evidence references when available.
• On arrival, secure scene and collect evidence, then update the ticket with photos and witness statements.
• Close ticket only after required fields and evidence are attached.

Step 5: Integrate dispatch software with CCTV, remote monitoring and access control

Map which events should auto-create tickets and which require human triage. Typical safe auto-ticket triggers are verified alarm zones, confirmed access-control breaches and monitored camera analytics that meet a confidence threshold. Link the ticket record to the CCTV clip ID, camera name and timestamp so the responding guard can view the evidence before arrival. Accure Security combines manned guarding with live remote monitoring and CCTV installation, which is the model most property managers use to align technology and field response.

When a ticket originates from a monitoring source, the dispatch record should show the source type and a short verification step performed by the operator. The ticket status should display job acceptance and offer real-time updates to the SOP workflow so the dispatcher can see when a guard has accepted the job and begun travel.

Which automations to allow and which to avoid

Safe automations to allow include auto-ticket creation from verified alarm systems, notifications that show job acceptance and camera snapshots attached to tickets. Automations to avoid include automatically dispatching guards to high-risk incidents without human triage, or scripting any automated instruction that would direct a guard to take enforcement action without supervisor approval. SOP workflow tools can connect automated steps to job creation, but always keep the human-in-the-loop for critical safety decisions.

Step 6: Define roles, train staff and standardize shift handovers

Document clear role definitions for dispatchers, field supervisors and guards. Train dispatchers on intake scripts, risk classification and the software interface. Train guards on job acceptance etiquette, travel ETA updates and evidence collection standards. Use a handover template for shift changes that lists open tickets, outstanding actions, last contact times and any safety concerns.

• Dispatcher training checklist: intake script, ticket creation, SOP triggers, escalation rules and police liaison procedures.
• Guard training checklist: job acceptance, ETA updates, on-site evidence capture, interaction with emergency services and post-incident reporting.
• Handover template: open ticket IDs, brief description, pending actions, assigned units, next steps and supervisor notes.

Step 7: Test the workflow, set KPIs and schedule continuous improvement

Run table-top and live tests for common scenarios such as false alarms, confirmed break-ins, medical emergencies and after-hours breaches. For each test, measure simple KPIs: time to ticket creation, time to assignment, time to acceptance, time to arrival and percent of tickets with required evidence attached. Maintain a log of post-incident reviews and update SOPs when you find repeated gaps.

Use the guard-management system to export reports and identify patterns, such as frequent false-alarm sources or repeated failure to accept jobs. Schedule quarterly reviews of the SOPs and software mappings to keep the workflow current with staffing and technology changes.

Common failure points and practical mitigations

• Poor ticket data: require minimum fields before a ticket can be assigned.
• Staffing gaps for short-notice coverage: publish a realistic short-notice policy and automate escalation to supervisors when no unit is available.
• False alarms: implement a verification step from monitoring before dispatching for low-priority events.
• Software mismatch: map critical fields between systems during procurement and test with real scenarios before go-live.

Ontario considerations: licensing, police liaison and data handling

Before deployment verify that any contracted guards are licensed for Ontario and that your SOPs align with local police notification practices. Document data retention policies for incident records and ensure access control for sensitive evidence. For contractors offering combined guarding and monitoring services it is useful to record their geographic footprint and service terms so your scope and escalation plans match what is actually available in the field.

Copyable dispatch ticket and SOP checklist

Dispatch ticket template: fields and sample entries

• Incident ID: 2026-0001
• Date/time reported: 2026-08-19 14:02
• Location: 123 Example St, Building A, Unit 2
• Call source: CCTV motion alert
• Caller: Remote monitor - Operator J. Smith
• Priority: Medium
• Incident description: Motion detected in loading dock, camera 4 shows person at door
• Assigned unit: Patrol Unit 5
• ETA: 18 minutes
• Attachments: Camera clip ID 20260819_CAM4_1401.jpg
• Actions requested: Attend, secure dock, hold for police if requested
• Closeout notes: Photos attached, witness statement collected, ticket closed

One-page SOP checklist

• Trigger and source verified
• Caller and location confirmed
• Severity classified and escalation decided
• Unit assigned and acceptance required
• On-site procedures and evidence checklist followed
• Emergency services called when required
• Ticket closed with required evidence and timestamps

Frequently asked questions

What fields must a dispatch ticket always include?

Always include incident ID, precise location, call source, caller name and phone, incident description, priority, assigned unit and time stamps. These required fields support accountability and post-incident reporting.

When should dispatchers call 911 instead of sending a guard?

Call 911 immediately for threats to life, active violence, major medical emergencies or ongoing criminal acts. Dispatch a guard only when the scene is secure or when police request a private security presence.

Which events should automatically create a dispatch ticket from CCTV or remote monitoring?

Auto-ticket creation is appropriate for verified alarm zones, confirmed access-control breaches and high-confidence analytic detections. Low-confidence motion alerts should route to human triage to avoid unnecessary dispatches. For examples of auto-ticket fields and workflows see the GuardsPro guidance and SOP workflow documentation.

How do you test a new dispatch workflow before putting it into live service?

Run table-top scenarios, then live drills that simulate typical incidents such as false alarms and after-hours breaches. Measure ticket creation times, assignment and acceptance metrics and verify evidence capture before declaring the workflow ready for live operation.

Can a dispatch workflow support short-notice coverage across the GTA and KWC regions?

Possibly, but you must document short-notice availability and verify contractor staffing levels for each region. If you use a provider that lists coverage for the Greater Toronto Area and Kitchener–Waterloo–Cambridge regions, record those service boundaries in your scope so dispatchers do not attempt assignments outside the available footprint.

If you prefer help implementing this workflow, Accure Security can perform on-site risk walk-throughs, design coverage and integrate guards with remote monitoring, CCTV and access control across Ontario. Contact Accure Security for details and a site assessment: Accure Security.