Which Turnover Costs Belong to the Vacancy, the Repair, or the Handoff?

When a rental unit costs more than expected between residents, what caused the difference: lost rent, repairs, cleaning, leasing work, or a late handoff? That is the research question. A portfolio owner who records only one turnover total cannot tell whether the next decision concerns pricing, vendor scope, readiness, or scheduling.

Method and evidence scope

This article uses a document-based method rather than a market-cost estimate. For each completed turnover, assemble the notice date, move-out date, first access record, inspection, work orders, invoices, listing dates, application or showing milestones, lease execution date, and ready-to-occupy confirmation. The unit is the observation. The event timeline is the unit of comparison. A portfolio may compare its own observations across similar units, but it should not present that local sample as a national benchmark.

The external evidence supplies definitions and boundaries. The IRS rental property guidance distinguishes rental expenses and recordkeeping questions that require tax advice. HUD's inspection resources show why physical condition evidence should be tied to observable deficiencies rather than a vague “turn cost.” The Census housing vacancy survey provides a population-level vacancy measurement, but its purpose and sampling frame differ from a property manager's unit timeline. The BLS Producer Price Index overview can provide price context for selected inputs, not a substitute for an invoice.

Four causes that should stay separate

The first bucket is vacancy exposure. It begins when the prior tenancy ends and ends when the next tenancy's agreed possession begins, subject to the portfolio's chosen definition. Record the dates and explain gaps. A unit can be physically ready while still unleased, or leased while a promised handoff is late. Those are different operating problems.

The second bucket is physical work. Attach inspection observations, approved scope, completion evidence, and invoice line items. “Paint and repairs” is too broad for later analysis. Separate a damaged door from routine touch-up, and separate an emergency response from planned replacement. The record should state who observed the condition and when. It should not infer resident fault from wear alone.

The third bucket is service preparation. Cleaning, linen handling, photography, lock changes, utility coordination, and safety checks may be required before a showing or handoff. Short-term rental operators may have a different preparation sequence from a long-term landlord. The same label should not be forced across both operating models.

The fourth bucket is decision and handoff time. This includes waiting for owner approval, missing vendor information, an incomplete scope, a delayed access arrangement, or a listing that could not go live because required facts were unconfirmed. The point is not to assign blame. The point is to preserve the queue state that existed when time passed.

What the comparison can show

For each unit, make a row for each event and include event type, start, end, source, amount if applicable, responsible next action, and confidence. Then calculate elapsed days by bucket only when the dates are supported. If the move-out date is known but the readiness date is not, report an incomplete interval rather than filling it with an estimate. If an invoice combines cleaning and repair, keep the amount combined and mark the attribution as uncertain.

The useful comparison is usually within a narrow group: similar unit type, similar service model, and a defined time window. Ask whether repeated delay appears before inspection, after approval, during vendor completion, or during leasing. Ask whether one cost category recurs without a corresponding delay. The analysis may lead to a better scope template, earlier access request, or clearer approval packet. It cannot prove that one intervention caused a later improvement without a designed comparison.

Facts, analysis, and limitations

The fact is the dated document: an invoice, inspection note, message, listing record, or signed lease. Analysis is the interpretation that a pattern may be associated with a process step. Keep the two in separate fields and link the interpretation to the evidence used. The IRS source supports careful rental recordkeeping, not an accounting classification for every portfolio. HUD inspection material supports condition documentation, not a private service-level target. Census vacancy measures support context, not a forecast for a particular building.

Small samples are noisy. A major appliance failure, insurance event, local rule, or unusual resident schedule can dominate one observation. Costs may also be shared across a building or charged outside the turnover invoice. Comparisons can become unfair when short-term and long-term turns are blended. No universal threshold tells an owner that a turnover is “good” or “bad.” Use the method to ask better questions of the next record.

Replication notes for a portfolio team

Before opening the sample, write the inclusion rule. For example, include turns that have a documented prior tenancy end and a documented next possession event, and list separately the turns missing either boundary. Decide whether an owner approval delay is an operating interval or an external exclusion. Apply the same choice to every unit. If the definition changes, split the results into periods instead of quietly revising old rows.

Review the records in their original order at least once. A later invoice or corrected inspection can explain an earlier ambiguity, but it should not erase the earlier state. Keep a note that the record was amended, the date of amendment, and the source for the amendment. When a source conflicts with another source, publish the conflict in the research notes and ask the accountable owner of that record to resolve it. That habit gives a future report more context than a polished final total would.

For each apparent pattern, write a competing explanation. A long vacancy may follow weak listing demand, a missing approval, a late repair, or an unavailable possession date. A high repair amount may reflect one capital item rather than a poor turnover process. Test the explanation against the event timeline and note which evidence would change the conclusion. This keeps the method useful for PortfolioRental work without pretending that a descriptive sample is a controlled experiment.

Evidence-led conclusion

A turnover total is an outcome, not an explanation. The evidence supports a stronger operating record when the owner separates vacancy exposure, physical work, preparation, and decision or handoff time, then preserves the source and confidence for each interval. That approach will not make every cost controllable. It does make recurring delays easier to distinguish from one-off conditions, which is the information a rental portfolio needs before changing a vendor scope, approval routine, or leasing assumption.