NYC Housing Maintenance Code — Extermination and Rodent Eradication

Applies in: New York City

What does the Housing Maintenance Code require about pests?

Two things, and they are separate obligations rather than one restated twice. Keep the premises free from pests. Exterminate when they are there.

The first is a standing condition. The Housing Maintenance Code, at Title 27, Chapter 2 of the New York City Administrative Code, requires that a dwelling be kept free from rodents and from infestation by insects and other pests — and, importantly, free from conditions conducive to them. That is a continuous duty. It is not discharged on a schedule and it does not switch on when somebody notices something. A building either meets the standard on any given day or it does not.

The second is a duty to act. Where an infestation is present, the code requires extermination, and the article dealing with it is written in the language of eradication rather than management. The distinction between the two duties matters more than it looks. An owner who exterminates every time a report arrives is complying with the second obligation while potentially failing the first, because the conditions conducive to infestation are still in place and the premises are therefore not being kept free of them. This is exactly the gap that produces buildings with a decade of continuous service and a permanent pest problem.

Article 4 of that chapter is where the extermination and rodent-eradication provisions sit. It is a short piece of drafting and it does something unusual for a housing code: it addresses rodents specifically and separately, with provisions aimed at eradication and at the conditions on the premises that sustain rodent life. New York City’s rat problem is old enough to have its own statutory furniture.

Everything on this page is general information about published rules, written for owners, boards and managing agents. It is not legal advice, it cannot account for the facts of a particular building, and it should not be relied on in place of the code text or of your attorney.

Which buildings and which owners does Article 4 cover?

Dwellings in New York City, with the substantive obligations falling on the owner — and owner is defined more broadly than people expect.

The code reaches the residential building stock generally rather than only large apartment houses, though the intensity of some obligations scales with the type of dwelling. Multiple dwellings carry the fullest set. Private dwellings and one- and two-family houses sit under a lighter regime for some provisions. Where a building falls on those lines is a classification question with real consequences, and it is worth confirming with HPD rather than inferring from the number of mailboxes in the vestibule.

The definition of owner is the part that catches people. It is not limited to the entity on the deed. The code’s definition sweeps in a range of parties in control of the premises — lessees, agents, and others exercising control — which is why a managing agent cannot always treat a violation as somebody else’s document. For a cooperative, the corporation is the owner and the shareholder is not, whatever the proprietary lease says about who pays for what. For a condominium, the position is more layered, because the units are separately owned real property and the board of managers controls the common elements rather than the whole building; where the condition sits will often determine who is answering for it. That is a question for counsel and the governing documents, not for a pest contractor, and we say so rather than guessing at it.

A practical consequence worth naming: the violation is recorded against the building, not against the apartment. That single fact reframes most of the arguments boards have about pest cost. Whatever the internal allocation, the exterior record — the one a lender, a purchaser’s attorney or a prospective shareholder will pull — is a building-level record. The board-level implications of that are covered under co-op and condo pest management; portfolio owners and agents will find the operational version under property management pest control.

Where does the occupant’s responsibility fit?

Alongside the owner’s, not instead of it. The code gives occupants duties of their own, and those duties do not transfer the owner’s.

An occupant is expected to keep the part of the premises they occupy in a clean condition and to avoid creating conditions that invite pests — which is a reasonable and unremarkable requirement, and a real one. Accumulated refuse in an apartment, food left available, clutter that makes a unit impossible to inspect or treat, and interior water damage that goes unreported all make a building’s job harder and can genuinely be the source of a specific problem.

What the occupant’s duty does not do is give the owner a defense. If an inspector finds an infestation, the finding attaches to the building. The owner may have entirely legitimate grievances about how the condition arose and may have contractual routes to recover cost, and neither of those changes what the record says or what has to be corrected.

