Who is this workflow for?

It is for refrigeration, exhaust/hood, plumbing, equipment, and facilities-service teams reviewing food-service customer facilities they already serve or are authorized to review.

Which sources are available?

The workflow is limited to named NYC Department of Health and Mental Hygiene, City of Chicago, San Antonio Metropolitan Health District weekly restaurant reports with the publisher total score preserved, Cincinnati Health Department, Public Health — Seattle & King County for Seattle-labeled records, Montgomery County Department of Health and Human Services for named local Maryland markets, Boston Inspectional Services Department, Southern Nevada Health District for exact Las Vegas facilities, Detroit Health Department, Minneapolis Health Department, New York State Department of Health outside the separate NYC workflow, Florida DBPR, and San Francisco Department of Public Health food-service sources. Detroit's publisher documents a reporting delay. Minneapolis and New York State remain searchable only while their publisher-date freshness guards are current, and the Montgomery County guide preserves its rodents-and-insects field separately from the publisher inspection status. Each source page identifies its publisher and historical date context.

Does a published record establish a service need?

No. A historical publisher record is source context only. It does not establish a current facility condition, a service need, or permission to contact a facility.

What can a Chicago food-service account check show?

For a selected Chicago facility with an exact DBA and street-address match, the workspace can return literal City of Chicago Business Licenses fields: license number, description, publisher status, term dates, and source link. Those source fields do not establish a current license, legal or compliance determination, health condition, or service need; the manual check does not enable ongoing license monitoring.

When can monitoring send an alert?

After an account's initial source baseline, an enabled account can receive an email when a later successful collection retains a newly collected matching publisher row. The alert describes source context and does not say an inspection just occurred.

What does the selected-account review queue show?

After setup, the private workspace can show one latest retained publisher row for each selected active account, with the issuing authority, publisher record date, source link, and match scope. It does not create a public facility directory or establish a current facility condition.

Selected account service docket

Keep a published record beside the kitchen-service account your team already supports.

For refrigeration, exhaust/hood, plumbing, equipment, and facilities-service teams: use named NYC, Chicago, San Antonio, Cincinnati, Seattle, Montgomery County, Boston, Las Vegas, Detroit, Minneapolis, New York State, Florida, and San Francisco food-service records as a source-dated review cue around selected customer facilities.

01 · ACCOUNT

Use facilities you know.

Add locations your service team already supports or is authorized to review. Keep the list tied to actual accounts, not a citywide directory.

02 · RECORD

Keep the publisher in view.

Review the issuing agency, inspection date, and published record context together. A historical row never becomes a present-tense condition claim.

03 · REVIEW

Route a source cue.

Confirm consequential information with the issuing agency and responsible facility team through your normal account process.

What monitoring can do after setup

Your first successful scan sets a historical source baseline. With property email alerts enabled, a later successful collection can notify your account only when it retains a newly collected publisher row matching a selected facility. The notice preserves source context; it does not say an inspection just occurred or establish a current facility condition.

When your team saves more than one selected account, the private source-record review queue can place one latest retained publisher row beside each active account. It keeps the issuing authority, publisher record date, source link, and exact match scope visible so historical context is not mistaken for a current facility condition.

Use the narrower workflow when it matches your account work

These selected-account workflows use a smaller literal publisher-text boundary in NYC and Chicago. They remain source-dated record research for facilities your team already serves or is authorized to review—not a service-need signal, restaurant directory, or contact workflow.

Hood, exhaust & grease serviceLiteral NYC “grease” or “ventilation” and Chicago “hood,” “grease,” or “ventilation” publisher text only.Review hood & grease account research

Refrigeration & food-service equipmentLiteral NYC and Chicago temperature-control publisher text only, with the source date kept visible.Review refrigeration account research

Check one existing account before trial.

Start with one food-service customer your team already serves or is authorized to review. The preview returns only a source-match receipt for named publishers, so you can verify the workflow before creating an account.

