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.
Homicide calls over time: volume, outcomes, and response speed
Homicide: 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 (52% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
homicide calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Homicide calls logged in CAD
2009
89
2010
87
2011
45
2012
82
2013
85
2014
109
2015
80
2016
71
2017
69
2018
68
2019
71
2020
113
2021
63
2022
81
2023
106
2024
99
2025
67
2026
68
Homicide Calls Are Down 41% From Their 2020 PeakSeattle Police logged 113 homicide calls in 2020 and 67 in 2025, the most recent full year.
Homicide: 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
89
3.4%
66.3%
25.8%
2.2%
2.2%
2010
87
8.0%
59.8%
27.6%
2.3%
2.2%
2011
45
6.7%
64.4%
24.4%
4.4%
—
2012
82
7.3%
63.4%
28.0%
—
1.2%
2013
85
4.7%
69.4%
21.2%
4.7%
—
2014
109
2.8%
79.8%
14.7%
2.8%
—
2015
80
7.5%
73.8%
17.5%
1.2%
—
2016
71
9.9%
76.1%
11.3%
1.4%
1.4%
2017
69
8.7%
78.3%
10.1%
—
2.8%
2018
68
8.8%
80.9%
7.4%
2.9%
—
2019
71
15.5%
66.2%
15.5%
2.8%
—
2020
113
15.0%
73.5%
11.5%
—
—
2021
63
4.8%
76.2%
12.7%
3.2%
3.2%
2022
81
12.3%
85.2%
2.5%
—
—
2023
106
13.2%
79.2%
4.7%
2.8%
—
2024
99
12.1%
77.8%
10.1%
—
—
2025
67
13.4%
77.6%
9.0%
—
—
2026
68
10.3%
70.6%
19.1%
—
—
“Unable to Locate” Outcomes Are Holding Near 0% of Homicide CallsReport-taken outcomes moved from 76% of calls in 2016 to 71% in 2026. “Unable to locate” means officers could not find the incident or the person who called.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Only a small share of homicide events are called in. The year with the fewest had only 19, 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
20
10.4 min
19.7 min
2010
20
11.2 min
16.8 min
2011
19
4.4 min
8.3 min
2012
31
4.4 min
8.0 min
2013
27
2.3 min
8.2 min
2014
44
20.8 min
26.6 min
2015
46
11.0 min
22.2 min
2016
36
7.0 min
11.7 min
2017
37
6.5 min
11.6 min
2018
41
6.5 min
16.3 min
2019
40
12.1 min
19.7 min
2020
58
11.8 min
20.7 min
2021
30
1.9 min
6.0 min
2022
50
17.4 min
22.4 min
2023
61
3.8 min
9.2 min
2024
56
27.2 min
21.3 min
2025
41
14.2 min
20.7 min
2026
36
61.7 min
60.7 min
The Average Call Waits 61 Minutes for an Officer to ArriveDespite a 6% drop in calls between 2016 and 2025, average response time has grown about 5-fold in the past 10 years, from 12 minutes in 2016 to 61 in 2026, driven largely by dispatch delays. This counts only the 48% of homicide calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 1 calls are a small share of homicide calls. The year with the fewest had only 12, 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
12
0.7 min
3.7 min
2010
12
0.6 min
2.5 min
2011
12
1.8 min
5.1 min
2012
15
0.6 min
3.4 min
2013
18
-0.1 min
5.9 min
2014
27
3.4 min
7.4 min
2015
30
2.1 min
5.5 min
2016
22
1.9 min
8.3 min
2017
29
0.9 min
4.4 min
2018
31
1.6 min
5.4 min
2019
28
-0.3 min
6.8 min
2020
40
9.8 min
16.2 min
2021
28
0.6 min
4.4 min
2022
43
1.1 min
5.2 min
2023
54
3.2 min
7.7 min
2024
39
1.0 min
5.0 min
2025
22
0.8 min
6.2 min
2026
16
24.1 min
28.8 min
Priority 1 Calls Get an Officer in 5.0 MinutesAverage response time for Priority 1 calls has decreased 9% since 2015, from 5.5 minutes in 2015 to 5.0 in 2024.
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.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 2 calls are a small share of homicide 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
3
3.2 min
16.0 min
2010
4
1.0 min
16.2 min
2011
1
4.2 min
8.4 min
2012
7
1.9 min
5.9 min
2013
4
8.7 min
12.8 min
2014
4
20.7 min
45.6 min
2015
2
2.4 min
11.9 min
2016
5
7.5 min
16.2 min
2017
2
32.9 min
36.5 min
2018
4
19.5 min
23.5 min
2019
2
62.6 min
105.4 min
2020
6
8.1 min
33.1 min
2021
1
6.3 min
18.8 min
2022
4
44.4 min
54.2 min
2023
2
2.5 min
12.0 min
2024
9
58.8 min
79.8 min
2025
9
26.9 min
38.2 min
2026
7
21.5 min
34.0 min
Priority 2 Calls Waited 34 Minutes on Average in 2026That is the average across 7 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.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 3 calls are a small share of homicide 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
5
37.8 min
60.4 min
2010
4
53.0 min
75.0 min
2011
5
10.6 min
17.9 min
2012
8
14.1 min
20.6 min
2013
4
7.5 min
14.8 min
2014
12
56.4 min
64.2 min
2015
14
31.3 min
59.3 min
2016
7
24.8 min
27.2 min
2017
5
29.1 min
43.2 min
2018
4
30.0 min
90.3 min
2019
9
36.6 min
40.8 min
2020
10
24.4 min
41.3 min
2021
1
34.1 min
34.1 min
2022
3
214.7 min
227.5 min
2023
5
10.5 min
24.4 min
2024
6
149.2 min
44.0 min
2025
6
42.1 min
52.1 min
2026
11
109.0 min
97.1 min
Priority 3 Calls Waited 97 Minutes on Average in 2026That is the average across 11 called-in Priority 3 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.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide events are called in. The year with the fewest had only 19, 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
1–4 hr
No recorded response
30–60 min
4–8 hr
Over 8 hr
2009
20
55.0%
35.0%
10.0%
—
—
—
—
2010
20
70.0%
10.0%
10.0%
5.0%
5.0%
—
—
2011
19
47.4%
36.9%
—
10.5%
5.3%
—
—
2012
31
61.3%
29.0%
3.2%
3.2%
3.2%
—
—
2013
27
48.1%
51.9%
—
—
—
—
—
2014
44
45.5%
29.6%
6.8%
4.5%
11.4%
2.3%
—
2015
46
41.3%
41.3%
15.2%
—
2.2%
—
—
2016
36
38.9%
38.9%
2.8%
11.1%
8.3%
—
—
2017
37
70.3%
21.6%
5.4%
—
2.7%
—
—
2018
41
53.7%
31.7%
4.9%
2.4%
7.3%
—
—
2019
40
47.5%
32.5%
10.0%
2.5%
7.5%
—
—
2020
58
46.5%
34.5%
8.6%
5.2%
5.2%
—
—
2021
30
63.3%
30.0%
—
3.3%
3.3%
—
—
2022
50
62.0%
30.0%
6.0%
—
—
—
2.0%
2023
61
47.5%
45.9%
3.3%
—
3.3%
—
—
2024
56
46.4%
39.3%
5.4%
3.6%
3.6%
—
1.8%
2025
41
48.8%
31.7%
9.8%
—
9.8%
—
—
2026
36
30.6%
36.1%
8.3%
5.6%
11.1%
5.6%
2.8%
The Average Call Waits 62 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 62 minutes in 2026, more than double what it was in 2016. 17% of calls took more than an hour to get a response in 2026, compared with 3% in 2016. This counts only the 48% of homicide calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide calls. The year with the fewest had only 12, 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
30–60 min
No recorded response
1–4 hr
4–8 hr
2009
12
83.3%
16.7%
—
—
—
—
2010
12
100.0%
—
—
—
—
—
2011
12
66.7%
33.3%
—
—
—
—
2012
15
80.0%
20.0%
—
—
—
—
2013
18
61.1%
38.9%
—
—
—
—
2014
27
70.4%
18.5%
11.1%
—
—
—
2015
30
63.3%
33.3%
3.3%
—
—
—
2016
22
54.5%
27.3%
13.6%
4.5%
—
—
2017
29
79.3%
20.7%
—
—
—
—
2018
31
64.5%
32.3%
3.2%
—
—
—
2019
28
53.6%
42.9%
3.6%
—
—
—
2020
40
55.0%
35.0%
5.0%
—
5.0%
—
2021
28
67.9%
28.6%
—
3.6%
—
—
2022
43
67.4%
32.6%
—
—
—
—
2023
54
53.7%
42.6%
—
—
3.7%
—
2024
39
59.0%
41.0%
—
—
—
—
2025
22
68.2%
27.3%
4.5%
—
—
—
2026
16
68.8%
25.0%
—
—
—
6.2%
Almost No Priority 1 Calls Wait Over an Hour for an OfficerFewer than 1 in 100 Priority 1 calls took more than an hour to get a response in both 2015 and 2024.
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.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide 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
30–60 min
No recorded response
1–4 hr
Over 8 hr
2009
3
100.0%
—
—
—
—
—
2010
4
25.0%
50.0%
25.0%
—
—
—
2011
1
100.0%
—
—
—
—
—
2012
7
42.9%
57.1%
—
—
—
—
2013
4
100.0%
—
—
—
—
—
2014
4
50.0%
—
—
25.0%
25.0%
—
2015
2
100.0%
—
—
—
—
—
2016
5
80.0%
—
—
20.0%
—
—
2017
2
—
50.0%
—
—
50.0%
—
2018
4
25.0%
25.0%
50.0%
—
—
—
2019
2
—
—
—
—
100.0%
—
2020
6
66.7%
16.7%
—
—
16.7%
—
2021
1
100.0%
—
—
—
—
—
2022
4
25.0%
25.0%
—
—
50.0%
—
2023
2
100.0%
—
—
—
—
—
2024
9
55.5%
11.1%
11.1%
—
11.1%
11.1%
2025
9
44.4%
33.3%
—
—
22.2%
—
2026
7
85.7%
—
—
—
14.3%
—
14% of Priority 2 Calls Took Over an Hour in 2026That is 14% of 7 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.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide 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
0–5 min
5–30 min
1–4 hr
No recorded response
30–60 min
4–8 hr
Over 8 hr
2009
5
20.0%
40.0%
40.0%
—
—
—
—
2010
4
—
25.0%
50.0%
25.0%
—
—
—
2011
5
20.0%
40.0%
—
20.0%
20.0%
—
—
2012
8
25.0%
37.5%
12.5%
12.5%
12.5%
—
—
2013
4
25.0%
75.0%
—
—
—
—
—
2014
12
8.3%
50.0%
8.3%
8.3%
16.7%
8.3%
—
2015
14
—
50.0%
50.0%
—
—
—
—
2016
7
—
57.1%
14.3%
28.6%
—
—
—
2017
5
40.0%
20.0%
20.0%
—
20.0%
—
—
2018
4
25.0%
25.0%
50.0%
—
—
—
—
2019
9
44.4%
11.1%
22.2%
—
22.2%
—
—
2020
10
30.0%
10.0%
20.0%
30.0%
10.0%
—
—
2021
1
—
—
—
—
100.0%
—
—
2022
3
33.3%
—
33.3%
—
—
—
33.3%
2023
5
—
60.0%
—
—
40.0%
—
—
2024
6
33.3%
—
33.3%
33.3%
—
—
—
2025
6
16.7%
16.7%
33.3%
—
33.3%
—
—
2026
11
—
18.2%
18.2%
18.2%
36.4%
9.1%
—
27% of Priority 3 Calls Took Over an Hour in 2026That is 27% of 11 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 78 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.
Homicide: 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 (52% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
homicide calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Homicide calls logged in CAD
Sep 2025
5
Oct 2025
7
Nov 2025
5
Dec 2025
7
Jan 2026
4
Feb 2026
7
Mar 2026
7
Apr 2026
4
May 2026
11
Jun 2026
2
Jul 2026
13
Aug 2026
6
Homicide Calls Totaled 78 Over the Last 12 MonthsSeattle Police logged 13 homicide calls in the busiest month (Jul 2026) and 2 in the quietest (Jun 2026). Counts this small can swing from one month to the next.
Homicide: 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
Arrest / citation
Resolved on scene
Sep 2025
5
100.0%
—
—
Oct 2025
7
57.1%
28.6%
14.3%
Nov 2025
5
80.0%
20.0%
—
Dec 2025
7
71.4%
14.3%
14.3%
Jan 2026
4
50.0%
—
50.0%
Feb 2026
7
42.9%
28.6%
28.6%
Mar 2026
7
71.4%
14.3%
14.3%
Apr 2026
4
50.0%
—
50.0%
May 2026
11
90.9%
—
9.1%
Jun 2026
2
—
—
100.0%
Jul 2026
13
76.9%
15.4%
7.7%
Aug 2026
6
83.3%
16.7%
—
“Unable to Locate” Ended 0% of Homicide Calls Over the Last 12 MonthsReport-taken outcomes were 71% of calls over the period.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Only a small share of homicide 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
14.4 min
15.4 min
Oct 2025
4
1.0 min
9.7 min
Nov 2025
3
0.6 min
18.7 min
Dec 2025
3
2.8 min
9.5 min
Jan 2026
3
7.6 min
9.9 min
Feb 2026
3
15.1 min
15.8 min
Mar 2026
4
34.6 min
45.9 min
Apr 2026
1
6.0 min
22.3 min
May 2026
7
99.1 min
104.6 min
Jun 2026
2
1.7 min
7.2 min
Jul 2026
4
112.8 min
145.8 min
Aug 2026
6
25.9 min
32.0 min
74% of Called-In Homicide Calls Got a Response Within 30 Minutes40% were answered in under 5 minutes over the last 12 months. This counts only the 48% of homicide calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 1 calls are a small share of homicide 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
0.8 min
2.2 min
Oct 2025
3
1.0 min
4.7 min
Nov 2025
3
0.6 min
18.7 min
Dec 2025
1
0.7 min
3.4 min
Jan 2026
2
0.6 min
4.1 min
Feb 2026
2
0.6 min
1.6 min
Mar 2026
2
0.3 min
7.0 min
Apr 2026
0
—
—
May 2026
3
1.0 min
10.8 min
Jun 2026
0
—
—
Jul 2026
2
187.6 min
192.4 min
Aug 2026
3
0.9 min
4.0 min
91% of Called-In Priority 1 Calls Got a Response Within 30 Minutes70% 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.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 2 calls are a small share of homicide 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
1.0 min
24.7 min
Nov 2025
0
—
—
Dec 2025
1
7.2 min
24.6 min
Jan 2026
0
—
—
Feb 2026
0
—
—
Mar 2026
2
69.0 min
84.8 min
Apr 2026
1
6.0 min
22.3 min
May 2026
1
1.4 min
10.3 min
Jun 2026
1
3.4 min
7.4 min
Jul 2026
0
—
—
Aug 2026
2
0.8 min
14.3 min
Priority 2 Calls Averaged 32 Minutes to Get an Officer Over the Last 12 MonthsBased on 9 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.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 3 calls are a small share of homicide 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
1
0.4 min
0.4 min
Jan 2026
1
21.5 min
21.5 min
Feb 2026
1
44.1 min
44.1 min
Mar 2026
0
—
—
Apr 2026
0
—
—
May 2026
2
102.0 min
102.1 min
Jun 2026
0
—
—
Jul 2026
2
37.9 min
52.5 min
Aug 2026
1
151.3 min
151.3 min
Priority 3 Calls Averaged 66 Minutes to Get an Officer Over the Last 12 MonthsBased on 8 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.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide 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
30–60 min
5–30 min
1–4 hr
Over 8 hr
No recorded response
4–8 hr
Sep 2025
3
66.7%
33.3%
—
—
—
—
—
Oct 2025
4
50.0%
—
50.0%
—
—
—
—
Nov 2025
3
66.7%
33.3%
—
—
—
—
—
Dec 2025
3
66.7%
—
33.3%
—
—
—
—
Jan 2026
3
66.7%
—
33.3%
—
—
—
—
Feb 2026
3
66.7%
33.3%
—
—
—
—
—
Mar 2026
4
25.0%
—
50.0%
25.0%
—
—
—
Apr 2026
1
—
—
100.0%
—
—
—
—
May 2026
7
14.3%
14.3%
42.9%
14.3%
14.3%
—
—
Jun 2026
2
—
—
100.0%
—
—
—
—
Jul 2026
4
—
25.0%
25.0%
—
—
25.0%
25.0%
Aug 2026
6
50.0%
—
33.3%
16.7%
—
—
—
12% of Called-In Calls Took Over an Hour to Get a ResponseThat is 12% of 43 called-in events over the last 12 months. This counts only the 48% of homicide calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide 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
30–60 min
4–8 hr
Sep 2025
2
100.0%
—
—
—
Oct 2025
3
66.7%
33.3%
—
—
Nov 2025
3
66.7%
—
33.3%
—
Dec 2025
1
100.0%
—
—
—
Jan 2026
2
100.0%
—
—
—
Feb 2026
2
100.0%
—
—
—
Mar 2026
2
50.0%
50.0%
—
—
Apr 2026
0
—
—
—
—
May 2026
3
33.3%
66.7%
—
—
Jun 2026
0
—
—
—
—
Jul 2026
2
—
50.0%
—
50.0%
Aug 2026
3
100.0%
—
—
—
4% of Called-In Priority 1 Calls Took Over an Hour to Get a ResponseThat is 4% 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.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide 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
Sep 2025
0
—
—
Oct 2025
1
100.0%
—
Nov 2025
0
—
—
Dec 2025
1
100.0%
—
Jan 2026
0
—
—
Feb 2026
0
—
—
Mar 2026
2
50.0%
50.0%
Apr 2026
1
100.0%
—
May 2026
1
100.0%
—
Jun 2026
1
100.0%
—
Jul 2026
0
—
—
Aug 2026
2
100.0%
—
11% of Priority 2 Calls Took Over an Hour Over the Last 12 MonthsThat is 11% of 9 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.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide 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
30–60 min
1–4 hr
No recorded response
Sep 2025
0
—
—
—
—
—
Oct 2025
0
—
—
—
—
—
Nov 2025
0
—
—
—
—
—
Dec 2025
1
100.0%
—
—
—
—
Jan 2026
1
—
100.0%
—
—
—
Feb 2026
1
—
—
100.0%
—
—
Mar 2026
0
—
—
—
—
—
Apr 2026
0
—
—
—
—
—
May 2026
2
—
—
50.0%
50.0%
—
Jun 2026
0
—
—
—
—
—
Jul 2026
2
—
—
50.0%
—
50.0%
Aug 2026
1
—
—
—
100.0%
—
25% of Priority 3 Calls Took Over an Hour Over the Last 12 MonthsThat is 25% of 8 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 23 events in this period, with no dispatches in 4 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.
Homicide: 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 (52% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
homicide calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Homicide calls logged in CAD
Week of Jun 15
—
Week of Jun 22
—
Week of Jun 29
1
Week of Jul 6
—
Week of Jul 13
1
Week of Jul 20
3
Week of Jul 27
8
Week of Aug 3
1
Week of Aug 10
2
Week of Aug 17
3
Week of Aug 24
—
Week of Aug 31
4
Homicide Calls Totaled 23 Over the Last 12 WeeksSeattle Police logged 8 homicide calls in the busiest week (Week of Jul 27); 4 of the 12 weeks had none. Counts this small can swing from one week to the next.
Homicide: 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
Arrest / citation
Resolved on scene
Week of Jun 29
0
100.0%
—
—
Week of Jul 13
0
—
100.0%
—
Week of Jul 20
0
33.3%
33.3%
33.3%
Week of Jul 27
0
100.0%
—
—
Week of Aug 3
0
100.0%
—
—
Week of Aug 10
0
100.0%
—
—
Week of Aug 17
0
66.7%
33.3%
—
Week of Aug 31
0
100.0%
—
—
“Unable to Locate” Ended 0% of Homicide Calls Over the Last 12 WeeksReport-taken outcomes were 83% of calls over the period.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Only a small share of homicide 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
1.0 min
10.6 min
Week of Jul 6
0
—
—
Week of Jul 13
0
—
—
Week of Jul 20
1
374.3 min
374.3 min
Week of Jul 27
2
37.9 min
52.5 min
Week of Aug 3
1
0.9 min
16.8 min
Week of Aug 10
2
0.7 min
4.1 min
Week of Aug 17
3
51.1 min
55.6 min
Week of Aug 24
0
—
—
Week of Aug 31
2
18.1 min
19.2 min
Called-In Events Averaged 60 Minutes to Get an Officer Over the Last 12 WeeksBased on 12 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.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 1 calls are a small share of homicide 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
1.0 min
10.6 min
Week of Jul 6
0
—
—
Week of Jul 13
0
—
—
Week of Jul 20
1
374.3 min
374.3 min
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
2
0.7 min
4.1 min
Week of Aug 17
1
1.2 min
3.8 min
Week of Aug 24
0
—
—
Week of Aug 31
1
1.2 min
2.7 min
Priority 1 Calls Averaged 67 Minutes to Get an Officer Over the Last 12 WeeksBased on 6 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.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 2 calls are a small share of homicide 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
0
—
—
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
1
0.9 min
16.8 min
Week of Aug 10
0
—
—
Week of Aug 17
1
0.7 min
11.8 min
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Priority 2 Calls Averaged 14 Minutes to Get an Officer Over the Last 12 WeeksBased on 2 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.
Homicide: 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 52% of homicide events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 3 calls are a small share of homicide 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
0
—
—
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
2
37.9 min
52.5 min
Week of Aug 3
0
—
—
Week of Aug 10
0
—
—
Week of Aug 17
1
151.3 min
151.3 min
Week of Aug 24
0
—
—
Week of Aug 31
1
34.9 min
35.8 min
Priority 3 Calls Averaged 73 Minutes to Get an Officer Over the Last 12 WeeksBased on 4 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.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide 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
5–30 min
4–8 hr
No recorded response
30–60 min
0–5 min
1–4 hr
Week of Jun 15
0
—
—
—
—
—
—
Week of Jun 22
0
—
—
—
—
—
—
Week of Jun 29
1
100.0%
—
—
—
—
—
Week of Jul 6
0
—
—
—
—
—
—
Week of Jul 13
0
—
—
—
—
—
—
Week of Jul 20
1
—
100.0%
—
—
—
—
Week of Jul 27
2
—
—
50.0%
50.0%
—
—
Week of Aug 3
1
100.0%
—
—
—
—
—
Week of Aug 10
2
—
—
—
—
100.0%
—
Week of Aug 17
3
33.3%
—
—
—
33.3%
33.3%
Week of Aug 24
0
—
—
—
—
—
—
Week of Aug 31
2
—
—
—
50.0%
50.0%
—
17% of Called-In Events Took Over an Hour Over the Last 12 WeeksThat is 17% of 12 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.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide 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
5–30 min
4–8 hr
0–5 min
Week of Jun 15
0
—
—
—
Week of Jun 22
0
—
—
—
Week of Jun 29
1
100.0%
—
—
Week of Jul 6
0
—
—
—
Week of Jul 13
0
—
—
—
Week of Jul 20
1
—
100.0%
—
Week of Jul 27
0
—
—
—
Week of Aug 3
0
—
—
—
Week of Aug 10
2
—
—
100.0%
Week of Aug 17
1
—
—
100.0%
Week of Aug 24
0
—
—
—
Week of Aug 31
1
—
—
100.0%
17% of Priority 1 Calls Took Over an Hour Over the Last 12 WeeksThat is 17% of 6 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.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide 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
5–30 min
Week of Jun 15
0
—
Week of Jun 22
0
—
Week of Jun 29
0
—
Week of Jul 6
0
—
Week of Jul 13
0
—
Week of Jul 20
0
—
Week of Jul 27
0
—
Week of Aug 3
1
100.0%
Week of Aug 10
0
—
Week of Aug 17
1
100.0%
Week of Aug 24
0
—
Week of Aug 31
0
—
0% of Priority 2 Calls Took Over an Hour Over the Last 12 WeeksThat is 0% 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.
Homicide: 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 52% of homicide events, because they have no wait. Because most homicide events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
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 homicide 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
1–4 hr
Week of Jun 15
0
—
—
—
Week of Jun 22
0
—
—
—
Week of Jun 29
0
—
—
—
Week of Jul 6
0
—
—
—
Week of Jul 13
0
—
—
—
Week of Jul 20
0
—
—
—
Week of Jul 27
2
50.0%
50.0%
—
Week of Aug 3
0
—
—
—
Week of Aug 10
0
—
—
—
Week of Aug 17
1
—
—
100.0%
Week of Aug 24
0
—
—
—
Week of Aug 31
1
—
100.0%
—
25% of Priority 3 Calls Took Over an Hour Over the Last 12 WeeksThat is 25% of 4 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.