Property Management

The stake: Portfolio-wide compliance, tenant complaint response, and documentation that survives an audit.

What is the actual exposure when you manage buildings rather than own them?

An obligation you operate but do not own, replicated across every property on the schedule, and a filing system that has to be able to answer for all of them at once.

That is a different job from pest control on a single building, and the difference is not scale. It is variance. A managing agent is not running one program fourteen times. They are running fourteen buildings of different ages, constructions, staffing arrangements, refuse systems and complaint cultures, under owners with different appetites for capital spending, while carrying a duty that in most cases legally attaches to those owners rather than to the agent.

The statutory position is worth stating precisely because agents are often vague about it. In New York City, the duties under the NYC Housing Maintenance Code at Title 27, Chapter 2, Article 4 — extermination and rodent eradication in a multiple dwelling — run to the owner. Local Law 55 of 2018, the Asthma Free Housing Act, likewise places its inspection and remediation duties concerning indoor allergen hazards, pests among them, on owners of multiple dwellings, with an annual inspection obligation attached. Where the management agreement sits within that, and what the agent’s own exposure is, is a question for counsel and for the specific contract rather than something a pest contractor should be pronouncing on. Read both instruments directly.

What is not ambiguous is the operational reality. The agent is the party who receives the complaint, dispatches the response, holds the records, briefs the owner and stands in front of the resident. Whatever the paperwork says about ultimate liability, the agent is where the work either happens or does not, and the agent’s file is the file that will be produced.

Three exposures follow from that, and they behave differently.

The first is the individual matter that escalates: a tenant reports, the response is thin, the reports continue, and eventually it becomes correspondence, a filed complaint or a rent proceeding. This is a per-building risk and it is largely a workflow problem.

The second is portfolio-level inconsistency: two buildings with the same problem get different responses because they have different supers and different contractors, and there is no way for anyone to notice until one of them fails. This is a standards problem.

The third is the slow accumulation of unfunded structural findings across the portfolio. Every year that a chase goes unsealed, the cost of the complaint traffic it generates is paid anyway, in staff time and in service visits, without ever reducing the underlying condition. This is a capital-planning problem, and it is the one most often invisible in the reporting.

Graduate Pest Control has worked with agents and buildings across Manhattan, Brooklyn, Queens, Nassau and Suffolk since 1983. The buildings vary enormously. The way portfolios get into trouble does not.

Why does a portfolio need one standard rather than one contractor per building?

Because without a shared standard the buildings cannot be compared, and a portfolio you cannot compare is a portfolio you cannot triage.

Consider what happens when each property is procured separately, which is the default in most portfolios that grew by acquisition. Building A has a contractor who visits monthly and writes a two-line log. Building B has one who visits quarterly and produces a detailed report with a severity scale. Building C’s super handles most of it himself and calls someone when it gets bad. All three might be adequately served. None of the three files can be read against the other two.

The consequence is not merely untidy. It means the agent cannot answer the only question that matters at portfolio level: which of these buildings is actually in trouble? Complaint counts are not comparable, because they measure reporting culture as much as infestation. Service frequency is not comparable, because it was set by three different sales conversations. The corrective findings are not comparable, because two of the three contractors do not record conditions at all.

What has to be standard is not necessarily the company. It is the specification. Specifically:

One scope definition. What a survey covers, what a routine visit covers, what triggers an adjacency assessment, and what falls outside the contract and gets referred to another trade.

One severity scale. Agreed language for what counts as an active population, an introduction, a condition and a resolved item, so that “active” means the same thing in every building’s log.

One reporting template. The same fields, the same headings, the same order, so that reading a second building’s report requires no adjustment.

One corrective register format. Findings, named owner, target date, closure evidence. This is the artefact the agent needs most and the one most contractors do not supply unless asked.

One escalation ladder. What happens on a second report from the same unit, on a bed bug confirmation, on a rodent sighting in a food-adjacent space, and on an access refusal.

Hold those five and the portfolio becomes legible. An agent can then look across it and see, in one view, which buildings are generating repeat complaints in the same locations, which have open structural items aging past a year, and which are quiet because they are actually fine rather than because nobody is looking.

Agents who then choose to keep multiple contractors can do so without losing that legibility, provided the specification is written by the agent and the contractors work to it. The failure is not multiple vendors. It is multiple standards.

How do you triage a portfolio?

By separating buildings that carry structural debt from buildings that are experiencing events, because those two conditions need entirely different spending.

