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

Warrant Services/Order

Warrant Services/Order calls over time: volume, outcomes, and response speed

Warrant Services/Order: 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 (72% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
05,00010,0002009: 4,419 warrant services/order calls logged in CAD2010: 7,595 warrant services/order calls logged in CAD2011: 6,053 warrant services/order calls logged in CAD2012: 5,401 warrant services/order calls logged in CAD2013: 5,586 warrant services/order calls logged in CAD2014: 4,398 warrant services/order calls logged in CAD2015: 4,569 warrant services/order calls logged in CAD2016: 4,576 warrant services/order calls logged in CAD2017: 4,966 warrant services/order calls logged in CAD2018: 4,919 warrant services/order calls logged in CAD2019: 4,620 warrant services/order calls logged in CAD2020: 2,128 warrant services/order calls logged in CAD2021: 1,302 warrant services/order calls logged in CAD2022: 1,739 warrant services/order calls logged in CAD2023: 1,714 warrant services/order calls logged in CAD2024: 2,034 warrant services/order calls logged in CAD2025: 2,315 warrant services/order calls logged in CAD2026: 1,722 warrant services/order calls logged in CAD2009n=4,4192011n=6,0532013n=5,5862015n=4,5692017n=4,9662019n=4,6202021n=1,3022023n=1,7142025n=2,3152026n=1,722
warrant services/order calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodWarrant services/order calls logged in CAD
20094,419
20107,595
20116,053
20125,401
20135,586
20144,398
20154,569
20164,576
20174,966
20184,919
20194,620
20202,128
20211,302
20221,739
20231,714
20242,034
20252,315
20261,722
Warrant Services/Order Calls Are Down 70% From Their 2010 PeakSeattle Police logged 7,595 warrant services/order calls in 2010 and 2,315 in 2025, the most recent full year.

Warrant Services/Order: 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: 72.2%2009 · Report taken, no arrest: 5.1%2009 · Resolved on scene: 13.8%2009 · Unable to locate: 7.4%2009 · Other (unfounded / cancelled): 1.4%2010 · Arrest / citation: 72.9%2010 · Report taken, no arrest: 4.5%2010 · Resolved on scene: 13.1%2010 · Unable to locate: 8.0%2010 · Other (unfounded / cancelled): 1.5%2011 · Arrest / citation: 72.3%2011 · Report taken, no arrest: 5.2%2011 · Resolved on scene: 13.4%2011 · Unable to locate: 8.1%2011 · Other (unfounded / cancelled): 1.0%2012 · Arrest / citation: 68.6%2012 · Report taken, no arrest: 7.9%2012 · Resolved on scene: 14.6%2012 · Unable to locate: 7.8%2012 · Other (unfounded / cancelled): 1.1%2013 · Arrest / citation: 68.5%2013 · Report taken, no arrest: 9.4%2013 · Resolved on scene: 13.9%2013 · Unable to locate: 7.0%2013 · Other (unfounded / cancelled): 1.1%2014 · Arrest / citation: 67.1%2014 · Report taken, no arrest: 11.9%2014 · Resolved on scene: 11.5%2014 · Unable to locate: 8.2%2014 · Other (unfounded / cancelled): 1.5%2015 · Arrest / citation: 67.2%2015 · Report taken, no arrest: 9.9%2015 · Resolved on scene: 12.7%2015 · Unable to locate: 8.6%2015 · Other (unfounded / cancelled): 1.5%2016 · Arrest / citation: 71.5%2016 · Report taken, no arrest: 7.1%2016 · Resolved on scene: 10.9%2016 · Unable to locate: 9.6%2016 · Other (unfounded / cancelled): 0.9%2017 · Arrest / citation: 70.1%2017 · Report taken, no arrest: 8.7%2017 · Resolved on scene: 11.0%2017 · Unable to locate: 9.1%2017 · Other (unfounded / cancelled): 1.2%2018 · Arrest / citation: 71.2%2018 · Report taken, no arrest: 8.6%2018 · Resolved on scene: 9.9%2018 · Unable to locate: 8.9%2018 · Other (unfounded / cancelled): 1.3%2019 · Arrest / citation: 75.1%2019 · Report taken, no arrest: 8.3%2019 · Resolved on scene: 7.0%2019 · Unable to locate: 8.4%2019 · Other (unfounded / cancelled): 1.3%2020 · Arrest / citation: 71.2%2020 · Report taken, no arrest: 8.1%2020 · Resolved on scene: 8.9%2020 · Unable to locate: 10.2%2020 · Other (unfounded / cancelled): 1.5%2021 · Arrest / citation: 64.2%2021 · Report taken, no arrest: 8.4%2021 · Resolved on scene: 12.2%2021 · Unable to locate: 13.8%2021 · Other (unfounded / cancelled): 1.4%2022 · Arrest / citation: 76.0%2022 · Report taken, no arrest: 8.3%2022 · Resolved on scene: 6.1%2022 · Unable to locate: 8.3%2022 · Other (unfounded / cancelled): 1.4%2023 · Arrest / citation: 73.7%2023 · Report taken, no arrest: 8.2%2023 · Resolved on scene: 7.2%2023 · Unable to locate: 9.0%2023 · Other (unfounded / cancelled): 1.9%2024 · Arrest / citation: 77.7%2024 · Report taken, no arrest: 8.4%2024 · Resolved on scene: 4.9%2024 · Unable to locate: 6.9%2024 · Other (unfounded / cancelled): 2.1%2025 · Arrest / citation: 77.4%2025 · Report taken, no arrest: 9.4%2025 · Resolved on scene: 5.4%2025 · Unable to locate: 6.0%2025 · Other (unfounded / cancelled): 1.8%2026 · Arrest / citation: 75.8%2026 · Report taken, no arrest: 11.3%2026 · Resolved on scene: 5.6%2026 · Unable to locate: 5.3%2026 · Other (unfounded / cancelled): 2.0%2009n=4,4192011n=6,0532013n=5,5862015n=4,5692017n=4,9662019n=4,6202021n=1,3022023n=1,7142025n=2,3152026n=1,722
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)
20094,41972.2%5.1%13.8%7.4%1.4%
20107,59572.9%4.5%13.1%8.0%1.5%
20116,05372.3%5.2%13.4%8.1%1.0%
20125,40168.6%7.9%14.6%7.8%1.1%
20135,58668.5%9.4%13.9%7.0%1.1%
20144,39867.1%11.9%11.5%8.2%1.5%
20154,56967.2%9.9%12.7%8.6%1.5%
20164,57671.5%7.1%10.9%9.6%0.9%
20174,96670.1%8.7%11.0%9.1%1.2%
20184,91971.2%8.6%9.9%8.9%1.3%
20194,62075.1%8.3%7.0%8.4%1.3%
20202,12871.2%8.1%8.9%10.2%1.5%
20211,30264.2%8.4%12.2%13.8%1.4%
20221,73976.0%8.3%6.1%8.3%1.4%
20231,71473.7%8.2%7.2%9.0%1.9%
20242,03477.7%8.4%4.9%6.9%2.1%
20252,31577.4%9.4%5.4%6.0%1.8%
20261,72275.8%11.3%5.6%5.3%2.0%
5% of Warrant Services/Order Calls End “Unable to Locate,” Down From 10%Report-taken outcomes moved from 7% of calls in 2016 to 11% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Warrant Services/Order: 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 72% of warrant services/order 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 warrant services/order 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 min40 min80 min2009: 18.5 min2010: 14.4 min2011: 14.1 min2012: 18.9 min2013: 19.8 min2014: 24.8 min2015: 26.6 min2016: 21.7 min2017: 21.8 min2018: 26.4 min2019: 24.8 min2020: 24.4 min2021: 26.7 min2022: 29.3 min2023: 40.0 min2024: 52.9 min2025: 60.4 min2026: 62.8 min2009: 27.1 min2010: 22.6 min2011: 23.5 min2012: 30.7 min2013: 31.5 min2014: 38.4 min2015: 36.3 min2016: 28.7 min2017: 29.5 min2018: 34.6 min2019: 31.1 min2020: 30.9 min2021: 38.1 min2022: 37.6 min2023: 48.4 min2024: 60.7 min2025: 70.8 min2026: 73.2 min2009n=1,0402011n=1,4542013n=1,5232015n=1,3242017n=1,2932019n=1,3052021n=4422023n=7322025n=8352026n=698
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
20091,04018.5 min27.1 min
20101,64114.4 min22.6 min
20111,45414.1 min23.5 min
20121,47718.9 min30.7 min
20131,52319.8 min31.5 min
20141,44724.8 min38.4 min
20151,32426.6 min36.3 min
20161,20221.7 min28.7 min
20171,29321.8 min29.5 min
20181,24826.4 min34.6 min
20191,30524.8 min31.1 min
202061924.4 min30.9 min
202144226.7 min38.1 min
202261329.3 min37.6 min
202373240.0 min48.4 min
202473952.9 min60.7 min
202583560.4 min70.8 min
202669862.8 min73.2 min
The Average Call Waits 73 Minutes for an Officer to ArriveDespite a 49% drop in calls between 2016 and 2025, average response time has more than doubled in the past 10 years, from 29 minutes in 2016 to 73 in 2026, driven largely by dispatch delays. This counts only the 28% of warrant services/order 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.

