How the numbers are made
Methodology and limits
Every figure on this site is computed from public records. Public does not mean complete or error-free, and several steps involve inference. This page says where.
This report summarizes historical Florida DBPR records. A past emergency closure or administrative fine does not necessarily describe an establishment's current condition or compliance status. Associations based on names, dates, or incomplete ownership records may be inferred rather than confirmed. A current license holder may not have operated the establishment when a historical event occurred. Consult the original DBPR records before drawing conclusions about a business or individual.
Sources
- Emergency closure orders: weekly extracts from DBPR (closures dated 2021-12-27 through 2026-11-13).
- Administrative fines: monthly files from DBPR, from 2015-01 (through 2026-10). February 2024 is missing: the state serves a copy of January's file at that address.
- License rosters and license-holder changes: the per-district food-service rosters (as of 2026-11-18) and the state's records of approved license-holder changes.
- Inspection visits: the state's inspection extracts, from fiscal year 2016–17.
Each file is checked by content before use: the state's server answers a request for a missing file with its home page, so a successful download is not proof of data.
How a fine is associated with a closure
The two datasets share no incident identifier, so every association is inferred. Neither a license match nor a date window establishes that a fine was for a particular closure; the match does not consider violation type or closure condition. Two things are involved, and they are separate:
- Which license. Fines and closures are joined on the license number (fines carry a letter prefix such as SEA; closures use the bare digits, and the digits are compared). When a fine's license has no closure records at all, the association falls back to the business name and city. A name-and-city association is provisional: a different business can share a name and city. These are left out of every total and ranking and are summarized separately on the businesses page.
- Which dates. A closure is associated with a fine when it is dated
within a window before or after a fine date. Three relationships are
recorded:
- Violation-date proximity: within 60 days of the violation date.
- Order-date proximity: within 365 days of the final-order signature date, because orders are signed months after the violation. Where only this window matched, it is described as nearer the violation (the closure within 180 days of the violation date) or further from it (more than 180 days, or no violation date).
- Both windows.
A fine case is counted once, using its closest date relationship to any closure. Dollar amounts are summed per administrative case, never per associated closure. Where a case was published more than once, the latest order is kept. The amount is the figure in DBPR's final-order field; the records do not show whether it was paid or collected. 807 of 39,519 fine cases have no amount in the source; they are counted as cases but add $0 to every total, so dollar totals cover only the cases with a recorded amount. A true $0 amount and a missing amount are kept distinct in the build.
License holders
- The name shown is the licensee of record: the party holding the license in the state's files. It may be a landlord, a holding company or a franchisee, and is not necessarily who ran the establishment. Some are individuals. A current license holder may not have held the license when a historical event occurred.
- A fine is associated with the holder on record on the date of the final order (or, if that is missing, the violation date), and a closure with the holder on record on the closure date, using the state's record of approved license-holder changes. When no transfer is recorded for a license, the historical holder may be unknown; the current roster alone cannot verify past ownership. In that case the current roster holder is shown as an inference.
- Owner-change history covers 2017-07 to 2026-11, except 2026-02 to 2026-06, where the state published no change records. Cases with no holder on record are counted on the license-holder report and left out of holder totals, so holder figures are minimums.
- Licenses listed under different holders in different district rosters (mostly mobile vendors) keep the first listing.
How to check a record
- Take the license number shown in the table (the business and license-holder tables list it).
- Look it up in DBPR's own license search (by name or license number) to see the license holder, location and status DBPR shows now.
- The records behind this analysis are DBPR's downloadable public-record files,
listed on its public records page:
weekly emergency-closure files (
EOS_Weekly_Extract_YYYY-MM-DD.xlsx), monthly administrative-fine files (rdarMMYY.csv), license rosters, license-holder change files and inspection files. A fine case is identified by its case number (for example1--2020037004), a closure by its license, date and approval time. - Each figure is computed once per fine case or closure event. If a record here does not match DBPR's, use the corrections contact below with the license number and the page.
Grouping license-holder names
Names are grouped to merge punctuation, spacing and legal-suffix variants (“NORA GRACE LLC” and “NORA GRACE, LLC”). A short hand-curated list also merges named corporate families and spelling oddities; those merges are editorial judgments, not verified legal identity. Two different people with the same name cannot be told apart, and one holder's name spelled differently may be split.
Rates and trends
Where a figure is shown per 10,000 licenses, the numerator is historical closure events over the whole record and the denominator is the licenses on today's roster. It compares places against today's license population; it is not an annual rate or the probability that a license is closed. Raw counts are shown beside it. Closures that cannot be mapped to a county are excluded from county figures; the trends report says how many. A closure with no reopening date found in the available records is not the same as a closure that never ended.
The closures page shows how often a license had another closure within 730 days after its first closure that listed a given condition. A license whose first such closure is less than 730 days before the last closure on record has not had the full period, so it is counted separately and left out of the share. This describes what the records show; it says nothing about what any establishment will do.
How the numbers are checked
Each time the site is updated, 35 automated checks run on how this analysis handled the data, and the update is not published unless all of them pass. The last full run was on 2026-11-19. They test our processing, not whether the state's records are right, and they do not test whether a fine-to-closure link or an owner attribution is the correct one (those are inferences; see above).
Reconciliation: every record accounted for between steps, and every figure printed on a page agreeing with the underlying tables and with the other figures it must add up to.
- Closure events = single-closure + repeat + unlicensed-vendor events.
- The repeat-closure list names exactly the licenses closed 2+ times, with the right counts.
- Each repeat row's date list is as long as its count.
- Unlicensed-vendor file accounts for every placeholder-license closure.
- The fines table has one row per case number.
- Every matched pair's fine exists in the fines table with the same amount.
- Every matched pair's closure exists in the closures table.
- Every pair records a valid match method and the closure's license.
- License-identity pairs share a license, and name-and-city pairs only occur where the fine's license has no closures.
- License-identity pairs + name-and-city pairs = all pairs.
- Business report headline figures equal the underlying tables.
- Business report states how many fine cases have no amount.
- The seven district tabs add up to the statewide figures.
- License-holder report: recorded + inferred + unresolved cases = matched fine cases.
- License-holder report: recorded + inferred + unresolved amounts = matched amounts.
Independent recomputation: the headline figures rebuilt straight from the raw state files by a separate, simpler implementation that shares no parsing or matching code with the main one, then compared with the published figures.
- Closure events recomputed from the raw weekly files = the closures table.
- The same licenses and dates appear in both, in both directions.
- Restaurants closed 2+ times recomputed from the raw files = the repeat-closure list.
- Fine cases recomputed from the raw files = the fines table.
- Fine cases with no amount recomputed from the raw files = the fines table.
- Total fine dollars recomputed from the raw files = the fines table.
- Every case carries the same dollar amount in both.
- Every case carries the same final-order date in both.
- The independent reader could interpret every fine row.
- The fines a simple license + 60-day rule matches are exactly the license-identity pairs within the violation window.
- Every name-and-city pair is explained: the fine's license has no closures of its own and a closure with that name and city exists.
- License-holder evidence recomputed from the transfer and roster tables = the license-holder report.
- Closure-behavior report: event, re-open and no-re-open counts recomputed from the closures table.
- Closure-behavior report: days-to-re-open buckets recomputed from the closures table.
- Closure-behavior report: count of licenses with 2+ closures = the repeat-closure list.
- Trends report: closures per condition recomputed from the closures table.
- Trends report: the license denominator = licenses on the roster.
- Inspections report: visit and establishment counts recomputed from the visits table.
- Inspections report: visits by type recomputed from the visits table.
- Inspections report: visits by disposition recomputed from the visits table (the rest grouped as 'everything else').
Currency
The data is refreshed when the state publishes new files, which is weekly for closures and monthly for fines. License holders can change after the data date, and records change at the state's end too, so a figure here can differ from what DBPR shows today.
Corrections and changes
Email corrections@civicrecordlab.com with the license number, the page and table where you saw the figure, and what you believe is wrong, ideally with the DBPR record that shows it.
Each request is checked against the original DBPR records. If the error is in this analysis it is fixed in the next update and listed below with the date. If the original DBPR record is itself wrong, the figure is left as published by DBPR and the request can be sent to DBPR. Material changes to how figures are calculated are listed here too.
No corrections have been made so far.
This is an independent analysis of public records. It is not produced by, endorsed by or affiliated with the State of Florida or DBPR.