Start with locations you know.
Add facilities your organization operates, manages, or is authorized to review. Keep the list bounded to work your team actually owns.
Set a source-dated baseline around named NYC, Chicago, San Antonio, Cincinnati, Seattle, Montgomery County, Boston, Las Vegas, Detroit, Minneapolis, New York State, Florida, and San Francisco official food-service records for facilities your organization operates, manages, or is authorized to review. A later successful collection can alert an enabled account when it retains a newly collected matching publisher row.
Add facilities your organization operates, manages, or is authorized to review. Keep the list bounded to work your team actually owns.
Review the issuing agency, inspection date, and published record context together—without converting historical entries into present-tense claims.
Confirm consequential information with the issuing agency and responsible facility team before making any operational decision.
For selected food-service facilities outside the separate NYC workflow, the New York State Department of Health publishes a dated latest-inspection record with critical-count fields. The guide stays searchable only while the publisher-date guard is current; a row is historical source context, not a current restaurant status or operating conclusion.
The San Antonio Metropolitan Health District publishes weekly restaurant reports. For a selected San Antonio facility, ViolationNet preserves the dated publisher total score and individual report link together; a historical report is not a current restaurant status or operating conclusion.
Your first successful source scan establishes a historical baseline. With property email alerts enabled, a later successful collection can notify your account only when it retains a newly collected matching publisher row. The notice reports source context; it does not say an inspection just occurred or establish a current facility condition.
After setup, the private source-record review queue can show one latest retained publisher row for each selected active location, with its issuing authority, record date, source link, and match scope. It is not a public restaurant directory and does not state a current location condition.
Paste up to 10 facilities your organization operates, manages, or is authorized to review. We return only a source-match receipt for named NYC, Chicago, San Antonio, Cincinnati, Seattle, Montgomery County, Boston, Las Vegas, Detroit, Minneapolis, New York State, Florida, and San Francisco publishers, so you can test the workflow before setup.
ViolationNet exposes this workflow only where a named official publisher supports it. Review the source fields and date context before adding a facility.
For named local Montgomery County facilities, this official source preserves a rodents-and-insects field separately from the broader publisher inspection status. Review both fields in their historical source-date context.
Detroit Health Department records preserve the publisher’s historical is_in_compliance field with the inspection date. The City documents a publication delay, so this source is not presented as a current-status or immediate-alert feed.
Minneapolis Health Department records retain literal publisher FoodCodeText that mentions pest, rodent, or insect with its inspection date. The source guide stays searchable only while the publisher-date freshness guard is current; a historical row is not a current restaurant status or operating conclusion.
This is the status of ViolationNet's retained collection, not a publisher conclusion about a facility. A missing or stale receipt is shown as unavailable rather than as zero records or an implied recent check.
What this is: selected-facility, source-dated public-record research. What it is not: a restaurant directory, contact list, risk score, safety conclusion, compliance determination, or outreach authorization. Read the selected-location workflow guide.