A restaurant health inspection report is a dated record issued by the authority responsible for the exact facility. Identify that authority, match the licensed premises and inspection event, read the local result legend, then connect each finding to correction, reinspection, closure, or reopening evidence. Do not compare raw letters or numbers until the jurisdictions’ methods are known.
Checked August 26, 2026 against the current routes published by U.S. Food and Drug Administration, U.S. Food and Drug Administration, New York City Department of Health and Mental Hygiene, Maricopa County Environmental Services Department, District of Columbia Department of Health.
The FDA Food Code is a model, not a national report database
The FDA Food Code page describes the Code as a model that regulators use to develop or update retail-food rules. FDA’s adoption overview says restaurant oversight in the United States is typically handled at state and local levels and documents variation in adoption. That is why the correct report source starts with the restaurant’s jurisdiction, not a single federal grade lookup.
Local result systems cannot be translated by label alone
A lower number can be better in one system, another authority can issue voluntary letters, and another can use pass-fail without grades. Record the authority’s wording and rules in force for the inspection date. A shared letter does not establish a shared threshold, violation model, or follow-up process.
| Official example | What its source shows | Lesson for report reading |
|---|---|---|
| NYC Health ABCEats | Violation points correspond to local letter grades; lower scores are better | Use NYC’s point direction and event rules only for NYC records |
| Maricopa County ratings | A-D participation is voluntary and NP still accompanies an inspection | Separate participation from the report’s findings |
| DC Health Division of Food | DC uses pass-fail rather than letter grades and links separate closure/restoration material | Do not manufacture a letter or merge disposition with enforcement |
Classify each source layer before drawing a conclusion
| Source layer | Question it answers | Common mistake |
|---|---|---|
| Authority/program page | Who regulates the address and where records are published | Assuming the postal city owns the inspection |
| Facility profile | Which licensed premises and identifier the history belongs to | Using a chain name as the match |
| Inspection event | What happened on a date and what type of visit it was | Treating a complaint or follow-up as a full routine visit |
| Legend/code method | What the displayed grade, score, status, or risk category means | Translating another jurisdiction’s scale |
| Later enforcement record | Whether correction, reinspection, closure, or restoration was documented | Calling an old result the current status |
Capture the identity, event, finding, and later record together
The worksheet below is the core reading asset. Complete it from the official facility and event pages, not from a search-engine snippet. Keep one inspection per event row and preserve the exact terminology. When a field is not published, label it unavailable through that source instead of filling it with an assumption.
Restaurant inspection record capture worksheet
An inspection search is useful only when another person can reproduce the match. Save the inspecting authority and the exact facility record before interpreting a score or violation. The seven fields below separate the restaurant identity, the dated visit, and the later enforcement history so that an old grade, another branch, or a routine inspection is not mistaken for the current status.
| Field to capture | What to record exactly | Why it changes the answer |
|---|---|---|
| 1. Facility identity | Licensed name, trading name, and inspecting authority | A chain name can return several branches or a former operator. |
| 2. Address | Street number, unit, city, county, state, and postcode or ZIP | Nearby branches can use different inspection systems and scales. |
| 3. Facility or permit ID | The permanent identifier shown by the official database | Names change; the authority’s identifier is usually the stronger match. |
| 4. Inspection date and type | Date plus routine, complaint, follow-up, pre-opening, or other label | A complaint visit and a routine inspection may not be scored the same way. |
| 5. Result, score, or grade | Exact wording, number, letter, status, and local scale | Numbers and letters cannot be compared across unlike jurisdictions. |
| 6. Violations | Code, description, severity label, and correction status | A headline score can hide which finding caused enforcement or follow-up. |
| 7. Corrective and follow-up record | Correction date, reinspection, closure, reopening, appeal, or later visit | A later entry can supersede the result that first appears in search. |
Read the report in a reproducible order
- Confirm jurisdiction. The restaurant’s postal city does not always identify the agency that inspects it. Start with the city, county, state, council, or regional authority responsible for the exact address.
- Match the establishment. Compare the licensed name, branch address, suite, and facility or permit ID. Do not rely on a map pin, review listing, or chain name alone.
- Open the dated detail. Record the inspection date and type before reading a score. A current profile page can contain several visits with different purposes.
- Read the local definitions. Open the authority’s legend, code, methodology, or FAQ. The same number can mean different things in different systems.
- Continue through the timeline. Check every later correction, reinspection, closure, reopening, appeal, or publication update before describing the current record.
When the report is missing, delayed, or older than expected
| What you see | Next check | Do not assume |
|---|---|---|
| No matching facility | Try the licensed operator, exact address, former name, permit ID, and neighboring jurisdiction. | That the restaurant was never inspected. |
| Only an old inspection | Check publication lag, archived records, open-data downloads, and the authority’s records-request route. | That the old result describes today’s operation. |
| Score without violation detail | Open the inspection PDF or detailed event record and the local scoring rules. | That a number explains the underlying findings. |
| Closure or suspension | Look for a later reinspection, reopening, reinstatement, appeal, or rescission. | That a historical enforcement action is still active. |
| Conflicting entries | Compare facility IDs, visit dates, update timestamps, and the authority that owns each record. | That the highest-ranking search result is the newest official record. |
Use the official restaurant record lookup guide to locate the correct authority and facility. Once the record is matched, use the restaurant score and grade guide for the local scale, and the inspection violation guide for finding and follow-up language. An inspection report documents what the authority published for a dated event; it does not guarantee present conditions, food safety, or future compliance.
Resolve conflicting records by provenance
Two official-looking results can conflict because they refer to different branches, operators, visit types, publication dates, or enforcement stages. Compare identifiers before comparing outcomes. Prefer the source owned by the responsible authority for the dated event, and retain the other record as a separate source until the mismatch is explained.
| Conflict | Test | Result to write |
|---|---|---|
| Same name, different address | Compare street, suite, and facility ID | Separate branch histories |
| Same address, different operator | Compare permit holder and effective dates | One premises timeline with an ownership boundary |
| Score card and detailed report differ | Check event date, inspection type, and update timestamp | Identify which item belongs to which event |
| Closure and later open status | Find closure plus reinstatement/restoration record | State both official dates |
| Portal result and records response differ | Compare requested period and document identifiers | Explain the access scope rather than choosing the larger count |
Use a conclusion ladder instead of a safety verdict
- Facility match: state the licensed premises and authority you verified.
- Event fact: state the inspection date, type, and displayed result.
- Finding fact: state the individual observation and local category without diagnosing illness.
- Action fact: state correction or enforcement only when the official record documents it.
- Current limit: identify the newest event reviewed and leave later conditions unverified.
An official inspection report supports a claim about the named facility and dated visit. A present-day claim requires the newest relevant official event, not a remembered grade or an isolated search result.
Download the restaurant inspection record worksheet
The CSV version turns the seven-field table into a reusable research sheet. Keep one row for each field, add the official source URL and lookup date in your working copy, and preserve later reinspections or reopening records instead of overwriting the earlier event.
Method and scope: Original worksheet by Restaurant Inspection Check, published August 6, 2026. It structures identity, visit, result, violation, and follow-up fields from an official record. It does not reproduce an authority’s report, certify a restaurant, or guarantee present conditions.
Choose the next guide from the unresolved field
If the authority is unknown, use Restaurant Inspection Check by City. If a code or observation is unclear, continue to Food Inspection Reports: How to Read Violations. If the first event is understood but its outcome is not, use the reinspection follow-up check instead of rereading the same score.