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

Administrative

Administrative calls over time: volume, outcomes, and response speed

Administrative: 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 (97% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
02,0004,0002009: 1,052 administrative calls logged in CAD2010: 2,555 administrative calls logged in CAD2011: 3,041 administrative calls logged in CAD2012: 3,243 administrative calls logged in CAD2013: 3,452 administrative calls logged in CAD2014: 3,294 administrative calls logged in CAD2015: 2,537 administrative calls logged in CAD2016: 2,890 administrative calls logged in CAD2017: 2,938 administrative calls logged in CAD2018: 2,597 administrative calls logged in CAD2019: 2,080 administrative calls logged in CAD2020: 1,505 administrative calls logged in CAD2021: 922 administrative calls logged in CAD2022: 835 administrative calls logged in CAD2023: 1,042 administrative calls logged in CAD2024: 617 administrative calls logged in CAD2025: 411 administrative calls logged in CAD2026: 522 administrative calls logged in CAD2009n=1,0522011n=3,0412013n=3,4522015n=2,5372017n=2,9382019n=2,0802021n=9222023n=1,0422025n=4112026n=522
administrative calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodAdministrative calls logged in CAD
20091,052
20102,555
20113,041
20123,243
20133,452
20143,294
20152,537
20162,890
20172,938
20182,597
20192,080
20201,505
2021922
2022835
20231,042
2024617
2025411
2026522
Administrative Calls Are Down 88% From Their 2013 PeakSeattle Police logged 3,452 administrative calls in 2013 and 411 in 2025, the most recent full year.

Administrative: 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%2009 · Arrest / citation: 0.4%2009 · Report taken, no arrest: 1.8%2009 · Resolved on scene: 87.9%2009 · Unable to locate: 2.5%2009 · Other (unfounded / cancelled): 7.4%2010 · Arrest / citation: 0.3%2010 · Report taken, no arrest: 1.6%2010 · Resolved on scene: 94.1%2010 · Unable to locate: 1.4%2010 · Other (unfounded / cancelled): 2.5%2011 · Arrest / citation: 0.1%2011 · Report taken, no arrest: 0.8%2011 · Resolved on scene: 96.9%2011 · Unable to locate: 1.1%2011 · Other (unfounded / cancelled): 1.1%2012 · Arrest / citation: 0.1%2012 · Report taken, no arrest: 1.7%2012 · Resolved on scene: 96.5%2012 · Unable to locate: 0.7%2012 · Other (unfounded / cancelled): 0.9%2013 · Arrest / citation: 0.1%2013 · Report taken, no arrest: 0.3%2013 · Resolved on scene: 97.8%2013 · Unable to locate: 0.7%2013 · Other (unfounded / cancelled): 1.0%2014 · Report taken, no arrest: 0.3%2014 · Resolved on scene: 96.6%2014 · Unable to locate: 0.9%2014 · Other (unfounded / cancelled): 2.2%2015 · Arrest / citation: 0.1%2015 · Report taken, no arrest: 0.4%2015 · Resolved on scene: 96.8%2015 · Unable to locate: 0.6%2015 · Other (unfounded / cancelled): 2.1%2016 · Arrest / citation: 0.1%2016 · Report taken, no arrest: 0.2%2016 · Resolved on scene: 95.1%2016 · Unable to locate: 2.4%2016 · Other (unfounded / cancelled): 2.2%2017 · Arrest / citation: 0.2%2017 · Report taken, no arrest: 0.4%2017 · Resolved on scene: 91.8%2017 · Unable to locate: 4.4%2017 · Other (unfounded / cancelled): 3.2%2018 · Report taken, no arrest: 0.2%2018 · Resolved on scene: 82.0%2018 · Unable to locate: 13.2%2018 · Other (unfounded / cancelled): 4.5%2019 · Arrest / citation: 0.4%2019 · Report taken, no arrest: 0.7%2019 · Resolved on scene: 90.4%2019 · Unable to locate: 5.4%2019 · Other (unfounded / cancelled): 3.1%2020 · Arrest / citation: 0.3%2020 · Report taken, no arrest: 0.6%2020 · Resolved on scene: 94.0%2020 · Unable to locate: 3.7%2020 · Other (unfounded / cancelled): 1.4%2021 · Arrest / citation: 0.3%2021 · Report taken, no arrest: 0.5%2021 · Resolved on scene: 93.5%2021 · Unable to locate: 4.1%2021 · Other (unfounded / cancelled): 1.5%2022 · Arrest / citation: 0.4%2022 · Report taken, no arrest: 4.7%2022 · Resolved on scene: 88.0%2022 · Unable to locate: 4.9%2022 · Other (unfounded / cancelled): 2.0%2023 · Arrest / citation: 0.1%2023 · Report taken, no arrest: 3.6%2023 · Resolved on scene: 91.6%2023 · Unable to locate: 3.2%2023 · Other (unfounded / cancelled): 1.6%2024 · Report taken, no arrest: 11.0%2024 · Resolved on scene: 82.8%2024 · Unable to locate: 4.7%2024 · Other (unfounded / cancelled): 1.5%2025 · Arrest / citation: 0.5%2025 · Report taken, no arrest: 1.2%2025 · Resolved on scene: 91.7%2025 · Unable to locate: 2.4%2025 · Other (unfounded / cancelled): 4.1%2026 · Arrest / citation: 0.4%2026 · Report taken, no arrest: 0.6%2026 · Resolved on scene: 66.1%2026 · Unable to locate: 31.6%2026 · Other (unfounded / cancelled): 1.3%2009n=1,0522011n=3,0412013n=3,4522015n=2,5372017n=2,9382019n=2,0802021n=9222023n=1,0422025n=4112026n=522
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
PeriodEventsArrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
20091,0520.4%1.8%87.9%2.5%7.4%
20102,5550.3%1.6%94.1%1.4%2.5%
20113,0410.1%0.8%96.9%1.1%1.1%
20123,2430.1%1.7%96.5%0.7%0.9%
20133,4520.1%0.3%97.8%0.7%1.0%
20143,294—0.3%96.6%0.9%2.2%
20152,5370.1%0.4%96.8%0.6%2.1%
20162,8900.1%0.2%95.1%2.4%2.2%
20172,9380.2%0.4%91.8%4.4%3.2%
20182,597—0.2%82.0%13.2%4.5%
20192,0800.4%0.7%90.4%5.4%3.1%
20201,5050.3%0.6%94.0%3.7%1.4%
20219220.3%0.5%93.5%4.1%1.5%
20228350.4%4.7%88.0%4.9%2.0%
20231,0420.1%3.6%91.6%3.2%1.6%
2024617—11.0%82.8%4.7%1.5%
20254110.5%1.2%91.7%2.4%4.1%
20265220.4%0.6%66.1%31.6%1.3%
32% of Administrative Calls End “Unable to Locate,” Up From 2%Report-taken outcomes moved from 0% of calls in 2016 to 1% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Administrative: 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 97% of administrative 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 administrative 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 min150 min300 min2009: 15.0 min2010: 7.8 min2011: 13.2 min2012: 10.4 min2013: 20.7 min2014: 16.8 min2015: 31.6 min2016: 25.3 min2017: 19.8 min2018: 28.3 min2019: 16.8 min2020: 8.2 min2021: 60.9 min2022: 119.0 min2023: 181.7 min2024: 253.1 min2025: 157.8 min2026: 109.2 min2009: 25.3 min2010: 17.3 min2011: 16.7 min2012: 17.4 min2013: 36.4 min2014: 37.3 min2015: 55.7 min2016: 38.8 min2017: 27.1 min2018: 41.2 min2019: 21.1 min2020: 16.4 min2021: 64.5 min2022: 141.7 min2023: 73.1 min2024: 268.4 min2025: 171.5 min2026: 110.0 min2009n=272011n=842013n=452015n=222017n=362019n=382021n=262023n=712025n=262026n=169
Average response timeAverage dispatch delay
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
20092715.0 min25.3 min
2010717.8 min17.3 min
20118413.2 min16.7 min
20126710.4 min17.4 min
20134520.7 min36.4 min
20142616.8 min37.3 min
20152231.6 min55.7 min
20163425.3 min38.8 min
20173619.8 min27.1 min
20183828.3 min41.2 min
20193816.8 min21.1 min
2020308.2 min16.4 min
20212660.9 min64.5 min
202284119.0 min141.7 min
202371181.7 min73.1 min
202482253.1 min268.4 min
202526157.8 min171.5 min
2026169109.2 min110.0 min
The Average Call Waits 110 Minutes for an Officer to ArriveDespite an 86% drop in calls between 2016 and 2025, average response time has more than doubled in the past 10 years, from 39 minutes in 2016 to 110 in 2026, driven largely by dispatch delays. This counts only the 3% of administrative calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
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.

Administrative: 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 97% of administrative events, because they have no wait. Because most administrative 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%2009 · No recorded response: 14.8%2009 · 0–5 min: 11.1%2009 · 5–30 min: 51.8%2009 · 30–60 min: 14.8%2009 · 1–4 hr: 7.4%2010 · No recorded response: 26.8%2010 · 0–5 min: 39.4%2010 · 5–30 min: 15.5%2010 · 30–60 min: 11.3%2010 · 1–4 hr: 7.0%2011 · No recorded response: 23.8%2011 · 0–5 min: 50.0%2011 · 5–30 min: 9.5%2011 · 30–60 min: 9.5%2011 · 1–4 hr: 7.1%2012 · No recorded response: 7.5%2012 · 0–5 min: 59.7%2012 · 5–30 min: 19.4%2012 · 30–60 min: 3.0%2012 · 1–4 hr: 10.4%2013 · No recorded response: 13.3%2013 · 0–5 min: 31.1%2013 · 5–30 min: 26.7%2013 · 30–60 min: 13.3%2013 · 1–4 hr: 13.3%2013 · 4–8 hr: 2.2%2014 · No recorded response: 11.5%2014 · 0–5 min: 23.1%2014 · 5–30 min: 34.6%2014 · 30–60 min: 19.2%2014 · 1–4 hr: 7.7%2014 · 4–8 hr: 3.9%2015 · No recorded response: 4.5%2015 · 0–5 min: 22.7%2015 · 5–30 min: 36.4%2015 · 30–60 min: 9.1%2015 · 1–4 hr: 22.7%2015 · 4–8 hr: 4.5%2016 · No recorded response: 2.9%2016 · 0–5 min: 23.5%2016 · 5–30 min: 47.1%2016 · 30–60 min: 14.7%2016 · 1–4 hr: 8.8%2016 · Over 8 hr: 2.9%2017 · No recorded response: 8.3%2017 · 0–5 min: 36.1%2017 · 5–30 min: 33.3%2017 · 30–60 min: 8.3%2017 · 1–4 hr: 13.9%2018 · No recorded response: 15.8%2018 · 0–5 min: 23.7%2018 · 5–30 min: 42.1%2018 · 30–60 min: 7.9%2018 · 1–4 hr: 7.9%2018 · 4–8 hr: 2.6%2019 · No recorded response: 13.2%2019 · 0–5 min: 21.1%2019 · 5–30 min: 50.0%2019 · 30–60 min: 7.9%2019 · 1–4 hr: 7.9%2020 · No recorded response: 10.0%2020 · 0–5 min: 30.0%2020 · 5–30 min: 43.3%2020 · 30–60 min: 6.7%2020 · 1–4 hr: 10.0%2021 · No recorded response: 11.5%2021 · 0–5 min: 23.1%2021 · 5–30 min: 46.2%2021 · 30–60 min: 3.9%2021 · 1–4 hr: 7.7%2021 · 4–8 hr: 3.9%2021 · Over 8 hr: 3.9%2022 · No recorded response: 40.5%2022 · 0–5 min: 8.3%2022 · 5–30 min: 14.3%2022 · 30–60 min: 7.1%2022 · 1–4 hr: 21.4%2022 · 4–8 hr: 6.0%2022 · Over 8 hr: 2.4%2023 · No recorded response: 33.8%2023 · 0–5 min: 14.1%2023 · 5–30 min: 31.0%2023 · 30–60 min: 8.4%2023 · 1–4 hr: 7.0%2023 · 4–8 hr: 2.8%2023 · Over 8 hr: 2.8%2024 · No recorded response: 28.1%2024 · 0–5 min: 12.2%2024 · 5–30 min: 11.0%2024 · 30–60 min: 3.7%2024 · 1–4 hr: 22.0%2024 · 4–8 hr: 9.8%2024 · Over 8 hr: 13.4%2025 · No recorded response: 7.7%2025 · 0–5 min: 15.4%2025 · 5–30 min: 42.3%2025 · 1–4 hr: 7.7%2025 · 4–8 hr: 11.5%2025 · Over 8 hr: 15.4%2026 · No recorded response: 1.8%2026 · 0–5 min: 34.9%2026 · 5–30 min: 21.9%2026 · 30–60 min: 10.1%2026 · 1–4 hr: 19.5%2026 · 4–8 hr: 7.7%2026 · Over 8 hr: 4.1%2009n=272011n=842013n=452015n=222017n=362019n=382021n=262023n=712025n=262026n=169
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
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
20092714.8%11.1%51.8%14.8%7.4%——
20107126.8%39.4%15.5%11.3%7.0%——
20118423.8%50.0%9.5%9.5%7.1%——
2012677.5%59.7%19.4%3.0%10.4%——
20134513.3%31.1%26.7%13.3%13.3%2.2%—
20142611.5%23.1%34.6%19.2%7.7%3.9%—
2015224.5%22.7%36.4%9.1%22.7%4.5%—
2016342.9%23.5%47.1%14.7%8.8%—2.9%
2017368.3%36.1%33.3%8.3%13.9%——
20183815.8%23.7%42.1%7.9%7.9%2.6%—
20193813.2%21.1%50.0%7.9%7.9%——
20203010.0%30.0%43.3%6.7%10.0%——
20212611.5%23.1%46.2%3.9%7.7%3.9%3.9%
20228440.5%8.3%14.3%7.1%21.4%6.0%2.4%
20237133.8%14.1%31.0%8.4%7.0%2.8%2.8%
20248228.1%12.2%11.0%3.7%22.0%9.8%13.4%
2025267.7%15.4%42.3%—7.7%11.5%15.4%
20261691.8%34.9%21.9%10.1%19.5%7.7%4.1%
The Average Call Waits 109 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 109 minutes in 2026, more than double what it was in 2016. 31% of calls took more than an hour to get a response in 2026, compared with 12% in 2016. This counts only the 3% of administrative calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
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. 2009 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.