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

Detox

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

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

Swipe sideways to see the full chart →
01252502009: 192 detox calls logged in CAD2010: 40 detox calls logged in CAD2011: 10 detox calls logged in CAD2012: 11 detox calls logged in CAD2013: 11 detox calls logged in CAD2014: 10 detox calls logged in CAD2015: 9 detox calls logged in CAD2016: 5 detox calls logged in CAD2017: 1 detox calls logged in CAD2018: 4 detox calls logged in CAD2019: 6 detox calls logged in CAD2020: 7 detox calls logged in CAD2021: 2 detox calls logged in CAD2022: 2 detox calls logged in CAD2023: 2 detox calls logged in CAD2024: 3 detox calls logged in CAD2025: 1 detox calls logged in CAD2009n=1922011n=102013n=112015n=92017n=12019n=62021n=22023n=22025n=1
detox calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodDetox calls logged in CAD
2009192
201040
201110
201211
201311
201410
20159
20165
20171
20184
20196
20207
20212
20222
20232
20243
20251
Detox Calls Average About 8 a YearSeattle Police logged 316 detox calls between 2009 and 2025, with a high of 192 in 2009.

Detox: 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 · Report taken, no arrest: 1.6%2009 · Resolved on scene: 89.6%2009 · Unable to locate: 4.7%2009 · Other (unfounded / cancelled): 4.2%2010 · Report taken, no arrest: 2.5%2010 · Resolved on scene: 57.5%2010 · Unable to locate: 2.5%2010 · Other (unfounded / cancelled): 37.5%2011 · Resolved on scene: 30.0%2011 · Other (unfounded / cancelled): 70.0%2012 · Resolved on scene: 27.3%2012 · Other (unfounded / cancelled): 72.7%2013 · Other (unfounded / cancelled): 100.0%2014 · Resolved on scene: 10.0%2014 · Other (unfounded / cancelled): 90.0%2015 · Resolved on scene: 33.3%2015 · Other (unfounded / cancelled): 66.7%2016 · Resolved on scene: 80.0%2016 · Other (unfounded / cancelled): 20.0%2017 · Other (unfounded / cancelled): 100.0%2018 · Resolved on scene: 25.0%2018 · Other (unfounded / cancelled): 75.0%2019 · Resolved on scene: 33.3%2019 · Other (unfounded / cancelled): 66.7%2020 · Resolved on scene: 28.6%2020 · Other (unfounded / cancelled): 71.4%2021 · Other (unfounded / cancelled): 100.0%2022 · Resolved on scene: 50.0%2022 · Other (unfounded / cancelled): 50.0%2023 · Resolved on scene: 50.0%2023 · Other (unfounded / cancelled): 50.0%2024 · Resolved on scene: 33.3%2024 · Other (unfounded / cancelled): 66.7%2025 · Other (unfounded / cancelled): 100.0%2009n=1922011n=102013n=112015n=92017n=12019n=62021n=22023n=22025n=1
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)
20091921.6%89.6%4.7%4.2%
2010402.5%57.5%2.5%37.5%
201110—30.0%—70.0%
201211—27.3%—72.7%
201311———100.0%
201410—10.0%—90.0%
20159—33.3%—66.7%
20165—80.0%—20.0%
20171———100.0%
20184—25.0%—75.0%
20196—33.3%—66.7%
20207—28.6%—71.4%
20212———100.0%
20222—50.0%—50.0%
20232—50.0%—50.0%
20243—33.3%—66.7%
20251———100.0%
3% of Detox Calls End “Unable to Locate”Across 2009 to 2025, report-taken outcomes were 1% of calls. “Unable to locate” means officers could not find the incident or the person who called.

Detox: 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 14% of detox 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. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
0 min8 min15 min2009: 5.0 min2010: 3.0 min2011: 1.9 min2012: 1.8 min2013: 4.7 min2014: 1.3 min2015: 1.3 min2016: 2.2 min2018: 0.3 min2019: 1.6 min2020: 1.4 min2021: 1.4 min2022: 0.8 min2023: 1.4 min2024: 0.7 min2025: 2.1 min2009: 12.2 min2010: 10.2 min2011: 2.4 min2012: 4.7 min2013: 2.1 min2014: 4.4 min2015: 3.5 min2016: 2.8 min2020: 0.8 min2023: 2.8 min2024: 6.7 min2009n=1802011n=62013n=82015n=52017n=02019n=22021n=12023n=22025n=1
Average response timeAverage dispatch delay
Small sample: Only a small share of detox events are called in. The year with the fewest had only 1, 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
20091805.0 min12.2 min
2010353.0 min10.2 min
201161.9 min2.4 min
2012111.8 min4.7 min
201384.7 min2.1 min
201461.3 min4.4 min
201551.3 min3.5 min
201622.2 min2.8 min
20170——
201820.3 min—
201921.6 min—
202061.4 min0.8 min
202111.4 min—
202210.8 min—
202321.4 min2.8 min
202430.7 min6.7 min
202512.1 min—
17% of Called-In Detox Calls Get a Response Within 30 Minutes11% were answered in under 5 minutes, across all years on record.
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.

Detox: 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 14% of detox events, because they have no wait. 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: 85.0%2009 · 0–5 min: 7.8%2009 · 5–30 min: 6.1%2009 · 30–60 min: 0.6%2009 · 1–4 hr: 0.6%2010 · No recorded response: 91.4%2010 · 0–5 min: 2.9%2010 · 5–30 min: 5.7%2011 · No recorded response: 83.3%2011 · 0–5 min: 16.7%2012 · No recorded response: 72.7%2012 · 0–5 min: 18.2%2012 · 5–30 min: 9.1%2013 · No recorded response: 75.0%2013 · 0–5 min: 25.0%2014 · No recorded response: 50.0%2014 · 0–5 min: 33.3%2014 · 5–30 min: 16.7%2015 · No recorded response: 80.0%2015 · 0–5 min: 20.0%2016 · No recorded response: 50.0%2016 · 0–5 min: 50.0%2018 · No recorded response: 100.0%2019 · No recorded response: 100.0%2020 · No recorded response: 33.3%2020 · 0–5 min: 66.7%2021 · No recorded response: 100.0%2022 · No recorded response: 100.0%2023 · No recorded response: 50.0%2023 · 0–5 min: 50.0%2024 · No recorded response: 66.7%2024 · 5–30 min: 33.3%2025 · No recorded response: 100.0%2009n=1802011n=62013n=82015n=52017n=02019n=22021n=12023n=22025n=1
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of detox events are called in. The year with the fewest had only 1, 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 hr
200918085.0%7.8%6.1%0.6%0.6%
20103591.4%2.9%5.7%——
2011683.3%16.7%———
20121172.7%18.2%9.1%——
2013875.0%25.0%———
2014650.0%33.3%16.7%——
2015580.0%20.0%———
2016250.0%50.0%———
20170—————
20182100.0%————
20192100.0%————
2020633.3%66.7%———
20211100.0%————
20221100.0%————
2023250.0%50.0%———
2024366.7%—33.3%——
20251100.0%————
0% of Called-In Detox Calls Wait Over an Hour for a ResponseAcross 2009 to 2025, 0% of called-in events took more than an hour to get a response.
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 2025 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.