The guest hasn’t even found the parking bay yet. They’re standing outside with two suitcases, looking for the key safe, and their welcome message begins with twelve rules in capital letters. That’s not a great start.
Short-term rental house rules need to protect the property, the neighbours and the turnover schedule. But they also need to sound as though you’re welcoming a paying guest, not reading out the terms of their detention. The answer isn’t to make the rules vague or overly sweet. It’s to make them clear, useful and easy to follow.
For an Airbnb host, that balance matters: the rules should feel like part of the stay, not a penalty notice before check-in.
Start with a clear rule structure
House rules should remove surprises
A good house rule tells the guest something they need to know before it becomes a problem. It should answer at least one of these questions:
- What is or isn’t allowed?
- What does the guest need to do?
- When does the rule apply?
- Where should something be left or parked?
- Who should the guest contact if they need an exception?
“Please respect the property” sounds friendly, but it doesn’t tell anyone whether visitors are allowed, where smoking is permitted or what time noise needs to come down. Specific rules are easier to follow and easier for your team to enforce.
Separate rules from instructions
Many house-rule lists are too long because they contain everything the manager has ever needed to tell a guest. The Wi-Fi code isn’t a house rule. Neither are directions to the key safe, instructions for the heating controller or a photo showing which parking bay belongs to the flat.
Keep the categories separate:
- House rules cover behaviour and boundaries, such as smoking, parties, pets and overnight visitors.
- Property instructions explain how to use things, such as the heating, television, appliances and door entry system.
- Arrival information covers access, parking directions and where to find the building.
- Checkout instructions explain the departure time and the few tasks guests genuinely need to complete.
This matters because guests skim. If your access code is buried between a warning about smoking and three paragraphs about recycling, somebody will still be standing outside the building at 10:15pm asking where the key safe is. The same applies to Wi-Fi. If three guests ask for the password in one week, the likely problem is where you’ve put the password, not the guests’ reading ability.
For a deeper look at separating rules from practical instructions, see how to write guest instructions guests can actually follow.
How to write short-term rental house rules clearly
A useful rule usually contains three parts:
- The boundary: What should or shouldn’t happen?
- The context: Why does it matter?
- The next step: What should the guest do if they need help or an exception?
For example:
Please keep noise low after 10:00pm, particularly in the hallway and on the balcony. We have close neighbours. Message us if another property is causing a disturbance.
The boundary is clear. The reason is short. The guest also knows what to do if the noise isn’t theirs. Not every rule needs all three parts. “Smoking isn’t permitted inside the property” is clear enough on its own. But rules that affect plans, visitors or additional costs often benefit from a little context.
A good rule should make the next right action obvious.
If you want more ready-to-adapt wording, see Airbnb house rules examples guests actually remember.
Cover the rules guests ask about most
Noise and parties: say what “quiet” means
“Please respect our neighbours” is polite, but two groups of guests can have very different ideas about what respectful noise sounds like. Give a time and name the areas where sound carries.
Instead: NO LOUD MUSIC. NO PARTIES. ANY COMPLAINT WILL RESULT IN IMMEDIATE REMOVAL.
Try: Parties and events aren’t permitted. Please keep music and conversations low after 10:00pm, including on the balcony and in shared hallways.
Adjust the time and wording to suit the property. A detached cottage has different noise risks from a second-floor flat above a family with young children.
If your team receives a noise complaint, that usually needs human judgement. A routine question about quiet hours can be answered automatically. An angry neighbour calling at 1:00am should be passed to someone who can assess what’s happening.
Smoking: be direct about the boundary
Smoking rules don’t need a long lecture. They do need to make clear whether the restriction covers the entire property, indoor areas only, balconies, shared entrances or gardens.
Smoking and vaping aren’t permitted inside the flat or in the shared entrance. Please use the designated outdoor area and dispose of cigarette ends in the container provided.
Only mention a designated area if one actually exists. If guests can smoke outside, tell them where. Otherwise, flower pots, window ledges and drinking glasses have a habit of becoming improvised ashtrays.
Pets: avoid the one-line policy
“Pets allowed” leaves a lot unanswered. Does that mean one dog or three? Are pets allowed on beds? Can they be left alone? Is the garden enclosed? Where should waste be placed?
A clearer example might be:
One dog is welcome with prior approval. Please keep pets off the beds and don’t leave them alone in the property. Pet waste should be bagged and placed in the outdoor general-waste bin.
Every property will need different wording. A rural cottage with a fenced garden needs a different pet note from a serviced apartment with a shared lift and no outdoor space. Keep useful pet instructions near the rule too. Guests may need to know where spare towels are kept after a muddy walk, or whether the cleaner needs advance notice.
Extra guests and visitors: remove the awkward guessing
Occupancy rules often sound suspicious before the guest has done anything wrong. You can still be firm without writing as though every visitor is planning a secret party.
Only the guests included in the booking may stay overnight. Please message us before inviting additional visitors, as the property has a maximum occupancy.
That gives the guest a clear boundary and a route to ask. Sometimes the first sign of an undeclared guest is a request for two more towels at 9:30pm. A clear rule saves your team from turning a simple linen request into detective work. It also helps with genuine situations. A relative may want to visit for an hour. A parent may need to add a child or request a cot. Those questions need a sensible answer, not an automatic accusation.
Parking: combine the rule with useful directions
A parking bay can be completely obvious to the owner and nearly invisible to everybody else.
The rule might be:
Please use bay 14 only. Other numbered bays belong to neighbouring residents.
The instructions should then explain how to find it:
Bay 14 is behind the blue gate, on the right-hand side beside the brick wall. A photo is included in the arrival guide.
Guests need both pieces. “Park only in the allocated space” won’t help when the numbers have faded, the building has two entrances and the guest has arrived in the rain. If there are height restrictions, permit requirements or vehicle limits, include the exact property-specific details. Don’t make the guest discover them after driving into the car park.
Bins and recycling: keep the guest’s job reasonable
Bin instructions often grow into a small council handbook. Most guests need to know:
- Where the bins are
- Which bin is used for general waste
- What can be recycled
- Whether rubbish must be removed at checkout
- Whether there is one unusual collection instruction
Use the labels and bin colours found at the property. These vary, so generic wording can create more confusion.
Please place bagged general waste in the black bin beside the rear gate. Clean glass, cans and cardboard go in the labelled recycling bins. Don’t leave rubbish in the shared hallway.
If guests need to move a bin on a particular evening, send that reminder near the collection day. Putting it in a guidebook they received two weeks earlier is unlikely to work. And think carefully about whether guests really need to manage the collection schedule. For many short stays, that is better handled by the cleaner or operations team. Bins going out on the wrong night can create just as much work as bins not going out at all.
Checkout: protect the turnover without assigning a shift
The cleaner arriving at 10:05am while the previous guest is still asking for a late checkout is an avoidable mess. State the checkout time clearly and explain how late-checkout requests are handled.
Checkout is by 10:00am. Please message us by 6:00pm the day before if you’d like to request a later departure. Late checkout depends on the next booking and cleaning schedule, so we can’t always offer it.
Then keep the task list short. A reasonable checkout message might ask guests to:
- Lock doors and close windows
- Put rubbish in the correct bins
- Leave keys in the agreed place
- Report any damage or missing items
- Check cupboards and chargers before leaving
Guests are checking out, not joining the turnover team. Long lists involving stripped beds, sorted laundry, wiped surfaces, emptied dishwashers and several trips to an outdoor bin store can create frustration, especially where a cleaning service is already part of the stay.
Make rules easy to find and maintain
Friendly wording shouldn’t make the rule weak
There’s a point where soft language becomes unclear. “Perhaps try to keep the noise down where possible” isn’t a useful rule. Neither is “We’d really appreciate it if you considered not smoking indoors.”
Be polite, but say what you mean:
Please keep noise low after 10:00pm.
Smoking isn’t permitted inside.
Parties and events aren’t allowed.
Checkout is by 10:00am.
“Please” doesn’t weaken a clear sentence. Three paragraphs of warnings, capital letters and exclamation marks rarely make it stronger.
Consequences should also be accurate. Only mention charges, cancellation steps or other outcomes that are genuinely part of your booking terms and operating process. Dramatic threats that your team won’t enforce teach guests that the rest of the rules may be optional too.
Put each rule where it can prevent the problem
Repeating the entire house-rule list in every message makes guests less likely to read any of it. Use the right moment instead.
Before booking
Show rules that could affect the decision to stay:
- Pet restrictions
- Maximum occupancy
- Smoking policy
- Party restrictions
- Parking limitations
- Any important visitor rules
Nobody should arrive with a dog and discover that the property doesn’t accept pets.
Before arrival
Remind guests about details linked to arrival:
- Where they may park
- How to enter shared areas quietly
- Whether additional guests must be registered
- Any access restrictions
Keep these reminders beside the actual check-in instructions, but don’t bury the door code under a full copy of every rule.
During the stay
Make everyday answers easy to find:
- Quiet hours
- Smoking areas
- Bin locations
- Pet instructions
- Visitor rules
This is where guidebook-powered guest support is useful. A guest asking on WhatsApp whether their sister can visit shouldn’t need to search a PDF or wait for somebody in the office to finish a turnover call.
For the broader guidebook problem behind this, see why guests do not read your short-let guidebook.
Before checkout
Send the departure time, key-return instructions and short task list at a useful hour on the day before departure. This is also the right time to explain how to request a late checkout. Waiting until the cleaner is outside is too late for everybody.
Clear rules make the stay easier for everyone
House rules don’t need to sound warm and fluffy. They need to be fair, specific and easy to act on. Tell guests what matters. Explain the reason where it helps. Put the information where they’ll see it at the right moment. That protects the property without making the welcome message feel like a warning letter.
If your team keeps answering the same questions about visitors, pets, parking, bins and checkout, letbloom can give guests answers from your property guidebook on WhatsApp, with complaints and urgent exceptions passed back to your team. See how letbloom works.