This is the highest-value analytical work an agent can do in this area, and it takes an afternoon with the complaint log rather than a consultant.

Look at spread before volume. Ten complaints in one building is not informative on its own. Ten complaints spread across seven different lines, on multiple floors, in units that have nothing in common except the building, describes a population living in shared voids and moving through them. Ten complaints all originating from two adjacent units on one floor describes something local. The first needs correction. The second needs a competent local response and a look at the neighbors.

Look at repetition at the same location. A unit that reports, is treated, goes quiet and reports again three months later is the strongest single signal that the diagnosis was wrong the first time. Repeat rate at the same address is more diagnostic than total volume, and it is usually easy to extract from an existing work-order system.

Look at vertical alignment. Reports at the same relative position on stacked floors — the third-floor and fourth-floor apartments on the same line, the same corner of the same kitchen — are a chase signature. Once an agent knows to look for it, it becomes visible in logs that have been sitting unread for years.

Look at seasonality. Reports clustering in autumn point at rodents entering the envelope. Reports rising in summer point at cockroach breeding and refuse conditions. A building with a flat complaint rate year-round has something living inside it permanently.

Look at what changed. Renovation is the most reliable predictor of a new problem in a previously stable building, because opening walls exposes chases that were undisturbed and the work is rarely sealed afterwards. Sewer work, sidewalk sheds, demolition on an adjoining lot and the removal of long-standing ground cover all move rodents onto neighboring properties. Cross-reference the complaint spike against the capital calendar and the source is often obvious.

From that, buildings sort into three tiers, and each gets a different budget conversation with the owner.

Tier one — structural debt. Multiple lines affected, repeats at the same locations, vertical alignment, flat seasonality. These buildings need a full survey and a correction program, and the money spent on routine service until that happens is largely holding costs.

Tier two — event-driven. Isolated reports, low repeat rate, identifiable introductions or sanitation causes. These buildings need a fast, competent response workflow, cyclical inspection, and attention to refuse. Structural spending here would be poorly targeted.

Tier three — stable. Little activity, no repeats, good staff practice. These need the inspection cycle, monitors that are actually read, and someone to notice if the picture changes.

The value of this exercise is that it stops the portfolio from being managed at the average. Portfolios almost always contain one or two buildings carrying most of the risk, and an averaged report is precisely the instrument that hides them.

How is a portfolio program structured?

As a common framework with a per-building baseline underneath it, rolled out in a sequence set by the triage rather than alphabetically.

Baseline surveys, worst first. Every building eventually needs a written assessment, but the tier-one buildings need theirs immediately, because they are the ones where routine service is currently being spent without effect. A baseline covers the cellar and mechanical spaces, refuse handling from chute door to curb, common areas, roof and bulkhead, the exterior at grade and the drainage, and a sample of units chosen by stack. It produces a condition list and a route map, not a product recommendation.

A standing response capability everywhere. Regardless of tier, every building needs the same thing available: a report is received, an assessment happens within a stated window, adjacent units are included by default, findings are recorded, and the resident is told what happens next. Most of what residents experience as good or bad pest management is this, not the treatment.

Correction, phased and specified. For tier-one buildings, the structural work — sealing penetrations through the stacks, closing joist pockets, chute doors and refuse rooms, door sweeps on service and cellar doors, drainage repairs — is scoped so that other trades can price it and phased so that it can be funded across cycles. The detail of that work is set out under structural exclusion. The specification matters more than who executes it; a finding that says “seal penetrations in kitchen stack, floors two through six, at the waste line and both supply lines, mesh and mortar, verify after” can be handed to a carpenter. A finding that says “seal gaps” cannot.

Rolling exclusion at turnover. The mechanism that quietly does most of the work over time, covered in its own section below.

Cyclical inspection. In New York City this intersects directly with the Local Law 55 annual inspection obligation, and an agent running several multiple dwellings should be building that cycle into the operating calendar rather than treating it as a separate compliance exercise. Practically, the unit inspection that satisfies a cyclical obligation is the same walk-through that finds the conditions worth finding — moisture under sinks, gaps behind cabinetry, harborage, evidence of activity in units that have never complained. Doing it once and using it for both purposes is straightforwardly more efficient than doing it twice.

Consolidated review. A portfolio-level read at a set interval, described further down, where the triage is refreshed and the corrective backlog is examined by age.

What does a complaint workflow look like when it works?

It converts every report, whatever channel it arrived through, into a dated record with an assessment attached — and it treats a second report differently from a first.

