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.
Custodial Interference calls over time: volume, outcomes, and response speed
Custodial Interference: 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 (8% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
custodial interference calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Custodial interference calls logged in CAD
2009
28
2010
49
2011
45
2012
31
2013
38
2014
39
2015
36
2016
34
2017
32
2018
24
2019
20
2020
17
2021
36
2022
32
2023
24
2024
23
2025
26
2026
22
Custodial Interference Calls Average About 32 a YearSeattle Police logged 556 custodial interference calls between 2009 and 2026, with a high of 49 in 2010.
Custodial Interference: 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)
Arrest / citation
2009
28
75.0%
14.3%
3.6%
7.2%
—
2010
49
61.2%
22.4%
12.2%
4.1%
—
2011
45
73.3%
17.8%
4.4%
4.4%
—
2012
31
77.4%
9.7%
3.2%
6.5%
3.2%
2013
38
60.5%
18.4%
10.5%
10.5%
—
2014
39
71.8%
15.4%
5.1%
5.1%
2.6%
2015
36
77.8%
13.9%
—
8.3%
—
2016
34
67.6%
11.8%
8.8%
11.8%
—
2017
32
71.9%
15.6%
3.1%
9.4%
—
2018
24
79.2%
—
8.3%
12.5%
—
2019
20
95.0%
—
—
5.0%
—
2020
17
76.5%
—
11.8%
11.8%
—
2021
36
83.3%
2.8%
—
13.9%
—
2022
32
78.1%
3.1%
12.5%
3.1%
3.1%
2023
24
66.7%
16.7%
8.3%
—
8.3%
2024
23
52.2%
13.0%
30.4%
—
4.3%
2025
26
57.7%
11.5%
15.4%
3.8%
11.5%
2026
22
40.9%
13.6%
36.4%
9.1%
—
9% of Custodial Interference Calls End “Unable to Locate”Across 2009 to 2026, report-taken outcomes were 70% of calls. “Unable to locate” means officers could not find the incident or the person who called.
Custodial Interference: 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 8% of custodial interference 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 custodial interference events are called in. The year with the fewest had only 16, 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
27
61.8 min
69.7 min
2010
48
34.7 min
44.5 min
2011
43
41.1 min
54.4 min
2012
29
63.6 min
84.4 min
2013
35
55.2 min
71.4 min
2014
37
51.5 min
71.2 min
2015
31
73.7 min
96.6 min
2016
30
54.8 min
66.0 min
2017
26
83.0 min
110.5 min
2018
21
84.6 min
92.4 min
2019
16
102.6 min
106.2 min
2020
16
55.9 min
60.3 min
2021
34
112.3 min
140.5 min
2022
32
173.9 min
180.7 min
2023
20
122.0 min
168.5 min
2024
22
264.5 min
292.5 min
2025
22
150.0 min
170.6 min
2026
22
163.8 min
156.5 min
34% of Called-In Custodial Interference Calls Get a Response Within 30 Minutes3% 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
0
—
—
2010
0
—
—
2011
1
4.1 min
10.4 min
2012
0
—
—
2013
3
2.0 min
11.4 min
2014
3
1.0 min
4.3 min
2015
1
0.1 min
10.4 min
2016
1
3.2 min
11.6 min
2017
0
—
—
2018
0
—
—
2019
0
—
—
2020
2
0.9 min
4.9 min
2021
1
3.1 min
25.0 min
2022
2
303.8 min
320.9 min
2023
3
2.0 min
11.7 min
2024
1
1.3 min
6.2 min
2025
2
1.1 min
8.2 min
2026
1
3.4 min
9.9 min
Priority 1 Calls Waited 9.9 Minutes on Average in 2026That is the average across 1 called-in Priority 1 events in 2026. 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
1
3.0 min
37.0 min
2010
2
4.5 min
32.6 min
2011
5
84.5 min
93.7 min
2012
7
47.6 min
55.9 min
2013
4
10.7 min
38.3 min
2014
7
27.7 min
36.2 min
2015
5
58.1 min
75.0 min
2016
6
18.6 min
27.8 min
2017
5
8.7 min
16.7 min
2018
5
54.9 min
84.9 min
2019
3
126.8 min
133.9 min
2020
1
5.3 min
119.1 min
2021
3
77.7 min
89.9 min
2022
3
168.2 min
182.7 min
2023
8
28.9 min
71.3 min
2024
3
110.7 min
179.4 min
2025
3
53.8 min
96.2 min
2026
3
82.3 min
79.3 min
Priority 2 Calls Waited 79 Minutes on Average in 2026That is the average across 3 called-in Priority 2 events in 2026. 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference calls. The year with the fewest had only 9, 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
26
64.1 min
71.2 min
2010
46
36.0 min
45.1 min
2011
37
36.2 min
49.9 min
2012
22
68.7 min
93.9 min
2013
28
67.3 min
83.4 min
2014
27
63.3 min
87.8 min
2015
25
79.8 min
104.8 min
2016
23
66.5 min
77.7 min
2017
21
100.7 min
135.2 min
2018
16
93.9 min
95.1 min
2019
13
97.0 min
99.3 min
2020
13
68.3 min
65.1 min
2021
30
119.4 min
150.8 min
2022
26
170.8 min
175.4 min
2023
9
244.8 min
285.5 min
2024
17
274.7 min
291.8 min
2025
17
184.5 min
216.3 min
2026
17
194.9 min
186.2 min
Priority 3 Calls Wait 151 Minutes for an Officer to ArriveAverage response time for Priority 3 calls has grown about 3-fold in the past 10 years, from 50 minutes in 2011 to 151 in 2021, driven largely by dispatch delays.
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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference events are called in. The year with the fewest had only 16, 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
4–8 hr
Over 8 hr
2009
27
14.8%
3.7%
29.6%
22.2%
29.6%
—
—
2010
48
10.4%
4.2%
47.9%
12.5%
25.0%
—
—
2011
43
7.0%
2.3%
37.2%
25.6%
25.6%
2.3%
—
2012
29
3.5%
3.5%
31.0%
10.3%
48.3%
3.5%
—
2013
35
5.7%
2.9%
28.6%
22.9%
37.1%
2.9%
—
2014
37
—
5.4%
56.8%
13.5%
16.2%
5.4%
2.7%
2015
31
3.2%
—
29.0%
19.4%
38.7%
9.7%
—
2016
30
10.0%
3.3%
36.7%
20.0%
23.3%
6.7%
—
2017
26
7.7%
—
34.6%
23.1%
19.2%
15.4%
—
2018
21
9.5%
4.8%
23.8%
19.1%
38.1%
—
4.8%
2019
16
6.2%
—
25.0%
12.5%
50.0%
6.2%
—
2020
16
12.5%
6.2%
37.5%
12.5%
25.0%
6.2%
—
2021
34
11.8%
2.9%
11.8%
14.7%
41.2%
14.7%
2.9%
2022
32
12.5%
—
21.9%
3.1%
46.9%
6.2%
9.4%
2023
20
10.0%
—
25.0%
10.0%
45.0%
—
10.0%
2024
22
13.6%
—
9.1%
4.5%
50.0%
4.5%
18.2%
2025
22
22.7%
—
18.2%
18.2%
18.2%
13.6%
9.1%
2026
22
18.2%
4.5%
31.8%
18.2%
13.6%
—
13.6%
41% of Called-In Custodial Interference Calls Wait Over an Hour for a ResponseAcross 2009 to 2026, 41% 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
5–30 min
0–5 min
Over 8 hr
2009
0
—
—
—
2010
0
—
—
—
2011
1
100.0%
—
—
2012
0
—
—
—
2013
3
66.7%
33.3%
—
2014
3
66.7%
33.3%
—
2015
1
100.0%
—
—
2016
1
100.0%
—
—
2017
0
—
—
—
2018
0
—
—
—
2019
0
—
—
—
2020
2
50.0%
50.0%
—
2021
1
100.0%
—
—
2022
2
50.0%
—
50.0%
2023
3
100.0%
—
—
2024
1
100.0%
—
—
2025
2
100.0%
—
—
2026
1
100.0%
—
—
0% of Priority 1 Calls Took Over an Hour in 2026That 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
30–60 min
5–30 min
4–8 hr
0–5 min
1–4 hr
No recorded response
Over 8 hr
2009
1
100.0%
—
—
—
—
—
—
2010
2
50.0%
50.0%
—
—
—
—
—
2011
5
20.0%
60.0%
20.0%
—
—
—
—
2012
7
14.3%
42.9%
—
14.3%
28.6%
—
—
2013
4
25.0%
50.0%
—
—
25.0%
—
—
2014
7
42.9%
42.9%
—
—
14.3%
—
—
2015
5
20.0%
40.0%
—
—
40.0%
—
—
2016
6
—
66.7%
—
—
16.7%
16.7%
—
2017
5
20.0%
80.0%
—
—
—
—
—
2018
5
—
40.0%
—
—
60.0%
—
—
2019
3
—
33.3%
33.3%
—
33.3%
—
—
2020
1
—
—
—
—
100.0%
—
—
2021
3
—
—
—
—
100.0%
—
—
2022
3
33.3%
33.3%
—
—
—
—
33.3%
2023
8
12.5%
12.5%
—
—
50.0%
25.0%
—
2024
3
—
—
33.3%
—
33.3%
33.3%
—
2025
3
33.3%
—
—
—
66.7%
—
—
2026
3
33.3%
—
—
—
33.3%
33.3%
—
33% of Priority 2 Calls Took Over an Hour in 2026That is 33% of 3 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference calls. The year with the fewest had only 9, 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
4–8 hr
Over 8 hr
2009
26
15.4%
3.9%
30.8%
19.2%
30.8%
—
—
2010
46
10.9%
4.3%
47.8%
10.9%
26.1%
—
—
2011
37
8.1%
2.7%
32.4%
27.0%
29.7%
—
—
2012
22
4.5%
—
27.3%
9.1%
54.5%
4.5%
—
2013
28
7.1%
—
21.4%
25.0%
42.9%
3.6%
—
2014
27
—
3.7%
59.3%
7.4%
18.5%
7.4%
3.7%
2015
25
4.0%
—
24.0%
20.0%
40.0%
12.0%
—
2016
23
8.7%
4.3%
26.1%
26.1%
26.1%
8.7%
—
2017
21
9.5%
—
23.8%
23.8%
23.8%
19.1%
—
2018
16
12.5%
6.2%
18.8%
25.0%
31.2%
—
6.2%
2019
13
7.7%
—
23.1%
15.4%
53.8%
—
—
2020
13
15.4%
—
38.5%
15.4%
23.1%
7.7%
—
2021
30
13.3%
3.3%
10.0%
16.7%
36.7%
16.7%
3.3%
2022
26
15.4%
—
15.4%
—
57.7%
7.7%
3.9%
2023
9
—
—
11.1%
11.1%
55.5%
—
22.2%
2024
17
11.8%
—
5.9%
5.9%
58.8%
—
17.6%
2025
17
29.4%
—
11.8%
17.6%
11.8%
17.6%
11.8%
2026
17
17.6%
5.9%
35.3%
11.8%
11.8%
—
17.6%
57% of Priority 3 Calls Wait Over an Hour for an Officer57% of Priority 3 calls took more than an hour to get a response in 2021, compared with 30% in 2011.
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 31 events in this period, with no dispatches in 1 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.
Custodial Interference: 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 (8% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
custodial interference calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Custodial interference calls logged in CAD
Sep 2025
3
Oct 2025
—
Nov 2025
4
Dec 2025
3
Jan 2026
2
Feb 2026
2
Mar 2026
3
Apr 2026
2
May 2026
2
Jun 2026
1
Jul 2026
8
Aug 2026
1
Custodial Interference Calls Totaled 31 Over the Last 12 MonthsSeattle Police logged 8 custodial interference calls in the busiest month (Jul 2026); 1 of the 12 months had none. Counts this small can swing from one month to the next.
Custodial Interference: 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)
Sep 2025
0
100.0%
—
—
—
Nov 2025
0
50.0%
25.0%
25.0%
—
Dec 2025
0
66.7%
33.3%
—
—
Jan 2026
0
—
—
50.0%
50.0%
Feb 2026
0
100.0%
—
—
—
Mar 2026
0
33.3%
33.3%
33.3%
—
Apr 2026
0
50.0%
—
50.0%
—
May 2026
0
—
50.0%
50.0%
—
Jun 2026
0
—
—
—
100.0%
Jul 2026
0
50.0%
—
50.0%
—
Aug 2026
0
100.0%
—
—
—
“Unable to Locate” Ended 29% of Custodial Interference Calls Over the Last 12 MonthsReport-taken outcomes were 52% of calls over the period.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
Average response time
Sep 2025
2
460.0 min
381.6 min
Oct 2025
0
—
—
Nov 2025
4
38.6 min
75.3 min
Dec 2025
3
59.4 min
67.1 min
Jan 2026
2
132.4 min
37.6 min
Feb 2026
2
84.2 min
87.4 min
Mar 2026
3
357.9 min
401.1 min
Apr 2026
2
12.7 min
26.3 min
May 2026
2
42.8 min
45.0 min
Jun 2026
1
736.1 min
—
Jul 2026
8
144.3 min
193.8 min
Aug 2026
1
23.4 min
23.7 min
33% of Called-In Custodial Interference Calls Got a Response Within 30 Minutes3% were answered in under 5 minutes over the last 12 months.
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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
Average response time
Sep 2025
0
—
—
Oct 2025
0
—
—
Nov 2025
0
—
—
Dec 2025
0
—
—
Jan 2026
0
—
—
Feb 2026
1
3.4 min
9.9 min
Mar 2026
0
—
—
Apr 2026
0
—
—
May 2026
0
—
—
Jun 2026
0
—
—
Jul 2026
0
—
—
Aug 2026
0
—
—
Priority 1 Calls Averaged 9.9 Minutes to Get an Officer Over the Last 12 MonthsBased on 1 called-in Priority 1 events with a recorded arrival. 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
Average response time
Sep 2025
0
—
—
Oct 2025
0
—
—
Nov 2025
2
68.9 min
122.2 min
Dec 2025
0
—
—
Jan 2026
0
—
—
Feb 2026
0
—
—
Mar 2026
0
—
—
Apr 2026
0
—
—
May 2026
1
27.4 min
31.7 min
Jun 2026
0
—
—
Jul 2026
2
109.7 min
126.9 min
Aug 2026
0
—
—
Priority 2 Calls Averaged 106 Minutes to Get an Officer Over the Last 12 MonthsBased on 5 called-in Priority 2 events with a recorded arrival. 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
Average response time
Sep 2025
2
460.0 min
381.6 min
Oct 2025
0
—
—
Nov 2025
2
8.4 min
28.4 min
Dec 2025
3
59.4 min
67.1 min
Jan 2026
2
132.4 min
37.6 min
Feb 2026
1
165.0 min
165.0 min
Mar 2026
2
516.3 min
581.1 min
Apr 2026
2
12.7 min
26.3 min
May 2026
1
58.2 min
58.2 min
Jun 2026
1
736.1 min
—
Jul 2026
6
155.8 min
207.1 min
Aug 2026
1
23.4 min
23.7 min
39% of Called-In Priority 3 Calls Got a Response Within 30 Minutes4% were answered in under 5 minutes over the last 12 months.
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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
4–8 hr
5–30 min
30–60 min
1–4 hr
Over 8 hr
0–5 min
Sep 2025
2
50.0%
50.0%
—
—
—
—
—
Oct 2025
0
—
—
—
—
—
—
—
Nov 2025
4
—
—
25.0%
25.0%
50.0%
—
—
Dec 2025
3
—
—
33.3%
33.3%
33.3%
—
—
Jan 2026
2
50.0%
—
—
50.0%
—
—
—
Feb 2026
2
—
—
50.0%
—
50.0%
—
—
Mar 2026
3
—
—
—
33.3%
—
66.7%
—
Apr 2026
2
—
—
100.0%
—
—
—
—
May 2026
2
—
—
—
100.0%
—
—
—
Jun 2026
1
100.0%
—
—
—
—
—
—
Jul 2026
8
25.0%
—
37.5%
—
12.5%
12.5%
12.5%
Aug 2026
1
—
—
100.0%
—
—
—
—
30% of Called-In Calls Took Over an Hour to Get a ResponseThat is 30% of 30 called-in events over the last 12 months.
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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
5–30 min
Sep 2025
0
—
Oct 2025
0
—
Nov 2025
0
—
Dec 2025
0
—
Jan 2026
0
—
Feb 2026
1
100.0%
Mar 2026
0
—
Apr 2026
0
—
May 2026
0
—
Jun 2026
0
—
Jul 2026
0
—
Aug 2026
0
—
0% of Priority 1 Calls Took Over an Hour Over the Last 12 MonthsThat is 0% of 1 called-in Priority 1 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
1–4 hr
30–60 min
No recorded response
Sep 2025
0
—
—
—
Oct 2025
0
—
—
—
Nov 2025
2
100.0%
—
—
Dec 2025
0
—
—
—
Jan 2026
0
—
—
—
Feb 2026
0
—
—
—
Mar 2026
0
—
—
—
Apr 2026
0
—
—
—
May 2026
1
—
100.0%
—
Jun 2026
0
—
—
—
Jul 2026
2
50.0%
—
50.0%
Aug 2026
0
—
—
—
60% of Priority 2 Calls Took Over an Hour Over the Last 12 MonthsThat is 60% of 5 called-in Priority 2 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference 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
4–8 hr
5–30 min
30–60 min
1–4 hr
Over 8 hr
0–5 min
Sep 2025
2
50.0%
50.0%
—
—
—
—
—
Oct 2025
0
—
—
—
—
—
—
—
Nov 2025
2
—
—
50.0%
50.0%
—
—
—
Dec 2025
3
—
—
33.3%
33.3%
33.3%
—
—
Jan 2026
2
50.0%
—
—
50.0%
—
—
—
Feb 2026
1
—
—
—
—
100.0%
—
—
Mar 2026
2
—
—
—
—
—
100.0%
—
Apr 2026
2
—
—
100.0%
—
—
—
—
May 2026
1
—
—
—
100.0%
—
—
—
Jun 2026
1
100.0%
—
—
—
—
—
—
Jul 2026
6
16.7%
—
50.0%
—
—
16.7%
16.7%
Aug 2026
1
—
—
100.0%
—
—
—
—
26% of Called-In Priority 3 Calls Took Over an Hour to Get a ResponseThat is 26% of 23 called-in events over the last 12 months.
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.
Small sample: this category had 10 events in this period, with no dispatches in 7 of the 12 weeks. Percentages and average times can swing widely when counts are this small, so read the trends with caution; the n= under each week shows its count.
Custodial Interference: 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 (8% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
custodial interference calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Custodial interference calls logged in CAD
Week of Jun 15
—
Week of Jun 22
—
Week of Jun 29
1
Week of Jul 6
3
Week of Jul 13
4
Week of Jul 20
1
Week of Jul 27
—
Week of Aug 3
—
Week of Aug 10
1
Week of Aug 17
—
Week of Aug 24
—
Week of Aug 31
—
Custodial Interference Calls Totaled 10 Over the Last 12 WeeksSeattle Police logged 4 custodial interference calls in the busiest week (Week of Jul 13); 7 of the 12 weeks had none. Counts this small can swing from one week to the next.
Custodial Interference: 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
Other (unfounded / cancelled)
Report taken, no arrest
Unable to locate
Week of Jun 29
0
100.0%
—
—
Week of Jul 6
0
—
33.3%
66.7%
Week of Jul 13
0
—
50.0%
50.0%
Week of Jul 20
0
—
100.0%
—
Week of Aug 10
0
—
100.0%
—
“Unable to Locate” Ended 40% of Custodial Interference Calls Over the Last 12 WeeksReport-taken outcomes were 50% of calls over the period.
Custodial Interference: 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 8% of custodial interference 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 custodial interference events are called in. The week with the fewest had only 1, so averages can swing widely; the n= under each week 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
Week of Jun 15
0
—
—
Week of Jun 22
0
—
—
Week of Jun 29
1
736.1 min
—
Week of Jul 6
3
35.4 min
6.3 min
Week of Jul 13
4
34.5 min
53.5 min
Week of Jul 20
1
910.1 min
989.5 min
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
1
23.4 min
23.7 min
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Called-In Events Averaged 138 Minutes to Get an Officer Over the Last 12 WeeksBased on 9 called-in events with a recorded arrival. Counts this small can swing from one week 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.
Custodial Interference: 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 8% of custodial interference 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 WeeksThere 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference calls. The week with the fewest had only 1, so averages can swing widely; the n= under each week 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
Week of Jun 15
0
—
—
Week of Jun 22
0
—
—
Week of Jun 29
0
—
—
Week of Jul 6
1
102.9 min
—
Week of Jul 13
1
116.5 min
126.9 min
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
0
—
—
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Priority 2 Calls Averaged 127 Minutes to Get an Officer Over the Last 12 WeeksBased on 1 called-in Priority 2 events with a recorded arrival. Counts this small can swing from one week 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference calls. The week with the fewest had only 1, so averages can swing widely; the n= under each week 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
Week of Jun 15
0
—
—
Week of Jun 22
0
—
—
Week of Jun 29
1
736.1 min
—
Week of Jul 6
2
1.6 min
6.3 min
Week of Jul 13
3
7.1 min
16.8 min
Week of Jul 20
1
910.1 min
989.5 min
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
1
23.4 min
23.7 min
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Priority 3 Calls Averaged 154 Minutes to Get an Officer Over the Last 12 WeeksBased on 7 called-in Priority 3 events with a recorded arrival. Counts this small can swing from one week 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference events are called in. The week with the fewest had only 1, so shares can swing widely; the n= under each week 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
1–4 hr
Over 8 hr
Week of Jun 15
0
—
—
—
—
—
Week of Jun 22
0
—
—
—
—
—
Week of Jun 29
1
100.0%
—
—
—
—
Week of Jul 6
3
33.3%
33.3%
33.3%
—
—
Week of Jul 13
4
25.0%
—
50.0%
25.0%
—
Week of Jul 20
1
—
—
—
—
100.0%
Week of Jul 27
0
—
—
—
—
—
Week of Aug 3
0
—
—
—
—
—
Week of Aug 10
1
—
—
100.0%
—
—
Week of Aug 17
0
—
—
—
—
—
Week of Aug 24
0
—
—
—
—
—
Week of Aug 31
0
—
—
—
—
—
20% of Called-In Events Took Over an Hour Over the Last 12 WeeksThat is 20% of 10 called-in events. Counts this small can swing from one week 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.
Custodial Interference: 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 8% of custodial interference 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 WeeksThere 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference calls. The week with the fewest had only 1, so shares can swing widely; the n= under each week 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
1–4 hr
Week of Jun 15
0
—
—
Week of Jun 22
0
—
—
Week of Jun 29
0
—
—
Week of Jul 6
1
100.0%
—
Week of Jul 13
1
—
100.0%
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
0
—
—
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
50% of Priority 2 Calls Took Over an Hour Over the Last 12 WeeksThat is 50% of 2 called-in Priority 2 events. Counts this small can swing from one week 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.
Custodial Interference: 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 8% of custodial interference 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 custodial interference calls. The week with the fewest had only 1, so shares can swing widely; the n= under each week 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
Over 8 hr
Week of Jun 15
0
—
—
—
—
Week of Jun 22
0
—
—
—
—
Week of Jun 29
1
100.0%
—
—
—
Week of Jul 6
2
—
50.0%
50.0%
—
Week of Jul 13
3
33.3%
—
66.7%
—
Week of Jul 20
1
—
—
—
100.0%
Week of Jul 27
0
—
—
—
—
Week of Aug 3
0
—
—
—
—
Week of Aug 10
1
—
—
100.0%
—
Week of Aug 17
0
—
—
—
—
Week of Aug 24
0
—
—
—
—
Week of Aug 31
0
—
—
—
—
12% of Priority 3 Calls Took Over an Hour Over the Last 12 WeeksThat is 12% of 8 called-in Priority 3 events. Counts this small can swing from one week 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.
“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.
“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. “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. “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.