The Turn Metrics Operators Track, and the Three They Miss

Almost every operator can tell you their average turn time. Far fewer can tell you what a turn costs them by trade, or how often a unit gets called ready and then fails.

Turn time is the metric that survived the move from the dry-erase board to the spreadsheet, because it is the one number the board could hold. It is not the number that moves NOI.

Here is what most turn reporting covers, what it misses, and what good looks like on each.

Average turn time. Days from move-out to move-in ready. Universally tracked, usually as a portfolio average.

The problem with the portfolio average is that it hides the distribution. A portfolio averaging 8 days might be running most units in 5 and a long tail in 20. The average tells you nothing about which units are in the tail or why. The tail is where the vacancy loss is.

Track the median and the 90th percentile alongside the average. If your 90th percentile is more than double your median, you do not have a turn time problem. You have a specific, findable coordination problem affecting a minority of units.

Vacancy days. Usually tracked by finance, usually disconnected from the turn team's reporting. If your ops team and your asset management team are looking at two different numbers for the same unit, that gap is worth closing before you optimize anything.

1. Cost per turn, broken out by trade.

Most operators know total turn spend. Far fewer can say what they paid per turn for paint versus cleaning versus punch, per property, against what those trades should cost in that market.

Without the breakout you cannot tell the difference between a turn that cost more because the unit was in bad shape and a turn that cost more because you are paying above market for paint in that submarket. Those require completely different responses.

Northwood Ravin recovers about $100 per turn in OpEx across a 10,000-plus unit Class A portfolio. That number did not come from negotiating one big contract. It came from seeing rates at the trade level and acting on the outliers.

2. Schedule slip.

The gap between when a service was scheduled and when it actually happened.

This is the single most diagnostic turn metric and almost nobody reports it. Turn time tells you the unit took 12 days. Schedule slip tells you the painter came two days late, which pushed the punch crew, which pushed the final clean, which is why it took 12 days instead of 6.

Turn time is the symptom. Slip is the cause. If you only measure the symptom, every conversation about turn time becomes a conversation about pressure rather than a conversation about sequencing.

Northwood Ravin's Florida portfolio moved from 10 days to 6. Ginkgo reduced turn time by more than 10 days across 9,000-plus units in 56 Southeast communities. In both cases the work was in the sequence, not in making anyone move faster.

3. Callback rate by vendor and by trade.

How often work has to be redone after a unit is called ready.

A callback is expensive twice. You pay for the remediation, and you lose the days between the unit being marked ready and the problem being found. A portfolio with a strong turn time and a quiet callback rate is not fast. It is marking units ready before they are.

Track callbacks per vendor, per trade, and per property. One vendor driving a disproportionate share is a vendor conversation. One trade driving it across vendors is a scope or standards problem.

Not because operators do not want them. Because of where the data lives.

Turn time can be derived from the PMS. Move-out date and unit-ready date are both already in there.

Cost per turn by trade requires invoice-level data joined to the unit and the trade. In most portfolios invoices arrive as PDFs, get coded to a GL account at the property level, and the trade detail is gone by the time anything is reportable.

Schedule slip requires a scheduled date to compare against. If scheduling happens by phone call and text message, there is no scheduled date in any system. There is nothing to slip against.

Callback rate requires knowing that the second visit was a callback and not new work. Without a link between the two work orders, a callback looks like additional scope.

All three are data availability problems, not analysis problems. The reporting is not hard once the data exists in the right shape.

If you want a starting benchmark:

• Median turn time under 7 days, with the 90th percentile under 14. The spread matters more than the midpoint.
• Schedule slip under one day on the critical path trades. Paint and flooring are usually the ones that cascade.
• Callback rate in low single digits, measured within 10 days of completion. Anything higher and your QC gate is not a gate.
• Cost per turn variance by property within 15% once you normalize for unit size and condition. Wider than that and you are looking at rate differences, not condition differences.

These are starting points for a conversation with your own data, not industry benchmarks. Run them against your last 200 turns before you decide whether they are the right targets for your portfolio.

Every one of these metrics requires the turn to be scheduled in a system before the work happens, not recorded after it.

That is the real shift. Reporting after the fact tells you what happened. Scheduling in a system, with a scope and a date and a rate attached before the resident has moved out, is what makes the measurement possible at all. It is also what makes the measurement worth having, because by the time you can see slip you can still act on it.

If your turn data only becomes visible once the invoices arrive, you are running a monthly post-mortem. That is a reporting function. It is not turn management.