Response Time Commitments: Promising What You Can Deliver
Set response time commitments that survive a bad week — priority tiers, honest clocks, after-hours cover, and the written records that prove you met them.
Nearly every tenant complaint about speed is really a complaint about a promise nobody wrote down. The resident was told "someone will come", waited three days, and drew a conclusion about the building; the manager thought a three-day turnaround was reasonable for a dripping tap and never knew the expectation had been set at "soon".
Response time commitments fix this by turning speed from an impression into a schedule with a clock, a priority tier and a record. They also protect the manager, because a published standard is a defence against the resident whose emergency is a scuffed door.
Key takeaways
- Commit to acknowledgement separately from resolution. Most goodwill is lost in the silence before pickup, not in the repair itself.
- Set the clock from the data: use the 80th percentile of your last 90 days of tickets, not your best week, then add a buffer you can genuinely hold.
- Three tiers — emergency, urgent, standard — are enough. More tiers produce arguments about classification rather than faster service.
- State hours of cover explicitly, including whether a Saturday call counts from Saturday or Monday morning.
- Log every request with a timestamp, and report the misses as well as the hits. A commitment you never measure is a slogan.
Why do response time commitments fail?
They fail because they were copied from a template rather than measured, and because nobody owns the clock. A standard of "24 hours" written into a lease schedule means nothing if the ticket system stamps arrival at the next business day and the contractor receives work orders in a batch each evening.
Three failure modes account for most of it. The commitment covers resolution but not acknowledgement, so residents hear nothing for days. The commitment is uniform, so an elevator entrapment and a squeaking cabinet hinge are promised the same speed. Or the commitment has no measured baseline, so the building misses it in the first busy month and quietly stops referring to it.
A fourth, subtler one: the promise is made by whoever answers the phone, which in a residential building may be a concierge with no authority over scheduling. That is how a resident gets a different standard each time they call.
What should response time commitments cover?
Five moments, each with its own clock: the acknowledgement that the request was received, the first real update, attendance on site, a booked resolution date, and confirmation that the work is closed. Promise only the moments you control and measure them separately.
Acknowledgement is the highest-value minute in the whole process. A resident who gets a same-day reply saying "received, logged, we will have a date for you by Thursday" is patient. A resident who gets silence for two days phones again, and now the second call is a complaint about the first.
Closure matters just as much. The record should show who closed the request, on what date, and with what evidence — a photo for a cleaning or condition item, a contractor sign-off for a trade. Without closure data, your commitment cannot be reported, only remembered.
How do you set a commitment you can keep?
Measure before you promise. Pull the last 90 days of requests, calculate the median and the 80th percentile for each stage, and set the commitment at or slightly above the 80th percentile. That way the standard is met on all but the worst one in five cases, and the misses are visible rather than routine.
Then name the constraint. If attendance depends on a contractor with a four-hour dispatch window, your on-site commitment cannot be two hours; either buy a faster dispatch tier or change the number. Commitments that ignore the supply chain are commitments to fail.
Finally, publish the exclusions. A commitment does not cover a repair the building cannot authorise, a part on backorder, or access the resident has not granted. Saying so at the start prevents the argument that arrives on day four.
The commitment ladder in practice
Four tiers cover residential and commercial buildings, provided the classification rule is written down and the evidence is recorded at every stage. Times below are examples of the shape of a commitment, not a recommended standard for your building — measure first, then set your own.
| Tier | Examples | Acknowledge | On site | Booked resolution | Evidence recorded |
|---|---|---|---|---|---|
| Emergency | Flooding, no heat in winter, elevator entrapment, door that will not secure | 15 minutes | 2 hours | Control the risk same day, repair booked | Call log, photo, work order number |
| Urgent | No hot water, power loss in a suite, failed entry system | 2 business hours | 4 hours | 1 business day | Ticket timestamps at each stage |
| Standard | Dripping tap, appliance fault, burnt-out corridor lighting | 1 business day | 3 business days | 5 business days | Ticket plus photo of the completed work |
| Planned | Cosmetic items, seasonal work, resident-requested upgrades | 3 business days | By booking | Agreed date | Booking record and completion note |
Two rules make a ladder usable. The receiver classifies the request, not the resident, and any reclassification is explained in writing the same day. And an emergency tier applies only to genuine risk to people or property; a manager does not assess electrical faults, gas smell, structural movement or life-safety system faults. Those get isolated, reported to the responsible trade or authority, and commissioned.
What about after-hours and weekends?
Say exactly what the hours are, who answers, and whether the clock stops. "Requests received after 17:00 are acknowledged the next business day" is honest; a 24/7 promise with a voicemail box behind it destroys credibility fastest.
If the building offers after-hours cover, define the threshold for waking somebody: emergencies only, defined in the same terms as the ladder. Everything else waits for the next business day and the resident is told so at the time of the call, not when they follow up.
Weekend cover needs the same treatment. If a Saturday request is logged but attended Monday, the Saturday acknowledgement should say Monday. Residents rarely object to the timeline; they object to discovering it after the fact.
How do you measure whether the commitments are being kept?
Report on four numbers monthly: percentage acknowledged inside the tier, percentage attended inside the tier, percentage resolved by the booked date, and the count of misses with reasons. Anything else is commentary.
Then split them: by tier to show whether the emergency promise is real, by building to show whether one property is under-resourced, by source to show whether residents are calling the right channel.
Watch the reclassification rate. If a large share of routine requests are being reclassified as urgent, the standard tier is too slow or the residents have learned that urgency gets attention. Both are fixable, and neither shows up in a satisfaction score.
How do you communicate the commitment?
Put it on one page, in the resident's language, in three lines per tier: what counts, how fast we acknowledge, how fast we attend. Publish it at move-in, include it in the notice pack, and repeat it in the confirmation message for every request.
Give residents a way to see status without calling. A confirmation with a reference number and the booked date removes most follow-up calls and produces the timestamp your reporting needs.
When you report to owners, show the same numbers. A quarterly page with the four measures, the misses and what changed is more persuasive than any narrative about responsiveness at budget time.
What happens when a commitment is missed?
Tell the resident before they notice, give the reason, and give the new date. A missed commitment handled in the first hour costs an apology; the same miss discovered by the resident on day five costs the relationship.
Log the miss against the tier and the stage it broke. Two misses on acknowledgement in a month is a staffing or process problem. Repeated misses at attendance are a contractor dispatch problem. Repeated misses at resolution are usually a parts or approval problem, and they belong in the capital or procurement conversation rather than in another apology to the resident.
Not legal advice. Statutory repair obligations, notice requirements and the remedies available to a tenant are set by provincial tenancy law, and they are not the same as your operational commitment. The Landlord and Tenant Board in Ontario and equivalent tribunals elsewhere publish those rules. Where a request turns into a legal question or a dispute, document it and refer it to the owner's counsel or the tenancy board rather than interpreting it for the resident.
Who owns the clock?
One named person per building owns the acknowledgement standard, the classification decisions and the weekly exception list. The cleaning contractor, the trades and the security desk feed the timestamps, but accountability sits with the manager.
Ownership shows up in small habits: a morning check of anything logged after hours, a same-day call on anything reclassified, a Friday review of the misses. Without them the commitment becomes a document nobody opens after the first quarter.
Frequently asked questions
Should a response time commitment be in the lease?
Keep the operational commitment in a resident guide and let the owner's counsel decide what belongs in the lease. Putting a repair turnaround into a lease creates a contractual obligation with legal consequences, which is a decision for the owner rather than the manager.
How many priority tiers do we need?
Three or four. Emergency, urgent and standard cover almost every request, and a planned tier handles the rest. Every additional tier adds a classification argument at the front desk and produces no measurable improvement.
What counts as acknowledgement?
Any response that confirms receipt and gives the resident a next step with a date — a call, an email, a portal update or a text. An automated "your request has been received" with no owner and no date is a receipt, not an acknowledgement.
Do we count business hours or calendar hours?
Business hours for urgent and standard work, calendar hours for the emergency tier. State both explicitly, including the start time, and make sure the ticket system stamps in the same time zone and calendar the resident was told about.
What do we do when a contractor cannot meet the commitment?
Renegotiate the commitment or change the contractor. Do not keep publishing a standard the supply chain cannot meet. Take dispatch performance to the contract review with the numbers attached.
Prove the commitment, don't just publish it
A standard is only worth what you can evidence. NeatScore lets property managers run area-specific cleaning inspections with APPA 1–5 scoring, critical items flagged, photos on every item, offline inspections that sync, and a dated branded report — the closure record that turns a commitment into something a resident, an owner or a contractor can check. Try it free for 14 days, or see pricing.
For the wider picture, start with tenant relations in property management. The classification rules are covered in priority and triage for building requests, the routing in service request workflows, and the complaint side in handling tenant complaints so they do not escalate.