This produces a recurring and avoidable failure mode. A building that responds to a report by taking a position on fault — the apartment is dirty, the resident brought it in, the tenant should deal with it — spends weeks on an argument while the population continues. Buildings that resolve these matters quickly do the opposite: inspect first, establish where the population actually lives, correct what is theirs to correct, and settle the cost question afterwards with the managing agent and counsel on the basis of a finding rather than an assumption.

There is one more consequence that is worth flagging because it costs buildings real money. If residents believe they will be blamed, charged or evicted, they stop reporting. Delayed reporting is the single variable that most reliably determines what a bed bug or cockroach problem costs a shared building, and a blame-first posture buys the building silence rather than compliance.

What does an owner actually have to do to comply?

Look, act, correct the condition and keep the paper — with the emphasis on the third of those, because that is where the code’s language actually points.

Look. The standing duty to keep the premises free of pests cannot be met by a building that never looks at itself. In practice that means routine inspection of the common areas, the cellar and mechanical spaces, the refuse system, the yard and exterior at grade, and a real route into apartments. The separate annual inspection obligation created by Local Law 55 now sits on top of this and makes the looking explicit rather than implied.

Act on reports promptly. Response speed is the cheapest compliance investment a building makes. A report handled within days rarely becomes a 311 call; a report that sits for three weeks reliably does.

Exterminate properly, which means eradication rather than suppression. Where an infestation is present the code contemplates its elimination. In a shared building that generally cannot be achieved inside one apartment, because the population is not living in one apartment — it is living in the chase, the riser void, the compactor room or the cellar and foraging into whichever unit is currently easiest. Treating the unit alone reduces the count where somebody was looking and redistributes the remainder.

Remove the conditions conducive. This is the clause that does the work, and it is where the durable compliance lives. Water first: leaking supply lines and waste lines, condensation on uninsulated risers, a cellar that floods, a yard that drains toward the foundation. Then food and refuse: chute door gaskets, compactor room floor and drain, the interval between a bag leaving an apartment and material leaving the property, storage practice in the cellar. Then access: pipe penetrations, chase openings, joist pockets at party walls, cellar doors and sidewalk hatches, and the building’s connection to the sewer, where a failed house trap or a broken cellar line is a very common and very invisible rat route. The physical discipline behind that list is set out under structural exclusion, with the species detail under rodent control and cockroach control.

Register the property and keep the registration current. An owner cannot certify correction of a violation without a valid HPD registration, which turns an administrative lapse into an inability to close violations at all.

Keep the record. Findings by location, service and monitoring logs, notices and access attempts, a corrective register, photographs, certifications. The record is not an artefact of compliance. In any dispute, it is the compliance.

How does a complaint become a violation?

Through a short and fairly mechanical sequence: report to 311, HPD inspection, finding, violation notice, correction period, certification, and possible re-inspection.

The report. A resident who is not getting a response from the building can report the condition to the city, generally through 311. It is worth understanding that this route exists as a backstop and that residents use it when the building has gone quiet. Most 311 pest complaints are not really about the pest; they are about not having heard anything for two weeks.

The inspection. HPD sends an inspector to look at the reported condition. Access is the usual friction point: the inspector needs to get into the unit, and buildings sometimes learn about the visit only afterwards.

The finding. If the condition is present, the inspector records it. What is recorded is a condition at a location on a date, and that description is what the building will later have to answer.

The violation notice. The finding is issued as a violation against the building, classified by severity, with a correction period and a certification requirement attached.

Correction and certification. The owner corrects the condition within the period the class allows and certifies to HPD that the work was done. The certification has to be filed in the department’s required form and within its required window.

Re-inspection. The department may verify. A condition that reappears, or a certification that does not match what an inspector later finds, is a substantially worse position than the original violation.

The leverage, and it is considerable, is all at the front. A building with a working intake process — a logged report, an acknowledgment to the resident, an inspection within days and a visible response — resolves most matters before step one ever happens.

How does the code classify violations, and what do the classes mean?

By severity, on a scale running from non-hazardous through hazardous to immediately hazardous, with the correction window contracting sharply as severity increases.

