Try looking up a restaurant’s health inspection record using your city’s official portal. Depending on where you live, you’ll land on a Socrata data table, a state health department search form, a county ArcGIS database, or — if you’re lucky — a page that actually loads on a phone.
This is public data. Paid for with public money. Generated by public employees. About the places where the public eats. And in nearly every case, the system was designed for the inspectors and the agencies — not for you.
Compliance Theater
The inspection system is a regulatory compliance tool. Health departments need to track which restaurants have been inspected, what was found, and whether corrective action was taken. The database supports the enforcement workflow. Consumer access was an afterthought.
The data is “available” in the sense that it’s not classified. But the presentation assumes you already know how the system works, what the codes mean, and how to interpret the results. In some cities, the scoring runs backwards. In others, the same violation code means different things depending on when the inspection happened. In one city we cover, the inspection format changed three times in eight years.
Publishing a dataset that requires a data engineer to interpret isn’t transparency. It’s compliance. It checks the legal box without delivering the public benefit.
Visibility Changes Behavior
The notable exception is mandatory letter-grade display — the big A, B, or C posted in the restaurant window. Research on these systems shows measurable impact. When the grade is on the wall, restaurants fix their problems faster. When diners can see the score, they make different choices. Surveys consistently find that large majorities of consumers use posted grades when deciding where to eat.
But most American cities don’t require grade display. Most publish the data somewhere on a website and leave it at that. The result is a system where the information exists, technically, but the average person standing outside a restaurant with a phone has no practical way to use it.
What We’re Doing About It
Eat or Beat exists because the gap between “public data” and “useful data” is worth closing. The inspections are already happening. The violations are already documented. The only thing missing is translation — turning government records into something a normal person can use in five seconds.
One word. One score. Full inspection history. No PDFs. No Socrata queries. No acronyms.
We’re not doing anything the health department couldn’t do. We’re just doing the part they were never asked to do.
Every score on Eat or Beat is computed from public health-department records. We don’t visit restaurants. We don’t accept payments from restaurants. We translate what’s already on file.