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.
Predictive Policing calls over time: volume, outcomes, and response speed
Predictive Policing: 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 (100% of the total). Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
predictive policing calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Predictive policing calls logged in CAD
2013
27,901
2014
5,492
2015
383
2016
792
Predictive Policing Calls Are Down 97% From Their 2013 PeakSeattle Police logged 27,901 predictive policing calls in 2013 and 792 in 2016, the most recent full year.
Predictive Policing: What Happened When Officers Responded
Outcomes show how each call ended, based on the disposition officers recorded when the call was closed: an arrest or citation, a report taken with no arrest, resolved on scene, unable to locate (officers could not find the incident or the person who called), or other (unfounded or cancelled). Each bar shows the share of that period’s calls.
Included: Every event, called in or officer-initiated, using the disposition recorded when the event was closed. Excluded: Nothing.
Swipe sideways to see the full chart →
Swipe sideways to see the full chart →
Arrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
View as table
What happened when officers responded — same numbers as the chart above
Period
Events
Report taken, no arrest
Resolved on scene
Unable to locate
Other (unfounded / cancelled)
Arrest / citation
2013
27,901
0.1%
98.2%
1.3%
0.3%
—
2014
5,492
0.1%
98.4%
1.1%
0.4%
—
2015
383
0.3%
99.0%
0.8%
—
—
2016
792
2.5%
96.5%
0.8%
—
0.3%
“Unable to Locate” Outcomes Are Holding Near 1% of Predictive Policing CallsReport-taken outcomes moved from 0% of calls in 2013 to 2% in 2016. “Unable to locate” means officers could not find the incident or the person who called.
Predictive Policing: 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 100% of predictive policing 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 predictive policing 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 predictive policing events are called in. The year with the fewest had only 1, so averages can swing widely; the n= under each year shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
2013
33
10.7 min
16.7 min
2014
12
7.6 min
10.6 min
2015
3
3.3 min
7.8 min
2016
1
0.4 min
—
No Response Times Were Recorded in 2016None of the 1 called-in events had a recorded officer arrival.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Predictive Policing: 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 100% of predictive policing 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 predictive policing 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 predictive policing 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
2013
5
0.9 min
6.5 min
2014
1
0.6 min
1.2 min
2015
1
4.5 min
7.8 min
2016
0
—
—
Priority 1 Calls Waited 7.8 Minutes on Average in 2015That is the average across 1 called-in Priority 1 events in 2015. 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.
Predictive Policing: 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 100% of predictive policing 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 predictive policing 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 predictive policing calls. The year with the fewest had only 2, so averages can swing widely; the n= under each year shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
2013
5
11.5 min
13.0 min
2014
2
1.7 min
1.7 min
2015
0
—
—
2016
0
—
—
Priority 2 Calls Waited 1.7 Minutes on Average in 2014That is the average across 2 called-in Priority 2 events in 2014. 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.
Predictive Policing: 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 100% of predictive policing 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 predictive policing 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 predictive policing 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
2013
11
23.3 min
85.4 min
2014
7
12.3 min
34.6 min
2015
2
2.7 min
—
2016
1
0.4 min
—
No Priority 3 Response Times Were Recorded in 2016None of the 1 called-in Priority 3 events had a recorded officer arrival.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Predictive Policing: 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 100% of predictive policing events, because they have no wait. Because most predictive policing 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 predictive policing events are called in. The year with the fewest had only 1, so shares can swing widely; the n= under each year shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
No recorded response
0–5 min
5–30 min
30–60 min
1–4 hr
2013
33
33.3%
39.4%
12.1%
6.1%
9.1%
2014
12
41.7%
41.7%
8.3%
—
8.3%
2015
3
66.7%
—
33.3%
—
—
2016
1
100.0%
—
—
—
—
0% of Called-In Events Took Over an Hour in 2016That is 0% of 1 called-in 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.
Predictive Policing: 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 100% of predictive policing events, because they have no wait. Because most predictive policing 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 predictive policing calls. The year with the fewest had only 1, so shares can swing widely; the n= under each year shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
No recorded response
0–5 min
5–30 min
2013
5
40.0%
20.0%
40.0%
2014
1
—
100.0%
—
2015
1
—
—
100.0%
2016
0
—
—
—
0% of Priority 1 Calls Took Over an Hour in 2015That 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.
Predictive Policing: 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 100% of predictive policing events, because they have no wait. Because most predictive policing 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 predictive policing calls. The year with the fewest had only 2, so shares can swing widely; the n= under each year shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
No recorded response
0–5 min
5–30 min
30–60 min
2013
5
20.0%
20.0%
40.0%
20.0%
2014
2
—
100.0%
—
—
2015
0
—
—
—
—
2016
0
—
—
—
—
0% of Priority 2 Calls Took Over an Hour in 2014That is 0% of 2 called-in Priority 2 events. Counts this small can swing a lot from year to year.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Predictive Policing: 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 100% of predictive policing events, because they have no wait. Because most predictive policing 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 predictive policing 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
1–4 hr
5–30 min
2013
11
72.7%
27.3%
—
2014
7
71.4%
14.3%
14.3%
2015
2
100.0%
—
—
2016
1
100.0%
—
—
0% of Priority 3 Calls Took Over an Hour in 2016That is 0% of 1 called-in Priority 3 events. Counts this small can swing a lot from year to year.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.
Showing the 12 full calendar months, Sep 2025 through Aug 2026, one bar per month. The current month is left out because it is incomplete.
No events in this period. Seattle Police logged no predictive policing calls in this window, so there is nothing to chart. Switch to Historical to see the full record.
Showing the 12 most recent full weeks (Monday to Sunday): Jun 15 through Sep 6, 2026, one bar per week, labeled by its first day. The current week is left out because it is incomplete.
No events in this period. Seattle Police logged no predictive policing calls in this window, so there is nothing to chart. Switch to Historical to see the full record.
“CAD” is Computer-Aided Dispatch, the system Seattle Police use to log and time every call for service — every number on this page comes from it. 2013 and 2016 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. 2013 and 2016 may be partial years (data begins mid-2009; the latest year runs through the site's last data pull). “n=” under each month is the number of events logged that month in the volume and outcomes charts, and the number of called-in events dispatched to an officer in the response-time charts. Events officers log themselves (on view) are included in volume and outcomes and left out of response times, because they have no wait. The response-time bands measure time from call queued to first unit on scene; “no recorded response” means no arrival was ever logged. Hover any point for its exact value.
“CAD” is Computer-Aided Dispatch, the system Seattle Police use to log and time every call for service — every number on this page comes from it. 2013 and 2016 may be partial years (data begins mid-2009; the latest year runs through the site's last data pull). “n=” under each week is the number of events logged that week in the volume and outcomes charts, and the number of called-in events dispatched to an officer in the response-time charts. Events officers log themselves (on view) are included in volume and outcomes and left out of response times, because they have no wait. The response-time bands measure time from call queued to first unit on scene; “no recorded response” means no arrival was ever logged. Hover any point for its exact value.