The general architecture is easy to describe and the specifics are HPD’s to state. A non-hazardous condition is something the code wants fixed but does not regard as urgent. A hazardous condition is more serious and carries a shorter period. An immediately hazardous condition is one the code treats as requiring near-term correction and where the department’s own response is quickest.

For pests, the practically important point is that active vermin infestation in a dwelling unit is not treated as a cosmetic matter. It sits toward the serious end of the scale, and buildings that assume they have months to respond are working from the wrong assumption.

Two cautions, both deliberate. First, this page does not state the number of days allowed for any class, because those windows are set by the code and by the department and are precisely the sort of detail that a summary gets subtly wrong and a board then relies on. Read them from HPD. Second, classification is not always intuitive from the outside. A condition that a building considers minor can be classified more seriously than expected, particularly where the record shows the same finding recurring, and repeated non-compliance can itself escalate how a matter is treated.

What a board should take from the class system is operational rather than legal. The class tells you how much time you have, and time is the resource buildings most consistently misjudge, because the corrective work that actually resolves the condition — masonry, carpentry, plumbing — runs on a trade lead time and a budget cycle rather than on a violation clock. That mismatch is the reason to do the structural work before a violation exists rather than after one does.

What happens if a violation is not corrected?

Penalties that accumulate, the city arranging the work and charging for it, exposure in housing court, and a public record that follows the building.

Civil penalties. The code provides for penalties where a violation is not corrected within the period allowed, and for penalties where a certification is filed falsely. These are not identical and the second is treated far more severely, for obvious reasons. Penalties for uncorrected conditions can accrue over time rather than sitting as a single fixed charge, which is how a modest repair becomes a disproportionate cost through inattention alone. The figures are published; read them from the department rather than from a contractor.

The Emergency Repair Program. Where a serious condition is not addressed, HPD can arrange for the work to be performed and bill the owner. That charge can become a lien against the property, which changes its character entirely — it is no longer a bill the building can dispute at leisure, and it will surface in any refinancing or sale. It is also, invariably, more expensive than the same work procured directly.

Housing court. A resident can bring an HP proceeding to compel repairs, and an uncorrected pest condition supports habitability claims and rent abatement arguments. The building’s own file becomes evidence, and a file recording repeated findings without corresponding corrective work is evidence against the building rather than for it.

The public record. Open violations are visible. Purchasers’ attorneys pull them, lenders look at them, prospective shareholders and their brokers read them, and a pattern of open vermin violations affects how a building is perceived in ways that are hard to quantify and easy to feel. For a co-op, this is a shareholder-value issue as much as a maintenance one, which is often the framing that finally gets structural work funded.

And the compounding one. Every cycle of uncorrected condition, new complaint and new violation adds another dated entry demonstrating that the building knew. That accumulation is worse than any single penalty.

How does a building demonstrate compliance in practice?

With a file that shows the building looking, finding, assigning, correcting and verifying — over time, by location, with names and dates attached.

Six components, in the order buildings usually acquire them.

A baseline survey. A written assessment of the whole building at a point in time, with findings recorded by location rather than as a narrative. Every later claim of improvement is measured against it.

Service and monitoring logs with real content. A log entry naming a monitor location, a date and a count is evidence. An entry recording that the building was serviced is not, and a year of the second kind is a poor document to be holding when somebody reads it critically.

An access and notice record. Which units were noticed, when, which were inspected, which refused, and each re-attempt. This is the component buildings most often lack and the one that most often decides how a dispute reads, because a building that tried repeatedly and could not get in is in a different position from one that cannot show it tried at all.

A corrective-action register. Every structural and sanitation finding with a named responsible party, a target date and a closure record. Most of these items belong to trades other than the pest contractor, and a register full of unassigned findings is simply a documented record of known, unaddressed conditions.

Photographic evidence. Conditions found, and the same locations after correction. Before-and-after images of a sealed penetration or a rebuilt chute door are the most persuasive item in any file precisely because they show a change to the building rather than an activity performed on a date.

