A Cleaning Schedule Built Around 17-Day Stays

A weekly rota assumes the flat empties every seven days. A seventeen-night booking empties it once, and that single fact moves every clean in the month.

Last updated: October 30, 2026

A cleaning rota is a set of assumptions written as a calendar. The most common one is that each booking ends inside a week, so every unit gets a turnover roughly every seven days. A seventeen-night stay removes that assumption without announcing it, and the rota keeps running as though nothing changed.

Key Takeaways

• The rota isn't wrong, its premise is. Weekly turns are a reasonable default for weekend bookings and a bad fit for a long stay.
• A long booking has two cleaning events, not seven. One turnover at the end, one refresh in the middle, and nothing else unless you decide otherwise.
• Build it backwards from checkout. The checkout time is the only fixed point; everything else is a window offset from it.
• The linen run is the constraint, not the clean. Washing takes longer than wiping, and it's what usually forces the mid-stay date.
• Tell the guest before arrival. A clean nobody warned them about is a privacy complaint; a clean they expected is service.

Why a weekly rota breaks

Most small operations build their rota from the calendar they had last year: weekends busy, midweek quiet, a turnover on Sunday and another on Friday. The rota encodes that rhythm and it works, until a booking arrives that doesn't fit it.

A seventeen-night stay fits nothing. The unit doesn't empty on day seven, so the cleaner booked for that slot arrives at a flat with someone living in it. Either the clean is skipped, or it happens with the guest in the room and a conversation nobody planned for.

The downstream damage is bigger than one missed clean. That cleaner's day was built around a two-hour turnover, and now has a gap in it. The next unit gets their slot compressed. The linen order was placed for a turnover that didn't happen, and the following week's order is now wrong too.

None of this is a discipline problem. It's a scheduling problem caused by a rota that describes the average week and not the actual month. The fix isn't to abandon weekly turns — for weekend bookings they're right — but to know which bookings they don't describe.

The two cleaning events that matter

A hotel cleans every day because a hotel sells a night at a time. A short let sells a stay, and a stay has two moments when cleaning genuinely matters.

The first is the turnover: the full clean between guests, when the unit is empty and everything can be reset. Beds stripped, linen changed, bathroom deep-cleaned, supplies restocked, the state of the place photographed or at least looked at properly.

The second is the mid-stay refresh: a shorter visit while the guest is in residence. Fresh linen and towels, bins out, bathroom and kitchen surfaces, and a look at anything that's drifting — a drain, a bulb, a chair that's coming apart. It isn't a turnover, and treating it like one wastes the slot.

For a seventeen-night stay, those are the only two events the calendar needs. Everything in between is a habit imported from hotels, and every one of them costs a slot that could have gone to another unit. Two visits also mean one conversation with the guest rather than seven.

The mid-stay refresh is the one hosts skip, usually because it's awkward to arrange and easy to postpone. It's also the visit that decides what the turnover at the end looks like: a unit refreshed halfway through is a two-hour turnover, and the same unit left alone for seventeen nights is a different job entirely.

Building the rota backwards from checkout

The checkout is the only fixed point in the whole schedule, so start there and work backwards. The day is known when the booking is confirmed, and it doesn't move unless the guest asks.

First, fix the checkout time and the turnover window that follows it. That window is not negotiable in the same way: if the next arrival is the same day, the turnover has to fit between the two, and if it isn't, you have slack you should use rather than spend.

Then step back to the linen. The wash takes longer than the clean, and it usually has to be collected, processed and returned before the next beds are made. Whatever lead time your laundry needs, the mid-stay date is the latest point at which a set can go out and come back without the guest noticing a shortage.

Then place the refresh itself. Roughly the middle of the stay is the default, and it's a good one, because it splits the interval the guest spends in unchanged linen. Move it for a reason — a guest working from the flat all day, a weekend they'd rather not be disturbed — not for convenience.

Then check the arrival day at the front. The unit needs to be ready before the guest arrives, and the supplies need to be bought before that. Working backwards from the checkout is what tells you whether the front of the stay is actually covered.

Write the offsets on the unit's own line once they're decided, rather than keeping them in your head. Checkout date, turnover window, linen out, linen back, refresh date. Five entries, and the next booking gets the same five worked out from its own checkout.

localsbnb.com is where the checkout date comes from. The day's departures and the current availability sit in the same place, so the fixed point and the slack around it are read in one view instead of being reconstructed from four booking confirmations.

What to tell the guest

The guest needs three things before they arrive: the date of the refresh, the window it will happen in, and what it involves. Not the cleaner's name, not the internal reason for the timing — the three facts they'd ask about if they thought to ask.

Say it at booking, not the day before. A guest who booked seventeen nights and was told at the start that someone will come on day nine between ten and twelve plans around it. The same guest told on day eight feels watched.

Say what the visit includes, in plain terms. Linen and towels changed, bins emptied, bathroom and kitchen wiped, and the rest left alone. Guests worry about someone moving their things, and a sentence that addresses it costs nothing.

Then say what you need from them. Access to the unit, or permission to enter while they're out, and a clear instruction about anything on the floor they'd rather wasn't touched. If they'd rather be present, agree a time instead of a window.

Two smaller things belong in the same message. That there's no daily cleaning — the most common misunderstanding in a long stay — and that any extra clean can be arranged, with the cost confirmed first. Keep that last part simple and honest, and check the platform's terms before you charge for it.

FAQ

Should a seventeen-night stay get more than one refresh?

That's a judgement, not a rule. One refresh in the middle is the minimum that keeps the linen and the bathroom in reasonable condition. Longer stays, or stays in a hot season, usually justify a second visit, and the decision is cheaper to make at booking than on day twelve.

What happens to the weekly rota for the other units?

It keeps running. The point isn't to replace the weekly rhythm, it's to keep long bookings out of it. Put the long stay on its own line with its own dates, and the weekly units continue on the pattern that suits them.

Do I need to tell the guest the cleaner's name?

No, and it's usually better not to. What the guest needs is the date, the window and the scope. Names belong in your own records, along with who has keys, so that a change of cleaner doesn't turn into a change of plan the guest has to absorb.

A rota that starts from the checkout is a rota that survives a long booking. It's also the version you can explain to a cleaner in one sentence. localsbnb.com keeps departures and availability in one calendar across four channels. The fixed point every rota is built from is visible before the month gets planned.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Cleaning standards, notice rules for entering a let unit and limits on charging for extra services differ by jurisdiction and by platform; confirm them with the competent authority and each platform's current terms.