Waiting for returned keys leaves make-ready planning too late. This two-clock system helps U.S. property managers coordinate notice, access, work, inspection, and leasing readiness.
In U.S. property management companies, the unit turnover workflow often starts too late. The team waits for keys, then finds a long repair list, a vendor conflict, missing access instructions, or a leasing promise built on a date nobody verified. By then, every fix puts pressure on the schedule.
A unit turn is the work required to inspect, repair, clean, and prepare a vacated apartment for the next resident, as Entrata describes in its multifamily terminology. The physical work starts after possession returns. Planning should start earlier. This article lays out a two-clock system that connects leasing, maintenance, vendors, inspection, and listing readiness without pretending a forecast is a commitment.
Most turnover checklists begin with an event: the resident moves out. That event matters, but it is not the first useful signal. Once a notice to vacate is accepted, the team has a likely unit, a likely date, a rough scope, and several dependencies it can begin checking.
Early planning does not require false certainty. A reported move-out date is not returned possession. A preliminary scope is not an approved work order. A vendor hold is not a confirmed appointment. Keep those distinctions visible and the team can prepare without telling leasing that the unit is ready.
Turnover work crosses systems whether the software makes that obvious or not. Leasing sees notices and future availability. The property manager coordinates with the resident and controls access. Maintenance estimates labor and likely materials. Vendors need usable windows. Leasing eventually needs a date it can defend. Major property-management platforms span these same functions; Yardi's multifamily overview connects leasing, maintenance, resident services, and unit turns. Local teams often split that work across several screens and conversations.
PASMO recommends two clocks for the first version. The forecast clock starts when notice is accepted. The execution clock starts when possession is confirmed and the team can enter the unit. Mixing them creates bad signals. Work looks booked when it is only anticipated, or a unit looks untouched even though useful preparation is already done.
This two-track plan is a practical starting point. Set the actual time limits around the property's unit types, staffing, vendor availability, and service standard.
| State | Track | Named owner | Evidence to advance | Exception route |
|---|---|---|---|---|
| Notice accepted | Forecast | Property manager | Move-out date and unit record confirmed | Conflicting dates return to resident coordination |
| Pre-turn scoped | Forecast | Maintenance lead | Known issues, access needs, labor class, and vendor needs recorded | Unknown condition stays flagged instead of being guessed |
| Possession confirmed | Execution | Site manager | Keys or access and move-out inspection available | Hold work and leasing promises if access is disputed |
| Work released | Execution | Maintenance coordinator | Sequence, assignments, materials, and vendor windows accepted | Blocked tasks go to one exception owner |
| Ready verified | Execution | Property or quality owner | Inspection evidence and open-item decision complete | Reject incomplete work with a named recovery action |
| Available to lease | Both reconciled | Leasing manager | Verified ready date reaches the leasing record | Withdraw or revise an unsupported availability promise |
The important distinction is not automated versus manual. It is forecast versus authorized. Software can move records and send notifications. A person still owns each decision that changes what the business can promise.
A reliable handoff has an input, an acceptance decision, and evidence. Notice information first moves from leasing into a forecast record owned by property operations. Known unit history and likely scope then become a capacity request for maintenance. Once possession and scope are confirmed, the work package goes to internal technicians or vendors. After the final walk, inspection-backed readiness returns to leasing as an availability commitment.
A sent notification is not acceptance. An email to a flooring vendor does not mean the window is booked. Assigning a work order does not prove that access and materials are ready. Marking tasks complete does not mean the unit passed its final walk. Each transition needs a positive receiving action, even if it is only a status change with a name and timestamp.
This is where the usual advice about one master checklist breaks down. A checklist can describe the work. It cannot settle competing versions of the date. If leasing, maintenance, and a vendor each hold a different assumption, extra checklist items simply document the disagreement in more detail. The system needs an authoritative date, a visible confidence level, and one owner.
The normal path is rarely the problem. Turns lose time when keys are not returned, the unit condition is worse than expected, a vendor rejects the slot, a material is unavailable, or the final inspection sends work back. A general alert to a group inbox will not resolve any of those events. Each one needs a decision owner and a permitted next move.
Put a short exception map beside the two-track plan. For every recurring failure, record who decides, what that person may change, which promise must be protected, and when the issue moves up a level. A site manager may confirm access but should not quietly change a marketed ready date. A maintenance lead can resequence internal work, while leasing owns the customer-facing availability. A regional operator can decide whether a vendor failure warrants moving capacity between properties.
Keep version one small. One unit record, one forecast date, one possession state, one work-release state, and one verified-ready state will beat a maze of statuses nobody trusts. Add detail after a repeated exception proves the team lacks information needed for a real decision.
Start with one property and a small batch of upcoming turns. Map the tools already in use: the property-management system, work-order tool, shared calendar, vendor channel, inspection form, and listing record. Pick the system that owns the unit state. Other tools can receive updates, but they should not create a second version of truth in the background.
During the pilot, measure transitions instead of hiding everything inside one average turn time. Watch notice-to-pre-scope time, possession-to-work-release time, blocked hours by reason, final-walk rejections, and the difference between forecast and verified ready dates. Those measures tell you whether the delay came from planning, access, capacity, execution, quality, or an optimistic promise.
Review exceptions each week with the people receiving the work. The point is not to shame the slowest stage. It is to find the handoff that lacks evidence, authority, or capacity. When the same problem returns, change the state definition, the owner, or the planning assumption before buying another automation.
The turnover clock should help a property team make earlier decisions without manufacturing certainty. PASMO designs connected operating workflows that keep forecasts, human approvals, field work, and leasing commitments in step. The sensible starting point is one building, one turn record, and a clear rule for when each promise becomes real.