Disclaimer: This site uses publicly accessible data from the City of Seattle. We use artificial intelligence to interpret and visualize the data. We present the data as is. Any further analysis or interpretation of the data is strictly the responsibility of the end user.
Cookies: This site uses cookies and similar browser storage, including Google Analytics, to measure traffic and to remember your choice. You must accept cookies to view this site. See our Privacy Policy.
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 →
Swipe sideways to see the full chart →
detox calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Detox calls logged in CAD
2009
192
2010
40
2011
10
2012
11
2013
11
2014
10
2015
9
2016
5
2017
1
2018
4
2019
6
2020
7
2021
2
2022
2
2023
2
2024
3
2025
1
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 →
Swipe sideways to see the full chart →
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
Period
Events
Report taken, no arrest
Resolved on scene
Unable to locate
Other (unfounded / cancelled)
2009
192
1.6%
89.6%
4.7%
4.2%
2010
40
2.5%
57.5%
2.5%
37.5%
2011
10
—
30.0%
—
70.0%
2012
11
—
27.3%
—
72.7%
2013
11
—
—
—
100.0%
2014
10
—
10.0%
—
90.0%
2015
9
—
33.3%
—
66.7%
2016
5
—
80.0%
—
20.0%
2017
1
—
—
—
100.0%
2018
4
—
25.0%
—
75.0%
2019
6
—
33.3%
—
66.7%
2020
7
—
28.6%
—
71.4%
2021
2
—
—
—
100.0%
2022
2
—
50.0%
—
50.0%
2023
2
—
50.0%
—
50.0%
2024
3
—
33.3%
—
66.7%
2025
1
—
—
—
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 →
Swipe sideways to see the full chart →
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
Period
Called-in events
Average dispatch delay
Average response time
2009
180
5.0 min
12.2 min
2010
35
3.0 min
10.2 min
2011
6
1.9 min
2.4 min
2012
11
1.8 min
4.7 min
2013
8
4.7 min
2.1 min
2014
6
1.3 min
4.4 min
2015
5
1.3 min
3.5 min
2016
2
2.2 min
2.8 min
2017
0
—
—
2018
2
0.3 min
—
2019
2
1.6 min
—
2020
6
1.4 min
0.8 min
2021
1
1.4 min
—
2022
1
0.8 min
—
2023
2
1.4 min
2.8 min
2024
3
0.7 min
6.7 min
2025
1
2.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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 1 calls are a small share of detox calls. 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
Period
Called-in events
Average dispatch delay
Average response time
2009
13
2.2 min
4.2 min
2010
7
1.1 min
—
2011
1
0.4 min
—
2012
5
1.1 min
—
2013
2
14.1 min
—
2014
4
0.8 min
4.7 min
2015
2
1.0 min
—
2016
0
—
—
2017
0
—
—
2018
1
0.6 min
—
2019
2
1.6 min
—
2020
1
0.7 min
0.7 min
2021
0
—
—
2022
1
0.8 min
—
2023
1
0.1 min
—
2024
1
0.4 min
—
2025
0
—
—
No Priority 1 Response Times Were Recorded in 2024None of the 1 called-in Priority 1 events had a recorded officer arrival.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 2 calls are a small share of detox calls. The year with the fewest had only 2, 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
Period
Called-in events
Average dispatch delay
Average response time
2009
6
5.0 min
6.4 min
2010
2
8.2 min
14.6 min
2011
0
—
—
2012
2
1.5 min
6.8 min
2013
0
—
—
2014
0
—
—
2015
0
—
—
2016
0
—
—
2017
0
—
—
2018
0
—
—
2019
0
—
—
2020
0
—
—
2021
0
—
—
2022
0
—
—
2023
0
—
—
2024
0
—
—
2025
0
—
—
Priority 2 Calls Waited 6.8 Minutes on Average in 2012That is the average across 2 called-in Priority 2 events in 2012. Counts this small can swing a lot from year to year.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 3 calls are a small share of detox calls. 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
Period
Called-in events
Average dispatch delay
Average response time
2009
161
5.2 min
14.4 min
2010
26
3.2 min
1.5 min
2011
5
2.2 min
2.4 min
2012
4
2.9 min
0.5 min
2013
6
1.5 min
2.1 min
2014
2
2.3 min
3.8 min
2015
3
1.4 min
3.5 min
2016
2
2.2 min
2.8 min
2017
0
—
—
2018
1
0.0 min
—
2019
0
—
—
2020
5
1.5 min
0.8 min
2021
1
1.4 min
—
2022
0
—
—
2023
1
2.8 min
2.8 min
2024
2
0.8 min
6.7 min
2025
1
2.1 min
—
No Priority 3 Response Times Were Recorded in 2025None of the 1 called-in Priority 3 events had a recorded officer arrival.
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 →
Swipe sideways to see the full chart →
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
Period
Called-in events
No recorded response
0–5 min
5–30 min
30–60 min
1–4 hr
2009
180
85.0%
7.8%
6.1%
0.6%
0.6%
2010
35
91.4%
2.9%
5.7%
—
—
2011
6
83.3%
16.7%
—
—
—
2012
11
72.7%
18.2%
9.1%
—
—
2013
8
75.0%
25.0%
—
—
—
2014
6
50.0%
33.3%
16.7%
—
—
2015
5
80.0%
20.0%
—
—
—
2016
2
50.0%
50.0%
—
—
—
2017
0
—
—
—
—
—
2018
2
100.0%
—
—
—
—
2019
2
100.0%
—
—
—
—
2020
6
33.3%
66.7%
—
—
—
2021
1
100.0%
—
—
—
—
2022
1
100.0%
—
—
—
—
2023
2
50.0%
50.0%
—
—
—
2024
3
66.7%
—
33.3%
—
—
2025
1
100.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.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 1 calls are a small share of detox calls. 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
Period
Called-in events
No recorded response
0–5 min
5–30 min
2009
13
84.6%
7.7%
7.7%
2010
7
100.0%
—
—
2011
1
100.0%
—
—
2012
5
100.0%
—
—
2013
2
100.0%
—
—
2014
4
50.0%
25.0%
25.0%
2015
2
100.0%
—
—
2016
0
—
—
—
2017
0
—
—
—
2018
1
100.0%
—
—
2019
2
100.0%
—
—
2020
1
—
100.0%
—
2021
0
—
—
—
2022
1
100.0%
—
—
2023
1
100.0%
—
—
2024
1
100.0%
—
—
2025
0
—
—
—
0% of Priority 1 Calls Took Over an Hour in 2024That is 0% of 1 called-in Priority 1 events. Counts this small can swing a lot from year to year.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 2 calls are a small share of detox calls. The year with the fewest had only 2, 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
Period
Called-in events
No recorded response
0–5 min
5–30 min
2009
6
16.7%
50.0%
33.3%
2010
2
—
—
100.0%
2011
0
—
—
—
2012
2
—
50.0%
50.0%
2013
0
—
—
—
2014
0
—
—
—
2015
0
—
—
—
2016
0
—
—
—
2017
0
—
—
—
2018
0
—
—
—
2019
0
—
—
—
2020
0
—
—
—
2021
0
—
—
—
2022
0
—
—
—
2023
0
—
—
—
2024
0
—
—
—
2025
0
—
—
—
0% of Priority 2 Calls Took Over an Hour in 2012That is 0% of 2 called-in Priority 2 events. Counts this small can swing a lot from year to year.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 3 calls are a small share of detox calls. 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
Period
Called-in events
No recorded response
0–5 min
5–30 min
30–60 min
1–4 hr
2009
161
87.6%
6.2%
5.0%
0.6%
0.6%
2010
26
96.2%
3.9%
—
—
—
2011
5
80.0%
20.0%
—
—
—
2012
4
75.0%
25.0%
—
—
—
2013
6
66.7%
33.3%
—
—
—
2014
2
50.0%
50.0%
—
—
—
2015
3
66.7%
33.3%
—
—
—
2016
2
50.0%
50.0%
—
—
—
2017
0
—
—
—
—
—
2018
1
100.0%
—
—
—
—
2019
0
—
—
—
—
—
2020
5
40.0%
60.0%
—
—
—
2021
1
100.0%
—
—
—
—
2022
0
—
—
—
—
—
2023
1
—
100.0%
—
—
—
2024
2
50.0%
—
50.0%
—
—
2025
1
100.0%
—
—
—
—
0% of Priority 3 Calls Took Over an Hour in 2025That is 0% of 1 called-in Priority 3 events. Counts this small can swing a lot from year to year.
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.
Showing the 12 full calendar months, Sep 2025 through Aug 2026, one bar per month. The current month is left out because it is incomplete.
Small sample: this category had 1 events in this period, with no dispatches in 11 of the 12 months. Percentages and average times can swing widely when counts are this small, so read the trends with caution; the n= under each month shows its count.
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 →
Swipe sideways to see the full chart →
detox calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Detox calls logged in CAD
Sep 2025
—
Oct 2025
1
Nov 2025
—
Dec 2025
—
Jan 2026
—
Feb 2026
—
Mar 2026
—
Apr 2026
—
May 2026
—
Jun 2026
—
Jul 2026
—
Aug 2026
—
Detox Calls Totaled 1 Over the Last 12 MonthsSeattle Police logged 1 detox calls in the busiest month (Oct 2025); 11 of the 12 months had none. Counts this small can swing from one month to the next.
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 →
Swipe sideways to see the full chart →
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
Period
Other (unfounded / cancelled)
Oct 2025
100.0%
“Unable to Locate” Ended 0% of Detox Calls Over the Last 12 MonthsReport-taken outcomes were 0% of calls over the period.
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Only a small share of detox events are called in. The month with the fewest had only 1, so averages can swing widely; the n= under each month shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Sep 2025
0
—
Oct 2025
1
2.1 min
Nov 2025
0
—
Dec 2025
0
—
Jan 2026
0
—
Feb 2026
0
—
Mar 2026
0
—
Apr 2026
0
—
May 2026
0
—
Jun 2026
0
—
Jul 2026
0
—
Aug 2026
0
—
No Response Times Were Recorded Over the Last 12 MonthsNone of the 1 called-in events had a recorded officer arrival.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
No Priority 1 Calls Over the Last 12 MonthsThere were no called-in Priority 1 events in the period.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
No Priority 2 Calls Over the Last 12 MonthsThere were no called-in Priority 2 events in the period.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 3 calls are a small share of detox calls. The month with the fewest had only 1, so averages can swing widely; the n= under each month shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Sep 2025
0
—
Oct 2025
1
2.1 min
Nov 2025
0
—
Dec 2025
0
—
Jan 2026
0
—
Feb 2026
0
—
Mar 2026
0
—
Apr 2026
0
—
May 2026
0
—
Jun 2026
0
—
Jul 2026
0
—
Aug 2026
0
—
No Priority 3 Response Times Were Recorded Over the Last 12 MonthsNone of the 1 called-in Priority 3 events had a recorded officer arrival.
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 →
Swipe sideways to see the full chart →
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 month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
No recorded response
Sep 2025
0
—
Oct 2025
1
100.0%
Nov 2025
0
—
Dec 2025
0
—
Jan 2026
0
—
Feb 2026
0
—
Mar 2026
0
—
Apr 2026
0
—
May 2026
0
—
Jun 2026
0
—
Jul 2026
0
—
Aug 2026
0
—
0% of Called-In Events Took Over an Hour Over the Last 12 MonthsThat is 0% of 1 called-in events. Counts this small can swing from one month to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
No Priority 1 Calls Over the Last 12 MonthsThere were no called-in Priority 1 events in the period.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
No Priority 2 Calls Over the Last 12 MonthsThere were no called-in Priority 2 events in the period.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 3 calls are a small share of detox calls. The month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
No recorded response
Sep 2025
0
—
Oct 2025
1
100.0%
Nov 2025
0
—
Dec 2025
0
—
Jan 2026
0
—
Feb 2026
0
—
Mar 2026
0
—
Apr 2026
0
—
May 2026
0
—
Jun 2026
0
—
Jul 2026
0
—
Aug 2026
0
—
0% of Priority 3 Calls Took Over an Hour Over the Last 12 MonthsThat is 0% of 1 called-in Priority 3 events. Counts this small can swing from one month to the next.
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.
Showing the 12 most recent full weeks (Monday to Sunday): Jun 15 through Sep 6, 2026, one bar per week, labeled by its first day. The current week is left out because it is incomplete.
No events in this period. Seattle Police logged no detox calls in this window, so there is nothing to chart. Switch to Historical to see the full record.
“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.
“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 month is the number of events logged that month 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.
“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 week is the number of events logged that week 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.