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.
Assist the Officer calls over time: volume, outcomes, and response speed
Assist the Officer: 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 (49% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
assist the officer calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Assist the officer calls logged in CAD
2009
111
2010
82
2011
70
2012
118
2013
82
2014
78
2015
70
2016
74
2017
72
2018
71
2019
67
2020
41
2021
32
2022
43
2023
47
2024
52
2025
60
2026
54
Assist the Officer Calls Are Down 49% From Their 2012 PeakSeattle Police logged 118 assist the officer calls in 2012 and 60 in 2025, the most recent full year.
Assist the Officer: 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
Arrest / citation
Report taken, no arrest
Resolved on scene
Unable to locate
Other (unfounded / cancelled)
2009
111
0.9%
2.7%
75.7%
4.5%
16.2%
2010
82
—
—
40.2%
1.2%
58.5%
2011
70
4.3%
4.3%
31.4%
1.4%
58.6%
2012
118
1.7%
3.4%
53.4%
1.7%
39.8%
2013
82
—
3.7%
59.8%
1.2%
35.4%
2014
78
—
1.3%
64.1%
1.3%
33.3%
2015
70
—
1.4%
58.6%
—
40.0%
2016
74
—
2.7%
63.5%
—
33.8%
2017
72
—
2.8%
50.0%
2.8%
44.4%
2018
71
—
1.4%
56.3%
—
42.3%
2019
67
1.5%
3.0%
64.2%
3.0%
28.4%
2020
41
—
4.9%
56.1%
4.9%
34.1%
2021
32
—
9.4%
50.0%
3.1%
37.5%
2022
43
2.3%
4.7%
30.2%
—
62.8%
2023
47
2.1%
—
34.0%
6.4%
57.4%
2024
52
5.8%
1.9%
38.5%
11.5%
42.3%
2025
60
—
6.7%
40.0%
20.0%
33.3%
2026
54
—
1.9%
44.4%
14.8%
38.9%
15% of Assist the Officer Calls End “Unable to Locate,” Up From 0%Report-taken outcomes moved from 3% of calls in 2016 to 2% in 2026. “Unable to locate” means officers could not find the incident or the person who called.
Assist the Officer: 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 49% of assist the officer 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 assist the officer events are called in. The year with the fewest had only 18, 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
49
19.4 min
27.0 min
2010
47
4.3 min
9.8 min
2011
35
5.4 min
11.1 min
2012
48
14.8 min
23.5 min
2013
31
9.4 min
17.7 min
2014
33
11.9 min
17.8 min
2015
27
4.1 min
11.0 min
2016
31
7.6 min
14.6 min
2017
35
4.9 min
10.8 min
2018
37
15.2 min
25.7 min
2019
28
7.4 min
16.0 min
2020
22
6.9 min
14.8 min
2021
18
25.1 min
40.5 min
2022
33
5.5 min
13.7 min
2023
31
13.7 min
29.8 min
2024
39
61.8 min
91.3 min
2025
39
42.4 min
64.9 min
2026
40
21.7 min
34.5 min
The Average Call Waits 34 Minutes for an Officer to ArriveDespite a 19% drop in calls between 2016 and 2025, average response time has more than doubled in the past 10 years, from 15 minutes in 2016 to 34 in 2026, 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer calls. The year with the fewest had only 3, 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
9
1.6 min
3.6 min
2010
13
2.1 min
5.2 min
2011
11
0.3 min
1.6 min
2012
11
0.5 min
1.9 min
2013
8
0.8 min
3.5 min
2014
7
1.4 min
4.8 min
2015
10
0.7 min
3.3 min
2016
5
0.2 min
1.4 min
2017
16
1.2 min
3.5 min
2018
6
0.4 min
3.4 min
2019
5
0.5 min
2.1 min
2020
4
0.9 min
1.6 min
2021
3
0.5 min
5.8 min
2022
7
2.1 min
6.5 min
2023
3
0.5 min
1.6 min
2024
4
9.8 min
18.7 min
2025
10
1.2 min
7.3 min
2026
8
11.5 min
23.3 min
Priority 1 Calls Waited 23 Minutes on Average in 2026That is the average across 8 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer calls. The year with the fewest had only 13, 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
22
9.5 min
19.3 min
2010
28
3.9 min
10.0 min
2011
23
7.2 min
14.2 min
2012
30
5.5 min
13.0 min
2013
20
11.0 min
19.3 min
2014
22
13.9 min
20.0 min
2015
16
6.1 min
15.4 min
2016
24
5.5 min
14.1 min
2017
18
8.4 min
16.8 min
2018
30
15.8 min
25.6 min
2019
21
9.5 min
16.9 min
2020
16
6.8 min
19.0 min
2021
13
13.7 min
26.1 min
2022
23
6.8 min
12.8 min
2023
27
13.5 min
31.8 min
2024
31
42.0 min
57.3 min
2025
26
21.0 min
36.6 min
2026
32
24.3 min
37.9 min
Priority 2 Calls Wait 38 Minutes for an Officer to ArriveAverage response time for Priority 2 calls has more than doubled since 2012, from 13 minutes in 2012 to 38 in 2026, 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
45.1 min
55.6 min
2010
4
10.0 min
22.5 min
2011
0
—
—
2012
5
101.5 min
134.1 min
2013
3
21.3 min
34.1 min
2014
2
16.4 min
74.0 min
2015
1
6.3 min
11.6 min
2016
2
50.6 min
77.0 min
2017
1
0.0 min
0.0 min
2018
0
—
—
2019
0
—
—
2020
2
19.7 min
0.5 min
2021
1
270.9 min
278.4 min
2022
1
3.9 min
68.3 min
2023
1
58.8 min
74.8 min
2024
2
432.2 min
624.2 min
2025
3
365.9 min
387.9 min
2026
0
—
—
Priority 3 Calls Waited 388 Minutes on Average in 2025That is the average across 3 called-in Priority 3 events in 2025. 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer events are called in. The year with the fewest had only 18, 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
49
14.3%
26.5%
44.9%
4.1%
8.2%
2.0%
—
2010
47
25.5%
25.5%
46.8%
2.1%
—
—
—
2011
35
8.6%
37.1%
45.7%
5.7%
2.9%
—
—
2012
48
16.7%
27.1%
43.8%
6.2%
4.2%
2.1%
—
2013
31
29.0%
22.6%
41.9%
—
6.5%
—
—
2014
33
18.2%
21.2%
48.5%
3.0%
9.1%
—
—
2015
27
14.8%
22.2%
59.2%
3.7%
—
—
—
2016
31
25.8%
19.4%
51.6%
—
3.2%
—
—
2017
35
22.9%
42.9%
25.7%
5.7%
2.9%
—
—
2018
37
27.0%
21.6%
40.5%
5.4%
2.7%
2.7%
—
2019
28
21.4%
25.0%
35.7%
17.9%
—
—
—
2020
22
22.7%
27.3%
36.4%
13.6%
—
—
—
2021
18
11.1%
5.6%
55.5%
16.7%
5.6%
5.6%
—
2022
33
42.4%
9.1%
42.4%
3.0%
3.0%
—
—
2023
31
22.6%
16.1%
48.4%
3.2%
6.5%
3.2%
—
2024
39
20.5%
15.4%
38.5%
10.3%
7.7%
2.6%
5.1%
2025
39
20.5%
5.1%
51.3%
7.7%
10.3%
2.6%
2.6%
2026
40
12.5%
12.5%
52.5%
15.0%
5.0%
2.5%
—
The Average Call Waits 22 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 22 minutes in 2026, more than double what it was in 2016. 8% of calls took more than an hour to get a response in 2026, compared with 3% in 2016.
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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer calls. The year with the fewest had only 3, 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
0–5 min
5–30 min
No recorded response
30–60 min
1–4 hr
2009
9
77.8%
22.2%
—
—
—
2010
13
38.5%
30.8%
30.8%
—
—
2011
11
90.9%
—
9.1%
—
—
2012
11
63.6%
9.1%
27.3%
—
—
2013
8
50.0%
12.5%
37.5%
—
—
2014
7
71.4%
28.6%
—
—
—
2015
10
60.0%
20.0%
20.0%
—
—
2016
5
80.0%
—
20.0%
—
—
2017
16
62.5%
6.2%
31.2%
—
—
2018
6
33.3%
16.7%
50.0%
—
—
2019
5
60.0%
—
40.0%
—
—
2020
4
75.0%
—
25.0%
—
—
2021
3
33.3%
33.3%
33.3%
—
—
2022
7
14.3%
28.6%
57.1%
—
—
2023
3
100.0%
—
—
—
—
2024
4
25.0%
25.0%
25.0%
25.0%
—
2025
10
20.0%
40.0%
40.0%
—
—
2026
8
12.5%
62.5%
—
12.5%
12.5%
12% of Priority 1 Calls Took Over an Hour in 2026That is 12% of 8 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer calls. The year with the fewest had only 13, 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
22
18.2%
18.2%
54.5%
4.5%
4.5%
—
—
2010
28
17.9%
21.4%
60.7%
—
—
—
—
2011
23
8.7%
13.0%
69.6%
4.3%
4.3%
—
—
2012
30
10.0%
20.0%
63.3%
6.7%
—
—
—
2013
20
30.0%
15.0%
50.0%
—
5.0%
—
—
2014
22
18.2%
9.1%
59.1%
4.5%
9.1%
—
—
2015
16
12.5%
—
81.2%
6.2%
—
—
—
2016
24
25.0%
8.3%
66.7%
—
—
—
—
2017
18
16.7%
22.2%
44.5%
11.1%
5.6%
—
—
2018
30
23.3%
20.0%
46.7%
6.7%
—
3.3%
—
2019
21
14.3%
19.1%
47.6%
19.1%
—
—
—
2020
16
18.8%
12.5%
50.0%
18.8%
—
—
—
2021
13
7.7%
—
69.2%
15.4%
7.7%
—
—
2022
23
43.5%
4.3%
47.8%
4.3%
—
—
—
2023
27
25.9%
7.4%
55.6%
3.7%
3.7%
3.7%
—
2024
31
19.4%
12.9%
45.2%
9.7%
6.5%
3.2%
3.2%
2025
26
15.4%
—
61.5%
11.5%
11.5%
—
—
2026
32
15.6%
12.5%
50.0%
15.6%
3.1%
3.1%
—
6% of Priority 2 Calls Wait Over an Hour for an Officer6% of Priority 2 calls took more than an hour to get a response in 2026, compared with 0% in 2012.
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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
4–8 hr
Over 8 hr
2009
13
7.7%
7.7%
53.8%
7.7%
15.4%
7.7%
—
2010
4
25.0%
25.0%
25.0%
25.0%
—
—
—
2011
0
—
—
—
—
—
—
—
2012
5
20.0%
—
20.0%
—
40.0%
20.0%
—
2013
3
—
—
66.7%
—
33.3%
—
—
2014
2
50.0%
—
—
—
50.0%
—
—
2015
1
—
—
100.0%
—
—
—
—
2016
2
50.0%
—
—
—
50.0%
—
—
2017
1
—
100.0%
—
—
—
—
—
2018
0
—
—
—
—
—
—
—
2019
0
—
—
—
—
—
—
—
2020
2
50.0%
50.0%
—
—
—
—
—
2021
1
—
—
—
—
—
100.0%
—
2022
1
—
—
—
—
100.0%
—
—
2023
1
—
—
—
—
100.0%
—
—
2024
2
—
50.0%
—
—
—
—
50.0%
2025
3
—
—
—
—
33.3%
33.3%
33.3%
2026
0
—
—
—
—
—
—
—
100% of Priority 3 Calls Took Over an Hour in 2025That is 100% of 3 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 70 events in this period. 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.
Assist the Officer: 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 (49% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
assist the officer calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Assist the officer calls logged in CAD
Sep 2025
4
Oct 2025
5
Nov 2025
7
Dec 2025
3
Jan 2026
7
Feb 2026
8
Mar 2026
3
Apr 2026
6
May 2026
6
Jun 2026
5
Jul 2026
9
Aug 2026
7
Assist the Officer Calls Totaled 70 Over the Last 12 MonthsSeattle Police logged 9 assist the officer calls in the busiest month (Jul 2026) and 3 in the quietest (Dec 2025). Counts this small can swing from one month to the next.
Assist the Officer: 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
Other (unfounded / cancelled)
Resolved on scene
Unable to locate
Sep 2025
4
25.0%
75.0%
—
—
Oct 2025
5
—
—
80.0%
20.0%
Nov 2025
7
14.3%
28.6%
14.3%
42.9%
Dec 2025
3
—
33.3%
33.3%
33.3%
Jan 2026
7
—
42.9%
28.6%
28.6%
Feb 2026
8
12.5%
75.0%
12.5%
—
Mar 2026
3
—
—
100.0%
—
Apr 2026
6
—
33.3%
50.0%
16.7%
May 2026
6
—
16.7%
33.3%
50.0%
Jun 2026
5
—
60.0%
40.0%
—
Jul 2026
9
—
22.2%
66.7%
11.1%
Aug 2026
7
—
28.6%
57.1%
14.3%
“Unable to Locate” Ended 19% of Assist the Officer Calls Over the Last 12 MonthsReport-taken outcomes were 4% of calls over the period.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
3
0.8 min
7.2 min
Oct 2025
1
0.5 min
9.3 min
Nov 2025
3
125.6 min
135.9 min
Dec 2025
3
26.0 min
45.5 min
Jan 2026
5
13.0 min
23.5 min
Feb 2026
6
40.3 min
57.0 min
Mar 2026
1
1.8 min
7.5 min
Apr 2026
5
9.8 min
23.5 min
May 2026
6
77.9 min
77.2 min
Jun 2026
5
8.8 min
39.7 min
Jul 2026
6
6.6 min
15.5 min
Aug 2026
5
3.0 min
7.7 min
65% of Called-In Assist the Officer Calls Got a Response Within 30 Minutes10% 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
3
0.8 min
7.2 min
Oct 2025
0
—
—
Nov 2025
0
—
—
Dec 2025
1
0.9 min
—
Jan 2026
0
—
—
Feb 2026
3
29.1 min
42.3 min
Mar 2026
0
—
—
Apr 2026
2
1.3 min
15.0 min
May 2026
1
0.9 min
19.0 min
Jun 2026
0
—
—
Jul 2026
1
0.6 min
1.7 min
Aug 2026
1
1.1 min
9.3 min
75% of Called-In Priority 1 Calls Got a Response Within 30 Minutes17% 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
1
0.5 min
9.3 min
Nov 2025
2
4.4 min
12.4 min
Dec 2025
2
38.6 min
45.5 min
Jan 2026
5
13.0 min
23.5 min
Feb 2026
3
51.5 min
79.0 min
Mar 2026
1
1.8 min
7.5 min
Apr 2026
3
15.6 min
29.1 min
May 2026
5
97.2 min
88.8 min
Jun 2026
5
8.8 min
39.7 min
Jul 2026
5
7.8 min
18.2 min
Aug 2026
4
3.5 min
7.2 min
64% of Called-In Priority 2 Calls Got a Response Within 30 Minutes8% 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
1
367.9 min
382.9 min
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
—
—
Priority 3 Calls Averaged 383 Minutes to Get an Officer Over the Last 12 MonthsBased on 1 called-in Priority 3 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
0–5 min
5–30 min
4–8 hr
No recorded response
1–4 hr
30–60 min
Sep 2025
3
33.3%
66.7%
—
—
—
—
Oct 2025
1
—
100.0%
—
—
—
—
Nov 2025
3
—
66.7%
33.3%
—
—
—
Dec 2025
3
—
33.3%
—
33.3%
33.3%
—
Jan 2026
5
—
60.0%
—
20.0%
—
20.0%
Feb 2026
6
—
33.3%
—
16.7%
33.3%
16.7%
Mar 2026
1
—
100.0%
—
—
—
—
Apr 2026
5
20.0%
60.0%
—
—
—
20.0%
May 2026
6
—
83.3%
16.7%
—
—
—
Jun 2026
5
—
20.0%
—
40.0%
—
40.0%
Jul 2026
6
33.3%
50.0%
—
—
—
16.7%
Aug 2026
5
20.0%
60.0%
—
20.0%
—
—
10% of Called-In Calls Took Over an Hour to Get a ResponseThat is 10% of 49 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
0–5 min
5–30 min
No recorded response
30–60 min
1–4 hr
Sep 2025
3
33.3%
66.7%
—
—
—
Oct 2025
0
—
—
—
—
—
Nov 2025
0
—
—
—
—
—
Dec 2025
1
—
—
100.0%
—
—
Jan 2026
0
—
—
—
—
—
Feb 2026
3
—
33.3%
—
33.3%
33.3%
Mar 2026
0
—
—
—
—
—
Apr 2026
2
—
100.0%
—
—
—
May 2026
1
—
100.0%
—
—
—
Jun 2026
0
—
—
—
—
—
Jul 2026
1
100.0%
—
—
—
—
Aug 2026
1
—
100.0%
—
—
—
8% of Called-In Priority 1 Calls Took Over an Hour to Get a ResponseThat is 8% of 12 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
1–4 hr
No recorded response
30–60 min
0–5 min
4–8 hr
Sep 2025
0
—
—
—
—
—
—
Oct 2025
1
100.0%
—
—
—
—
—
Nov 2025
2
100.0%
—
—
—
—
—
Dec 2025
2
50.0%
50.0%
—
—
—
—
Jan 2026
5
60.0%
—
20.0%
20.0%
—
—
Feb 2026
3
33.3%
33.3%
33.3%
—
—
—
Mar 2026
1
100.0%
—
—
—
—
—
Apr 2026
3
33.3%
—
—
33.3%
33.3%
—
May 2026
5
80.0%
—
—
—
—
20.0%
Jun 2026
5
20.0%
—
40.0%
40.0%
—
—
Jul 2026
5
60.0%
—
—
20.0%
20.0%
—
Aug 2026
4
50.0%
—
25.0%
—
25.0%
—
8% of Called-In Priority 2 Calls Took Over an Hour to Get a ResponseThat is 8% of 36 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
4–8 hr
Sep 2025
0
—
Oct 2025
0
—
Nov 2025
1
100.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
—
100% of Priority 3 Calls Took Over an Hour Over the Last 12 MonthsThat is 100% 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.
Small sample: this category had 19 events in this period, with no dispatches in 5 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.
Assist the Officer: 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 (49% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
assist the officer calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Assist the officer calls logged in CAD
Week of Jun 15
—
Week of Jun 22
2
Week of Jun 29
3
Week of Jul 6
4
Week of Jul 13
2
Week of Jul 20
—
Week of Jul 27
3
Week of Aug 3
2
Week of Aug 10
3
Week of Aug 17
—
Week of Aug 24
—
Week of Aug 31
—
Assist the Officer Calls Totaled 19 Over the Last 12 WeeksSeattle Police logged 4 assist the officer calls in the busiest week (Week of Jul 6); 5 of the 12 weeks had none. Counts this small can swing from one week to the next.
Assist the Officer: 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
Resolved on scene
Other (unfounded / cancelled)
Unable to locate
Week of Jun 22
0
50.0%
50.0%
—
Week of Jun 29
0
66.7%
33.3%
—
Week of Jul 6
0
75.0%
25.0%
—
Week of Jul 13
0
50.0%
—
50.0%
Week of Jul 27
0
33.3%
66.7%
—
Week of Aug 3
0
100.0%
—
—
Week of Aug 10
0
33.3%
33.3%
33.3%
“Unable to Locate” Ended 11% of Assist the Officer Calls Over the Last 12 WeeksReport-taken outcomes were 0% of calls over the period.
Assist the Officer: 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 49% of assist the officer 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 assist the officer events are called in. The week with the fewest had only 2, 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
2
15.3 min
52.2 min
Week of Jun 29
3
6.7 min
13.1 min
Week of Jul 6
2
1.1 min
16.9 min
Week of Jul 13
2
9.9 min
13.6 min
Week of Jul 20
0
—
—
Week of Jul 27
2
5.6 min
9.1 min
Week of Aug 3
0
—
—
Week of Aug 10
3
1.3 min
7.2 min
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Called-In Events Averaged 17 Minutes to Get an Officer Over the Last 12 WeeksBased on 14 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
0.6 min
1.7 min
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
1
1.1 min
9.3 min
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Priority 1 Calls Averaged 5.5 Minutes to Get an Officer Over the Last 12 WeeksBased on 2 called-in Priority 1 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
2
15.3 min
52.2 min
Week of Jun 29
3
6.7 min
13.1 min
Week of Jul 6
1
1.6 min
32.2 min
Week of Jul 13
2
9.9 min
13.6 min
Week of Jul 20
0
—
—
Week of Jul 27
2
5.6 min
9.1 min
Week of Aug 3
0
—
—
Week of Aug 10
2
1.4 min
6.2 min
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
67% of Called-In Priority 2 Calls Got a Response Within 30 Minutes17% were answered in under 5 minutes over the last 12 weeks.
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.
Assist the Officer: 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 49% of assist the officer 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 3 Calls Over the Last 12 WeeksThere were no called-in Priority 3 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer events are called in. The week with the fewest had only 2, 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
30–60 min
5–30 min
0–5 min
Week of Jun 15
0
—
—
—
—
Week of Jun 22
2
50.0%
50.0%
—
—
Week of Jun 29
3
—
—
100.0%
—
Week of Jul 6
2
—
50.0%
—
50.0%
Week of Jul 13
2
—
—
50.0%
50.0%
Week of Jul 20
0
—
—
—
—
Week of Jul 27
2
50.0%
—
50.0%
—
Week of Aug 3
0
—
—
—
—
Week of Aug 10
3
—
—
66.7%
33.3%
Week of Aug 17
0
—
—
—
—
Week of Aug 24
0
—
—
—
—
Week of Aug 31
0
—
—
—
—
0% of Called-In Events Took Over an Hour Over the Last 12 WeeksThat is 0% of 14 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
0–5 min
5–30 min
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
0
—
—
Week of Jul 20
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
—
—
0% of Priority 1 Calls Took Over an Hour Over the Last 12 WeeksThat is 0% of 2 called-in Priority 1 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.
Assist the Officer: 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 49% of assist the officer 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 assist the officer 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
30–60 min
5–30 min
0–5 min
Week of Jun 15
0
—
—
—
—
Week of Jun 22
2
50.0%
50.0%
—
—
Week of Jun 29
3
—
—
100.0%
—
Week of Jul 6
1
—
100.0%
—
—
Week of Jul 13
2
—
—
50.0%
50.0%
Week of Jul 20
0
—
—
—
—
Week of Jul 27
2
50.0%
—
50.0%
—
Week of Aug 3
0
—
—
—
—
Week of Aug 10
2
—
—
50.0%
50.0%
Week of Aug 17
0
—
—
—
—
Week of Aug 24
0
—
—
—
—
Week of Aug 31
0
—
—
—
—
No Called-In Priority 2 Calls Took Over an Hour to Get a ResponseNone of the 12 called-in events over the last 12 weeks took more than an hour.
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.
Assist the Officer: 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 49% of assist the officer 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 3 Calls Over the Last 12 WeeksThere were no called-in Priority 3 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.
“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.