Somewhere in your owner reporting there is a maintenance response time. It is probably good. It is probably improving. It is almost certainly the number your operations team leads with, and it is the number the industry has agreed to compete on.
It is in the report for a reason that has nothing to do with its usefulness. Most property management platforms report response time prominently because it is the easiest maintenance performance metric to calculate, requiring only data every system already captures. Two timestamps, one subtraction. Every other measure of maintenance quality requires knowing what actually happened inside the unit, which is harder, so the industry standardised on the easy one and then began treating it as though it meant something.
The argument here is not that the number is wrong. It is a legitimate operational signal. It is that it is being asked to carry weight it cannot bear, and that the weight is landing on your maintenance line.
What The Clock Is Actually Timing
Response time measures the interval between a resident reporting a problem and a technician arriving. That is the whole of it. The clock stops on arrival, or in some configurations on ticket closure, and in neither case does it register whether the problem was solved.
This produces an accounting identity that should trouble anyone reading the report. A work order closed after a correct repair and a work order closed after a temporary patch are the same event in your data. They cost the same to report and they read identically on the dashboard. One of them is going to generate two more work orders.
A visit that fixes nothing is not a service level. It is a scheduled return trip.
Aquant, a field service analytics firm, has published the mechanism directly. Service records can show an asset serviced twice inside a month with both visits logged as first-time fixes, which is not a view the customer would recognise, and measuring fix rates in short windows produces false positives. The record says resolved. The unit says otherwise.
What Repeat Visits Actually Cost
The good cost data on this comes from industrial and medical field service rather than multifamily, because no equivalent published dataset exists for apartment maintenance. Apartment maintenance lacks the benchmarks, but it does not lack the economics. A failed first visit consumes another dispatch, another travel leg, another block of a technician's day and another interruption to a resident's, whether the asset in question is a chiller or a garbage disposal. The cost structure of arriving and not fixing is close to identical across both.
The headline finding is the one worth taking to your operations meeting. Aquant's 2026 benchmark, drawn from its analysis of service organisations across some 600,000 technician records, puts failed visits at 25 percent of total service cost at the median. For bottom performers they consume 44 percent of service spend, against 14 percent for the top group. Worth noting that Aquant sells software aimed at reducing failed visits, so it has an interest in the figure being large. The direction of the finding is nonetheless consistent across their reporting years and matches what any operator would predict. GlobeNewswire
The spread on the underlying metric is wider than most operators would guess. The same 2026 benchmark puts the industry first-time fix rate at 77 percent, with top performers at 88 percent and bottom performers at 60 percent. And the cost of a miss compounds rather than doubling: Aquant's 2025 report found that a failed first visit adds two further visits on average and extends resolution by 14 days. SalesTech Star
Run that against a portfolio. Take 2,000 doors at five reported issues per unit per year, so 10,000 distinct problems, at an illustrative fully loaded cost of $180 per visit. Both inputs vary widely and the second in particular runs lower for in-house teams than for vendor dispatch, so substitute your own figures.
At the 77 percent industry benchmark, 2,300 problems fail on the first attempt and generate 4,600 additional visits. Total visits, 14,600. Annual cost, $2.63 million.
At 88 percent, the same 10,000 problems generate 12,400 visits and $2.23 million.
The eleven point difference in fix rate is worth $396,000 a year, equivalent to adding $198 to annual maintenance cost per unit through nothing except the quality of the first visit. A bottom-quartile operation at 60 percent runs to $3.24 million, which is $1.008 million above the 88 percent case, or roughly $504 a door.
One honest note on the model. Applying the two-extra-visits average uniformly across all failures produces a failed-visit share of about 31 percent of total spend, somewhat above the 25 percent median cited above. The real multiplier is not uniform, so treat these figures as directional and adjust the repeat factor toward your own history if you have it.
None of this appears in a report built around arrival times. In fact it improves one. Three visits inside 24 hours each is three data points of excellent performance.
The Metric Is Not Neutral
This is the part that matters to a finance function, because it changes the metric from a reporting problem into an operating cost.
An operation gets better at the thing it is scored on. Score it on arrival and it will get faster at arriving, which is a different skill from getting better at maintenance and can be improved without touching the second at all.
Every incentive in the chain runs the same way once the scorecard is set. Diagnosis takes longer than a patch. A technician who leaves to source the correct part has an open ticket and a worse number than the one who improvises something that holds for a fortnight. Closing fast is visible and rewarded. Closing correctly is invisible and, on the report, indistinguishable.
So the metric does not merely fail to capture the cost. It funds it. The organisation is paying for repeat visits with one hand and rewarding the behaviour that generates them with the other, and both hands are reporting good results.
What It Costs Past The Work Order Line
Two second-order effects, both of which land in accounts the CFO owns. Repeat visits consume technician capacity that is already scarce. NAA data reported in 2023 put annual turnover among onsite maintenance technicians at 39.2 percent, so the hours burned on rework are drawn from the most expensive and least replaceable input in the operation. mPro Digital Edge
And unresolved maintenance reaches the revenue line through retention. NAA puts the cost of a single non-renewal at roughly $4,000 once unit turnover costs, marketing and lost rent during vacancy are counted, and poor maintenance responsiveness ranks among the leading controllable reasons residents decline to renew. On a 2,000 door portfolio at typical turnover, if even three percent of departures trace to a maintenance issue that took three visits to resolve, that is another $120,000 against the same root cause. Second Nature
The residents who left did not experience a fast response. They experienced three afternoons taken off work.
What To Report Instead
Not instead of response time. Alongside it, and above it. Report first-time fix rate measured at 30 days. The window is the entire point. Measured at ticket closure, the number will read close to 100 percent and tell you nothing, because closure is the event you are trying to audit. Measured at 30 days, a second work order on the same unit and system invalidates the original close. The rate now becomes a measure of whether problems stayed solved, rather than whether tickets were closed.
Two comparisons make it operational. Run the rate at seven days and at 30 and look at the gap, since a wide divergence is the false-positive rate in plain sight. Then break it out by technician and by unit, which is where the actionable variance lives.
The data required is unit-level work order history with enough detail to tell a recurrence from a new problem. Most operations technically hold it and few can query it, which is why the metric stays unreported, the easy one stays on the cover, and maintenance cost per unit keeps rising in portfolios whose response times have never looked better. Making that history queryable at the unit level is much of what a platform like RIOO is for here.
Your report describes how quickly technicians arrive, not how often they solve anything. The gap between those two things is roughly a quarter of what you spend.
FAQ
1. What is first-time fix rate?
The percentage of reported problems resolved on the first technician visit, without a return trip, additional parts or a second diagnosis. It is standard in field service and largely absent from multifamily reporting.
2. How do I measure it without producing a false positive?
Set a 30-day window. Count a work order as a first-time fix only if no further work order arrives on the same unit and the same system within 30 days of closure. Measuring at the point of closure produces a rate near 100 percent that reflects your ticketing discipline rather than your repair quality.
3. Should we stop reporting response time?
No. It remains a real signal of dispatch and staffing adequacy, and residents do care about being attended to. The change is one of hierarchy. Arrival speed tells you the operation is reacting. Fix rate tells you it is working. Report both and lead with the second.
4. What is a good first-time fix rate?
Published field service benchmarks put the median around 77 percent, with strong performers approaching 88 percent. Residential maintenance has no equivalent published benchmark, so the more useful comparison in year one is against your own baseline and across your own properties and technicians, where the variance is usually larger than any industry average.
5. Our work order history is incomplete. Where do we start?
Start with the recurrence count, which is a cruder metric but needs far less data: how many units generated more than one work order on the same system within 30 days. It requires only unit, category and date. Once that number exists it is usually sufficient on its own to establish whether the problem is worth a proper fix rate programme.