Seattle Police
Call volumeOutcomesHow long it tookHow long it took, in full

Amber Alerts

Amber Alerts calls over time: volume, outcomes, and response speed

Amber Alerts: 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. All were called in; officers logged none themselves. Excluded: Nothing.

Swipe sideways to see the full chart →
0112010: 1 amber alerts calls logged in CAD2013: 1 amber alerts calls logged in CAD2014: 1 amber alerts calls logged in CAD2015: 1 amber alerts calls logged in CAD2010n=12014n=12015n=1
amber alerts calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodAmber alerts calls logged in CAD
20101
20131
20141
20151
Calls for Amber Alerts Are Rare: Only 4 on RecordSeattle Police logged 4 amber alerts calls between 2010 and 2015, with a high of 1 in 2010. Counts this small are too thin to read as a trend.

Amber Alerts: 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 →
100%50%0%2010 · Other (unfounded / cancelled): 100.0%2013 · Other (unfounded / cancelled): 100.0%2014 · Other (unfounded / cancelled): 100.0%2015 · Other (unfounded / cancelled): 100.0%2010n=12014n=12015n=1
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
PeriodEventsOther (unfounded / cancelled)
20101100.0%
20131100.0%
20141100.0%
20151100.0%
0% of Calls for Amber Alerts End “Unable to Locate”Across 2010 to 2015, report-taken outcomes were 0% of calls. “Unable to locate” means officers could not find the incident or the person who called.

Amber Alerts: 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), of which there are none in this category, 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 →
0 min40 min80 min2010: 61.3 min2013: 36.0 min2014: 8.4 min2015: 21.2 min2010: 61.3 min2013: 36.0 min2014: 8.4 min2015: 21.2 min2010n=12014n=12015n=1
Average response timeAverage dispatch delay
Small sample: Only a small share of amber alerts 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
PeriodCalled-in eventsAverage dispatch delayAverage response time
2010161.3 min61.3 min
2013136.0 min36.0 min
201418.4 min8.4 min
2015121.2 min21.2 min
Called-In Events Waited 21 Minutes on Average in 2015That is the average across 1 called-in 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.

Amber Alerts: 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), of which there are none in this category, 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 →
100%50%0%2010 · 1–4 hr: 100.0%2013 · 30–60 min: 100.0%2014 · 5–30 min: 100.0%2015 · 5–30 min: 100.0%2010n=12014n=12015n=1
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of amber alerts 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
PeriodCalled-in events1–4 hr30–60 min5–30 min
20101100.0%——
20131—100.0%—
20141——100.0%
20151——100.0%
0% of Called-In Events Took Over an Hour in 2015That 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.

“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. 2010 and 2015 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.