A resident submits notice to vacate. Inside most multifamily operating platforms, that single action sets off a well-instrumented cost sequence. The unit enters the make-ready queue. Turn vendors are scheduled. The revenue management system starts pricing the vacancy. Someone begins counting days.
What almost never starts is a revenue process.
This is the one moment in the entire resident lifecycle where an operator knows, with near certainty, that a household is about to spend money on moving services. The resident is going to hire movers. They are going to buy packing materials. Some of them will need storage. Most of them will need insurance at the next address. All of that purchasing happens inside a window the operator opened and can see, and almost all of it happens somewhere the operator cannot see.
The window is already the most instrumented moment in your portfolio
Operators measure this period closely, because the costs are severe and well understood.
Turn costs have been climbing. The National Apartment Association reported that leasing expenses reached $292 per unit in 2024, “largely driven by a 17.5% increase in turnover costs year-over-year” (NAA Income/Expense IQ 2024 National Summary). On the individual turn, Zego’s Resident Experience Management Report, published through NAA, put the cost at “$4,000 per unit, which includes lost rent, concessions and maintenance.”
The vacancy side has moved against operators as well. RealPage Analytics found that “nationwide, average vacant days hovered at 34.4 at the end of 2024, compared to about 30 in early 2020,” and noted that “with more than half a million stabilized units unoccupied, the additional impact to property operations quickly adds up.”
So the window is not an unknown. Every operator at 10,000 units and above already has dashboards pointed at it. The instrumentation exists. It is pointed exclusively at cost.
Why the revenue side stays invisible
Three things make this window commercially blind for most operators in residential real estate.
The first is timing. Notice arrives through a portal, an email, or a conversation with a leasing associate. It creates a task. It does not create an offer. By the time anyone in the organization is thinking commercially about that household, the household has already booked a mover.
The second is ownership. Move-out sits between departments. Leasing owns the new lease. Maintenance owns the turn. Accounting owns the deposit. Nobody owns the departing resident as a customer, so nobody is accountable for what that customer buys.
The third is measurement. If revenue in this window is never captured in a system of record, it never appears in a report, and a category that never appears in a report never gets a target. The absence becomes self-sustaining.
What the departing household is actually buying
The commercial content of this window is concrete, and it is dominated by moving services.
Movers come first. This is the largest single purchase most households make during a move and the one with the tightest booking window. Packing services and materials attach directly to it. Storage attaches for the subset of households whose move-out date and move-in date do not line up, which is a common pattern in urban portfolios.
Insurance sits alongside those services as a financial risk mitigation item rather than a convenience. A departing resident needs coverage at the next address, and the operator receiving that resident needs verified coverage in place before keys change hands. Handled as an afterthought, this becomes a compliance chase after occupancy. Handled inside the move workflow, it becomes a condition of the move itself.
Utilities and connectivity follow the same pattern. Both are service decisions the resident has to make anyway, on a schedule the operator already controls.
None of these are new services. They are purchases that already happen on a predictable schedule, inside a window the operator opens. The question is whether the operator participates in them or watches them leave.
The retention argument runs through the same window
Retention is unusually strong right now, which changes the economics of every move that does happen. RealPage Analytics reported that “just over 54% of renters in market-rate apartments renewed their leases in the year-ending October 2024, amounting to a 120 basis point (bps) climb over last year.”
Large operators are seeing the same pattern in their own portfolios. Multifamily Dive reported Essex Property Trust’s CEO describing “a notably low turnover rate of 35%, while achieving positive new lease rate growth and stable occupancy levels,” MAA “reported improving turnover at 41.5% in Q1,” and Camden’s Keith Oden saying “our first quarter 2025 annualized net turnover rate of 31% was one of the lowest in our company’s history.”
Fewer moves means each remaining move carries more weight. It also means the quality of the move-out experience feeds directly back into reputation and referral, which feed back into the next lease-up.
This is also where resident-facing programs belong in the conversation. Paylode, which became a Moved company through an acquisition in November 2025, exists to make resident perks and offers a structured part of the operator’s relationship with the household rather than a scattering of one-off discounts. In the move-out window, that structure is what turns a service offer into something a resident actually accepts.
What this looks like when it is built properly
At 10,000 units and above, this has to be a system rather than a set of instructions to site teams. A few design requirements follow from that.
Notice has to trigger an offer, automatically, in the same motion that it triggers the make-ready task. If the trigger depends on a leasing associate remembering, the program will work at some communities and fail at others, and the portfolio-level number will never move.
The offer has to be the same everywhere. Portfolio-wide consistency is what makes the revenue measurable and what makes vendor economics work. A different arrangement at every region produces a number nobody can report on.
Every transaction has to land in a system of record, attributed to the property and the move event. Revenue that cannot be attributed cannot be reported, and revenue that cannot be reported has no standing with an asset management team.
And the move-in and move-out sides have to be treated as one workflow rather than two, because the household leaving one of your communities is frequently the household arriving at another, and the same services apply at both ends.
Traditional tools focus on task tracking and administrative coordination. Moved embeds revenue-generating services and insurance verification directly into the workflow.
What to measure
Four things tell you whether the window is actually working.
Offer rate: the share of notices that produced a service offer inside the window. This is the honest test of whether the trigger is automated. Anything materially below full coverage means the process still depends on memory.
Time from notice to first offer. The mover booking decision happens early. An offer that arrives a week after notice is competing against a decision the household has already made.
Attach rate by service, tracked separately for movers, packing, storage, insurance, utilities and connectivity. A single blended number hides which part of the workflow is failing.
Consistency across the portfolio. Compare the spread between your best-performing region and your worst. A wide spread is a process problem rather than a market problem.
Where to start
Pull one quarter of notices across the portfolio and answer a single question for each: what did this household buy, and did we see any of it. Most operators cannot answer for the majority of records, and the size of that blind spot is the finding.
From there the sequence is straightforward. Automate the trigger off the notice event. Standardize the offer set across every region. Put the transactions into a system of record. Then measure the four numbers above and hold them at the portfolio level rather than the property level.
Frequently asked questions
Is this the same as charging residents more fees?
No. The services described here are purchases the household is already making with an outside provider. The change is that the operator participates in a transaction that is happening anyway and takes responsibility for its quality. Regulatory attention on rental fee disclosure is increasing, which makes the distinction between a mandatory charge and an optional service the resident chooses more important, not less.
Does this slow down the turn?
Handled inside the workflow, it does the opposite. Coordinated move-out scheduling, confirmed key return, and booked elevator or loading dock time all reduce the resident-driven delays that push vacant days up.
We already offer some of this at a few communities. Why change anything?
Property-level programs produce property-level results. The reason to systematize is that a portfolio number only exists when the trigger, the offer set, and the reporting are identical everywhere. Without that, there is nothing for an asset management team to underwrite.
What about residents who do not want to be sold anything?
The offer should be genuinely optional and clearly presented. The service quality standard matters here as well, because the operator’s name is attached to whoever shows up on moving day.
Closing
The notice-to-vacate window is already the most closely watched period in the resident lifecycle. The instrumentation exists. The dates are known. The household’s purchasing intent is as clear as it will ever be. What is missing is a commercial process pointed at the same window the cost process already occupies.
If you manage 10,000 units or more and want to see what your notice-to-vacate window currently produces, reach out to our team to walk through it with your own data.
Related reading: how operators turn the move-in and move-out process into a revenue workflow, and the complete guide to resident onboarding automation. For how this shows up on the resident side, see Moved for residents, and for the operator view, see Moved for multifamily.
