Setting House Rules a First-Time Guest Understands

House rules fail for a boring reason: they're written for an argument that hasn't happened yet. Write them for the guest who wants to get it right.

Last updated: October 1, 2026

Almost every rule list starts the same way. Something went wrong — a late party, a damaged wall, a neighbour's complaint — and a rule gets added so it can't happen again. That's a reasonable instinct and it's the reason so many lists fail. The guest reading your rules isn't the one who caused the problem. It's someone who wants to get it right, and a document written for an argument reads to them like an accusation.

Key Takeaways

• Long lists get skimmed. A guest scanning ten rules remembers none of them; a guest scanning three remembers two.
• Three rules carry the weight. Protect the neighbours, protect the property, protect the guest's own stay — the rest is optional.
• A rule needs a number, a time or a place. Add a reason and it becomes followable instead of negotiable.
• Preferences aren't rules. If breaking it changes no outcome, it belongs in the check-out note, not the rules block.
• One wording, two places. The guest should find the same sentence where they booked and where they stay.

Why long rule lists get skimmed and then broken

Rules aren't broken out of defiance. They're broken out of overload, and length is what creates the overload.

Think about the moment a guest reads them. They're halfway through a booking, comparing two places, on a phone, deciding in about ninety seconds. At that point, a rules block is competing with photos, price and reviews for a small share of attention. Ten rules read as a warning label. Three read as instructions.

There's a second failure, and it's about precision rather than length. A rule that nobody can measure can't be followed. "Please keep noise to a minimum" sounds considerate and tells a guest nothing — not a time, not a limit, not what counts. When a guest can't tell whether they're inside the line or outside it, they stop trying to work it out. The rule hasn't been broken. It's been ignored, because it couldn't be used.

Then there's the third failure: a rule with no reason attached. "No shoes inside" invites a debate in a way that "no shoes inside — the floors are original and scratch easily" doesn't. The reason answers the question a guest would otherwise ask you at eleven at night.

Fix the shape and the content starts working. Put the two rules that matter most first. Give each one a number, a time or a place. Add the reason in the same breath. Cut anything that only matters to you.

Three rules worth stating, and how to word each one

Most properties need about three rules, and they fall into three jobs: protecting the neighbours, protecting the property, and protecting the guest's own stay.

Quiet. This is the one that decides whether you keep your neighbours. Word it as a window, name what carries, and stop there.

Quiet hours run from 10pm to 7am. The building has wooden floors and sound travels down, so music and hard shoes land in the flat below.

Notice what that does. It gives a time, so it's testable. It gives a reason, so it doesn't sound arbitrary. It names the specific behaviours, so a guest knows what to change.

Occupancy and visitors. A guest with an uninvited overnight visitor is a neighbour problem and an insurance problem at the same time, so state the number and the route.

The flat sleeps four. Extra overnight guests need to be agreed before they arrive — message me and it's usually fine.

That last clause matters more than it looks. A rule with a visible way to comply gets followed. A rule with no route around it gets worked around.

Smoking. Say where it's allowed, and add the one detail that actually affects the building.

Smoking is fine on the balcony with the door closed. Not inside, and not in the stairwell.

Three rules, each with a number, a time or a place, each with a reason. That's a list a guest can read once and hold.

The difference between a rule and a preference

Most rule lists are too long because they mix two different documents. A rule and a preference look like sentences, and they behave nothing alike.

A rule changes an outcome and applies to everyone. A preference describes how you'd like things done, with no consequence attached. Put four preferences in a rules block and a guest who quietly skips one learns that the list is flexible — which is exactly the assumption you don't want them carrying into the quiet-hours rule.

Three tests separate them.

Could you tell whether it happened? You can tell whether there was a party. You can't tell, without inspecting, whether someone rinsed the dishes before leaving. Testability is the first sign you're holding a rule.

Does it apply to you too? If you'd do it yourself when staying somewhere, and nobody's harmed when it's skipped, it's a preference. "Take the bins out on Tuesday" is a real request with a real consequence for the building, so it can be a rule. "Please strip the beds" is a courtesy.

Would you say it to a guest's face as a condition, or as a favour? Conditions go in the rules. Favours go in the check-out note, phrased as a request, with the reason attached.

Keep both documents. They just need to be different documents. Move the preferences into your check-out message, where they sit next to the practical items a guest is already reading: where to leave the keys, which bin goes out, what to do with the towels.

Where rules live so a guest can find them twice

A guest meets your rules twice: once when they book, and once when they're standing in the flat with the kettle on. Both moments need the same words.

The first is the rules field in your listing. Guests arrive through whichever channel they booked on, so the rules need to be present on all of them. Airbnb, Booking.com, Agoda and Trip.com are the four channels LOCALSBNB connects to directly at localsbnb.com, which keeps availability and rates in step from one calendar instead of four. That turns the job from retyping the same paragraph into getting the wording right once.

The second is physical and online in the flat: one card, in the same spot in every property, plus the same text in the arrival message. A guest who wants to double-check quiet hours at nine at night shouldn't have to scroll back through a booking thread to find them.

When you set up a property, you can bring the basics across from Airbnb — the title, the photos, the base capacity and the calendar structure — so the setup time goes on the parts a guest actually reads. Then take one rule and write it once, in a document you own, and paste that exact wording into the listing and the card. Three slightly different versions of the same rule is how a conversation about a door code turns into an argument about whether smoking was ever allowed.

Finally, look at your list once a year and delete. Rules accumulate after problems, and problems fade. A rule that hasn't mattered in eighteen months is one more line between a guest and the three that do.

FAQ

How many house rules should a listing have?

Around three, and rarely more than five. Anything beyond that is either a preference or an administrative note, and both have better places to live. If you can't remember your own list without reading it, a guest on a phone won't manage it either.

Should I add numbers to a quiet-hours rule?

Yes. A time makes the rule testable for the guest and explainable for you. "Keep it down" leaves a guest guessing at a line they can't see, and guessing is what produces a complaint you'd rather have avoided.

What if a guest breaks a rule I never wrote down?

Treat it as a gap rather than a violation. Write the rule, word it with the reason, and put the same wording in both places. Most first-time guests break an unwritten rule, which is usually the host's fault rather than theirs.

Rules are one of the few parts of hosting where less work produces a better result. State three, word each one with a number and a reason, move everything else to the check-out note, and let a guest find the same words twice. It's a short document, and a short document is the one that gets read. Hosts who keep their channels and their property details together at localsbnb.com spend the time they save on the wording guests actually meet, rather than on copying the same paragraph into four places.

---

This article is general guidance for hosts and isn't legal, tax or platform policy advice. House rules, local rules and platform terms differ by place and change over time; check the current terms of each platform you use and the requirements that apply where the property sits.