How to Set Response Standards a Manager Can Hold You To

Why this matters

A property manager's own performance is measured on how fast things get fixed, so the first real question in any portfolio conversation is what your response time is. Most shops answer with an adjective. "We are very responsive" survives exactly until the first cold snap, when the manager discovers that responsive meant Tuesday. The shop that instead names four numbers, states the conditions under which they hold, and reports against them monthly wins work from competitors who quote lower, because a manager can defend a number to an owner and cannot defend an adjective.

The trap on the other side is agreeing to a standard your crew cannot staff. A missed committed response is worse than no commitment, because now you are in breach of something written rather than merely slow.

Step 1: Separate the four clocks

"Response time" means four different things and the manager usually means the third while you are quoting the first. Define all four or the disagreement is guaranteed.

• Acknowledge: a human at your shop confirms receipt and states what happens next. Not an auto-reply.
• Dispatch: a named tech is assigned with an arrival window.
• On site: a tech is physically at the unit.
• Resolve: the fault is fixed, or the unit is made safe and the remaining work is quoted and scheduled.

Only the first three are inside your control. Resolve depends on parts availability and on somebody approving spend, neither of which you own, and committing to a resolve time is how shops end up in breach for waiting on an owner's decision. Commit hard on acknowledge, dispatch and on site. On resolve, commit to a communication cadence instead.

Step 2: Use three priority tiers, not five

Five tiers look thorough and collapse in practice, because the person triaging at 11pm cannot tell tier 2 from tier 3. Three tiers, defined by consequence rather than by trade:

• P1 emergency: an active hazard, an active water release, loss of heat in freezing conditions, loss of power to a dwelling unit, or anything that makes the unit unfit to occupy tonight.
• P2 urgent: a loss of function the occupant feels daily but can live with for a day - no hot water, one appliance down, a partial outage in a room, a slow leak that is contained.
• P3 routine: everything else, including deferred findings and cosmetic work.

Write two or three concrete examples per tier into the agreement, in the manager's vocabulary. Categories argued in the abstract get argued forever; categories with examples get sorted in ten seconds.

Step 3: Set the numbers

Here are defaults that a well-run small shop can actually hold. They are starting points, not law - tune them to your crew size and drive times, then commit to the tuned version.

Two more numbers belong in the same table and get left out of most agreements. Window slippage: when you know you will miss an agreed arrival window, you notify within 15 minutes of knowing, not at the end of the window. Update cadence on an open P1: every 2 hours until it is resolved or made safe, even when there is nothing new to say. Managers do not escalate because you are slow; they escalate because they have nothing to tell the tenant who has called them three times.

Step 4: Check the numbers against your capacity before you sign

Do this arithmetic before the meeting, not after the first breach.

Take your average door-to-door time for an emergency call on that portfolio - drive, diagnose, make safe, write up. Call that the service time. Then ask how many P1 calls can be open at once before your on-call coverage cannot meet the on-site number, and treat that count as a hard staffing trigger with a stated step size.

The arithmetic is unforgiving and it is worth doing on paper, because the answer is usually smaller than it feels. Work it through in the example below.

Step 5: Decide what happens when you miss, and write it yourself

Every standard gets breached eventually. If you do not define the consequence, the manager will define it in the moment and it will be worse than what you would have offered.

A workable structure: a missed acknowledge or dispatch gets a same-day written explanation. A missed on-site target on a P1 gets the trip charge waived on that call. Three misses of the same tier within a rolling quarter triggers a scheduled review of the standard itself, at which either the number changes or your staffing does. Rolling quarter is the unit of analysis, per tier, and the step is a review, not a penalty escalator - a penalty escalator makes you hide misses, which destroys the data the standard runs on.

Also write the surge exception, in numbers, in the same clause as the standard. A defensible form: the P1 on-site standard applies except when portfolio-wide P1 volume in any 24-hour period exceeds three times the portfolio's weekly average, during which calls are worked in triage order by hazard, the acknowledge and update cadence still hold in full, and the manager gets a status list every 2 hours. That is a real commitment during a storm and it is one you can keep. "Except in extraordinary circumstances" is not.

Step 6: Instrument it, or it is a slogan

You need four timestamps per ticket: received, acknowledged, dispatched, on site. If those are not captured automatically they will not be captured. A standard you cannot measure is one the manager will measure for you, from memory, in the meeting where they are annoyed.

