Property-management workflow

Monitor the city-published records tied to the properties you manage.

ViolationNet organizes public code-enforcement records around the specific addresses your team selects, so you can review an agency-published signal with its source and date before routing follow-up.

01 — SELECT

Choose the addresses that matter

Add the properties your team is authorized to monitor. Unit details and city-specific address formats matter because public records vary.

02 — REVIEW

Keep the record in source context

Review the city-published category, status, date, and available case reference. Publication timing and fields vary by jurisdiction.

03 — VERIFY

Route verified work internally

Confirm the agency’s current case before assigning maintenance, legal, asset-management, or resident-facing follow-up.

Bring a bounded portfolio list when it fits your workflow

Portfolio users can upload a UTF-8 CSV of up to 100 selected properties using address, city, and state columns (with an optional nickname). Each row is checked against the currently supported-city inventory before it is saved; unsupported, incomplete, or duplicate rows are reported instead of being silently monitored.

Download the CSV template to see the exact column format before starting setup. The example rows are placeholders; replace them with properties your team is authorized to monitor.

The initial screen shows a bounded source-backed match count when that scan is available. It is a setup receipt—not a complete inspection, legal conclusion, or guarantee that every public record will match an address.

A simple operating procedure for selected properties

  • Review the city’s coverage and source context before relying on a market.
  • When a matching record appears, preserve the visible source, case reference, date, and status.
  • Open or contact the issuing agency to confirm the record’s present state and instructions.
  • Assign the verified item to the appropriate operational owner, then track internal resolution separately from the public record.

Coverage and matching limits stay visible

Supported cities do not all publish the same fields, history, or refresh cadence. An address match is only as complete as the public record; owner or mailing context is available only where that source publishes it. ViolationNet does not replace inspections, legal advice, agency correspondence, or a compliance program.

Check a short portfolio city list, review city coverage and source dates, or read the address-level workflow guide.

Multifamily operations teams: use the selected-building workflow for a focused property list, then keep agency verification and internal routing separate. See the multifamily monitoring workflow →

Commercial property operations teams: use the same selected-property workflow for office, retail, industrial, hospitality, or other non-residential properties—then verify meaningful records with the issuing agency. See the commercial-property workflow →

Start with the properties you already manage.

Use a source-backed monitoring workflow for selected addresses, then verify each meaningful record with the city or agency that published it.

Start a 7-day monitoring trial