The Changeover Saturday: Sequencing Two Teams

Two teams, one afternoon, four properties. The order you send them out in decides whether anyone ends up waiting.

Last updated: October 4, 2026

A changeover Saturday looks like a cleaning problem and behaves like a routing one. The work is the same whether you send the teams out well or badly. What changes is how many of them finish standing around, and whether the last arrival of the day meets a property that's ready. The fix happens on Friday night, on paper, not on Saturday morning in the car.

Key Takeaways

• Map the day before it starts. List departures, arrivals and the route between them the night before, not at the first door.
• Send a team along a route, not to a property. Assigning by area beats assigning by whoever's closest to the next job.
• One dependency usually decides the order. Shared linen, a single key set or one supply store can gate the whole afternoon.
• Name one owner at each crossing. Where the two teams meet, someone has to be accountable for the handover rather than for their half.
• Hold back the last slot. A buffer kept for the turnover that slips is cheaper than discovering the slip at the last arrival.

Mapping the day before it starts

The sequencing for Saturday is done on Friday. By the time the first team is at a door, the plan should already be written, and Saturday should only be about following it.

Start with a single list. Every property, its departure and its arrival, in time order. Two lists, one per team, is how a property ends up in neither. One list, with the properties marked as you assign them, keeps the whole day visible while you decide.

Then mark the pressure. Which arrivals are earliest? Which properties sit furthest apart? Where does the linen live, and does any property hold something the others need? Those marks, not the order you wrote the list in, are what decide the sequence.

Read the day from the arrivals backwards. Each arrival sets a deadline, and working back from those deadlines shows you which turnover has the least room around it. The property with the tightest gap between its departure and its arrival is the one that anchors the plan, and everything else gets arranged around it.

One more thing belongs on the Friday list: what could move. If a guest is due to leave late, or a flight lands in the evening, note it. Knowing which arrival is soft and which is fixed is what lets you move a job later without guessing.

Which property goes first, and why

The instinct is that the earliest arrival always goes first. It's usually right, and it's worth knowing when it isn't, because those are the days that go wrong.

Arrival time is the first filter. A property whose next guest checks in early has to be finished before the others, almost regardless of anything else. Put those at the front of the queue.

Dependency is the second filter, and it can outrank the first. If the linen for two properties sits at one of them, that property may need to be done first so the second team can collect on the way. The same applies to a single key set, a shared supply cupboard or a parking space both teams need. A property that unlocks another one is a gate, and a gate opens before the queue behind it moves.

The travel chain is the third. A route that runs in one direction across the afternoon leaves no dead miles; a route that doubles back does. When two properties are similarly urgent, give the team the one that sets up the shorter run to what comes next, not the one that happens to be nearest to where they start.

Then rank the risk rather than the distance. The property with the fussiest arrangement, or the one where something usually goes wrong, deserves the slot with the most room around it. Sequencing the known-tricky property into a tight gap is how a whole day loses its shape.

LOCALSBNB shows each connected channel's dates and source status beside the calendar, so the arrivals that set your deadlines are visible in order rather than collected from separate apps and remembered.

Where the two teams cross paths

With four properties and two teams, the day has at most one or two places where the teams meet. Those are the points where a good plan either holds together or comes apart.

The crossing is usually a handover, not a shared job. One team finishes a property that holds the linen, and the other collects from it. One team returns a set of keys the other needs. One team uses the supply cupboard the other is waiting on. Each of those is a moment when one team's finish is another team's start, and the whole afternoon can hinge on it.

Sequence the crossing rather than hoping it works out. Decide which team reaches the shared point first, and tell both teams so. A crossing left to chance is the one where two people arrive at the same cupboard at the same time, and one of them waits while the other works.

Name an owner at each crossing. It should be one person, not both, and the owner is accountable for the handoff rather than for their own half of the day. Where two teams are each responsible for half of a crossing, nobody owns the join, and the join is exactly where the key or the linen goes missing.

Keep the teams out of the same property at once. Two people working the same small flat get in each other's way and use more time than either would alone. If a property needs more than one pair of hands, that's a signal to give it the room rather than to double up inside it.

A single source of truth for who is where makes the crossings calm. When both teams can see the day's order, the handover stops being a phone call and becomes a time both sides already know.

The buffer you keep for the one that slips

Something always slips on a changeover Saturday, and the plan that survives is the one that expected it.

Hold back the last slot of the day. Don't fill it with an extra property or an early start; leave it open. That slot is what absorbs the late departure, the longer-than-expected job or the arrival that moves earlier. On the days nothing slips, it converts into an early finish, which is a fair reward for the teams doing the work.

Then resist spending the buffer early. The temptation on a good morning is to push ahead and take on more, believing you've banked the spare time. You haven't; you've borrowed it from the afternoon, which is exactly when you might need it back. A buffer spent at ten in the morning is a buffer that's gone by four.

Decide in advance which property gets the buffer. It should be the one most likely to slip or the one whose arrival is latest, not whichever team finishes first. Naming it on Friday means the answer doesn't have to be negotiated in the moment, when everyone is tired and one team has already gone home.

Watch the whole day, not just each door. The Home dashboard's occupancy and average nightly rate give you a quick sense of how loaded the stretch is, and the calendar shows the arrivals in one place. localsbnb.com keeps that picture together, so a heavy Saturday is something you plan around rather than discover.

FAQ

Should the earliest arrival always be cleaned first?

Almost always, but dependency can outrank it. If one property holds the linen another needs, or unlocks a shared key or supply point, it may need to go first so the rest of the day can move. When the two rules conflict, the property that gates the others wins, because everything behind it waits on it.

How do I split four properties between two teams?

By route rather than by count. Give each team a run that moves in one direction and keeps the crossings to a minimum, then check that the tightest arrival sits on the team that can reach it first. Splitting by two properties each sounds fair and often doubles the driving.

What if one team finishes early and the other is behind?

That's what the buffer is for, and it should go to the property that was named for it rather than to whichever team asks first. Sending the early team to help can break a schedule that was working, so keep the spare capacity where the plan said it would be needed.

A changeover Saturday rewards the host who planned it on Friday. Map the day, rank the properties by arrival, dependency and travel, own the crossings and hold back a slot for the one that slips. localsbnb.com keeps the day's arrivals and the week's numbers in one place, so the order you set is the order two teams can actually follow.

---

This article is general guidance for hosts rather than legal, tax or insurance advice. Cleaning arrangements, local rules and platform terms differ by place and change over time; check your own setup and the current terms of each platform you use.