Operationalizing hotspot policing—from analysis to field action using ArcGIS

April 13, 2026

Shaun Hildebrand

Hotspot policing is grounded in decades of research showing that crime is not evenly distributed—it concentrates in a small number of locations. These micro-locations, or “hotspots,” generate a disproportionate share of calls for service, victimization, and harm. Identifying hotspots is an important first step, but analysis alone does not reduce crime. A hotspot map that lives in a briefing deck may inform, but it does not drive action. Hotspot policing creates value only when analysis translates into consistent field activity, when agencies capture what was done on the ground, and when outcomes are measured over time. This evolution—from analysis to action—is reflected across three Ontario police services.

Hotspots only matter when they produce action

In Ontario, in 2023, London Police Service began operationalizing hotspots by turning priority locations into clear, shift-friendly tasks—supporting adoption and consistency in the field.

Barrie Police Service strengthened the analytical foundation by publishing a harm-focused methodology to better target locations and evaluate whether interventions occurred.

Building on both approaches, Ottawa Police Service used ArcGIS to scale hotspot policing into a coordinated workflow—from identification to tasking, execution, and performance tracking.

Ottawa’s Community Outreach, Response and Engagement Strategy (C.O.R.E.) demonstrates how hotspots can function as part of an operating model, not just an analytical output.

C.O.R.E. focuses on reducing crime in specific areas—such as the ByWard Market and Rideau Street—through evidence-based policing, partner engagement, and solutions that address root causes. A central component is the Neighbourhood Operations Centre (NOC), which improves coordination, visibility, and collaboration across partners.

At its core, C.O.R.E. operates as a repeatable cycle: identify priority locations, coordinate resources, deploy focused action, document activity, and learn from results.

Five-step operational cycle: identify, coordinate, act, document, and adjust.

In practical terms, C.O.R.E. contains five operational components that map cleanly into an ArcGIS workflow:

NOC coordination: a common operating picture and tasking hub for downtown safety.
Hotspots: a defensible academic based method to identify the small number of places where a large share of crime concentrates.
Focused enforcement: concentrated effort where appropriate, including attention to a small number of repeat offenders driving disproportionate harm.
Situation Table (ICST): partner-led pathways to stabilize risk through wraparound supports (medical care, addiction treatment, mental health support, legal assistance, housing).
Community Advisory Board (CAB): governance and longer-term coordination to address systemic issues.

From model to method: Target → Test → Track

Together, C.O.R.E. serves as the ArcGIS operating model, Barrie provides a repeatable harm-focused analytical framework, and London offers years of experience in implementation, operational gamification, and adoption.

Together, they align with evidence-based policing:

Target the right locations
Test a defined intervention
Track results—including whether activity occurred as intended

The “Track” step is where many initiatives break down. Agencies can identify hotspots but struggle to connect them to consistent field activity and measurable outcomes.

ArcGIS helps close this gap by supporting an end-to-end workflow—from analysis to coordination, field execution, and performance monitoring.

An operational ArcGIS workflow for hotspot policing

ArcGIS enables agencies to move from identifying hotspots to operationalizing them through a connected system:

Build defensible hotspots in ArcGIS Pro
Coordinate and task in Experience Builder
Execute in Field Maps
Capture activity in Survey123
Monitor outcomes through dashboards

ArcGIS workflow from hotspot analysis to field execution and reporting.

An operational ArcGIS workflow for hotspot policing

Bringing it all together

Step 1 — Build defensible hotspots in ArcGIS Pro

Start by transforming incident data (calls for service, occurrences, reported crimes) into stable, operational hotspot units.

A hexagonal grid is particularly effective—it supports consistent comparisons over time and creates clear units that can be assigned and evaluated.

Core steps include:

