Key points
- Keep a release date for every wave and building.
- Make final cleaning depend on completion of work that could undo it.
- Track releasable units and blockers alongside completed tasks.
Build waves around real constraints
The residence manager brings together confirmed departures, planned arrivals, extended occupations and known works. Create groups with comparable conditions: building, floor, access and deadline. A wave does not need to be large. It needs to help managers decide where teams should work and which units can be returned to use.
Keep occupied units in a separate scope. A planned departure date does not itself authorise entry or work. Access follows the applicable agreements and rules. The UK National Code addresses access and maintenance separately for its members; those provisions should not be treated as a universal turnover timetable for every residence.
Set five release gates
The move-out record identifies defects and missing equipment. Triage converts observations into actions, and repairs make the unit ready for final cleaning. Inspection then checks preparation and unresolved items. A designated owner finally authorises release for the next occupation.
| Stage | Proposed owner | Evidence for moving forward |
|---|---|---|
| Move-out | Residence team | Identified unit, occupation ended and dated observations |
| Triage | Technical manager | Defined actions, confirmed access and supplies |
| Repairs | Assigned contractor or technician | Work report and remaining exceptions |
| Preparation | Cleaning team | Agreed service completed in the correct unit |
| Release | Inspector or manager | Accepted inspection with no open blocker |
Completing one task should not bypass subsequent gates. Replacing a piece of furniture may create a new cleaning requirement. A failed inspection should reopen the relevant action without erasing the work already completed or making the earlier history impossible to understand.
Maintain a wave-level campaign board
Use columns for building, wave, expected units, accessible units, repairs in progress, preparation in progress, releasable units, blockers and next decision. Add the target date and the person responsible for each exception. Keep unit references behind the totals so that the position can be traced to actual rooms.
Start each progress review with the waves nearest their target date. Ask which dependency prevents the next gate: an outstanding part, unconfirmed access, cleaning rework or an unavailable inspector. A precise answer allows a manager to move resources. “Almost finished” gives the arrivals team little usable information and should be replaced by a clearly stated remaining action.
Use the right denominator for available capacity
In a fictional example, building A has a wave of 40 expected units. At the review, 32 have been cleaned, but 4 still await inspection. Only 28 are releasable: 28 / 40 = 70%. The cleaning completion rate of 80% does not describe the capacity actually available for the incoming residents.
If another building has ready units, do not simply add them to the available total without checking whether they match planned allocations. Unit type, equipment or an allocation commitment may matter. Management decides whether assignments can change and communicates any agreed changes to the teams responsible for preparing and welcoming residents.
Handle exceptions without stopping every wave
A resident extends their stay, a delivery is missing or work needs repeating. Remove that unit from the normal flow and assign an exception owner. The remainder of the wave can progress if access and work conditions allow. The revised release date remains a forecast until its dependencies are confirmed.
Do not release an area solely because bedrooms are clean when necessary shared spaces remain unavailable. A communal kitchen or circulation area undergoing work may affect the use of the wave. The technical manager assesses applicable restrictions, while the campaign board shows which units are affected and what decision is needed to move them forward.
Close the campaign and improve the next one
Closure includes the list of released units, exceptions accepted by the appropriate owners and actions continuing outside the campaign. Preserve the reference condition needed for the next occupation under internal record rules. Keep any financial decision separate from the operational move-out observation.
Review three questions: which waves were poorly sized, which dependencies emerged too late and which evidence was difficult to obtain? Adjust the grouping and preparation dates for the next campaign. Avoid turning an isolated incident into a large new procedure unless the review shows a recurring problem that the additional step would actually address.
For the wider setting of a property serving different guest groups, see The Social Hub hybrid operations case.
Frequently asked questions
Can a wave include several buildings?
Yes, when access arrangements, teams and deadlines genuinely align. Still retain building-level subtotals. Otherwise progress on one site can hide a delay in the building where the next residents are due to arrive.
When should final cleaning be scheduled?
After work likely to create dirt or obstruction has finished. If a contractor must return, the wave owner reassesses the preparation needed. The schedule should follow that dependency rather than a cleaning date fixed before the repair scope was known.
