Chicago publishes a pass / pass-with-conditions / fail result for every inspection. Violations are tagged Critical, Serious, or Minor. We reproduce the records and count them.
THE RECORDS.
THE SOURCES.
What we reproduce, where it comes from, and how to flag an error.
WHAT THE RECORDS ARE
Every restaurant page on EatOrBeat reproduces public health-inspection records from the agency that performed the inspection. The page shows the agency's own result — pass / pass-with-conditions / fail, or a letter grade, or a numeric score, or a tiered-violation summary, depending on the market — dated to the inspection it describes. The full inspection history is listed below the coin, with violations and severity labels in the source vocabulary.
EatOrBeat does not assign a verdict, score, or grade of its own. Arithmetic over the records — counts of inspections, dates, the last-10 strip, totals of high-band violations in the last 12 months — is presented alongside the official record.
PER-MARKET SOURCES
NYC DOHMH publishes letter grades (A/B/C) plus formal closure and reopen actions. Violations are tagged Critical or Not Critical. Grades and inspections are different official facts with different lifetimes — both are dated on the page.
Dallas publishes a numeric inspection score (100 = clean, deductions for each violation cited). Violations carry point values. We reproduce the score and the points. The current Dallas snapshot ends in February 2024 — anything more recent is not yet in the public dataset we read.
SF publishes a numeric inspection score and a result for each visit. Violations are categorized as High Risk, Moderate Risk, or Low Risk where the official record carries that field. We reproduce the records.
LA County publishes a letter grade (A/B/C) on the inspection placard and a point-deduction score per visit. Violations carry point values and a critical/non-critical flag. We reproduce both the grade and the point values.
Florida DBPR publishes a result (Inspection Completed / Warning Issued / Emergency Order Issued / etc.) and tiered violations: High Priority, Intermediate, Basic. Emergency-order closures appear on the coin when the most recent event is an unresolved closure; complied-callback or pass replaces it. We reproduce the records.
VIOLATION GROUPINGS
Some pages display a per-category violation count — for example, "Pest activity noted in 3 of 12 inspections." The categories (Sanitation, Pest, Temperature, Handwashing, etc.) are EatOrBeat's organization of official violation codes into topic nouns for readability. Every grouped finding traces back to specific violation titles in the inspection timeline below. The grouping is descriptive, not evaluative — the same code is in the same category for every restaurant in the same market.
LIMITATIONS
- The records are not real-time. Pages display the "records current as of" date for each market. Anything between that date and your visit is not yet reflected.
- Inspections happen at intervals. A restaurant inspected six months ago is not necessarily in the same condition today. Pages older than 18 months carry a staleness caveat.
- EatOrBeat is not a substitute for the source. The agency record is the authoritative version. Every detail page links to the dataset or the per- restaurant record so you can verify.
- EatOrBeat does not inspect restaurants and does not enforce health code. Concerns about a restaurant should be reported to the issuing agency.
REPORT AN ERROR
If EatOrBeat reproduced a public record incorrectly — a wrong date, a missing violation, a stale headline — let us know: corrections@eatorbeat.com. Include the page URL and a short description of the problem. We respond by email and update the page on the next weekly rebuild (or sooner for material errors).
If the underlying health-department record is wrong, EatOrBeat cannot change the source data — only its reproduction of it. Contact the issuing agency listed in the per-market source section above to dispute or correct the official record.