Seattle Police
Call volumeOutcomesHow long it tookHow long it took, in full

Directed Patrol

Directed Patrol calls over time: volume, outcomes, and response speed

Directed Patrol: Call Volume

Call volume is the number of events logged in the Seattle Police Department’s Computer-Aided Dispatch (CAD) system. It counts calls from the public (by 911, phone, text or alarm) as well as officer-initiated activity, once per event, grouped by the call type assigned when the call was dispatched, before any investigation. It is not the same as the number of crimes reported.

Included: Every event logged in CAD: calls from the public and events officers logged themselves (99% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
015,00030,0002012: 27,741 directed patrol calls logged in CAD2013: 22,619 directed patrol calls logged in CAD2014: 4,580 directed patrol calls logged in CAD2015: 1,788 directed patrol calls logged in CAD2016: 2,799 directed patrol calls logged in CAD2017: 10,093 directed patrol calls logged in CAD2018: 13,788 directed patrol calls logged in CAD2019: 16,786 directed patrol calls logged in CAD2020: 17,643 directed patrol calls logged in CAD2021: 10,110 directed patrol calls logged in CAD2022: 9,002 directed patrol calls logged in CAD2023: 11,817 directed patrol calls logged in CAD2024: 9,492 directed patrol calls logged in CAD2025: 13,898 directed patrol calls logged in CAD2026: 10,061 directed patrol calls logged in CAD2012n=27,7412014n=4,5802016n=2,7992018n=13,7882020n=17,6432022n=9,0022024n=9,4922026n=10,061
directed patrol calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodDirected patrol calls logged in CAD
201227,741
201322,619
20144,580
20151,788
20162,799
201710,093
201813,788
201916,786
202017,643
202110,110
20229,002
202311,817
20249,492
202513,898
202610,061
Directed Patrol Calls Are Down 50% From Their 2012 PeakSeattle Police logged 27,741 directed patrol calls in 2012 and 13,898 in 2025, the most recent full year.

Directed Patrol: What Happened When Officers Responded

Outcomes show how each call ended, based on the disposition officers recorded when the call was closed: an arrest or citation, a report taken with no arrest, resolved on scene, unable to locate (officers could not find the incident or the person who called), or other (unfounded or cancelled). Each bar shows the share of that period’s calls.

Included: Every event, called in or officer-initiated, using the disposition recorded when the event was closed. Excluded: Nothing.

Swipe sideways to see the full chart →
100%50%0%2012 · Report taken, no arrest: 0.3%2012 · Resolved on scene: 97.7%2012 · Unable to locate: 1.5%2012 · Other (unfounded / cancelled): 0.5%2013 · Report taken, no arrest: 0.4%2013 · Resolved on scene: 97.1%2013 · Unable to locate: 2.0%2013 · Other (unfounded / cancelled): 0.4%2014 · Arrest / citation: 0.1%2014 · Report taken, no arrest: 1.0%2014 · Resolved on scene: 97.3%2014 · Unable to locate: 1.5%2014 · Other (unfounded / cancelled): 0.1%2015 · Arrest / citation: 0.2%2015 · Report taken, no arrest: 0.3%2015 · Resolved on scene: 96.5%2015 · Unable to locate: 2.6%2015 · Other (unfounded / cancelled): 0.3%2016 · Arrest / citation: 0.1%2016 · Report taken, no arrest: 4.6%2016 · Resolved on scene: 91.9%2016 · Unable to locate: 3.3%2016 · Other (unfounded / cancelled): 0.1%2017 · Arrest / citation: 0.1%2017 · Report taken, no arrest: 3.3%2017 · Resolved on scene: 94.3%2017 · Unable to locate: 2.2%2017 · Other (unfounded / cancelled): 0.1%2018 · Report taken, no arrest: 1.7%2018 · Resolved on scene: 97.1%2018 · Unable to locate: 1.1%2018 · Other (unfounded / cancelled): 0.1%2019 · Arrest / citation: 0.1%2019 · Report taken, no arrest: 0.3%2019 · Resolved on scene: 96.3%2019 · Unable to locate: 3.3%2019 · Other (unfounded / cancelled): 0.1%2020 · Report taken, no arrest: 0.1%2020 · Resolved on scene: 96.0%2020 · Unable to locate: 3.8%2020 · Other (unfounded / cancelled): 0.1%2021 · Arrest / citation: 0.1%2021 · Report taken, no arrest: 0.1%2021 · Resolved on scene: 97.8%2021 · Unable to locate: 1.8%2021 · Other (unfounded / cancelled): 0.1%2022 · Arrest / citation: 0.6%2022 · Resolved on scene: 97.4%2022 · Unable to locate: 1.9%2022 · Other (unfounded / cancelled): 0.1%2023 · Arrest / citation: 0.3%2023 · Report taken, no arrest: 0.1%2023 · Resolved on scene: 97.1%2023 · Unable to locate: 2.4%2023 · Other (unfounded / cancelled): 0.1%2024 · Arrest / citation: 0.7%2024 · Report taken, no arrest: 0.3%2024 · Resolved on scene: 97.3%2024 · Unable to locate: 1.6%2024 · Other (unfounded / cancelled): 0.2%2025 · Arrest / citation: 0.3%2025 · Report taken, no arrest: 0.2%2025 · Resolved on scene: 98.4%2025 · Unable to locate: 1.0%2025 · Other (unfounded / cancelled): 0.2%2026 · Arrest / citation: 0.2%2026 · Report taken, no arrest: 0.2%2026 · Resolved on scene: 97.8%2026 · Unable to locate: 1.5%2026 · Other (unfounded / cancelled): 0.4%2012n=27,7412014n=4,5802016n=2,7992018n=13,7882020n=17,6432022n=9,0022024n=9,4922026n=10,061
Arrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
View as table
What happened when officers responded — same numbers as the chart above
PeriodEventsReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)Arrest / citation
201227,7410.3%97.7%1.5%0.5%—
201322,6190.4%97.1%2.0%0.4%—
20144,5801.0%97.3%1.5%0.1%0.1%
20151,7880.3%96.5%2.6%0.3%0.2%
20162,7994.6%91.9%3.3%0.1%0.1%
201710,0933.3%94.3%2.2%0.1%0.1%
201813,7881.7%97.1%1.1%0.1%—
201916,7860.3%96.3%3.3%0.1%0.1%
202017,6430.1%96.0%3.8%0.1%—
202110,1100.1%97.8%1.8%0.1%0.1%
20229,002—97.4%1.9%0.1%0.6%
202311,8170.1%97.1%2.4%0.1%0.3%
20249,4920.3%97.3%1.6%0.2%0.7%
202513,8980.2%98.4%1.0%0.2%0.3%
202610,0610.2%97.8%1.5%0.4%0.2%
“Unable to Locate” Outcomes Are Holding Near 2% of Directed Patrol CallsReport-taken outcomes moved from 5% of calls in 2016 to 0% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Directed Patrol: How Long It Took