The single largest source of avoidable escalation in managed housing is not slow treatment. It is silence. A resident who reports something and hears nothing concludes, reasonably, that nothing is happening, and their next move is upward. A resident who is told what was found, what will be done and when someone is returning waits, even when the problem is not yet fixed. That asymmetry is enormous, and it costs nothing to exploit.

A workable flow has six parts.

Single intake. Reports arrive by portal, by email, by letter, through the super’s phone and in person in the lobby. All of them need to land in one place with a date attached. The verbal report to a porter that never gets written down is the one that later makes the building look unresponsive, because the resident’s account of it will exist and the building’s will not.

Acknowledgment on the same business day. Short, specific, and containing a date. Not a resolution — a date.

Assessment within a stated window, including the neighbors. The assessment covers the reporting unit and, by default, the units adjacent, above and below on the same stack, plus the common space behind the wall. Making adjacency automatic rather than discretionary is the change that resolves the largest share of repeat complaints, because it catches the population where it actually lives instead of where it was noticed.

Access notice and refusal recording. Notices generated with dates, refusals logged individually with the re-attempt. An agent who can produce a record of three attempted entries stands somewhere entirely different from one who can produce nothing.

A second report triggers a different response. This is the discipline that most workflows lack. A repeat from the same location means the first diagnosis was incomplete, and the correct answer is to widen the assessment — more units, the chase, the riser, the common areas serving that line — rather than to repeat the same treatment more heavily. Building this into the workflow as an automatic trigger removes the need for anyone to make a judgment call under pressure.

Closure with notification. Tell the resident what was found and what was done. Record that you told them. Both halves matter.

On response times: set an internal standard, publish it to staff and contractors, and measure against it. Do not let the standard be inferred from whatever happened last time. Whether and how any legal timeframe applies to a given building is a matter to confirm with counsel; the internal service standard is a management decision and should be set deliberately, because it is the thing that actually governs behavior day to day.

Why is turnover the cheapest window for exclusion work?

Because a vacant apartment removes every cost driver that makes the same work expensive when someone lives there.

This is the most useful single idea on this page for an agent with a portfolio, and it is chronically underused.

In an occupied unit, sealing the chase penetrations behind a kitchen sink means arranging access, giving notice, working around a resident’s schedule, moving their belongings, working around installed appliances and cabinetry that cannot be pulled, and returning when it turns out something needed a second visit. Half the cost is logistics. In a vacant unit during make-ready, the appliances are already out or movable, the base cabinets can be pulled if needed, nobody needs notifying, and the trade is on site anyway doing paint and repairs.

So the work becomes a checklist item on the make-ready rather than a project. A sensible turnover list for pest purposes covers:

• The penetrations behind the sink base — waste line, both supply lines, and the annulus around each where it enters the wall.
• The gap behind the range and the gas line penetration.
• Escutcheons at exposed supply lines, which are decorative covers rather than seals and hide open holes underneath.
• The riser penetration through the floor slab where one is accessible, and the void beneath a radiator.
• The void behind a recessed medicine cabinet, which in older buildings frequently opens directly into the wall cavity and sometimes into the adjoining bathroom.
• The gap where a tub surround meets the wall and where the tub trap is accessed.
• Door sweeps on the entry door, and the gap at the strike side on older doors that have dropped.
• Window screening and, where relevant, the gaps around a through-wall air-conditioning sleeve.
• A photographic record of each item, filed against the unit.

None of these are large pieces of work individually. Their value is cumulative and it compounds. A building with ordinary turnover will cycle a substantial share of its units over several years, and if every one of them is sealed at the chase on the way through, the building’s internal pathways close progressively without a single capital project ever being approved. Agents who institute this find that the buildings running it drift downward in the complaint rankings without anyone being able to point at the intervention, which is exactly what durable work looks like.

Two caveats keep it honest. Turnover sealing does not substitute for correcting a building that already has an established chase population — the sequence still requires reducing the population before closing the routes, or the animals simply stay in the voids. And it only works if the make-ready specification actually names the items, with photographs required, because a line reading “seal any gaps” will be interpreted as no gaps found.

How do you get supers and in-house staff into the program?

By treating them as the observation layer and the process owners, and by being clear about the one thing they should not be doing.

Building staff have the information that no contractor can obtain. They are on site daily. They know which apartment has had a leak under the sink for a year, which resident hoards, which line has always been the bad line, which door has never closed properly, and what actually happens to the refuse between the chute and the curb. A contractor visiting monthly sees a snapshot. The super sees the film.

