Shared Spaces With Long-Stay Guests: Rules Before Check-In

A two-night guest tolerates a shared kitchen. A thirty-night guest negotiates it. The rules you send before arrival decide which conversation you have.

Last updated: October 19, 2026

The first week of a long stay is a honeymoon. The kitchen is used politely, the washing machine runs at reasonable hours, and everyone says good morning. Week three is when the rules get tested, and week three is too late to write them. The note you send before arrival is the version of the rules that survives the honeymoon.

Key Takeaways

• Two kinds of shared space need two kinds of rule. Some spaces can be scheduled; others can only be negotiated.
• Send the note before arrival, not at the door. A rule read in advance is a condition. A rule read at the door is a surprise.
• Under 400 words, numbered, in the guest's language. Long notes get skimmed, and a skimmed rule isn't a rule.
• Test every rule three ways. Is it observable, proportional and repeatable across thirty nights?
• Answer the first breach the same day, in writing. The first response sets the tone for the rest of the stay.

Two kinds of shared space

A shared entrance, a shared kitchen and a shared wall are not the same problem, even though they all get called shared space.

The first kind is schedulable. Someone uses the washing machine from seven to nine, someone else from nine to eleven. The kitchen is busy between six and eight in the evening, so a long-stay guest who cooks late gets a clear window. The parking space has an owner and a rota. These spaces can carry a timetable, and a timetable is easy to keep because it's visible.

The second kind is only negotiable. Noise through a floor. Cooking smells in a stairwell. A television at midnight. Bins that get put out on the wrong day. You can't schedule a smell. You can only agree a threshold, and a threshold works when both sides know where it sits.

Most host notes fail because they treat the second kind like the first. "Please respect quiet hours" is a timetable with no times in it. "Be considerate in shared areas" is a threshold with no number.

There's a second split worth naming, because it changes who enforces the rules. If you live on site, you're the referee, and the rules mostly describe what you'll ask for. If you live elsewhere and guests share with each other, the rules are the only referee. In that case, the note has to be specific enough for two strangers to apply it without you.

What belongs in the pre-arrival note

Send it three to seven days before arrival. One message, numbered, under 400 words. Write it in the language the guest used when booking; our workspace follows the property's language setting across six languages, and a rule in a language someone reads slowly is a rule half understood.

Eight things earn a place.

Which door, and how it opens. The entrance guests actually use, the code or key, and what to do if it fails at night. If entry is by smart lock, say that plainly and give the fallback. Don't turn it into a feature list; a guest standing outside wants one instruction.

Which spaces are shared, and with whom. "The kitchen and laundry are shared with the two guests in the back room" is useful. "Shared areas" is not.

Quiet hours with a reason. "No washing machine or vacuum between 22:00 and 08:00, because the neighbour's bedroom is above the utility room" gives a guest something to comply with and a reason to comply.

Kitchen arrangements, if the kitchen is tight. Shelf or cupboard allocation, fridge space, when the hob is busiest, where dirty dishes go if they're not washed tonight.

Laundry windows. Two slots a day beats "please be considerate". Long stays generate laundry, and laundry is where a polite arrangement quietly collapses.

Bins and recycling. Which bin, which day, who takes it out. A thirty-night stay will span at least four bin days.

One line on visitors. Whether a guest can have someone over, for how long, and whether that person counts as a guest for the shared spaces.

What to do when something breaks at night. One number, one instruction, and a promise about response time you can actually keep.

Leave out the history of previous guests, the apologies for the rules, and any list longer than this one. A note that reads as an apology gets treated as a suggestion.

Rules that hold for a month

A rule for a two-night stay only has to survive a weekend. A rule for thirty nights has to survive payday, a bad week at work and the point where the guest stops thinking of the flat as someone else's home.

Three tests will remove about half of what most hosts write.

Is it observable? Can a guest tell, in the moment, whether they're following it? "Keep noise down" fails, because nobody knows where the line is. "No washing machine after 22:00" passes, because the clock answers the question. If a rule needs a judgement call every time, it'll be interpreted in the guest's favour.

Is it proportional? Does the rule cost the guest something small and give them something clear? "Don't use the kitchen after nine" costs a night shift worker their dinner and gives them nothing. "Finish cooking by 22:00 and wipe the hob" costs ten minutes and keeps the kitchen usable. Long-stay guests follow rules that make sense to them, and quietly route around rules that don't.

Is it repeatable? Would you still enforce it in week four, on a rainy Tuesday, when you're tired? If not, don't write it. A rule you enforce in week one and abandon in week three teaches the guest that the note was decoration.

Two additions make a long stay easier for everyone.

Give each long-stay guest one place that's unambiguously theirs. A shelf in the fridge, a cupboard, a hook by the door. Shared space works better when it has a small private edge.

Check in at day seven, for five minutes. Not a survey. One message asking whether the kitchen timing works and whether anything in the note is unclear. Week-one friction is easy to fix and expensive to leave.

Handling the first breach

The first breach is the most important one, because it's the only one where the guest is still unsure whether the rule matters.

Answer the same day, in writing, and reference the rule rather than the person. Three sentences cover it: the rule, the effect, the fix.

"The washing machine ran past midnight last night. The neighbour above the utility room can hear it, and they've asked twice this month. Can we keep laundry to before 22:00 from here?"

That's it. No warning, no threat, no mention of the deposit. A first breach answered calmly usually ends there, and the guest now knows the note is real.

Write it down the same day. Date, what happened, what you sent, what came back. If the stay later needs to end early, that log is the difference between a decision and an argument. When a booking needs to be extended, moved or ended, those are actions our system runs only after you confirm the guest and the dates — the decision stays with you, which is the point.

If it happens a second time, move from a message to a conversation. Say what you've noticed, ask what's making it hard, and offer one adjustment that keeps the rule intact. A guest who's working nights may genuinely need a later laundry slot; a guest who's ignoring the rule needs a written consequence.

A third breach is a written warning with a named consequence, sent the same way. Keep it short and keep it factual. By then the log has three entries, and you're no longer relying on memory.

Then close the loop at check-out. A two-line message thanking them for the parts that worked costs nothing and makes the next long stay easier to start. When you want the check-in, the extension and the shared-space note in the same place as the booking, localsbnb.com is where they sit.

FAQ

What if a guest won't accept the rules before arrival?

Raise it before check-in, in writing, and be specific about which rule doesn't work for them. It's much easier to decide not to proceed before arrival than after, and a guest who argues with the note in advance is telling you something useful about week three.

How long should the note be?

Under 400 words, numbered, with the eight sections above. If it's longer, you're describing your preferences rather than the shared spaces. Cut anything a guest can't act on.

Does the note need to be in the guest's language?

It should be in the language they booked in. Our workspace follows the property's language setting across six languages, so the note and the booking record stay consistent, and a guest reads the rule in the words they use.

Write the note once, keep it as a template, and edit the two or three lines that change per guest. It takes twenty minutes the first time and three the next. You can keep the booking, the check-in and the note together at localsbnb.com, where the property's language and time zone are already set.

---

This is general guidance for hosts, not legal, tax or insurance advice. Sharing arrangements, tenancy rules and local requirements differ by market and change over time, so check the current rules where you operate and the terms you've agreed to.