Response time is how long it took, from the moment a called-in event was queued with dispatch, until the first officer arrived on scene. Dispatch delay is the first part of that wait: the time before an officer was assigned and sent. Both lines show the average, which a small number of very long waits pull up, so it runs higher than the typical (median) call.

Included: Only events called in by the public and dispatched to an officer. The averages use those with a recorded officer arrival. The n= under each bar is the number of called-in events. Excluded: Events officers logged themselves (on view), which are 99% of directed patrol events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most directed patrol events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
0 min1,000 min2,000 min2012: 9.1 min2013: 11.9 min2014: 9.0 min2015: 8.2 min2016: 24.1 min2017: 25.4 min2018: 24.9 min2019: 567.7 min2020: 38.5 min2021: 41.6 min2022: 59.7 min2023: 30.3 min2024: 107.1 min2025: 518.5 min2026: 1,392.4 min2012: 10.3 min2013: 13.7 min2014: 14.5 min2015: 10.5 min2016: 27.7 min2017: 31.0 min2018: 32.7 min2019: 622.3 min2020: 54.5 min2021: 39.9 min2022: 52.8 min2023: 35.5 min2024: 115.0 min2025: 506.4 min2026: 1,371.3 min2012n=1442014n=172016n=52018n=292020n=372022n=262024n=732026n=248
Average response timeAverage dispatch delay
Small sample: Only a small share of directed patrol events are called in. The year with the fewest had only 5, so averages can swing widely; the n= under each year shows its count.
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
20121449.1 min10.3 min
20136411.9 min13.7 min
2014179.0 min14.5 min
201558.2 min10.5 min
2016524.1 min27.7 min
20172525.4 min31.0 min
20182924.9 min32.7 min
201926567.7 min622.3 min
20203738.5 min54.5 min
20213041.6 min39.9 min
20222659.7 min52.8 min
20233830.3 min35.5 min
202473107.1 min115.0 min
2025288518.5 min506.4 min
20262481,392.4 min1,371.3 min
Called-In Events Waited 1371 Minutes on Average in 2026That is the average across 248 called-in events in 2026.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

Directed Patrol: How Long It Took, in Full

The same response times, broken into bands so the slowest calls are visible. Each bar shows the share of called-in events by how long the first officer took to arrive after the event was queued, including the ones that took hours. “No recorded response” means no arrival was ever logged.