They also control the variables that matter most. Refuse timing and handling is upstream of most cockroach and rodent pressure in a residential building, and it is entirely a staff practice. So is the condition of the compactor room, the state of the cellar storage, whether the service doors are propped in summer, and whether an access notice actually gets under the right doors.

What makes this work in practice is small and specific:

A shared vocabulary for evidence. Staff should know what a rub mark is and what it means, the difference between mouse and rat droppings, what cockroach fecal spotting looks like on a cabinet edge, and what fresh gnawing looks like against weathered wood. This is not a course. It is one walk-through with someone who can point at things, and it durably improves the quality of everything the building reports afterwards.

A photograph standard. A photo, a location, a date, sent to one address. That is the whole protocol, and it turns dozens of casual observations a year into a usable record.

Explicit ownership of the refuse interval. Someone should own the time between material leaving an apartment and leaving the property, and it should be measured occasionally rather than assumed.

Clarity about product. The thing staff should not be doing is applying product, and the reason is practical rather than territorial. Over-the-counter total-release foggers are the worst offender: they do not penetrate the voids where cockroaches actually live, and their repellent action tends to scatter a population deeper into the chase and outward into neighboring apartments, converting one unit’s problem into a line’s problem. Casual application also creates an undocumented gap in a record that is otherwise complete, which is a poor trade for whatever it saved.

Continuity. Staff turn over. The building’s knowledge should live in the file — the baseline, the register, the unit history — rather than in one person’s memory, so that a new super inherits something better than a set of rumors.

What documentation survives a challenge?

A dated chain from report to finding to action to closure, with the awkward entries left in.

The test to apply is simple and slightly uncomfortable: hand the file to someone who was not there, does not trust you, and has an interest in finding fault. Can they follow what happened? Most portfolio files fail that test not because the work was poor but because the file records attendance instead of findings.

What holds up:

The complaint record. Every report, including verbal ones, with date, unit, channel and what was reported. Complete beats tidy.

The inspection record. What was inspected, when, by whom, and what was found — including inspections that found nothing, which are evidence of looking.

Access notices and refusals. Dated, individual, with re-attempts. Repeatedly the pivotal documents.

Findings and corrective register. Each condition with a named owner, a target date and closure evidence. The named owner is the part that turns a list into work, and most of these owners are not the pest contractor — carpentry, plumbing, masonry, maintenance and housekeeping between them own the majority of any real corrective list.

Product records. The material used, the location, the rate, the date, and the label conditions it was applied under. That is a regulatory document before it is a management one.

A current device map. Monitors and stations with identifiers matching the physical site. Maps go stale after any renovation, and a stale map is a finding in itself.

The trend. Activity and complaint volume over time by building and by area. This is what demonstrates that a program functions, and it is the only part of the file that answers the question “is this working?” without requiring the reader to interpret a year of notes.

Two habits determine whether the file is worth anything. Record the unwelcome findings — the refused unit, the condition the owner declined to fund, the source that turns out to be the property next door — because a file with no problems in it is not credible and is worth nothing at the moment it is tested. And write findings in language a layperson can follow, because the eventual reader is a resident’s attorney, an owner, or an inspector, not a technician.

What does consolidated portfolio reporting need to show?

Comparison, ranking and aging — not averages.

An owner or a principal looking at a portfolio needs to answer three questions quickly: which buildings are getting worse, what is outstanding and how long has it been outstanding, and where should the next dollar go. A report that presents totals across the portfolio answers none of them, because a portfolio total is dominated by the largest buildings and smooths away exactly the signal that matters.

What earns its place in a consolidated report:

Complaint rate normalised by unit count, so a two-hundred-unit building and a thirty-unit building can be read side by side. Raw counts always flatter the small building and indict the large one.

Repeat rate, meaning the share of reports that come from a location that has reported before within a defined period. This is the closest thing to a quality measure for the response workflow.

Spread, meaning how many distinct lines or stacks within a building are generating reports. This is the structural-debt indicator.

Open corrective items by age. Not just how many, but how old. An item open for fourteen months is a different object from one open for three weeks, and aging is the discipline that stops registers from becoming archives.

Access refusal rate by building. Both an operational signal and a defensive one.

Monitor activity trend by building and area, which is the leading indicator that moves before complaints do.

A plain ranking. Which three buildings carry the most risk right now, and why. Someone has to be willing to write that sentence, and it is more useful than any chart.

