The Guest Who Wants a Third-Party Cleaning Service
A guest asking to bring their own cleaner is asking for a preference, and granting it hands you a liability. Three things move to your side of the line: access, attribution and building cover. Written terms before the visit keep the request small.
A guest asks to bring their own cleaner mid-stay. The request is reasonable, and it quietly transfers three risks to you unless you set terms first.
Last updated: October 14, 2026
A guest messages on day four asking whether they can bring in their own cleaner. It's a normal request, usually made by someone with an allergy, a preferred product, or a long stay and a habit. You can say yes. What you can't do is say yes without deciding who's responsible for the hour that follows.
Key Takeaways
- A preference isn't a liability. How the unit gets cleaned is a request you can grant. Who's inside it is a decision you own.
- Access outlives the stay. A code given to a cleaner doesn't come back when the guest checks out.
- Attribution is the quiet cost. Once someone else cleans, you can't separate their mark from the guest's or your own.
- Write the terms before the visit. Six lines in the thread do more than a paragraph of goodwill.
- Your turnover still runs. A mid-stay clean doesn't replace the clean between guests.
Separating a preference from a liability
Start with what the guest is actually asking for. In most cases it's a preference: they want the floors done on a Tuesday, they react to a fragrance, they've used the same cleaner for years and trust them. None of that threatens you. All of it can be accommodated.
The liability is a different sentence, and it usually arrives attached. It's about who enters the property, under what authority, with what access, and who answers if the tap is left running or the neighbour complains about a van in the loading bay.
Those two things get bundled because they arrive in one message. Your job is to unbundle them in your reply, politely and in one pass.
A workable line sounds like this: "Happy for your cleaner to come in on Thursday. Before then, I need to confirm a few things so there's no confusion later." You've granted the preference and kept the liability open, which is exactly where you want it.
What you're avoiding is the vaguer yes. "Sure, no problem" feels generous in the moment. It also means that when something goes wrong, there's no agreed version of what was supposed to happen, and the conversation becomes a negotiation about memory.
The test is simple. If the guest's cleaner damages something, who do you call? If the answer is "the guest, eventually," you've taken the risk without taking the terms.
Some requests aren't a preference at all. If the building bans outside contractors, if the guest wants a cleaner inside while nobody's present, or if the unit is mid-turnover when the request lands, the honest answer is no, with a reason attached.
A refusal lands better with an alternative. Offer your own cleaner on another day, a mid-stay linen swap, or a later checkout so the guest can do it themselves. What you're refusing is the unmanaged version, not the guest's comfort. A weekly cleaner for a month is also a different arrangement from one visit, closer to a service than a favour, and it deserves a price and a schedule rather than a yes.
The three risks that move to you
Access. A door code, a key or a building fob handed to a cleaner is handed to someone you didn't screen, and it doesn't come back on checkout day. Guests leave; codes stay valid. If the building uses a key safe, the combination is now known to a person outside the booking. Change what you can change, and write down what you can't.
Attribution. Once a third party cleans, damage stops being traceable. The chip on the sink, the mark on the wall, the missing towel: you can't say whether it happened before the visit, during it, or in the hour after. Your own standard becomes unverifiable, and so does the guest's defence.
Building and cover. Many buildings treat a paid contractor differently from a guest. There may be working hours, a registration step, a lift-protection rule, or a requirement that contractors are named in advance. Separately, whether a paid cleaner is covered under your own arrangements is a question for your insurer. Ask it before the visit, not after the claim.
There's a fourth pressure that doesn't count as a risk on its own: your supplies. A cleaner who brings their own products still uses your water, your vacuum, your bin bags and your linen. None of that gets counted unless you count it.
Terms to agree in writing before the visit
Put the terms in the same thread where the guest asked. Six lines are enough, and each one closes a gap you'd otherwise argue about later.
- One named person. A name, not "my cleaner" and not "the team". If a substitute turns up, you want to know before they're at the door.
- A date and a window. Two hours, not a day. It tells you when the unit is occupied by someone who isn't a guest.
- Who opens the door. The guest, ideally. If it's you, say so, and say what happens if nobody's there.
- What's covered. Rooms, and specifically what's excluded: the balcony, the storage cupboard, the linen. Guests assume everything.
- Products and equipment. What can't be used on the stone, the timber, the shower screen. Which of your items they may use and which stay untouched.
- The damage path. A photo and a message to you the same day, from the guest. Not a repair, not a replacement, and not silence.
Add one more line if the stay is long: the visit doesn't reset the booking. Nothing about the stay changes because a cleaner came in. If the visit turns into an extension or a room change, that's a separate decision, and it's one you confirm before it happens rather than after. In LOCALSBNB, changes like check-in, check-out, extension and room change run only on overseas stores and only once you've approved them, so the guest sees the request and you see the change.
The access side has a similar shape. When someone joins your operation, the permissions are scoped by domain, such as bookings, finance, availability or rates, and guest names and phone numbers are masked by default. A cleaner needs the calendar. They don't need the payout report.
None of this is hostile. It reads as competence, and most guests relax when they see it, because it tells them you've done this before.
What to check when the cleaner leaves
The check takes ten minutes and it's the same ten minutes whether the cleaner was yours or theirs.
Walk the unit with your phone and take the shots you already take at turnover: the kitchen from the doorway, the bathroom, the bedroom, the floor by the entry. Same angles, same order. Photos taken on the day are the only record that survives a disagreement three weeks later.
Then check the things that fail silently. Water on the floor near the shower. A window left open in a room with air conditioning. A bin bag in the hallway instead of the chute. A vacuum still plugged in. A door that's locked but not deadbolted.
Count the linen you left out, if you left any. A cleaner with their own products may still use your towels for the floors, and that's the kind of thing nobody mentions.
Then send one short message to the guest: the unit was checked at this time, these were the notes, thanks for arranging it. That message is the record. It also closes the loop while everyone's still being polite.
The last thing to check is your own calendar. A mid-stay clean doesn't move the checkout, and it doesn't shorten the turnover before the next arrival. If the visit ran long or the guest now expects a clean every week, that's a conversation about the stay, not a favour. If you want the whole picture in one place, localsbnb.com keeps the arrivals, the departures and the gap between them in a single view, so a mid-stay visit never quietly eats the window you need.
A refusal lands better with an alternative attached. You can offer your own cleaner on a different day, a mid-stay linen swap, or a later checkout that gives the guest time to do it themselves. What you're refusing is the unmanaged version, not the guest's comfort.
FAQ
Can I refuse a guest's request to bring their own cleaner?
Yes, and you should when the building bans contractors or nobody can be present. Refuse the unmanaged version and offer an alternative, such as your own cleaner on another day.
Who's responsible if their cleaner damages something?
Responsibility usually follows whoever arranged the cleaner, which is why the terms matter more than the answer. Ask for same-day photos and a message, and keep your own photos from before the visit.
Does a mid-stay clean replace the turnover?
No. The turnover before the next arrival still has to happen, on your schedule and to your standard. A mid-stay visit is an extra, not a substitution.
A guest's cleaner is rarely the problem. The missing terms are. Six lines in the thread, one named person and ten minutes with a phone turn an awkward request into a routine one. When you want the arrivals and departures behind that decision in one place, localsbnb.com is where they already sit.
This is general advice for hosts, and it isn't legal, tax or insurance advice. Rules and platform terms vary by place and change over time; check the current requirements of your local authority and the current terms of each platform you use.
Reviewed by
Localsbnb Editorial Team