Warrant Services/Order: 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 72% of warrant services/order events, because they have no wait. Because most warrant services/order 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: 2.6%2009 · 0–5 min: 21.0%2009 · 5–30 min: 50.8%2009 · 30–60 min: 14.6%2009 · 1–4 hr: 10.7%2009 · 4–8 hr: 0.4%2010 · No recorded response: 3.4%2010 · 0–5 min: 25.9%2010 · 5–30 min: 49.4%2010 · 30–60 min: 12.6%2010 · 1–4 hr: 8.5%2010 · 4–8 hr: 0.2%2011 · No recorded response: 2.9%2011 · 0–5 min: 26.1%2011 · 5–30 min: 50.0%2011 · 30–60 min: 11.9%2011 · 1–4 hr: 8.9%2011 · 4–8 hr: 0.1%2011 · Over 8 hr: 0.1%2012 · No recorded response: 4.0%2012 · 0–5 min: 21.1%2012 · 5–30 min: 46.9%2012 · 30–60 min: 15.2%2012 · 1–4 hr: 11.9%2012 · 4–8 hr: 0.7%2012 · Over 8 hr: 0.1%2013 · No recorded response: 3.3%2013 · 0–5 min: 23.8%2013 · 5–30 min: 46.8%2013 · 30–60 min: 14.1%2013 · 1–4 hr: 10.6%2013 · 4–8 hr: 1.2%2013 · Over 8 hr: 0.2%2014 · No recorded response: 3.0%2014 · 0–5 min: 17.5%2014 · 5–30 min: 45.5%2014 · 30–60 min: 15.9%2014 · 1–4 hr: 16.6%2014 · 4–8 hr: 1.4%2014 · Over 8 hr: 0.1%2015 · No recorded response: 3.0%2015 · 0–5 min: 20.0%2015 · 5–30 min: 45.7%2015 · 30–60 min: 14.0%2015 · 1–4 hr: 15.6%2015 · 4–8 hr: 1.4%2015 · Over 8 hr: 0.3%2016 · No recorded response: 2.1%2016 · 0–5 min: 22.4%2016 · 5–30 min: 51.1%2016 · 30–60 min: 11.8%2016 · 1–4 hr: 11.7%2016 · 4–8 hr: 0.9%2016 · Over 8 hr: 0.1%2017 · No recorded response: 2.9%2017 · 0–5 min: 21.1%2017 · 5–30 min: 51.4%2017 · 30–60 min: 12.8%2017 · 1–4 hr: 10.7%2017 · 4–8 hr: 0.9%2017 · Over 8 hr: 0.1%2018 · No recorded response: 3.1%2018 · 0–5 min: 20.5%2018 · 5–30 min: 46.1%2018 · 30–60 min: 14.1%2018 · 1–4 hr: 14.8%2018 · 4–8 hr: 1.0%2018 · Over 8 hr: 0.3%2019 · No recorded response: 3.0%2019 · 0–5 min: 21.8%2019 · 5–30 min: 50.2%2019 · 30–60 min: 10.9%2019 · 1–4 hr: 12.9%2019 · 4–8 hr: 1.1%2019 · Over 8 hr: 0.2%2020 · No recorded response: 3.7%2020 · 0–5 min: 24.4%2020 · 5–30 min: 47.0%2020 · 30–60 min: 11.0%2020 · 1–4 hr: 12.8%2020 · 4–8 hr: 0.8%2020 · Over 8 hr: 0.3%2021 · No recorded response: 3.9%2021 · 0–5 min: 14.0%2021 · 5–30 min: 52.5%2021 · 30–60 min: 13.3%2021 · 1–4 hr: 14.5%2021 · 4–8 hr: 1.4%2021 · Over 8 hr: 0.5%2022 · No recorded response: 4.7%2022 · 0–5 min: 22.5%2022 · 5–30 min: 46.5%2022 · 30–60 min: 11.4%2022 · 1–4 hr: 12.2%2022 · 4–8 hr: 2.1%2022 · Over 8 hr: 0.5%2023 · No recorded response: 5.0%2023 · 0–5 min: 18.3%2023 · 5–30 min: 48.0%2023 · 30–60 min: 10.2%2023 · 1–4 hr: 15.2%2023 · 4–8 hr: 1.6%2023 · Over 8 hr: 1.6%2024 · No recorded response: 5.4%2024 · 0–5 min: 14.9%2024 · 5–30 min: 42.6%2024 · 30–60 min: 12.3%2024 · 1–4 hr: 19.8%2024 · 4–8 hr: 3.2%2024 · Over 8 hr: 1.8%2025 · No recorded response: 4.7%2025 · 0–5 min: 14.7%2025 · 5–30 min: 42.1%2025 · 30–60 min: 11.9%2025 · 1–4 hr: 20.1%2025 · 4–8 hr: 4.0%2025 · Over 8 hr: 2.5%2026 · No recorded response: 4.9%2026 · 0–5 min: 13.8%2026 · 5–30 min: 40.3%2026 · 30–60 min: 12.3%2026 · 1–4 hr: 21.2%2026 · 4–8 hr: 5.3%2026 · Over 8 hr: 2.3%2009n=1,0402011n=1,4542013n=1,5232015n=1,3242017n=1,2932019n=1,3052021n=4422023n=7322025n=8352026n=698
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
20091,0402.6%21.0%50.8%14.6%10.7%0.4%—
20101,6413.4%25.9%49.4%12.6%8.5%0.2%—
20111,4542.9%26.1%50.0%11.9%8.9%0.1%0.1%
20121,4774.0%21.1%46.9%15.2%11.9%0.7%0.1%
20131,5233.3%23.8%46.8%14.1%10.6%1.2%0.2%
20141,4473.0%17.5%45.5%15.9%16.6%1.4%0.1%
20151,3243.0%20.0%45.7%14.0%15.6%1.4%0.3%
20161,2022.1%22.4%51.1%11.8%11.7%0.9%0.1%
20171,2932.9%21.1%51.4%12.8%10.7%0.9%0.1%
20181,2483.1%20.5%46.1%14.1%14.8%1.0%0.3%
20191,3053.0%21.8%50.2%10.9%12.9%1.1%0.2%
20206193.7%24.4%47.0%11.0%12.8%0.8%0.3%
20214423.9%14.0%52.5%13.3%14.5%1.4%0.5%
20226134.7%22.5%46.5%11.4%12.2%2.1%0.5%
20237325.0%18.3%48.0%10.2%15.2%1.6%1.6%
20247395.4%14.9%42.6%12.3%19.8%3.2%1.8%
20258354.7%14.7%42.1%11.9%20.1%4.0%2.5%
20266984.9%13.8%40.3%12.3%21.2%5.3%2.3%
The Average Call Waits 63 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 63 minutes in 2026, more than double what it was in 2016. 29% of calls took more than an hour to get a response in 2026, compared with 13% in 2016. This counts only the 28% of warrant services/order 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.