911Sentinel

Research · 6 min read

The Newest Edge of a Crime Map Isn’t Less Crime — It’s Missing Records

Occurrence-date totals for recent periods are structurally incomplete and should not be compared with settled historical periods.

You open the crime map Monday morning and your block looks quiet. Quiet because nothing happened — or because the records haven’t arrived yet? In Seattle’s public data, fewer than half of property-offense records show up within 24 hours, one in ten takes more than twelve days, and the median lag has grown longer with each report cohort. Last week’s map is not finished.

Our analysis of 116,787 records with a valid, nonnegative timestamp interval, reports published July 1, 2023–June 30, 2026.

Key takeaways

  • Only 44.2% of 116,787 valid Seattle property-offense records appeared within 24 hours of the recorded offense start; 16.4% took more than a week and 4.4% more than a month.
  • The delay is not a constant: the median rose from 21.4 hours for records published in 2023 to 54.6 hours for 2026, so recent periods are the least settled.
  • One extract can only measure records that eventually arrived, so it cannot calculate live-feed completeness — that requires saved historical snapshots.
  • Mark recent occurrence-date totals provisional and compare periods only at matching data maturity.

Why does the most recent stretch of a crime map always look quiet?

Among 116,787 Seattle property-offense records with valid intervals, only 44.2% were published within 24 hours of the recorded offense start, 67.7% within three days, and 16.4% took over a week — and the median lag climbed from 21.4 hours for the 2023 report cohort to 54.6 for 2026. Recent occurrence-date totals are structurally incomplete and should be marked provisional.

At a glance

The numbers behind the answer

Selected measures only. Denominators and interpretation stay attached so the headline cannot stand alone.

44.2%

Published within 24 hours

51,580 of 116,787 valid nonnegative publication intervals were no longer than one day.

16.4%

Published after 7 days

19,185 accepted records took longer than one week to appear.

292.5 h

90th-percentile lag

Nine in ten valid records appeared within about 12.2 days; one in ten took longer.

01The blind spot

A recent occurrence-date map is a partial view of the period

A dashboard can be refreshed this morning and still be wrong about last week. “Refreshed” means the data was re-downloaded — not that it describes everything that happened. In this extract, 44.2% of records were published within 24 hours of the recorded offense start. 67.7% made it within 72 hours, 83.6% within a week, and 95.6% within 30 days. The last few percent trickle in over months.

Which means the newest stretch of any occurrence-date chart is structurally incomplete. That reassuring dip at the right edge of the graph? Part of it is records that haven’t landed yet. The recent period isn’t a smaller version of history. It’s a different, unfinished product.

The shape of the delay is a long tail, not a wall. About one in five records arrives within six hours and just under a quarter more within a day — so a little over two in five are in by the next morning. Another 23.5% land in days one to three, 15.9% in days three to seven, and the remaining 16.4% spread across everything from a week to more than a month. There is no single filing deadline; there is a distribution, and its slow end is long.

Safe comparison

Compare settled periods with settled periods, and mark recent occurrence-date totals provisional.

02Not a fixed delay

The lag drifts with the report cohort

It would be convenient if the delay were a stable constant you could add as a buffer. It isn’t. Group the records by the year their report was published and the median offense-to-report lag climbs steadily: 21.4 hours for the 2023 cohort, 28.0 for 2024, 39.9 for 2025, and 54.6 for 2026. A record published this year is, on average, describing an offense that started later than a record published three years ago did.

Read that carefully, because it is not a claim that crime is getting older. It means recent publication carries more backlog: records about older offenses are surfacing alongside fresh ones, and earlier years have had more time for their long-tail entries to settle. For a property team the consequence is the same either way — the current period’s totals are less complete than an equal-looking historical total, and the gap widens as you approach the present.

Two quality checks round this out. Just 92 intervals were negative (a report timestamped before its offense start), and 10,253 records carry an exact-midnight offense time. If you suspect those midnight placeholders inflate the slow tail, they do, but only a little: drop them and the median falls from 32.7 hours to 28.4, the 90th percentile from 292.5 to 250.2, and the share taking over a week from 16.4% to 14.5%. Better, still slow.

03How long records take

The middle is measured in hours; the slow tail is measured in weeks

The typical record isn’t the problem. The median lag is 32.7 hours — annoying, but workable. The problem is the tail. The 90th percentile is 292.5 hours, about twelve days. The 95th is 622.6 hours: nearly four weeks.

The distribution also has an offense shape. Motor-vehicle theft’s median is 16.7 hours, burglary’s is 32.5, and all-other-larceny runs to 41.1, while arson surfaces in about 3. The slow categories are exactly the ones most likely to still be missing from a fresh map, which is why one global buffer under-protects some offense types and over-protects others. The companion survival study takes that split apart offense by offense.

If you suspect the exact-midnight timestamps inflate the tail, they do — a little. Excluding them, the median drops to 28.4 hours, the 90th percentile to 250.2 hours, and the share taking more than a week falls from 16.4% to 14.5%. Better. Still slow.