Generate a hexagonal tessellation over the operational area (e.g., downtown corridor, division boundary, or city).
Clip to the analysis boundary so the grid matches the jurisdictional footprint.
Aggregate incidents into each cell (e.g., Spatial Join) to create counts (and optionally harm-weighted totals).
Apply a defensible threshold to identify true outliers (rather than arbitrary “top 10” selections).
Publish the hotspot grid as a hosted feature layer (ArcGIS Online or ArcGIS Enterprise) to become the operational source of truth.

This creates a reliable hotspot layer—but the next step is turning it into action. That’s where the C.O.R.E. overlays come in.

Step 2 — Add operational context with three overlays

A hotspot shows where activity concentrates—but not what to do next. Adding contextual overlays transforms hotspots into actionable environments.

Overlay A: Known offenders and conditions:
Overlaying individuals with bail, probation, or parole conditions adds decision-making context—who is nearby, what conditions apply, and where targeted checks may reduce harm.

Overlay B: Recent crimes with suspect descriptions and MO summaries:
A time-windowed view of recent activity—paired with suspect descriptions and MO—bridges long-term patterns with real-time situational awareness.

Overlay C: Nearby social services and partner pathways (ICST-ready):
A services layer enables officers to connect individuals to appropriate supports, reinforcing a multi-disciplinary response aligned with the C.O.R.E. model.

Together, these overlays shift deployment from “go to the hotspot” to “act with purpose inside the hotspot.”

Step 3 — Experience Builder: the NOC-style coordination and tasking console

Experience Builder acts as a central coordination interface—similar to the NOC concept—bringing together hotspots, overlays, and tasking workflows.

A practical setup includes:

Filters for priority, offence type, and time window
A hotspot briefing panel with clear guidance and expectations
A combined operational view of all overlays
A workflow to assign hotspots into shift plans with defined outcomes

This turns analysis into coordinated action.

Step 4 — Field Maps: put hotspot context into officers’ hands

Field Maps delivers hotspot context directly to officers—clarifying where to go, what to do, and what to look for.

Adoption improves when tasks are simple, clear, and aligned with shift workflows. London Police Service demonstrated that structured tasking—supported by feedback loops—helps sustain consistent delivery.

Hotspots should also be treated as dynamic. As activity changes over time, hotspots can shift—allowing officers to focus on areas that still require attention.

Configure Field Maps pop-ups can include:

Priority tier, time window, and pattern summary (plain language).
Minimum standard for the hotspot check (dosage expectations and activity type).
Recent ‘look-for’ cues from the suspect/MO overlay.
Where appropriate, bail/offender proximity cues to support targeted checks.
Nearby social services and partner options with directions and contact pathways (ICST-ready).

Step 5 — Survey123: capture fidelity, actions, and outcomes

Survey123 captures happens at the point of action—consistently and in a structured format.

A simple “Hotspot Action” form can track:
Hotspot ID (auto from selected cell) and time on task (dosage).
Action type (visibility, bail compliance check, engagement/reassurance, enforcement, outreach/referral, POP follow-up).
Outputs (contacts, referrals, enforcement activity, partner notifications).
Observations and learnings (what changed, what worked, what needs follow-up).
Optional photos/attachments where policy permits.

This enables agencies to measure not just activity—but whether interventions were delivered as intended and what outcomes followed.

Step 6 — Close the loop: dashboards + refresh cadence + governance

Hotspot policing requires continuous refinement.

Dashboards bring together hotspot trends, field activity, and outcomes—supporting timely, evidence-based decisions. Regular refresh cycles ensure hotspots remain relevant, while appropriate governance ensures data is used responsibly and transparently.

Conclusion: hotspots become actionable when the operating model is built around them

Ottawa’s C.O.R.E. Strategy demonstrates how hotspot policing becomes operational—through coordinated deployment, partner engagement, and continuous evaluation.

Barrie provides a repeatable method for identifying and assessing hotspots, while London offers practical insight into driving frontline adoption.

ArcGIS connects these elements into a single operational system—from analysis to action to outcomes.

With the addition of contextual overlays—offenders, recent activity, and services—hotspots become more than locations. They become decision environments that enable meaningful, measurable action.