Porter County, Indiana’s Food Service Inspections page pairs two kinds of files in its 2025 monthly archive: an Inspection Report that lists visits and counts, and a Violation Report that gives dated, coded observations. The layout changes by period: March 2026 and later months on the current page have a single Inspection Reports link. Check the actual files offered for your month rather than assuming a second link is missing. A count in the first file points you to the second, where the inspector’s observations are. If the same establishment appears several times in one month, read each visit by its own date and purpose.
How to read Porter County’s Inspection Report and Violation Report
Choose the year and month on the county page. In the inspection file, find the facility using its name and address. Write down each row’s date, purpose and number of violations. A repeated name can mean a routine visit followed by one or more return visits; keep each row separate. The column headed “Number of Violations” is a count for that dated visit.
For a month with paired files, open the Violation Report for the same month. Search the facility name and match the inspection date as well. This file separates observations into P (priority), Pf (priority foundation) and C (core) categories, using the county’s definitions on its inspections page. Read the code and observation together. A “Corrected” entry belongs to the observation in that dated record; earlier visits and anything after the last posted report have their own records.
An August 2025 example: one routine visit and three follow-ups
The county’s August 2025 visit file contains an address-matched establishment with a routine visit and three later follow-ups. Its separate violation file supplies coded observations on the routine visit and two of the return dates. The example is about how the files connect, without a judgment about that establishment’s current condition.
| Visit date and purpose | Count in inspection file | What to check in the violation file |
|---|---|---|
| August 7, 2025 — routine | 15 | Read the individual categories, codes and observations dated August 7. |
| August 11 and 20 — follow-up | 1 on each date | Look for the observations bearing each return date; compare the issue, not just the count. |
| August 22 — follow-up | 0 | A zero-count visit lists no new violation there; the August 7 routine findings still stand on their date. |
The county says a priority violation that cannot be corrected during a visit calls for follow-up to verify correction. That explains why a return may be needed. The dated rows establish whether a return was recorded in this example. The planned return and each dated visit describe different parts of the record.
When a Porter County visit has no row in the violation file
If the monthly violation file has no row for a visit with a zero count, that is consistent with no violation listed for that visit. Which earlier observations were checked again is a question for the county, since a follow-up can be limited. If an expected return is missing from the same month, check the next month’s inspection file before concluding the public sequence ended. Record the facility address, visit date and code when asking the Porter County Food Service Division for clarification.
A focused request is easier to answer than “Was this restaurant cleared?” Identify the routine date, each return date, and the specific code you need traced. Ask whether the later visit checked that item and request the underlying inspection form if the summary leaves the answer unclear. If the question concerns a closure or reopening, ask for the dated administrative order and any release or approval as separate records.
For the broader meaning of a follow-up, see the reinspection guide. The report-reading guide explains why a violation category, inspector note and visit date answer different questions. Porter County Food Service Inspections page and both August 2025 files checked October 16, 2026.