Report monthly, unprompted, in one line per tier: calls, percent within standard, and the misses named individually with their cause. Volunteering your own misses is the single highest-trust act available in this relationship, and it costs you almost nothing compared to being caught out on one.

Step 7: Renegotiate on data, once a quarter

Standards drift out of alignment with reality as a portfolio grows or as drive times change. Once a quarter, look at your compliance by tier and by property. Two patterns are actionable: a single property that consistently misses (usually a drive-time or access problem, not a staffing one), and a tier that runs at high compliance with room to spare (which is an opportunity to tighten it publicly and win the next portfolio).

Worked example: sizing a 4-hour P1 standard

A shop is being asked to cover a 180-unit portfolio with a 4-hour on-site P1 standard, 24/7.

Volume. Their own prior-year ticket history for these properties shows 96 P1 calls across 12 months, an average of about 1.8 per week. But 34 of those 96, roughly 35%, arrived inside the 9 coldest days of the year. On those days the arrival rate ran about 3.8 P1 calls per day, against about 0.17 per day across the other 356 days - a peak-day rate roughly 22 times the ordinary-day rate. Staffing to the average covers 65% of the volume and fails on exactly the days the manager will remember.

Service time. Door-to-door on a P1 in this portfolio averages about 2.5 hours: drive, diagnose, make safe, write up.

Concurrency. One on-call tech, calls arriving in a cluster. Call A at hour 0, tech on site at 0.5, clear at 3.0. Call B arrives at 0.5, tech starts the drive at 3.0 and is on site at about 3.5, which is 3.0 hours after B came in - inside the standard. Call C arrives at 1.5, tech gets there at about 6.0, which is 4.5 hours after C came in. That is a breach.

So the rule that falls out is specific: with a 4-hour on-site standard and 2.5-hour average service time, one on-call tech holds the standard across at most 2 concurrent open P1s. The third breaches it. The staffing trigger is therefore stated in those terms - when open P1 count in the portfolio reaches 3, the second on-call tech is activated - and the step size is one additional tech per two additional concurrent calls.

Run the cold-snap numbers through that rule. At 3.8 calls per day spread over a waking day they do not all overlap, but the evening of the first hard freeze is when they stack, and 3 concurrent is not a rare event on that night. This portfolio needs two on-call techs available on forecast-freeze nights, not year-round. That is a manageable commitment: about 9 days a year of doubled on-call, triggered on a weather forecast rather than on a call already breaching.

What this changes in the negotiation. The shop can now offer the 4-hour standard, honestly, with the surge clause defined at three times the weekly average in 24 hours and the pre-activation on a freeze forecast. Compare that to the same shop agreeing to 4 hours flat: it would have held for roughly 65% of annual volume, breached repeatedly during the 9 days that generate the complaints, and put the shop in written breach at the exact moment the manager was under most pressure. Same crew, same trucks, completely different outcome, and the only difference is that somebody did the concurrency arithmetic before signing.

What changes the answer

A portfolio spread across a wide drive radius. Service time is dominated by drive, not by work, and the concurrency ceiling drops. Two properties an hour apart cannot share one on-call tech under a 4-hour standard, and the honest move is to price a longer standard for the outlying property rather than quietly miss it.

High-rise or gated properties with controlled access. Add the access time to service time before you compute concurrency. On some properties, getting from the gate to the unit is a meaningful fraction of the drive.

A portfolio with an on-site maintenance staff. They handle triage and first response, which pushes your P1 volume down sharply and changes what tier you are actually being asked to cover. Ask what their staff handles before you price 24/7 coverage you may not need to provide.

How to verify you got this right

Pull your last 20 emergency calls on managed property and compute actual on-site time from receipt. If your median is comfortably inside the number you are about to promise but your slowest three are well outside it, you do not have a response problem, you have a concurrency problem, and the fix is a staffing trigger rather than a lower standard.

Then check one thing about the standard itself: can the person answering the phone at 2am apply it without calling you. If tier assignment requires your judgment, the standard exists on paper and not in the field, and the first miss will happen during the call you slept through.

References

• See related: The Service Level Language Worth Agreeing in Advance
• See related: The Property Manager as a Repeat Client
• See related: How to Work a Turnover Window Without Blowing the Schedule
• Trade-standard practice for on-call rotation and after-hours coverage in small field-service shops