Corrections Policy

InspectFL deals with public-record data, live updates, and original editorial analysis. When something is wrong, unclear, or outdated, we want to fix it quickly and transparently.

Correction scope at a glance

Official source

Florida DBPR

Coverage

65,529+ restaurants

Counties

67 statewide

Best contact

hello@inspectfl.org

If InspectFL displayed, summarized, linked, or interpreted something incorrectly, tell us. If the problem is with the official government inspection record itself, DBPR is the authority that must correct it.

Factual correction

We used the wrong number, date, name, status, link, or description and need to fix the published page.

Clarification

The page may be technically accurate but confusing, incomplete, or too easy to misread without better context.

Source-record update

The underlying DBPR record changed after publication, so the page needs to reflect the newer official data.

Technical bug

A page, filter, link, chart, or page-level data display is broken even if the source record itself is not.

How to request a correction

Email hello@inspectfl.org or use the contact form with the restaurant name, page URL, and a short description of the issue.
If possible, include the DBPR link, inspection date, license number, or screenshot that shows the mismatch.
We review the issue against the underlying public record and the live page behavior.
If the issue is on our side, we update the page and note the correction when appropriate.
If the issue is in the official state record, we may clarify that on our side, but the source correction has to come from DBPR.

What helps us fix it faster

The exact page URL on InspectFL
Restaurant name and city
License number or inspection date if you have it
A short explanation of what looks wrong
A DBPR link or screenshot when available

When we correct vs. clarify

We issue a correction when the published information is materially wrong: the wrong restaurant, wrong link, wrong number, wrong interpretation of the record, or a broken data display.

We issue a clarification when the page could mislead readers because context is missing, wording is too broad, or a source distinction is not obvious enough.

Important boundary

InspectFL can correct our own pages. We cannot rewrite or erase the official government record.

If your concern is that a DBPR inspection, disposition, or establishment record is wrong at the source, the source correction must happen with DBPR first. Once the public record changes, we can update our side.

Correction log

This page is the public log for correction notices that deserve visible disclosure. Smaller technical fixes may still be handled silently, but material factual or source-linking issues will be noted here.

To report an issue now, email hello@inspectfl.org or use the contact page.

April 2026 Restaurant page correction

Restaurant detail and DBPR source-link corrections

After a reader report, InspectFL reviewed restaurant-detail pages and found two separate issues affecting some restaurant records.

Some restaurant pages and related content were showing unverified violation labels derived from bulk CSV data rather than the restaurant's confirmed DBPR inspection observations. That display logic was corrected on April 27, 2026, and affected pages were updated to rely on verified observation data or safer summary-level wording when observation text was not yet available.
Some outbound DBPR inspection-detail links from restaurant pages used the wrong DBPR license parameter and could open an unrelated establishment's record. That link-routing issue was corrected on April 30, 2026, and restaurant pages now build DBPR source links with the proper visit ID and internal DBPR license ID.

These fixes did not change Florida DBPR's official records. They corrected how InspectFL displayed violation detail and how InspectFL linked readers to the official source record.