DBPR inspectors logged 2,655 restaurant inspections from August 25 to September 1, 2026. In that window, 87 inspections ended with an emergency-order recommendation, while 24 closure-status license records landed inside the same seven-day window. That split is the story of this week. The paper trail is hotter in the inspection file than in the inactive-license ledger.
The named edge of the file runs through no in-window named cases. These are not the only restaurants with problems, but they are the five most anomalous publishable rows when inspection severity, recent history, peer-cuisine context, emergency-order history, and license status are stacked together.
The Big Five
Current-week anomaly cases
Source window has zero qualifying records for this table.
Raw counts mislead -- Putnam County losing 4 places is different from Miami losing 4. Use the rate or per-capita column for defensible comparisons. Methodology details linked above.
The Trend Section
This week produced 2,655 inspections versus a trailing-four-week average of 3258.8 per week. Emergency-order recommendations were up 7.1%, at 87 this week against 81.2 per week in the comparison window. High-priority violations ran down 3.7% on a per-inspection basis: 1.00 this week versus 1.04 across the trailing four weeks.
The closure-status ledger was quieter: 24 current-week closure-status updates versus 22.5 per week in the prior four-week window. That does not make the week clean. It means the immediate signal is inspections, callbacks, and emergency-order recommendations before the license-status file catches up.
The Cohort Movers
Pinellas County: 0 current-week anomaly rows, versus 0.2 per week across the prior four weeks. County moves matter because inspection staffing, tourist volume, and license density are local before they are statewide.
What to Watch Next Week
The 90-day closure model is not a next-Monday prophecy. It is a lead sheet. The names below sit at the top of the calibrated file, and the structural reasons are printed in plain language so a reader can audit the call before reacting to it.
Methodology
Methodology: IRL combines DBPR inspection history, high-priority violation counts, emergency-order dispositions, ORSM anomaly bands, and license context. Ratios compare the latest inspection to that restaurant's prior high-priority baseline; cohort percentiles compare the same count to city, county, or statewide cuisine peers when the local sample is too small.
Data sources: License records. Built from DBPR public inspection records, Florida Sunbiz business filings, and Foursquare/OSS location data. All counts are derived from public records — no estimates or projections unless labeled as forecast.