What questions should you ask about patrol response coordination?

Patrol response coordination describes how on-site guards, mobile patrols, remote monitoring, and access control work together to detect, verify, and resolve incidents. For property managers, event organisers, construction supervisors and municipal buyers in Ontario, the quality of that coordination determines whether an incident is handled cleanly and documented, or becomes a messy liability and communication failure. Accure Security combines licensed guard teams with live remote monitoring, CCTV installation and access control under a single operating plan, which is the model procurement teams should look for when testing patrol response coordination on a vendor site.

What patrol response coordination covers and why it matters

Scope: what to include in a coordinated plan

A complete patrol response coordination plan covers detection (sensors, cameras, alarms), verification (monitoring operator or patrol confirming the event), initial response (guard or mobile patrol attendance), escalation (police, EMS, client), and post-incident documentation (incident report, evidence handling, follow-up actions). The operating plan should explain how each step connects so responsibilities do not overlap or fall through gaps. Ontario's Incident Management System emphasises common objectives, shared information and coordinated tools to enable multi-organization responses, which is directly relevant when private security must liaise with public responders (IMS principles).

Who does what

Identify the named roles in the plan: incident commander (on-site lead), patrol supervisor, monitoring operator, police liaison, and the client site contact. Naming roles prevents the common dispute over who made a decision, and it lets procurement specify deliverables tied to each role, for example who will accompany police or who secures evidence after a forced entry.

Measurable outcomes to request

Ask for the outputs you will hold the vendor to: a runbook excerpt, incident reports with photo timestamps, daily patrol logs, and proof of chain-of-custody procedures for evidence. If a vendor cannot or will not show examples of those deliverables, treat that as a procurement concern.

Which roles and escalation levels your runbook must name

Your runbook must be explicit about escalation tiers and the triggers that move an incident between tiers. Ontario's IMS guidance assigns a clear site incident commander role and recommends defined escalation levels so responses scale appropriately from routine to multi-organization incidents (site coordination) and explains escalation categories by response level (response escalation).

Sample escalation tiers to ask for

• Tier 1 — Routine: Property check, minor rule breach, or false alarm. Patrol documents the event and no external agencies are notified.
• Tier 2 — Notifiable: Suspicious person, damage in progress, or repeated alarms. Client and patrol supervisor notified; police informed if risk to persons or property is present.
• Tier 3 — Critical: Violence, major property loss, fire, life safety threat. Patrol secures scene, calls 9-1-1, hands command to police or EMS on arrival and activates escalation contacts and evidence procedures.

Insist that the vendor defines each trigger in writing and that those definitions are appended to the contract. Vague escalation language invites disagreement during incidents.

Seven decision checks and red flags to use when evaluating vendors

Below are seven practical checks you can run during procurement interviews, reference calls, or a site walk-through. Each check includes what a good answer looks like and the red flag that should prompt further scrutiny.

1. Runbook exists and is site specific

Good answer: An excerpt of a runbook tied to your property type that shows named roles, escalation triggers, checklists, and communications scripts. Red flag: Only generic brochures or a refusal to share any redacted runbook content. Require a runbook excerpt as a pre-award deliverable.

2. Documented escalation paths with a police liaison

Good answer: A documented police liaison or local detachment contact, and written procedures describing who calls police, when they are notified, and what information will be shared. Red flag: Vendor claims "we always call police quickly" but cannot name a liaison or show evidence of local coordination. Ontario regulation recognises the need for coordinated response and search management when public safety agencies are involved, so naming how you will interact with police matters (O. Reg. 392/23).

3. Sample incident reports and evidence chain

Good answer: Recent, redacted incident reports with photo timestamps and an evidence-handling SOP. Red flag: No sample reports or inconsistent documentation. Require an incident-reporting template and chain-of-custody steps in contracts.

4. Unified operating plan linking guards to CCTV and access control

Good answer: A documented operating plan that explains how live monitoring, CCTV camera coverage and access control events create tasks for guards and patrols. Red flag: Vendor treats technology and guard duties as separate offerings without integration. Accure's model of combining guarding with CCTV and access control into one plan is the approach procurement teams should test for (Accure Security services).

5. Documented patrol logs and field reporting

Good answer: Digital or physical patrol logs with time-stamped checkpoints, supervisor review notes, and daily summaries. Red flag: Reliance on memory or sporadic paper logs. Include audit and access rights to logs in the contract.

