How Baltimore's News Outlets Report on Homicide Data, and Why the Numbers Shift
This guide explains what happens when you read about deaths in Baltimore over a seven-day period, why different outlets report different counts, and where to find the most current figures. After reading, you'll understand the lag between when deaths occur and when they're reported, which agencies track different categories of death, and how to interpret the numbers you see in print and online.
The Reporting Lag and Why Last Week's Count Changes
When Baltimore journalists write about deaths "last week," they're usually working from incomplete information. The Medical Examiner's Office does not release same-day death tallies, and causes of death require investigation that can stretch days or weeks. A homicide reported on a Tuesday might not appear in an official count until Thursday. By the following Monday, when outlets compile a "last week" summary, some deaths from six days earlier may still be pending classification.
The Baltimore Sun, the city's major daily, typically publishes a weekly homicide count every Monday or Tuesday. These figures draw from Baltimore Police Department statements and Medical Examiner records. However, the Sun's count for "last week" often differs slightly from counts published by other outlets on the same day because reporting cutoff times vary. If the Police Department releases a statement at 5 p.m. on Sunday, an outlet filing at 3 p.m. won't include it.
Local news radio stations including WBAL-AM and WIYY-FM report deaths as they're confirmed, creating a rolling tally that updates throughout the day. This means a single week may have three or four different "official" death counts depending on when you check and which source you consult. Neither approach is wrong; they simply reflect the friction between breaking news (immediate but incomplete) and verified reporting (slower but more accurate).
Which Deaths Get Counted and Why That Matters
The Baltimore Police Department and the Office of the Chief Medical Examiner use different definitions of what qualifies as a reportable death in the city's weekly statistics. Police count homicides where the death occurs within city limits and the victim's death is ruled a homicide by the Medical Examiner. This excludes deaths ruled suicide, accident, or natural cause, even if a weapon was involved. It also excludes deaths where the injury occurred in Baltimore but the person died at a hospital outside the city, though some outlets track these separately.
The Medical Examiner's Office reports deaths by manner of death (homicide, suicide, accident, natural, undetermined) and must wait for toxicology results and investigation completion before finalizing manner. A death initially classified as undetermined may be reclassified as homicide weeks later, which means a weekly count published on Monday might be revised upward by Wednesday. The Police Department's count and the Medical Examiner's count will therefore never perfectly align during any given week.
Nonprofit organizations tracking gun violence, including the Baltimore Ceasefire Initiative, sometimes publish their own counts because they include non-fatal shootings in addition to homicides. Their weekly totals will be higher than Baltimore Police homicide figures and serve a different analytical purpose. These groups focus on shootings as a public health metric, while police statistics track criminal homicides.
Where to Find This Week's Data
The Baltimore Police Department posts weekly crime statistics on its public website, updated typically on Tuesdays or Wednesdays, with a lag of one to three days. These figures are the baseline most outlets cite. The Medical Examiner's Office does not publish its own weekly public dashboard; deaths are reported through police statements or follow-up inquiries from reporters.
The Baltimore Sun maintains a homicide tracker that aggregates data from police statements and court records, allowing readers to search by date and neighborhood. This tracker lags behind the live count because it requires verification and context before each entry is added. WBAL-TV also publishes an updated homicide map and count on its website, refreshed daily.
Local nonprofit organizations including Safe Streets, which operates in multiple East and West Baltimore neighborhoods, compile their own safety data and often publish it through their community reports and social media. These counts emphasize particular neighborhoods and can highlight patterns that citywide statistics may obscure.
Why Weekly Counts Vary by Source
The most common cause of variation is the reporting cutoff. If the Police Department confirms three additional deaths on Monday morning but one outlet's Sunday night deadline has already passed, that outlet's "last week" count will be three behind. By Tuesday, both outlets report the same figure, but the initial discrepancy created confusion.
A secondary cause is geographic boundary disputes in rare cases. A death that occurs in Baltimore but is investigated by Baltimore County Police, or vice versa, may or may not appear in the city's official count depending on where the victim died versus where the death is prosecuted. This is rare but accounts for occasional single-digit differences between outlets.
The third cause is classification disputes. If a death is initially ruled undetermined and later reclassified as homicide, outlets that published before the reclassification will show a lower figure. Reputable outlets update these counts retroactively, but the original article remains unchanged, creating permanent discrepancies in the archive.
What the Numbers Mean Beyond the Weekly Total
A weekly count of 15 deaths in a single week in Baltimore represents roughly 2.1 deaths per 100,000 residents, based on the city's current population of approximately 585,000. This is substantially higher than the U.S. average of roughly 6 per 100,000 annually. However, comparing Baltimore's weekly rate to national annual rates requires converting weeks to years, a calculation that often gets skipped in casual reporting and can distort perception.
Neighborhood-level breakdowns are more actionable than citywide totals. Police District reports break homicides into categories by precinct. West Baltimore's Western District and Southwestern District account for a disproportionate share of the city's homicides; understanding this distribution shows where prevention resources are concentrated and where gaps remain. Outlets that report deaths by neighborhood provide information that city-total reporting obscures.
How to Read Multiple Sources Without Confusion
Start with the Baltimore Police Department's official statement, which is the primary source. Check the date of the statement and the date range it covers. If the statement was released Tuesday morning for "the week of January 6 to January 12," note that additional deaths from January 12 may not yet be included.
Cross-reference with the Baltimore Sun's Monday or Tuesday report, which typically provides context and identifies victims by name where reporting norms permit. Compare the figure to the outlet's previous week's count; a sudden spike or drop may indicate either a genuine pattern shift or a reporting lag catching up.
If you see conflicting numbers from two outlets published on the same day, check the timestamp of each source's underlying police statement. The outlet citing the more recent statement will have the more complete figure. Neither outlet is incorrect; they're simply working from different information cutoffs.
The practical takeaway: Baltimore's weekly death counts are real, tragic, and often reported differently by different outlets due to verification timelines, not falsification. Reading the byline date and the underlying police statement's timestamp will clarify why figures appear to conflict. No single "correct" count exists for a given week until several days after that week ends.

