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.
Bias calls over time: volume, outcomes, and response speed
Bias: 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 (19% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
bias calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Bias calls logged in CAD
2009
11
2010
5
2013
2
2014
9
2015
5
2016
6
2017
10
2018
16
2019
9
2020
8
2021
16
2022
14
2023
11
2024
15
2025
26
2026
13
Calls for Bias Average About 11 a YearSeattle Police logged 176 bias calls between 2009 and 2026, with a high of 26 in 2025.
Bias: 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
Other (unfounded / cancelled)
Unable to locate
2009
11
9.1%
63.6%
18.2%
9.1%
—
2010
5
—
40.0%
—
40.0%
20.0%
2013
2
—
100.0%
—
—
—
2014
9
—
55.6%
11.1%
33.3%
—
2015
5
—
20.0%
—
80.0%
—
2016
6
—
33.3%
—
50.0%
16.7%
2017
10
—
70.0%
—
30.0%
—
2018
16
—
87.5%
6.2%
6.2%
—
2019
9
—
44.4%
—
44.4%
11.1%
2020
8
25.0%
25.0%
—
37.5%
12.5%
2021
16
—
56.2%
—
43.8%
—
2022
14
14.3%
64.3%
—
14.3%
7.1%
2023
11
—
63.6%
—
27.3%
9.1%
2024
15
—
73.3%
6.7%
13.3%
6.7%
2025
26
—
53.8%
11.5%
19.2%
15.4%
2026
13
—
53.8%
—
30.8%
15.4%
7% of Calls for Bias End “Unable to Locate”Across 2009 to 2026, report-taken outcomes were 59% of calls. “Unable to locate” means officers could not find the incident or the person who called.
Bias: 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 19% of bias 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 bias events are called in. The year with the fewest had only 2, so averages can swing widely; the n= under each year shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
2009
11
21.4 min
28.7 min
2010
4
25.1 min
38.1 min
2013
2
27.8 min
33.8 min
2014
2
182.0 min
359.3 min
2015
5
42.2 min
52.1 min
2016
3
9.5 min
18.9 min
2017
9
72.9 min
91.7 min
2018
13
56.9 min
38.9 min
2019
8
40.8 min
48.7 min
2020
6
50.6 min
93.3 min
2021
13
84.4 min
110.6 min
2022
12
110.4 min
117.0 min
2023
11
70.4 min
61.8 min
2024
13
98.3 min
108.0 min
2025
19
213.6 min
244.8 min
2026
12
50.1 min
46.4 min
36% of Called-In Calls for Bias Get a Response Within 30 Minutes5% were answered in under 5 minutes, across all years on record.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias calls. The year with the fewest had only 1, so averages can swing widely; the n= under each year shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
2009
0
—
—
2010
0
—
—
2013
0
—
—
2014
0
—
—
2015
0
—
—
2016
0
—
—
2017
1
4.2 min
—
2018
0
—
—
2019
0
—
—
2020
2
1.0 min
11.1 min
2021
1
1.0 min
14.5 min
2022
0
—
—
2023
1
0.7 min
15.7 min
2024
1
29.3 min
48.4 min
2025
1
0.9 min
21.9 min
2026
0
—
—
Priority 1 Calls Waited 22 Minutes on Average in 2025That is the average across 1 called-in Priority 1 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.
Bias: 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 19% of bias 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 bias 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
11.7 min
15.4 min
2010
1
14.2 min
—
2013
1
55.3 min
56.1 min
2014
0
—
—
2015
2
31.5 min
35.0 min
2016
1
4.7 min
17.5 min
2017
1
23.3 min
—
2018
4
5.2 min
14.5 min
2019
4
1.3 min
16.8 min
2020
2
5.6 min
2.4 min
2021
5
92.8 min
199.1 min
2022
8
86.8 min
90.5 min
2023
0
—
—
2024
4
123.9 min
151.5 min
2025
7
37.5 min
11.5 min
2026
3
70.0 min
14.7 min
Priority 2 Calls Waited 15 Minutes on Average in 2026That is the average across 3 called-in Priority 2 events in 2026. Counts this small can swing a lot from year to year.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias 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
8
25.0 min
34.4 min
2010
3
28.7 min
38.1 min
2013
1
0.2 min
11.6 min
2014
2
182.0 min
359.3 min
2015
3
49.3 min
86.5 min
2016
2
11.9 min
20.4 min
2017
7
89.8 min
91.7 min
2018
9
79.8 min
51.1 min
2019
4
80.3 min
80.6 min
2020
2
145.1 min
348.8 min
2021
7
90.3 min
111.9 min
2022
4
157.5 min
169.9 min
2023
9
83.3 min
69.5 min
2024
8
94.1 min
96.2 min
2025
11
344.9 min
389.2 min
2026
8
47.7 min
66.5 min
Priority 3 Calls Waited 66 Minutes on Average in 2026That is the average across 8 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.
Bias: 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 19% of bias 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 bias events are called in. The year with the fewest had only 2, so shares can swing widely; the n= under each year shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
No recorded response
0–5 min
5–30 min
30–60 min
1–4 hr
4–8 hr
Over 8 hr
2009
11
9.1%
9.1%
54.5%
18.2%
9.1%
—
—
2010
4
25.0%
—
25.0%
50.0%
—
—
—
2013
2
—
—
50.0%
50.0%
—
—
—
2014
2
50.0%
—
—
—
—
50.0%
—
2015
5
40.0%
20.0%
—
—
40.0%
—
—
2016
3
33.3%
—
66.7%
—
—
—
—
2017
9
33.3%
—
33.3%
11.1%
11.1%
11.1%
—
2018
13
7.7%
—
53.8%
23.1%
15.4%
—
—
2019
8
25.0%
—
50.0%
12.5%
12.5%
—
—
2020
6
33.3%
16.7%
33.3%
—
—
16.7%
—
2021
13
38.5%
—
15.4%
15.4%
30.8%
—
—
2022
12
—
—
33.3%
—
50.0%
16.7%
—
2023
11
36.4%
9.1%
18.2%
9.1%
27.3%
—
—
2024
13
23.1%
—
7.7%
23.1%
38.5%
7.7%
—
2025
19
31.6%
10.5%
26.3%
—
10.5%
10.5%
10.5%
2026
12
33.3%
8.3%
33.3%
—
25.0%
—
—
28% of Called-In Calls for Bias Wait Over an Hour for a ResponseAcross 2009 to 2026, 28% of called-in events took more than an hour to get a response.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias 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
5–30 min
30–60 min
2009
0
—
—
—
2010
0
—
—
—
2013
0
—
—
—
2014
0
—
—
—
2015
0
—
—
—
2016
0
—
—
—
2017
1
100.0%
—
—
2018
0
—
—
—
2019
0
—
—
—
2020
2
—
100.0%
—
2021
1
—
100.0%
—
2022
0
—
—
—
2023
1
—
100.0%
—
2024
1
—
—
100.0%
2025
1
—
100.0%
—
2026
0
—
—
—
0% of Priority 1 Calls Took Over an Hour in 2025That is 0% of 1 called-in Priority 1 events. Counts this small can swing a lot from year to year.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias 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
30–60 min
No recorded response
1–4 hr
4–8 hr
2009
3
33.3%
33.3%
33.3%
—
—
—
2010
1
—
—
—
100.0%
—
—
2013
1
—
—
100.0%
—
—
—
2014
0
—
—
—
—
—
—
2015
2
50.0%
—
—
—
50.0%
—
2016
1
—
100.0%
—
—
—
—
2017
1
—
—
—
100.0%
—
—
2018
4
—
100.0%
—
—
—
—
2019
4
—
75.0%
—
25.0%
—
—
2020
2
50.0%
—
—
50.0%
—
—
2021
5
—
—
—
80.0%
20.0%
—
2022
8
—
37.5%
—
—
50.0%
12.5%
2023
0
—
—
—
—
—
—
2024
4
—
—
25.0%
25.0%
25.0%
25.0%
2025
7
14.3%
42.9%
—
42.9%
—
—
2026
3
—
66.7%
—
33.3%
—
—
0% of Priority 2 Calls Took Over an Hour in 2026That is 0% of 3 called-in Priority 2 events. Counts this small can swing a lot from year to year.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias 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
5–30 min
30–60 min
1–4 hr
4–8 hr
0–5 min
Over 8 hr
2009
8
12.5%
62.5%
12.5%
12.5%
—
—
—
2010
3
—
33.3%
66.7%
—
—
—
—
2013
1
—
100.0%
—
—
—
—
—
2014
2
50.0%
—
—
—
50.0%
—
—
2015
3
66.7%
—
—
33.3%
—
—
—
2016
2
50.0%
50.0%
—
—
—
—
—
2017
7
14.3%
42.9%
14.3%
14.3%
14.3%
—
—
2018
9
11.1%
33.3%
33.3%
22.2%
—
—
—
2019
4
25.0%
25.0%
25.0%
25.0%
—
—
—
2020
2
50.0%
—
—
—
50.0%
—
—
2021
7
14.3%
14.3%
28.6%
42.9%
—
—
—
2022
4
—
25.0%
—
50.0%
25.0%
—
—
2023
9
33.3%
11.1%
11.1%
33.3%
—
11.1%
—
2024
8
25.0%
12.5%
12.5%
50.0%
—
—
—
2025
11
27.3%
9.1%
—
18.2%
18.2%
9.1%
18.2%
2026
8
37.5%
12.5%
—
37.5%
—
12.5%
—
38% of Priority 3 Calls Took Over an Hour in 2026That is 38% of 8 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 23 events in this period, with no dispatches in 2 of the 12 months. Percentages and average times can swing widely when counts are this small, so read the trends with caution; the n= under each month shows its count.
Bias: 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 (19% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
bias calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Bias calls logged in CAD
Sep 2025
—
Oct 2025
4
Nov 2025
2
Dec 2025
4
Jan 2026
4
Feb 2026
—
Mar 2026
1
Apr 2026
1
May 2026
1
Jun 2026
1
Jul 2026
4
Aug 2026
1
Calls for Bias Totaled 23 Over the Last 12 MonthsSeattle Police logged 4 bias calls in the busiest month (Oct 2025); 2 of the 12 months had none. Counts this small can swing from one month to the next.
Bias: 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
Unable to locate
Other (unfounded / cancelled)
Resolved on scene
Oct 2025
0
50.0%
25.0%
25.0%
—
Nov 2025
0
100.0%
—
—
—
Dec 2025
0
50.0%
—
25.0%
25.0%
Jan 2026
0
75.0%
25.0%
—
—
Mar 2026
0
—
—
100.0%
—
Apr 2026
0
—
100.0%
—
—
May 2026
0
—
—
100.0%
—
Jun 2026
0
100.0%
—
—
—
Jul 2026
0
75.0%
—
25.0%
—
Aug 2026
0
—
—
100.0%
—
“Unable to Locate” Ended 13% of Calls for Bias Over the Last 12 MonthsReport-taken outcomes were 57% of calls over the period.
Bias: 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 19% of bias 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 bias 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
0
—
—
Oct 2025
2
648.1 min
951.3 min
Nov 2025
1
1.8 min
1.8 min
Dec 2025
4
75.1 min
11.3 min
Jan 2026
4
42.1 min
56.8 min
Feb 2026
0
—
—
Mar 2026
1
1.9 min
—
Apr 2026
1
8.9 min
8.9 min
May 2026
1
4.7 min
4.7 min
Jun 2026
0
—
—
Jul 2026
4
86.3 min
62.2 min
Aug 2026
1
71.5 min
—
Called-In Events Averaged 143 Minutes to Get an Officer Over the Last 12 MonthsBased on 17 called-in 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.
Bias: 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 19% of bias 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 bias 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.9 min
21.9 min
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 1 Calls Averaged 22 Minutes to Get an Officer Over the Last 12 MonthsBased on 1 called-in Priority 1 events with a recorded arrival. Counts this small can swing from one month to the next.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias 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
2
5.0 min
6.0 min
Jan 2026
2
4.1 min
14.7 min
Feb 2026
0
—
—
Mar 2026
0
—
—
Apr 2026
0
—
—
May 2026
0
—
—
Jun 2026
0
—
—
Jul 2026
1
201.8 min
—
Aug 2026
0
—
—
Priority 2 Calls Averaged 10 Minutes to Get an Officer Over the Last 12 MonthsBased on 4 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.
Bias: 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 19% of bias 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 bias 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
2
648.1 min
951.3 min
Nov 2025
1
1.8 min
1.8 min
Dec 2025
1
289.4 min
—
Jan 2026
2
80.0 min
141.0 min
Feb 2026
0
—
—
Mar 2026
1
1.9 min
—
Apr 2026
0
—
—
May 2026
1
4.7 min
4.7 min
Jun 2026
0
—
—
Jul 2026
3
47.9 min
62.2 min
Aug 2026
1
71.5 min
—
25% of Called-In Priority 3 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.
Bias: 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 19% of bias 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 bias events are called in. The month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
No recorded response
Over 8 hr
0–5 min
5–30 min
1–4 hr
Sep 2025
0
—
—
—
—
—
Oct 2025
2
50.0%
50.0%
—
—
—
Nov 2025
1
—
—
100.0%
—
—
Dec 2025
4
25.0%
—
25.0%
50.0%
—
Jan 2026
4
25.0%
—
—
50.0%
25.0%
Feb 2026
0
—
—
—
—
—
Mar 2026
1
100.0%
—
—
—
—
Apr 2026
1
—
—
—
100.0%
—
May 2026
1
—
—
100.0%
—
—
Jun 2026
0
—
—
—
—
—
Jul 2026
4
25.0%
—
—
25.0%
50.0%
Aug 2026
1
100.0%
—
—
—
—
21% of Called-In Events Took Over an Hour Over the Last 12 MonthsThat is 21% of 19 called-in events. Counts this small can swing from one month to the next.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias calls. The month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
5–30 min
Sep 2025
0
—
Oct 2025
0
—
Nov 2025
0
—
Dec 2025
1
100.0%
Jan 2026
0
—
Feb 2026
0
—
Mar 2026
0
—
Apr 2026
0
—
May 2026
0
—
Jun 2026
0
—
Jul 2026
0
—
Aug 2026
0
—
0% of Priority 1 Calls Took Over an Hour Over the Last 12 MonthsThat is 0% of 1 called-in Priority 1 events. Counts this small can swing from one month to the next.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias 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
Sep 2025
0
—
—
—
Oct 2025
0
—
—
—
Nov 2025
0
—
—
—
Dec 2025
2
50.0%
50.0%
—
Jan 2026
2
—
100.0%
—
Feb 2026
0
—
—
—
Mar 2026
0
—
—
—
Apr 2026
0
—
—
—
May 2026
0
—
—
—
Jun 2026
0
—
—
—
Jul 2026
1
—
—
100.0%
Aug 2026
0
—
—
—
0% of Priority 2 Calls Took Over an Hour Over the Last 12 MonthsThat is 0% of 5 called-in Priority 2 events. Counts this small can swing from one month to the next.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias calls. The month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
No recorded response
Over 8 hr
0–5 min
1–4 hr
5–30 min
Sep 2025
0
—
—
—
—
—
Oct 2025
2
50.0%
50.0%
—
—
—
Nov 2025
1
—
—
100.0%
—
—
Dec 2025
1
100.0%
—
—
—
—
Jan 2026
2
50.0%
—
—
50.0%
—
Feb 2026
0
—
—
—
—
—
Mar 2026
1
100.0%
—
—
—
—
Apr 2026
0
—
—
—
—
—
May 2026
1
—
—
100.0%
—
—
Jun 2026
0
—
—
—
—
—
Jul 2026
3
—
—
—
66.7%
33.3%
Aug 2026
1
100.0%
—
—
—
—
33% of Called-In Priority 3 Calls Took Over an Hour to Get a ResponseThat is 33% 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.
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 6 events in this period, with no dispatches in 7 of the 12 weeks. Percentages and average times can swing widely when counts are this small, so read the trends with caution; the n= under each week shows its count.
Bias: 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 (19% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
bias calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Bias calls logged in CAD
Week of Jun 15
1
Week of Jun 22
—
Week of Jun 29
—
Week of Jul 6
2
Week of Jul 13
—
Week of Jul 20
1
Week of Jul 27
1
Week of Aug 3
—
Week of Aug 10
—
Week of Aug 17
—
Week of Aug 24
1
Week of Aug 31
—
Calls for Bias Totaled 6 Over the Last 12 WeeksSeattle Police logged 2 bias calls in the busiest week (Week of Jul 6); 7 of the 12 weeks had none. Counts this small can swing from one week to the next.
Bias: 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)
Week of Jun 15
0
100.0%
—
Week of Jul 6
0
50.0%
50.0%
Week of Jul 20
0
100.0%
—
Week of Jul 27
0
100.0%
—
Week of Aug 24
0
—
100.0%
“Unable to Locate” Ended 0% of Calls for Bias Over the Last 12 WeeksReport-taken outcomes were 67% of calls over the period.
Bias: 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 19% of bias 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 bias 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
0
—
—
Week of Jul 6
2
140.6 min
98.5 min
Week of Jul 13
0
—
—
Week of Jul 20
1
61.2 min
72.2 min
Week of Jul 27
1
3.0 min
16.1 min
Week of Aug 3
0
—
—
Week of Aug 10
0
—
—
Week of Aug 17
0
—
—
Week of Aug 24
1
71.5 min
—
Week of Aug 31
0
—
—
Called-In Events Averaged 71 Minutes to Get an Officer Over the Last 12 WeeksBased on 4 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.
Bias: 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 19% of bias events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
No Priority 1 Calls Over the Last 12 WeeksThere were no called-in Priority 1 events in the period.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias 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
Week of Jun 15
0
—
Week of Jun 22
0
—
Week of Jun 29
0
—
Week of Jul 6
1
201.8 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
0
—
Week of Aug 17
0
—
Week of Aug 24
0
—
Week of Aug 31
0
—
No Priority 2 Response Times Were Recorded Over the Last 12 WeeksNone of the 1 called-in Priority 2 events had a recorded officer arrival.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias 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
79.4 min
98.5 min
Week of Jul 13
0
—
—
Week of Jul 20
1
61.2 min
72.2 min
Week of Jul 27
1
3.0 min
16.1 min
Week of Aug 3
0
—
—
Week of Aug 10
0
—
—
Week of Aug 17
0
—
—
Week of Aug 24
1
71.5 min
—
Week of Aug 31
0
—
—
Priority 3 Calls Averaged 62 Minutes to Get an Officer Over the Last 12 WeeksBased on 3 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.
Bias: 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 19% of bias 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 bias events are called in. The week with the fewest had only 1, so shares can swing widely; the n= under each week shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
No recorded response
1–4 hr
5–30 min
Week of Jun 15
0
—
—
—
Week of Jun 22
0
—
—
—
Week of Jun 29
0
—
—
—
Week of Jul 6
2
50.0%
50.0%
—
Week of Jul 13
0
—
—
—
Week of Jul 20
1
—
100.0%
—
Week of Jul 27
1
—
—
100.0%
Week of Aug 3
0
—
—
—
Week of Aug 10
0
—
—
—
Week of Aug 17
0
—
—
—
Week of Aug 24
1
100.0%
—
—
Week of Aug 31
0
—
—
—
40% of Called-In Events Took Over an Hour Over the Last 12 WeeksThat is 40% of 5 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.
Bias: 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 19% of bias events, because they have no wait. When a call priority is selected, only events of that priority are shown.
Call priority
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
No Priority 1 Calls Over the Last 12 WeeksThere were no called-in Priority 1 events in the period.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Bias: 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 19% of bias 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 bias 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
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
0
—
Week of Aug 17
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 1 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.
Bias: 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 19% of bias 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 bias 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
1–4 hr
5–30 min
No recorded response
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
1
100.0%
—
—
Week of Jul 27
1
—
100.0%
—
Week of Aug 3
0
—
—
—
Week of Aug 10
0
—
—
—
Week of Aug 17
0
—
—
—
Week of Aug 24
1
—
—
100.0%
Week of Aug 31
0
—
—
—
50% of Priority 3 Calls Took Over an Hour Over the Last 12 WeeksThat is 50% 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.