Included: Only events called in by the public and dispatched to an officer, including those with no recorded arrival (shown as “No recorded response”). Excluded: Events officers logged themselves (on view), which are 99% of directed patrol events, because they have no wait. Because most directed patrol events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
100%50%0%2012 · No recorded response: 4.9%2012 · 0–5 min: 81.9%2012 · 5–30 min: 6.2%2012 · 30–60 min: 4.9%2012 · 1–4 hr: 0.7%2012 · 4–8 hr: 1.4%2013 · No recorded response: 1.6%2013 · 0–5 min: 64.1%2013 · 5–30 min: 23.4%2013 · 30–60 min: 3.1%2013 · 1–4 hr: 7.8%2014 · No recorded response: 11.8%2014 · 0–5 min: 23.5%2014 · 5–30 min: 52.9%2014 · 30–60 min: 11.8%2015 · No recorded response: 20.0%2015 · 0–5 min: 40.0%2015 · 5–30 min: 40.0%2016 · 5–30 min: 80.0%2016 · 1–4 hr: 20.0%2017 · No recorded response: 12.0%2017 · 0–5 min: 40.0%2017 · 5–30 min: 24.0%2017 · 30–60 min: 16.0%2017 · 1–4 hr: 4.0%2017 · 4–8 hr: 4.0%2018 · No recorded response: 6.9%2018 · 0–5 min: 17.2%2018 · 5–30 min: 48.3%2018 · 30–60 min: 10.3%2018 · 1–4 hr: 17.2%2019 · No recorded response: 7.7%2019 · 0–5 min: 7.7%2019 · 5–30 min: 53.8%2019 · 30–60 min: 15.4%2019 · 1–4 hr: 11.5%2019 · Over 8 hr: 3.9%2020 · No recorded response: 21.6%2020 · 0–5 min: 13.5%2020 · 5–30 min: 37.8%2020 · 30–60 min: 13.5%2020 · 1–4 hr: 5.4%2020 · 4–8 hr: 8.1%2021 · No recorded response: 13.3%2021 · 0–5 min: 13.3%2021 · 5–30 min: 40.0%2021 · 30–60 min: 10.0%2021 · 1–4 hr: 23.3%2022 · No recorded response: 3.9%2022 · 0–5 min: 7.7%2022 · 5–30 min: 34.6%2022 · 30–60 min: 19.2%2022 · 1–4 hr: 34.6%2023 · No recorded response: 7.9%2023 · 0–5 min: 23.7%2023 · 5–30 min: 42.1%2023 · 30–60 min: 15.8%2023 · 1–4 hr: 7.9%2023 · 4–8 hr: 2.6%2024 · No recorded response: 12.3%2024 · 0–5 min: 16.4%2024 · 5–30 min: 19.2%2024 · 30–60 min: 16.4%2024 · 1–4 hr: 20.6%2024 · 4–8 hr: 11.0%2024 · Over 8 hr: 4.1%2025 · No recorded response: 15.3%2025 · 0–5 min: 4.9%2025 · 5–30 min: 9.4%2025 · 30–60 min: 5.9%2025 · 1–4 hr: 9.7%2025 · 4–8 hr: 24.6%2025 · Over 8 hr: 30.2%2026 · No recorded response: 10.9%2026 · 0–5 min: 2.4%2026 · 5–30 min: 5.2%2026 · 30–60 min: 1.6%2026 · 1–4 hr: 2.8%2026 · 4–8 hr: 3.2%2026 · Over 8 hr: 73.8%2012n=1442014n=172016n=52018n=292020n=372022n=262024n=732026n=248
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of directed patrol events are called in. The year with the fewest had only 5, so shares can swing widely; the n= under each year shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
PeriodCalled-in eventsNo recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
20121444.9%81.9%6.2%4.9%0.7%1.4%—
2013641.6%64.1%23.4%3.1%7.8%——
20141711.8%23.5%52.9%11.8%———
2015520.0%40.0%40.0%————
20165——80.0%—20.0%——
20172512.0%40.0%24.0%16.0%4.0%4.0%—
2018296.9%17.2%48.3%10.3%17.2%——
2019267.7%7.7%53.8%15.4%11.5%—3.9%
20203721.6%13.5%37.8%13.5%5.4%8.1%—
20213013.3%13.3%40.0%10.0%23.3%——
2022263.9%7.7%34.6%19.2%34.6%——
2023387.9%23.7%42.1%15.8%7.9%2.6%—
20247312.3%16.4%19.2%16.4%20.6%11.0%4.1%
202528815.3%4.9%9.4%5.9%9.7%24.6%30.2%
202624810.9%2.4%5.2%1.6%2.8%3.2%73.8%
80% of Called-In Events Took Over an Hour in 2026That is 80% of 248 called-in events.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

“CAD” is Computer-Aided Dispatch, the system Seattle Police use to log and time every call for service — every number on this page comes from it. 2012 and 2026 may be partial years (data begins mid-2009; the latest year runs through the site's last data pull). “n=” under each year is the number of events logged that year in the volume and outcomes charts, and the number of called-in events dispatched to an officer in the response-time charts. Events officers log themselves (on view) are included in volume and outcomes and left out of response times, because they have no wait. The response-time bands measure time from call queued to first unit on scene; “no recorded response” means no arrival was ever logged. Hover any point for its exact value.