Reports should be produced for the audience that acts on them. A site-level report is operational: open items, access issues, this month’s findings. An owner-level report is positional: trend, risk ranking, what is being asked for and what happens if it is deferred. Writing one document to serve both usually produces something that is too detailed for the owner and too abstract for the site, and the practical result is that necessary work sits unfunded through a whole cycle.

Why is the lowest per-building bid usually the most expensive option?

Because of what a low price actually purchases, which is a number of minutes rather than a result.

A per-visit price is set by dividing a route technician’s day among the stops on it. It buys attendance. Within that time it is possible to walk a cellar, check a handful of stations, apply something in the unit that complained and write a log entry. It is not possible to survey a stack, assess adjacent units, trace a rub mark to its origin, examine the refuse process end to end or write a corrective specification a carpenter could price. Those things are not omitted through carelessness. They were never in the price.

The incentive structure compounds it. A contract priced per visit rewards visits. A contractor paid to attend twelve times a year has no commercial reason to identify the structural work that would reduce the need to attend, and every reason to produce a log that documents uneventful attendance. That is not an accusation of bad faith; it is what the contract asks for.

Meanwhile the costs that the low bid did not remove continue to land, just in other budget lines. Staff time absorbing complaints. Work orders. Access coordination. Unit turnover where a resident leaves over an unresolved problem. Legal and administrative time when a matter escalates. And the structural conditions themselves, which are unchanged and which will still cost the same to correct whenever they are eventually addressed, plus whatever damage they caused in the interim.

The alternative is not to buy the most expensive proposal. It is to buy a different thing: a specified scope with a survey in it, a corrective register as a deliverable, adjacency assessment as standard rather than as an extra, and reporting written to the agent’s template. Then compare prices for that. Portfolios that make this switch usually find their tier-three buildings get cheaper, because they were being over-serviced by a standard frequency, and their tier-one buildings get properly funded for the first time.

What goes wrong across portfolios, and why?

The failure patterns repeat, and most of them are administrative rather than technical.

No baseline anywhere. Service was inherited with the building and nobody ever assessed it. There is nothing to measure against, so no improvement can be demonstrated and no decline can be detected.

Every building treated identically. A uniform monthly frequency across the portfolio over-serves the stable buildings and under-serves the one carrying structural debt, at a total cost higher than a triaged approach.

Files that record attendance. Twelve log entries a year saying the building was serviced. It satisfies an invoice and it demonstrates nothing.

Corrective items with no owner. The findings are there and the assignment is not, so the same conditions are re-recorded year after year until the register itself becomes evidence that the condition was known.

Reporting at the average. The portfolio looks fine because eleven buildings are fine, and the twelfth is not visible until it produces a legal matter.

Contractor churn. Rebidding annually means nobody holds a trend, every new contractor starts with no history, and the corrective backlog resets to zero on paper while remaining exactly where it was in the building.

Renovation that undoes the work. Units are gutted and rebuilt, chases are opened and closed unsealed, and a quiet stack starts reporting. The fix is in the specification: sealing and inspection written into the scope for any work opening a wall.

Turnover of staff and of the file. A program that lived in the outgoing super’s routine leaves with him. Documentation is the only defense.

Waiting for complaints to prioritize. Complaint volume measures reporting culture. A building where residents have stopped bothering to report looks quiet, and it is not.

How should an agent start?

With the complaint log and one survey, not with a portfolio-wide contract.

The fastest useful step costs nothing: pull two years of pest work orders and sort them by building, by unit and by date, and look for repeats at the same location and spread across lines. That exercise alone tells an agent which building to survey first, and it is more informative than any proposal.

Then survey that building properly and see what a real baseline looks like. It sets the standard the rest of the portfolio can be held to, and it gives the agent something concrete to take to an owner rather than a general argument about doing more.

Bring what you have: service history, the complaint log, the capital calendar, renovation dates, notes on which buildings have supers who see things and which do not. If the portfolio includes cooperatives or condominiums where a board rather than an owner makes the decision, the governance side of that is covered under co-op and condo boards. The broader compliance framework for buildings under obligation is on the commercial pest management hub, and the sealing discipline that underpins the durable half of all this work is described under structural exclusion. For the pests that generate most managed-housing complaints, see cockroach control, rodent control and bed bug treatment. Coverage across the city and Long Island is listed under locations, and Ryan Katz explains how buildings are read on the diagnostic side.

To begin, contact us with the portfolio: how many buildings, roughly what ages, and which ones you already know are the problem.