You are standing outside a restaurant in a new city, phone in hand, looking at a number. Maybe it's a 92. Maybe it's a letter in a window. Either way, your brain does the thing brains do: it compares. 92 is better than the 87 I saw back home, so this place must be cleaner.
That comparison is almost always wrong — not because the numbers are fake, but because they are not the same kind of number. Restaurant inspection scoring in the United States is set locally. There is no single national grade. What you are actually comparing is two different measuring systems that happen to both produce a number between 0 and 100.
There is no national restaurant grade
The FDA publishes a model Food Code — a detailed reference document covering things like cooking temperatures, handwashing, cold-holding, cross-contamination, and pest control. It is a model. It is not federal law binding on restaurants.
Adoption happens at the state level, and enforcement usually happens below that: county health departments, city health departments, or district offices. Each of those bodies decides:
- Which edition of the Food Code they adopted, and what they amended
- Whether results are expressed as a letter, a numeric score, or a pass/fail status
- How many points each violation costs
- Whether the result must be posted in the window, or only published online
- How often a given restaurant gets inspected
- How re-inspections and appeals affect the posted result
Change any one of those and the same kitchen produces a different-looking result. Change several and the two scores stop being comparable in any meaningful way.
Three scoring shapes you'll actually run into
Letter grades. Some jurisdictions post an A, B, or C in the window. The letter is usually derived from an underlying point total, and the cutoffs are local. A letter is easy to read and hard to interpret — an "A" can represent a wide band of underlying performance, and the width of that band differs by city.
Point scores. Many health departments start a restaurant at 100 and deduct for each violation found. Here's the trap: in some systems a higher number is better because you kept your points; in others the number reported is the count of demerits, so a lower number is better. Reading one convention with the other's assumptions inverts the meaning entirely.
Pass / fail or satisfactory / unsatisfactory. Plenty of jurisdictions publish no number at all. The inspection either meets standard or it doesn't, with the detail living in the written report. This is not a weaker system — it can be paired with very aggressive enforcement — but it collapses everything into a binary that can't be ranked against a 94.
Weighting matters more than the scale
The scale is the part people notice. The weighting is the part that actually decides the score.
Modern food-safety inspection distinguishes between violations that directly cause foodborne illness and violations that are about upkeep or documentation. In current Food Code language these are broadly priority, priority foundation, and core items. Older systems used "critical" and "non-critical."
A priority item is something like holding chicken at an unsafe temperature, or a food handler not washing hands between tasks. A core item might be a cracked floor tile, a missing thermometer sticker, or a torn door sweep. Both are real. Only one of them is likely to make you sick tonight.
Now consider two jurisdictions. In the first, a temperature violation costs a large chunk of the total and a cosmetic issue costs almost nothing. In the second, points are spread more evenly across categories. A restaurant with one serious temperature problem and a spotless facility might post a middling score in the first city and a strong score in the second. A restaurant with no serious problems but a long list of maintenance items might do the reverse.
Same kitchens. Same violations. Two different numbers — and neither number is lying.
The inspection date is doing more work than the score
Every posted score is a snapshot of one visit. It describes what an inspector observed during a window of a few hours, on one day, possibly months ago.
Inspection frequency is also local and usually risk-tiered: a facility doing complex cooking and cooling of potentially hazardous foods generally gets visited more often than a coffee counter that reheats packaged pastries. So a "current" score in one city might be six weeks old and in another might be more than a year old.
This is why a single number, stripped of its date and its jurisdiction, is close to meaningless as a comparison tool. An 88 from last month tells you more than a 96 from two years ago.
What re-inspections do to the picture
Many jurisdictions let a restaurant correct problems and be re-scored. That's good policy — the goal is compliance, not punishment. But it affects what you see on the wall.
Depending on local rules, the posted result may be the initial inspection, the re-inspection, or the most recent of any type. Some places post a grade-pending card while an appeal or re-inspection is in process. Two restaurants displaying the same letter may have arrived there very differently: one passed clean the first time, the other failed, fixed, and passed on the second visit.
The full inspection history usually shows this. The window card usually doesn't.
How to actually read a score
You don't need to memorize fifty scoring systems. You need four habits.
- Anchor to the jurisdiction, not the number. Before you judge a score, know which health department issued it and roughly how their scale runs. One search answers this, and the answer is good for every restaurant in that city.
- Check the date first. Recency beats magnitude. Look for the inspection date before you look at the result.
- Read the violation types, not just the total. Most health departments publish the itemized report. Scan for temperature control, handwashing, and cross-contamination. Those tell you more than the arithmetic.
- Look at the trend. One bad inspection in an otherwise clean five-year history is a bad day. Four mediocre inspections in a row is a pattern. Patterns are the actual signal.
Why cross-city comparison is a trap worth naming
The instinct to rank things is useful — it's how we make fast decisions with limited information. But cross-jurisdiction comparison of inspection scores fails in a specific and unhelpful way: it produces false confidence in both directions.
It makes travelers overly suspicious of restaurants in cities with strict, aggressive point deductions, where a lower score may reflect nothing more than a demanding system doing its job thoroughly. And it makes travelers overly relaxed in cities with generous scales or infrequent inspections, where a high number may simply reflect less scrutiny.
The healthier mental model: a score is a comparison tool within its own city, and a reading-comprehension exercise everywhere else. Within one jurisdiction, ranking restaurants by score is reasonable — same scale, same inspectors, same rules. Across jurisdictions, the number is a pointer to a report you should actually open.
The report is the product; the score is the packaging
Health departments do serious work, and most of them publish it. The written inspection report is the real artifact: what was observed, what category the violation fell into, whether it was corrected on site, and what the follow-up was.
The score exists because a report is too long to put in a window. It's a compression of that report — and like any compression, it loses information. Different cities chose to lose different information.
So the practical move when you're somewhere new is simple. Don't compare the number to the last number you saw. Find the report behind it, check the date, and read the few lines about temperature control and handwashing. That takes about ninety seconds, and it's a far better use of your attention than doing arithmetic across two systems that were never designed to be added together.
Look up any restaurant's real inspection history — free
FoodCodeScout covers 57,000+ restaurants across NYC, Seattle, and LA with real health-department records. Takes 30 seconds.
Search your city →About the author — Rick Jenkins is the founder of AI Revenue Forge. ARF builds vertical-specific AI virtual receptionists for service businesses in HVAC, dental, medspa, real estate, home health, credit repair, and pawn shops. Headquartered in Charlotte, NC. Part of Jenkins Worldwide Enterprises.