Current source register

This workflow is available only where a named official publisher supports the retained source record. Review field and date context before adding a facility.

New York CityNYC Department of Health and Mental Hygiene · publisher-labeled Critical findingsReview NYC source records

ChicagoCity of Chicago · Restaurant records with the publisher result preservedReview Chicago source records

CincinnatiCincinnati Health Department · source rows whose publisher description literally contains “Controlling Pests”Review Cincinnati source records

SeattlePublic Health — Seattle & King County · Seattle-labeled records with the publisher result Unsatisfactory preservedReview Seattle source records

BostonBoston Inspectional Services Department · Food Establishment Inspection records with the HE_Fail result preservedReview Boston source records

Las VegasSouthern Nevada Health District · exact Las Vegas facilities with B, C, or CLOSED publisher gradesReview Las Vegas source records

FloridaFlorida DBPR · food-service records with publisher high-priority counts preservedReview Florida source records

San FranciscoSan Francisco Department of Public Health · source rows whose publisher text contains “vermin”Review San Francisco source records

New named market: San Antonio, Texas

The San Antonio Metropolitan Health District publishes weekly restaurant reports. For a selected San Antonio account, ViolationNet preserves the dated publisher total score and individual report link together; a historical report is not a current-condition or service-need conclusion.

San Antonio, TXSan Antonio Metropolitan Health District · dated weekly publisher report and total scoreReview San Antonio source records

Chicago selected-facility license fields

For a Chicago food-service facility your team already serves or is authorized to review, the workspace can make a manual, exact DBA-and-street-address check of the City of Chicago’s public Business Licenses record. It returns only the publisher’s license number, description, status, dated term fields, and a source link.

Use it as a source check, not a conclusion.A publisher status or term date does not establish a current license, legal or compliance determination, health condition, service need, or outreach permission. The manual check does not activate ongoing license monitoring.Check a selected Chicago account

Primary publisherCity of Chicago Department of Business Affairs and Consumer Protection · public Business Licenses dataset.Open the City source

New named market: Montgomery County, Maryland

For named local Montgomery County facilities, the official source preserves a rodents-and-insects field separately from the broader publisher inspection status. Review both fields and the source date before using it in a selected account file.

Montgomery County, MDMontgomery County Department of Health and Human Services · source-dated historical fields, not a present service conclusion.Review Montgomery County source records

New named market: Detroit, Michigan

Detroit Health Department records preserve the publisher’s historical is_in_compliance field with its inspection date. The City documents a publication delay, so it is never treated as an immediate account alert or present facility condition.

Detroit, MIDetroit Health Department · dated historical source records with publication-delay contextReview Detroit source records

Named market: Minneapolis, Minnesota

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 facility condition or service conclusion.

Minneapolis, MNMinneapolis Health Department · dated literal publisher text with a source-date freshness gateReview Minneapolis source records

Named market: New York State

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 facility condition or service conclusion.

New York StateNew York State Department of Health · source-dated latest-inspection critical-count fieldsReview New York State source records

Source-receipt status

This is the status of ViolationNet's retained collection, not a publisher claim about a facility. The workflow never guesses from a missing receipt.

New York City · latest successful source collection: 2026-09-18.
Chicago · latest successful source collection: 2026-09-18.
San Antonio, TX · latest successful source collection: 2026-09-18.
Cincinnati, OH · latest successful source collection: 2026-09-18.
Seattle · latest successful source collection: 2026-09-18.
Montgomery County, MD · latest successful source collection: 2026-09-18.
Boston · latest successful source collection: 2026-09-18.
Las Vegas · latest successful source collection: 2026-09-18.
Detroit, MI · latest successful source collection: 2026-09-18.
Minneapolis · latest successful source collection: 2026-09-18.
New York State · latest successful source collection: 2026-09-18.
Florida · latest successful source collection: 2026-09-18.
San Francisco · no current successful source receipt is available; this does not mean zero records or no coverage.