A unit turn is a small construction project. It is easy to run it like a to-do list.

The difference sounds academic until you put two calendars side by side. Here is the same unit, the same work and the same vendors, scheduled two ways. The durations are illustrative, chosen to make the shape visible rather than to represent a benchmark.

Identical work. Four days of it, in both columns.

One unit is ready on day four. The other is ready on day eleven. Nobody worked faster. Nothing was skipped. The difference is entirely in what happened before the keys came back, and in the days nobody was working at all.

Why the right-hand column is shorter

Project management has a precise answer to this, and it is worth borrowing.

The Project Management Institute's PMBOK Guide defines the critical path as the sequence of activities that represents the longest path through a project, which determines the shortest possible duration. The US Government Accountability Office's schedule guidance states the consequence directly: delays in any task on the critical path directly impact the project's end date.

A turn has a critical path. In a particular turn, some tasks will depend on others. Repairs may need to finish before painting, and certain flooring or cleaning work may need to follow those tasks. The exact sequence depends on the scope and the property, but the principle holds whatever order you use.

Now look at the left-hand column again. The waiting days, for parts, for the painter, for the flooring crew, are not gaps beside the work. In this example they sit on the critical path, between dependent tasks. When waiting days sit on the critical path, each one can push the rent-ready date back.

That is why coordination matters more than speed. You can double how fast your painter works and save half a day. Remove the two days spent waiting for the painter to become available and you save two.

Some tasks never needed an empty unit

Here is the insight that turns the notice window from a nice idea into a structural advantage.

In critical path terms, the question is which tasks and dependencies determine the project's finish date. So ask what each turn task actually depends on.

Painting depends on the unit being empty. So does flooring, and so does the final clean.

Identifying likely scope does not, at least not entirely. Ordering parts does not. Booking a painter for a specific date does not. Arranging the flooring crew does not. None of these require the resident to have left. They only ended up in the post-move-out sequence because the turn was scheduled to start at move-out, which forced them to happen afterwards, one after another, before the physical work could begin.

Starting at notice moves those tasks into the weeks when the unit is still occupied. The project management term for how much a task can slip without delaying the finish is float, or slack. The notice window gives those tasks room to be completed or scheduled before move-out, rather than queuing behind it and consuming the first four days of the left-hand column.

Be honest about what you cannot see yet

The pre-move-out inspection is powerful and it is also partial, and treating it as complete causes its own problems.

Damage behind furniture, under rugs, inside cupboards the resident is still using, or caused during the move itself, will not show up until the unit is empty. Some repairs will only be scoped on move-out day.

So the goal is not to know everything in advance. It is to move everything knowable out of the post-move-out sequence, and to book vendors against the likely scope with room for what emerges. A turn that starts at notice and finds one surprise on move-out day still finishes far ahead of a turn that started from zero.

Two practical points. Entering an occupied unit for an inspection may require advance notice or other compliance with the lease and applicable local law, so build those requirements into the process rather than improvising them. And explain the reason for the inspection clearly to the resident.

The first-touch gap

Look at the top of the left-hand column once more. Notice received and filed.

That single row hides a delay that is easy to overlook. The gap between a resident giving notice and anyone in maintenance doing anything about it can become a significant source of delay.

The reason is structural. Notice to vacate usually arrives at leasing. It is a leasing event: a lease is ending, a renewal has failed, a unit is about to need marketing. The turn is a maintenance event. And in a great many operations, leasing and maintenance run in different systems, with different queues, and the handover between them is an email, a spreadsheet row, or a conversation at the Monday meeting.

Every day between the notice landing in leasing and it landing in maintenance is a day of float thrown away. The weeks that could have absorbed scoping, ordering and booking shrink, and tasks that could have been done in advance drift back into the sequence after move-out.

This is a handoff problem of exactly the kind described in our guide to the lead-to-lease process, except it runs between departments rather than between stages of the leasing funnel. The fix is the same shape: the notice should trigger the maintenance workflow, with an owner and a date, rather than depending on somebody remembering to pass it on.

Chasing the wrong vendor

Critical path thinking has one more implication that changes how a turn coordinator spends the day.

Not every delay matters equally. A task with float can slip without affecting the finish. A task on the critical path cannot slip by an hour without the rent-ready date moving with it. As one project scheduling guide puts it, without critical path visibility a project manager treats every delay as equally urgent, wasting effort expediting tasks that had slack to spare while missing the one quietly sinking the deadline.

In a turn, that looks like a coordinator chasing the appliance delivery that is not needed until day four, while the painter who was due on day two has not confirmed. Both are late. Only one is moving the date.