6. Verified staffing, licensing and local coverage

Good answer: Proof of licensed guards, local supervisor names, and a coverage map showing travel times. Red flag: Vague staffing promises or out-of-region crews without local supervision. Verify IDs and licensing during a site walk.

7. Short-notice capability and contingency plans

Good answer: A documented short-notice staffing plan, surge procedures, and backup communication channels. Red flag: Promises of "24/7" availability without explanation of how backfill, relief, or local surge will be achieved. Test this with a written contingency commitment.

What operational proofs vendors should include with a quote

Do not award a contract without requiring the following artifacts as part of the proposal or pre-award package: an anonymized runbook excerpt, an escalation matrix naming contacts and phone roles, a redacted incident report, an evidence-handling SOP, a coverage map showing local patrol radii, and a sample daily patrol log. Ask for references tied to similar property types and, if possible, a permissioned contact at a referenced site who can confirm the vendor's performance on a specific type of incident.

How private patrols should interact with police and emergency services in Ontario

Private security has useful powers and skills, but legal and operational boundaries exist. Private guards should secure scenes and preserve evidence, but they must not assume police command. Ontario's IMS guidance stresses that an incident commander role exists at the site and that command and coordination must be clear; when police arrive they may assume command for criminal or life-safety incidents (IMS coordination and command). Vendors should document handoff procedures, including who meets police, what information is transferred, and how evidence custody is recorded.

Where incidents escalate beyond a single site, Ontario's Provincial Emergency Response Plan requires a common understanding of roles and structured information sharing among stakeholders, which should inform your runbook if your site could be part of a wider emergency (PERP concept of operations). Include a clause in the contract that requires vendor cooperation with IMS-style coordination when applicable.

Common vendor claims and how to test them on site

• Claim: "Quick police response guaranteed." Test: Ask for a written liaison relationship or call the local detachment to confirm practical response patterns.
• Claim: "24/7 coverage across the region." Test: Request a coverage map, scheduled rosters, and sample shift handover logs for the site.
• Claim: "We handle all evidence and liability." Test: Require an evidence-handling SOP and clarify liability language in the contract; vendors cannot contractually assume public authority responsibilities.
• Claim: "We integrate with your cameras and access control." Test: Do a walk-through and ask to see a live feed, event log and the procedure that links an access control event to a guard task.

Simple, real-time verification during a site walk prevents surprises after award.

A concise procurement checklist to include in contracts

• Runbook with named roles, escalation tiers and decision triggers.
• Escalation matrix that names a police liaison and client emergency contacts.
• Incident report template, required fields, and photo/timestamp requirements.
• Evidence custody procedure and secure transfer steps to police or client.
• Daily patrol logs, supervisor review cadence and access rights for audits.
• Coverage map, staffing plan, and short-notice surge procedures.
• Obligation to cooperate with IMS-style coordination and multi-agency response when incidents escalate (IMS escalation guidance).
• Verification rights: on-site audits, redacted sample reports, and reference checks.

Frequently asked questions

How should private security coordinate with police and EMS during an incident in Ontario?

Private security should secure the scene, preserve evidence and provide timely, factual briefings to police or EMS on arrival. The vendor's runbook should name who meets public responders, how information is handed over, and how custody of evidence is recorded. Ontario's IMS guidance explains the importance of coordination and a clear command structure at the site (IMS coordination).

What specific documents should I require before approving patrol response coordination?

Require a runbook excerpt, escalation matrix with named contacts, a redacted incident report, evidence-handling SOP, coverage map and sample daily patrol logs. These artifacts are testable proofs you can place in an RFP or SOW before award.

Can a private security company direct police or assume command at an incident?

No. Private security cannot assume police authority. They can serve as on-site incident commanders until police or EMS assume command, but any formal command transfer should be recorded. Ontario regulation and IMS practices set expectations for public authority roles and coordinated response (O. Reg. 392/23).

What are reasonable escalation triggers to include in a patrol response runbook?

Reasonable triggers include forced entry or visible theft, violence or threats to persons, repeated alarm activations, evidence of arson, and any life-safety hazard. Each trigger should map to a tier with clear actions: secure scene, call 9-1-1, notify client and supervisor, and document the event.

Accure Security

Which patrol response coordination questions will you ask your security provider?