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

Fraud & Forgery

Fraud & Forgery calls over time: volume, outcomes, and response speed

Fraud & Forgery: 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 (18% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
02,5005,0002009: 2,070 fraud & forgery calls logged in CAD2010: 4,296 fraud & forgery calls logged in CAD2011: 3,163 fraud & forgery calls logged in CAD2012: 3,121 fraud & forgery calls logged in CAD2013: 3,329 fraud & forgery calls logged in CAD2014: 4,082 fraud & forgery calls logged in CAD2015: 3,708 fraud & forgery calls logged in CAD2016: 3,451 fraud & forgery calls logged in CAD2017: 3,406 fraud & forgery calls logged in CAD2018: 3,345 fraud & forgery calls logged in CAD2019: 3,001 fraud & forgery calls logged in CAD2020: 2,469 fraud & forgery calls logged in CAD2021: 1,973 fraud & forgery calls logged in CAD2022: 1,711 fraud & forgery calls logged in CAD2023: 2,088 fraud & forgery calls logged in CAD2024: 1,937 fraud & forgery calls logged in CAD2025: 2,214 fraud & forgery calls logged in CAD2026: 1,429 fraud & forgery calls logged in CAD2009n=2,0702011n=3,1632013n=3,3292015n=3,7082017n=3,4062019n=3,0012021n=1,9732023n=2,0882025n=2,2142026n=1,429
fraud & forgery calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodFraud & forgery calls logged in CAD
20092,070
20104,296
20113,163
20123,121
20133,329
20144,082
20153,708
20163,451
20173,406
20183,345
20193,001
20202,469
20211,973
20221,711
20232,088
20241,937
20252,214
20261,429
Fraud & Forgery Calls Are Down 48% From Their 2010 PeakSeattle Police logged 4,296 fraud & forgery calls in 2010 and 2,214 in 2025, the most recent full year.

Fraud & Forgery: 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%2009 · Arrest / citation: 2.9%2009 · Report taken, no arrest: 80.5%2009 · Resolved on scene: 9.2%2009 · Unable to locate: 2.1%2009 · Other (unfounded / cancelled): 5.2%2010 · Arrest / citation: 1.4%2010 · Report taken, no arrest: 83.2%2010 · Resolved on scene: 8.3%2010 · Unable to locate: 2.0%2010 · Other (unfounded / cancelled): 5.2%2011 · Arrest / citation: 2.2%2011 · Report taken, no arrest: 82.5%2011 · Resolved on scene: 8.7%2011 · Unable to locate: 2.2%2011 · Other (unfounded / cancelled): 4.4%2012 · Arrest / citation: 2.7%2012 · Report taken, no arrest: 75.1%2012 · Resolved on scene: 13.8%2012 · Unable to locate: 3.5%2012 · Other (unfounded / cancelled): 5.0%2013 · Arrest / citation: 1.5%2013 · Report taken, no arrest: 78.3%2013 · Resolved on scene: 12.3%2013 · Unable to locate: 5.2%2013 · Other (unfounded / cancelled): 2.8%2014 · Arrest / citation: 1.4%2014 · Report taken, no arrest: 77.2%2014 · Resolved on scene: 11.4%2014 · Unable to locate: 8.3%2014 · Other (unfounded / cancelled): 1.7%2015 · Arrest / citation: 1.1%2015 · Report taken, no arrest: 82.6%2015 · Resolved on scene: 8.2%2015 · Unable to locate: 6.7%2015 · Other (unfounded / cancelled): 1.3%2016 · Arrest / citation: 1.6%2016 · Report taken, no arrest: 83.8%2016 · Resolved on scene: 6.5%2016 · Unable to locate: 6.4%2016 · Other (unfounded / cancelled): 1.7%2017 · Arrest / citation: 1.5%2017 · Report taken, no arrest: 83.1%2017 · Resolved on scene: 7.1%2017 · Unable to locate: 6.6%2017 · Other (unfounded / cancelled): 1.7%2018 · Arrest / citation: 1.0%2018 · Report taken, no arrest: 83.1%2018 · Resolved on scene: 7.7%2018 · Unable to locate: 6.8%2018 · Other (unfounded / cancelled): 1.5%2019 · Arrest / citation: 1.1%2019 · Report taken, no arrest: 81.2%2019 · Resolved on scene: 8.6%2019 · Unable to locate: 7.7%2019 · Other (unfounded / cancelled): 1.5%2020 · Arrest / citation: 1.1%2020 · Report taken, no arrest: 78.9%2020 · Resolved on scene: 11.6%2020 · Unable to locate: 7.7%2020 · Other (unfounded / cancelled): 0.7%2021 · Arrest / citation: 1.0%2021 · Report taken, no arrest: 77.2%2021 · Resolved on scene: 11.4%2021 · Unable to locate: 9.8%2021 · Other (unfounded / cancelled): 0.6%2022 · Arrest / citation: 0.9%2022 · Report taken, no arrest: 76.2%2022 · Resolved on scene: 12.2%2022 · Unable to locate: 10.2%2022 · Other (unfounded / cancelled): 0.5%2023 · Arrest / citation: 0.5%2023 · Report taken, no arrest: 71.7%2023 · Resolved on scene: 12.1%2023 · Unable to locate: 15.1%2023 · Other (unfounded / cancelled): 0.5%2024 · Arrest / citation: 0.3%2024 · Report taken, no arrest: 70.7%2024 · Resolved on scene: 11.9%2024 · Unable to locate: 16.6%2024 · Other (unfounded / cancelled): 0.6%2025 · Arrest / citation: 0.8%2025 · Report taken, no arrest: 65.8%2025 · Resolved on scene: 14.5%2025 · Unable to locate: 18.3%2025 · Other (unfounded / cancelled): 0.6%2026 · Arrest / citation: 0.3%2026 · Report taken, no arrest: 65.6%2026 · Resolved on scene: 11.9%2026 · Unable to locate: 21.1%2026 · Other (unfounded / cancelled): 1.1%2009n=2,0702011n=3,1632013n=3,3292015n=3,7082017n=3,4062019n=3,0012021n=1,9732023n=2,0882025n=2,2142026n=1,429
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
PeriodEventsArrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
20092,0702.9%80.5%9.2%2.1%5.2%
20104,2961.4%83.2%8.3%2.0%5.2%
20113,1632.2%82.5%8.7%2.2%4.4%
20123,1212.7%75.1%13.8%3.5%5.0%
20133,3291.5%78.3%12.3%5.2%2.8%
20144,0821.4%77.2%11.4%8.3%1.7%
20153,7081.1%82.6%8.2%6.7%1.3%
20163,4511.6%83.8%6.5%6.4%1.7%
20173,4061.5%83.1%7.1%6.6%1.7%
20183,3451.0%83.1%7.7%6.8%1.5%
20193,0011.1%81.2%8.6%7.7%1.5%
20202,4691.1%78.9%11.6%7.7%0.7%
20211,9731.0%77.2%11.4%9.8%0.6%
20221,7110.9%76.2%12.2%10.2%0.5%
20232,0880.5%71.7%12.1%15.1%0.5%
20241,9370.3%70.7%11.9%16.6%0.6%
20252,2140.8%65.8%14.5%18.3%0.6%
20261,4290.3%65.6%11.9%21.1%1.1%
21% of Fraud & Forgery Calls End “Unable to Locate,” Up From 6%Report-taken outcomes moved from 84% of calls in 2016 to 66% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Fraud & Forgery: 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 18% of fraud & forgery 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 →
0 min100 min200 min2009: 47.4 min2010: 27.6 min2011: 31.7 min2012: 45.9 min2013: 53.3 min2014: 89.5 min2015: 78.5 min2016: 77.9 min2017: 79.9 min2018: 108.1 min2019: 92.2 min2020: 78.3 min2021: 108.4 min2022: 87.4 min2023: 103.1 min2024: 129.4 min2025: 139.0 min2026: 156.3 min2009: 54.5 min2010: 31.7 min2011: 37.9 min2012: 53.5 min2013: 61.5 min2014: 98.2 min2015: 86.7 min2016: 85.9 min2017: 89.7 min2018: 118.6 min2019: 98.6 min2020: 80.2 min2021: 112.7 min2022: 91.0 min2023: 109.3 min2024: 134.3 min2025: 140.9 min2026: 159.4 min2009n=1,5882011n=2,6292013n=2,8642015n=2,8882017n=2,5412019n=2,2792021n=1,7972023n=1,8372025n=1,9422026n=1,190
Average response timeAverage dispatch delay
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
20091,58847.4 min54.5 min
20103,59727.6 min31.7 min
20112,62931.7 min37.9 min
20122,65345.9 min53.5 min
20132,86453.3 min61.5 min
20143,33789.5 min98.2 min
20152,88878.5 min86.7 min
20162,63877.9 min85.9 min
20172,54179.9 min89.7 min
20182,497108.1 min118.6 min
20192,27992.2 min98.6 min
20202,22378.3 min80.2 min
20211,797108.4 min112.7 min
20221,46787.4 min91.0 min
20231,837103.1 min109.3 min
20241,660129.4 min134.3 min
20251,942139.0 min140.9 min
20261,190156.3 min159.4 min
The Average Call Waits 159 Minutes for an Officer to ArriveDespite a 36% drop in calls between 2016 and 2025, average response time has increased 86% in the past 10 years, from 86 minutes in 2016 to 159 in 2026, driven largely by dispatch delays.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

Fraud & Forgery: 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 18% of fraud & forgery 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 →
100%50%0%2009 · No recorded response: 3.6%2009 · 0–5 min: 12.6%2009 · 5–30 min: 32.8%2009 · 30–60 min: 20.1%2009 · 1–4 hr: 28.6%2009 · 4–8 hr: 2.1%2009 · Over 8 hr: 0.2%2010 · No recorded response: 2.6%2010 · 0–5 min: 26.3%2010 · 5–30 min: 40.6%2010 · 30–60 min: 16.4%2010 · 1–4 hr: 13.2%2010 · 4–8 hr: 0.8%2010 · Over 8 hr: 0.1%2011 · No recorded response: 2.8%2011 · 0–5 min: 25.4%2011 · 5–30 min: 35.7%2011 · 30–60 min: 16.1%2011 · 1–4 hr: 18.6%2011 · 4–8 hr: 1.4%2012 · No recorded response: 2.7%2012 · 0–5 min: 19.4%2012 · 5–30 min: 31.6%2012 · 30–60 min: 17.7%2012 · 1–4 hr: 25.9%2012 · 4–8 hr: 2.5%2012 · Over 8 hr: 0.2%2013 · No recorded response: 3.5%2013 · 0–5 min: 14.7%2013 · 5–30 min: 28.6%2013 · 30–60 min: 19.0%2013 · 1–4 hr: 31.0%2013 · 4–8 hr: 3.0%2013 · Over 8 hr: 0.1%2014 · No recorded response: 2.8%2014 · 0–5 min: 9.0%2014 · 5–30 min: 23.1%2014 · 30–60 min: 16.6%2014 · 1–4 hr: 37.9%2014 · 4–8 hr: 9.9%2014 · Over 8 hr: 0.7%2015 · No recorded response: 2.5%2015 · 0–5 min: 17.7%2015 · 5–30 min: 24.1%2015 · 30–60 min: 14.6%2015 · 1–4 hr: 32.5%2015 · 4–8 hr: 7.5%2015 · Over 8 hr: 1.2%2016 · No recorded response: 2.5%2016 · 0–5 min: 16.5%2016 · 5–30 min: 24.7%2016 · 30–60 min: 15.2%2016 · 1–4 hr: 32.0%2016 · 4–8 hr: 8.0%2016 · Over 8 hr: 1.0%2017 · No recorded response: 2.6%2017 · 0–5 min: 11.9%2017 · 5–30 min: 25.2%2017 · 30–60 min: 17.0%2017 · 1–4 hr: 34.3%2017 · 4–8 hr: 7.8%2017 · Over 8 hr: 1.2%2018 · No recorded response: 3.4%2018 · 0–5 min: 7.0%2018 · 5–30 min: 19.7%2018 · 30–60 min: 15.1%2018 · 1–4 hr: 40.2%2018 · 4–8 hr: 13.0%2018 · Over 8 hr: 1.6%2019 · No recorded response: 3.5%2019 · 0–5 min: 11.8%2019 · 5–30 min: 21.2%2019 · 30–60 min: 14.1%2019 · 1–4 hr: 39.3%2019 · 4–8 hr: 9.1%2019 · Over 8 hr: 1.0%2020 · No recorded response: 1.7%2020 · 0–5 min: 17.9%2020 · 5–30 min: 23.4%2020 · 30–60 min: 14.1%2020 · 1–4 hr: 36.3%2020 · 4–8 hr: 6.0%2020 · Over 8 hr: 0.6%2021 · No recorded response: 3.3%2021 · 0–5 min: 15.5%2021 · 5–30 min: 23.1%2021 · 30–60 min: 12.6%2021 · 1–4 hr: 32.3%2021 · 4–8 hr: 10.3%2021 · Over 8 hr: 2.8%2022 · No recorded response: 3.6%2022 · 0–5 min: 25.8%2022 · 5–30 min: 23.6%2022 · 30–60 min: 12.5%2022 · 1–4 hr: 24.3%2022 · 4–8 hr: 7.0%2022 · Over 8 hr: 3.1%2023 · No recorded response: 6.3%2023 · 0–5 min: 24.4%2023 · 5–30 min: 22.3%2023 · 30–60 min: 11.7%2023 · 1–4 hr: 23.0%2023 · 4–8 hr: 7.7%2023 · Over 8 hr: 4.6%2024 · No recorded response: 10.3%2024 · 0–5 min: 18.8%2024 · 5–30 min: 16.7%2024 · 30–60 min: 11.1%2024 · 1–4 hr: 26.1%2024 · 4–8 hr: 11.9%2024 · Over 8 hr: 4.9%2025 · No recorded response: 1.5%2025 · 0–5 min: 23.6%2025 · 5–30 min: 19.1%2025 · 30–60 min: 8.7%2025 · 1–4 hr: 24.2%2025 · 4–8 hr: 16.5%2025 · Over 8 hr: 6.3%2026 · No recorded response: 2.4%2026 · 0–5 min: 16.8%2026 · 5–30 min: 17.2%2026 · 30–60 min: 10.4%2026 · 1–4 hr: 26.9%2026 · 4–8 hr: 19.7%2026 · Over 8 hr: 6.6%2009n=1,5882011n=2,6292013n=2,8642015n=2,8882017n=2,5412019n=2,2792021n=1,7972023n=1,8372025n=1,9422026n=1,190
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
PeriodCalled-in eventsNo recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
20091,5883.6%12.6%32.8%20.1%28.6%2.1%0.2%
20103,5972.6%26.3%40.6%16.4%13.2%0.8%0.1%
20112,6292.8%25.4%35.7%16.1%18.6%1.4%—
20122,6532.7%19.4%31.6%17.7%25.9%2.5%0.2%
20132,8643.5%14.7%28.6%19.0%31.0%3.0%0.1%
20143,3372.8%9.0%23.1%16.6%37.9%9.9%0.7%
20152,8882.5%17.7%24.1%14.6%32.5%7.5%1.2%
20162,6382.5%16.5%24.7%15.2%32.0%8.0%1.0%
20172,5412.6%11.9%25.2%17.0%34.3%7.8%1.2%
20182,4973.4%7.0%19.7%15.1%40.2%13.0%1.6%
20192,2793.5%11.8%21.2%14.1%39.3%9.1%1.0%
20202,2231.7%17.9%23.4%14.1%36.3%6.0%0.6%
20211,7973.3%15.5%23.1%12.6%32.3%10.3%2.8%
20221,4673.6%25.8%23.6%12.5%24.3%7.0%3.1%
20231,8376.3%24.4%22.3%11.7%23.0%7.7%4.6%
20241,66010.3%18.8%16.7%11.1%26.1%11.9%4.9%
20251,9421.5%23.6%19.1%8.7%24.2%16.5%6.3%
20261,1902.4%16.8%17.2%10.4%26.9%19.7%6.6%
The Average Call Waits 156 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 156 minutes in 2026, more than double what it was in 2016. 53% of calls took more than an hour to get a response in 2026, compared with 41% in 2016.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

“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.