The practical version for a turn is simple. At any moment, know which task is currently on the critical path, and put your chasing effort there. Everything else can wait for the call.

When many turns overlap

Everything above treats one unit in isolation. Real portfolios rarely have that luxury.

When several units come due in the same window, the same painters and flooring crews get spread across all of them, and the waiting days in the left-hand column multiply. A vendor who can do three units a week and has seven booked is not just a scheduling detail. That resource constraint can delay the sequence of work across several turns at once.

This is where starting at notice matters most, because early booking gives you more opportunity to secure vendor capacity before the move-out date arrives. It is also why concentrated lease expirations are an operational risk rather than just a leasing one, which we covered in your leasing season was decided twelve months ago.

Rent-ready is not the finish line

A turn finishes when the unit is rent-ready. The unit does not earn anything until someone moves in.

Everything between those two points is leasing, and it is its own critical path: photographs, listing, tours, application, approval, lease signing. A turn that finishes on day four and then waits two weeks for photography, or sits while an application waits on a landlord reference, has only moved the delay rather than removed it.

Two connections worth making. The first is photography: a listing standard that requires photos of the actual unit taken since the last turn, which we argued for in why the same unit looks different on five sites, is only achievable if photography is booked as part of the turn rather than after it. The second is approval time, where the waiting rather than the deciding tends to consume the days, covered in three days to approve, almost none of it deciding.

And the most ambitious version of all is to market the unit during the notice window, so that a new resident is lined up before the old one leaves. That brings its own risks, since you are committing to a unit you do not yet control, and we cover them in pre-leasing an occupied unit: what you are actually promising.

What to put in place

Measuring the split between make-ready days and marketing days is covered in our article on what your days-on-market number is actually measuring, and what those days cost is covered in why a turn costs more than your budget says. This section is about the workflow itself.

• Make notice to vacate a trigger, not a record. The moment it is received, it should open the turn in maintenance with a named owner and a date, not wait to be forwarded.

• Schedule the pre-move-out inspection automatically. A standard number of days after notice, with any required resident notice built in.

• Book vendors against dates, not against availability. "Painter on the day after move-out" is a booking. "We'll call the painter when it's empty" is a waiting day.

• Stock the common parts. Filters, blinds, standard hardware, the paint colours you use in every unit. An order-and-wait cycle mid-turn puts a delay directly into the sequence.

• Sequence trades back-to-back, and confirm the day before. The confirmation call is where you find out about the waiting day while you can still do something about it.

• Know which task is critical today. Put the chasing effort there.

Put the two calendars side by side one more time. The right-hand column did not have a better painter, a bigger budget or a harder-working team. It had the notice arrive in maintenance on the day it arrived in leasing, and a coordinator who treated the empty unit as the moment to finish preparing rather than the moment to start.

That gap, between a notice arriving and anyone acting on it, is where the week in that illustration went. It is rarely a people problem. It is two departments running on two systems with a handover in between.

RIOO brings leasing and maintenance into the same property management environment. Move-ins and move-outs are managed alongside maintenance planning and scheduling, with vendor management in the same place, so leasing and maintenance activity can be managed within one environment rather than relying on a handoff between separate systems.

Take your last ten turns. For each, find the date notice was received and the date the first vendor was booked. The number of days between them is the float you have been giving away.

Frequently asked questions

Q1. When should the apartment turn process start?
When notice to vacate is received, not when the resident moves out. Tasks that do not require an empty unit, such as scoping likely work, ordering parts and booking vendors for specific dates, can be completed during the notice period, which removes them from the timeline after move-out.

Q2. Why do apartment turns take longer than the work itself?
Because a turn is a sequence of dependent tasks, and the waiting between them, for parts and for the next vendor, can sit on the critical path. When it does, each day of waiting can delay the finish, however quickly the work itself is done.

Q3. What is the critical path in a make-ready?
The longest chain of dependent tasks, which sets the shortest possible turn duration. The exact order depends on the scope and the property, but repairs commonly need to precede painting, with some flooring and cleaning work following. A delay on a task that sits on the critical path moves the rent-ready date.

Q4. Can you inspect a unit before the resident moves out?
Often, provided you follow the requirements of your lease and applicable local law. A pre-move-out inspection identifies much of the likely scope in advance, though some damage will only be visible once the unit is empty.

Q5. What delays a turn most often?
Frequently it is not the work but the time before and between it: the gap between notice being received and maintenance acting on it, parts ordered only after move-out, and vendors booked against availability rather than specific dates.