Turnover Planning
Key takeaways
- Reserve machine time as deliberately as the cleaner's hours.
- Sequence the loads around the earliest check-in, not the checkout order.
- Keep each unit's linens in a labeled bag or bin.
- Write a fallback for a broken machine before the busy weekend.
Operating data
Playbook
Why shared laundry changes the turnover plan
Two units that share a laundry look manageable until both check out on the same morning. The cleaner needs one set of linens washed, dried, and folded before the first arrival, while the second unit waits for the same machine. A plan that treats laundry as a background task will push one turnover late. The schedule should reserve machine time as deliberately as it reserves the cleaner's hours.
The constraint is not only the wash cycle. Drying, folding, and the walk between the units all take time that a simple checklist tends to hide. When both units have a same-day arrival, the second set may need to start before the first is finished. The coordinator should plan the sequence around the earliest check-in, not around the order the guests leave.
Map the machine time before the day starts
List the checkout time, the arrival time, and the linen needs for each unit before the day begins. A unit that sleeps six needs more sets than a studio, and a guest who requested extra towels adds another load. The coordinator should mark which loads are critical and which can wait. That ranking tells the cleaner what to start first when the day slips.
Check the machine capacity against the number of sets rather than the number of units. One large load may serve both units if the schedule allows a full dry cycle, while two small loads may be faster when time is short. The cleaner knows the equipment, so ask for the real cycle time instead of estimating from a manual. The plan should use the machine the property actually has.
Split the linen sets by unit
Keep each unit's linens in a labeled bag or bin so a set cannot drift between properties. A shared laundry makes it easy to return the wrong towels to the wrong unit, and the next guest notices the mismatch. The coordinator should confirm the count at the start and at the end. Labels are cheaper than a second trip.
Record any stained or torn item during the wash instead of returning it to the shelf. A shared laundry hides damage because the same set rotates through both units. The cleaner should flag the item and note whether a replacement is available. A shortage discovered at the next turnover is harder to solve than one caught during the cycle.
Build a fallback for a broken machine
Assume a machine will fail on the busiest day and decide what happens next. The fallback may be a nearby laundromat, a spare set kept in each unit, or a delay to the later arrival. The coordinator should know which option the owner has approved and who pays for it. A plan without a fallback turns a repair into a missed check-in.
Keep one emergency linen set for each unit and record when it is used. The set should be complete enough to dress the beds and the bathroom, not just a pile of spare towels. After use, the set must be washed and returned before the next busy weekend. A reserve that is never replenished is not a reserve.
Write the laundry step into the handoff
Write the laundry sequence into the turnover brief in the order the cleaner will follow it. Include the start time for each load, the unit it belongs to, and the point when the next arrival must be ready. The brief should also say who moves the laundry if the cleaner is running behind. A clear sequence lets a backup finish the job.
Ask the cleaner to send one update when the first load starts and another when the last set is folded. Two checkpoints are easier to act on than a stream of messages. The coordinator can use the second update to confirm the unit is ready before the guest arrives. The record should show the times, not just the word done.
Work through two Saturdays
Two cabins share a washer and dryer, and both guests check out at ten with arrivals at four. The coordinator starts the larger unit's load first, holds the second unit's arrival message until the first set is dry, and confirms the cleaner has a spare set if the dryer slows. Both units are ready before three. The record shows the sequence and the finish time.
In a second case, the washer stops mid-cycle on a Saturday. The cleaner moves the wet linens to the approved laundromat, uses the reserve set for the earlier arrival, and tells the coordinator which unit will need a fresh set. The later guest is not affected. The repair ticket is opened the same day, and the reserve is restored before the next weekend.
Review the laundry bottleneck
Review the laundry log for repeated overloads at the same time of day. A bottleneck that appears every Saturday may justify a second drying rack, a larger machine, or a different checkout window. The coordinator should compare the planned sequence with the actual finish times. The gap shows where the plan is borrowing time it does not have.
Choose one change and give it an owner. The change might be a labeled bin for each unit, a written fallback, or a rule that same-day arrivals are not promised when both units turn over. Test it on the next busy weekend and record the result. A shared laundry works when the sequence is planned and the fallback is ready.
Related services
- Turnover coordination - Property documentation - Guest communication
Sources
- EPA water efficiency resources
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.