Evidence visual

Share of valid records published by elapsed time

This is the observed lag among records present in the extract, not a direct estimate of how complete a live feed is at each age.

Within 6 hours20.4%
Within 24 hours44.2%
Within 72 hours67.7%
Within 7 days83.6%
Within 30 days95.6%
04What to do

A good dashboard separates data age from event age

You don’t have to stop using recent maps. You have to label them. A good dashboard runs two clocks: when the data was refreshed, and how mature each period’s totals are. Anything younger than a stated cutoff gets marked provisional, full stop.

And compare like with like: this month at 30 days old against last month at the same age — never against its final, settled total. A bar that reads “provisional” beside a settled bar is not a comparison; it is a comparison plus a correction you have to do in your head.

One caveat for the truly careful: a single extract can only measure the lag among records that eventually arrived. It cannot count the records that never showed up, because it has no record of their absence. Estimating true live-feed completeness requires saving snapshots of the dataset over time and diffing them — the maturity experiment this study would need is marked unavailable for exactly that reason. The checklist below turns the rest into policy.

  • Display both occurrence date and data-refresh date.
  • Mark recent totals provisional.
  • Use matching maturity windows for comparisons.
  • Keep negative and invalid intervals visible as quality checks.
  • Retain historical snapshots before claiming completeness.
05Where the delay concentrates

The lag is not uniform — it varies by neighborhood and reporting channel

The chain that ends in publication starts upstream, and the lag splits geographically. Median offense-to-report intervals run from 9.7 hours around Roxhill to 41.9 in Capitol Hill, 78.6 where the block label is unknown, and a 331.4-hour mean in Queen Anne. A single global buffer is therefore too coarse: the same 24-hour cutoff that is generous in one area is lenient in another.

That variation is what recording-practice research predicts. Recording practices vary by place and time within a single agency, and open-data assembly work documents how revisions, re-geocoding, and late entries ripple through counts — the same forces lengthening the tail measured here.

It also points at a larger, invisible delay. A record can only show up late if it was reported at all; the dark figure of unreported crime means a live view cannot see the offense that never entered the system, the one reclassified away, or the one still queued. Publication lag is the delay you can measure; the detection layer upstream is the one you cannot. Label the first and stay modest about the second.

The whole chain

Publication lag is the last visible delay; reporting and recording practice come first.

06Useful answers

Questions property teams ask

Does a live crime map show everything that happened yesterday?

Not necessarily. In this extract, only 44.2% of valid records were published within 24 hours of the recorded offense start.

How long should I wait before comparing recent totals?

There is no universal cutoff, but the observed curve shows that 83.6% appeared within seven days and 95.6% within 30 days. The dashboard should show its maturity rule explicitly.

Are late records wrong?

No. Publication delay and record accuracy are different questions. A record can be accurate and still appear after an operational or administrative lag.

Why is the median lag longer for recent report years?

Recent publication carries more backlog: records about older offenses surface alongside fresh ones, and earlier years have had more time for their long-tail entries to settle. It is a maturity effect, not a claim that offenses are getting older.

Is a seven-day buffer enough?

It depends on the offense and the decision. 16.4% of records exceed seven days overall, and the slow categories — all-other-larceny and theft-from-building — exceed it more often.

Can this study calculate exact feed completeness by day?

No. That requires saved historical snapshots of the dataset. A single current extract only measures lag among records that are now present.

Does publication lag measure how many crimes are never reported?

No. It measures how long a published record took to appear. Nonreporting is a separate and larger gap: many offenses never reach the records at all, and victimization surveys exist to estimate that difference.

07Inspect the work

Our methods, limits, and sources

How we calculated this

This is original 911 Sentinel research — we gathered the records, ran every calculation below, and published the aggregate dataset.

We subtracted each accepted record’s offense-start timestamp from its report timestamp, summarized 116,787 valid nonnegative intervals, and re-ran the summary by report cohort and with exact-midnight starts removed.

  1. We parsed offense-start and report timestamps for the study window and deduplicated by offense ID.
  2. We excluded 92 negative intervals and reported them as a quality check.
  3. We calculated the lag buckets, cumulative shares, and the median, P90, and P95 lag.
  4. We repeated the summary by publication year and after excluding exact-midnight offense starts.
  5. We recorded that a completeness experiment is not possible from a single extract without saved historical snapshots.
What this analysis cannot establish
  • The extract contains records that were published; it cannot reveal records still absent at extraction time.
  • Historical as-of snapshots are required to estimate live-feed completeness directly.
  • Offense start times may be estimated or may describe broad occurrence windows.
  • The rising median by report cohort mixes genuine backlog with the extra settling time older years have had.
  • The result describes Seattle’s publication process during this period and may change.

No obligation · free property walk

Read recent maps with the right clock

Use the coverage map as a screening view, then account for data age and inspect the property conditions that a public record cannot show.

911 SENTINEL — PROTECTIVE OPERATIONS STANDARDOPERATING RECORD AVAILABLE ON REQUEST SEATTLE, WA