A trend. Counts and complaint volume over time by area or by stack, so the direction of travel is visible without reading a year of field notes. If the frequency of service never comes down, that is the diagnostic: the corrective work either did not happen or did not hold.

Two habits make all of this survive a change of board or agent. Keep the file in the building’s permanent records rather than in a director’s inbox, and make the reporting legible to somebody who was not there. Institutional memory in a co-op has a term limit of about a year.

How does this interact with Local Law 55 and the pesticide rules?

They stack. The Housing Maintenance Code sets the standing duty, Local Law 55 adds a defined inspection cycle and prescribed work practices on top of it, and the pesticide notification statutes govern how any application is announced.

Reading only one of the three produces a predictable misjudgement in each direction. A building that knows the code but not Local Law 55 tends to be reactive, responding well to complaints and never performing the periodic inspection the newer law requires. A building that knows Local Law 55 but not the code sometimes treats the annual inspection as the whole obligation, when in fact the standing duty to keep the premises free of pests applies on every other day of the year as well. And a building that satisfies both while ignoring notification requirements can be entirely correct on the condition and in breach on the application — the city’s requirements are described under Local Law 36 pesticide notification and the state framework beneath them under the New York neighbor notification law.

There is a useful practical consequence of the stacking, which is that one well-designed program discharges all of it. An annual survey that reads the building rather than the complaint list generates the Local Law 55 record, identifies the conditions conducive that the code cares about, and reduces the amount of pesticide the building needs to apply, which in turn reduces its notification surface. Buildings that treat these as three separate compliance chores end up doing more work and holding a worse file.

What should you ask a pest contractor about code compliance?

Five questions, and none of them are about price.

“When you find a condition you cannot fix, what do I receive?” Most of the durable corrections under Article 4 are not pest work. They are plumbing, masonry, carpentry and refuse handling. The answer you want is a written specification precise enough for another trade to price, followed by verification once it is done. A contractor who reports only what they themselves can bill will leave the actual conditions in place indefinitely.

“How will you tell me where the population is living?” In a shared building this is the whole diagnostic question, and it is answerable — a chase population presents along a vertical line across units with very different housekeeping, and a unit-resident population presents in one apartment around a specific harborage. A contractor who cannot distinguish those two pictures will keep treating apartments.

“What will the record look like in two years?” Ask to see a real sample: findings by location, an access log with refusals, a corrective register with owners and dates, before-and-after photographs, a trend. Then ask who holds it and how the building gets a copy when the contract ends.

“How do you handle a violation that is already open?” The useful answer describes correcting the condition, documenting it and certifying accurately within the period — and includes a clear statement that they will not certify work that is not finished.

“What are you not able to tell us?” Violation classes, correction windows and penalty amounts are HPD’s to state. A contractor who quotes them with total confidence is repeating something they read. The better answer points you at the department’s published material and then talks about your building, which is the part they can actually speak to.

Where should we read the code for ourselves?

Directly, and it is more readable than its reputation suggests.

The text is published as the NYC Housing Maintenance Code, and the extermination and rodent-eradication provisions sit in Article 4 of Title 27, Chapter 2, alongside the rest of the maintenance obligations a building already knows. The allergen-hazard article added by Local Law 55 of 2018 sits in the same chapter and should be read with it rather than apart from it. HPD publishes the current violation classes, correction periods, certification procedures and penalty schedules, and those are the authoritative source for every number this page has deliberately declined to state.

Everything above is general information about published rules, offered as background rather than as legal advice. Rules change, agency practice changes, and how any of it applies depends on facts specific to your building. Confirm current requirements with HPD or with your attorney before acting.

For the program structure behind this — surveys, corrective registers, phased structural work and board-legible reporting — see commercial pest management, with the board view under co-op and condo pest management and the multi-building view under property management pest control. Ryan Katz sets out how the diagnostic side of this work is approached, and contact us with the building if you want a view on a specific open violation.