evidoria

← Back to browse

Good practice Imported

Chicago's Food Inspection Forecasting Model — Ranking Restaurants by Violation Risk to Catch Problems Sooner

United States of America · Chicago · See the United States of America profile · See the Chicago profile

Evidence: Quasi-experimental Top 15% 80/100 · Ask Evidence Copilot about this practice

Chicago's health department built a machine-learning model ranking restaurants by violation risk. An independent pilot evaluation found inspectors using its list caught 69% of violators in the first half of the schedule (vs 55% normally), about 7.5 days sooner.

69 %
Critical violations found in first half of schedule (model-ranked list) (Sep-Oct 2014 pilot)
55 %
Critical violations found in first half of schedule (standard practice) (Sep-Oct 2014 pilot)
7.5 days sooner on average
Earlier detection of violations (Sep-Oct 2014 pilot)
1,637 establishments
Establishments in pilot comparison (Sep-Oct 2014)
178 of 258 establishments
Establishments with critical violations found via model list (Sep-Oct 2014)
37 establishments
Estimated additional violating establishments caught in first month (2014)
Chicago's Food Inspection Forecasting Model — Ranking Restaurants by Violation Risk to Catch Problems Sooner

Details

Promoter
Chicago Department of Public Health
Period
2014–2019
Keywords
public health, food safety, municipal government, predictive analytics

Context

In 2014, Chicago's Department of Public Health, working with the Department of Innovation and Technology, the Civic Consulting Alliance and Allstate Insurance, built a machine-learning model to forecast which food establishments were most likely to have critical food-safety violations.

Objectives

Reallocate a fixed number of food-safety inspections more efficiently by prioritising establishments most likely to have critical violations, without reducing oversight or replacing inspector judgment.

Activities

The model scored licensed establishments using about 100,000 past inspections, nearby 311 complaints, weather, burglary reports, licensing status, facility type and time since last inspection. A formal pilot ran September-October 2014, comparing the ML-ranked inspection order to Chicago's normal complaint- and rotation-driven scheduling on 1,637 establishments, of which 258 had critical violations.

Results

Inspectors working the model's list found 69% of establishments with critical violations (178 of 258) in the first half of the schedule, versus 55% under standard practice, and found problems roughly 7.5 days earlier on average. The city estimated the model would have caught 37 additional violating establishments in the first month alone. An independent 2019 hindsight analysis (arXiv:1910.04906) reproduced the results, finding the reported gains directionally robust while flagging methodological caveats around how the original comparison was constructed.

Conclusions

Chicago published the full source code, training data and evaluation methodology openly on GitHub, making the project a widely cited reference case for open, auditable government risk-scoring, though no confirmed case of another city operationally adopting the codebase was found.

Implementation

Indicative cost
Low (< €50k)
Time to results
Medium (1–3 years) — Built starting 2014; formal pilot evaluation September-October 2014; independent academic hindsight analysis published 2019 (arXiv:1910.04906); practice period 2014-2019.
Staffing & skills
Chicago Department of Public Health, Department of Innovation and Technology, Civic Consulting Alliance, Allstate Insurance (partner)

Conditions for success

  • Every flagged establishment still received a full human inspection rather than the model replacing inspector judgment
  • Open publication of source code, training data and evaluation methodology on GitHub, enabling independent verification

Common failure modes

  • Independent 2019 hindsight analysis flagged methodological caveats around how the original pilot comparison was constructed
  • No confirmed case of another city operationally adopting the codebase despite open availability

Commonly funded by

National / regional programmes

Indicative funding routes for practices of this type — always check each programme's current calls and eligibility rules.

Replication kit

Reusable artefacts from this practice — as published by their sources.

Do you run this practice? Claim it — verified implementers get a public contact pathway and can propose corrections.

Data sources

Where this practice's information was retrieved from, and when.

Attachments

Similar practices you may find useful