Skip to main content

How property managers track violations across many buildings

Last reviewed Oct 6, 2026 · Property management compliance

Most portfolios run on a rota of manual lookups recorded in a spreadsheet, which works until roughly the point where checking every building weekly stops being realistic. Beyond that, teams either accept gaps or move to monitoring the published data.

The arithmetic that decides this

Checking one building properly means HPD Online, the DOB property profile, DOB NOW, ECB Ticket Finder, OATH and 311. Done carefully, that is ten to twenty minutes.

Six buildings checked weekly is a couple of hours a week — tedious but entirely doable, and plenty of well-run small portfolios do exactly that. Forty buildings checked weekly is most of a full-time job, and it is work nobody enjoys, which means it is the first thing to slip when something urgent happens.

What slips is not uniform. People check the buildings they are worried about and skip the quiet ones, so gaps open precisely where nobody is watching — which is where a surprise is most likely to be sitting.

The four approaches, and where each stops working

Reactive only
Deal with what arrives in the post. Cheap, and it fails on the two things that matter most: service that does not reach you, and deadlines that are already running when the letter arrives.
A rota and a spreadsheet
Each building checked on a schedule, findings recorded. Genuinely effective at small scale. Breaks down when the schedule competes with urgent work, and depends on one person remembering the method.
Open Data queries
Query the city datasets directly for your buildings. Scales well and costs nothing but requires someone comfortable with the data, and the identifier matching is harder than it looks — particularly where sources publish no BIN.
Continuous monitoring
Something reads the sources on a schedule and tells you what changed. Scales past the point where attention does, which is the only real argument for it.

If you are building a process from scratch

  1. Fix the identifiers first

    BIN and BBL for every building, recorded once and verified. Everything downstream depends on querying the right building, and address matching is where portfolios quietly lose records.

  2. Decide who acts, per building

    A violation that reaches a central inbox reaches nobody. Name the person for each building who can actually send a contractor.

  3. Separate deadlines from information

    Most records are context. A few carry dates that convert into money — HPD correction windows, OATH hearings, authorisation expiries. Those need a different treatment from a notification.

  4. Write down how you verify a closure

    Deciding in advance what counts as "cleared" prevents the most common portfolio-level error, which is a building everyone believes is clean because somebody said so eighteen months ago.

Common questions

How often should a building be checked?

Most of the relevant city datasets refresh daily, so daily is the ceiling on usefulness. Weekly is a reasonable manual compromise. Monthly is long enough for a 24-hour Class C correction window and an OATH hearing date to pass unnoticed.

Can I just use NYC Open Data?

Yes, and for a technical team it is a sound approach — it is the same data the official lookups are built on. Budget for the identifier matching rather than the querying; that is where the real work is.

Is this something a managing agent should already do?

Many do, to varying standards. It is worth asking specifically which sources are checked, how often, and how you are told — the answers vary far more than owners expect.

Official sources

Rules and figures change. Check anything you are about to act on against the agency itself.

More in Property management compliance · All categories