5 rules every STR house rules packet is missing

I've read a lot of short-term rental house rules packets. Most of them have the same problem, and it isn't that they're missing rules — it's that the rules they have are written to sound reasonable, not to be enforced.

There's a difference. A rule written to sound reasonable reads well and makes the host feel like a decent person. A rule written to be enforced can survive being pointed at later — by a guest, by an Airbnb Resolution Center agent, by a small-claims clerk — and have everyone agree on what it meant. Most packets are full of the first kind.

The fix is usually not adding rules. It's rewriting five specific ones so they're concrete enough that a guest can read each line and genuinely acknowledge it — and so that "I agreed to that" means something specific later. Here are the five, with wording you can use.

1. Occupancy — state a number

The weak version: "Please do not exceed the property's occupancy limit." Or worse, nothing at all, because the host assumes the Airbnb listing's guest count covers it.

The problem with "the occupancy limit" is that it's a pointer to a number that lives somewhere else. The guest has to go find it, and when six people show up and you raise it, there's room to argue about what the limit was, whether children count, whether the air mattress in the living room is fine.

Write the number into the rule itself:

Maximum occupancy is 4 guests, including children and infants. This is the total number of people permitted to stay overnight or be on the property at any time. Bookings made for fewer guests than will actually stay are a violation of this rule.

Now there's nothing to interpret. A guest acknowledging that line is acknowledging the number 4, not a concept. And if you charge an extra-guest fee, this is the rule the fee attaches to — which is why it has to be a number.

2. Quiet hours — put a clock time on it

The weak version: "Please be respectful of neighbors and keep noise down, especially at night."

"At night" is not a time. "Respectful" is not a standard. If a neighbor complains at 11:40 PM, you and the guest can each believe you were right, because the rule never said when night started.

Give it a clock:

Quiet hours are 10:00 PM to 8:00 AM, local time. During quiet hours, keep noise — voices, music, TV — at a level that cannot be heard outside the unit or from a neighboring property. Outdoor spaces (patio, pool, balcony) are closed to use during quiet hours.

Two specifics doing the work: a start and end time, and a definition of "quiet" tied to whether the sound crosses a boundary. A guest can acknowledge that and know exactly what they agreed to. So can anyone reviewing it later.

3. Unregistered guests — name the fee

The weak version: "No parties or events. Only registered guests are allowed."

This one usually exists, but it stops short of the part that matters: the consequence. "Only registered guests are allowed" tells the guest what the rule is. It doesn't tell them what happens if they break it — and a rule with no stated consequence is, in practice, a request.

State the fee, as a number, in the rule:

Only the guests named on this reservation may stay overnight or visit the property. Visitors who are not on the reservation are not permitted without prior written approval. An unregistered-guest fee of $100 per person per night applies to anyone staying or present at the property who was not named on the booking. Repeat or large-scale violations may result in the reservation being ended.

This is the rule that, when a guest acknowledges it individually, becomes a fee you can actually disclose and bill. A consequence the guest signed off on in advance is enforceable. A consequence they're hearing about for the first time during a dispute is not. The fee belongs in the rule and in your itemized fee schedule — same number in both places.

4. Pets — decide, and say it plainly

The weak version: "Please ask before bringing a pet." Or a packet that simply doesn't mention pets at all, which a guest will read as permission.

"Please ask" is a rule that depends on the guest choosing to ask. Many won't. And if a dog shows up unannounced and you never wrote anything down, you've got nothing — not a fee, not a cleaning charge, not a record that the guest knew better.

Pick a position and state it without hedging. If pets are not allowed:

Pets are not permitted at this property, with the exception of service animals as defined under the ADA. Bringing a non-service animal without written approval is a rule violation; an additional cleaning and remediation fee of $150 applies, and you may be charged for any pet-related damage.

If pets are allowed with conditions:

Up to one dog under 40 lbs is permitted with prior written approval and a non-refundable pet fee of $75. Pets must not be left unattended in the unit. Cats and other animals are not permitted.

Either way, the guest knows the answer before they pack the car, and the service-animal carve-out keeps you on the right side of the law. A clear pet clause also gives you a clean place to attach a fee — the same logic as the unregistered-guest rule.

5. Checkout time — make it a time, and a short list

The weak version: "Checkout is in the morning. Please leave the place tidy."

"In the morning" is not enforceable on a same-day turnover, and "tidy" means something different to every guest. If your cleaner can't get in until the guest leaves, a vague checkout time is a direct cost.

Give the time and a short, finite list of what checkout means:

Checkout is no later than 11:00 AM. Late checkout is not available on this reservation unless approved in writing in advance; a late-checkout fee of $50 per hour applies otherwise. Before you leave, please: start the dishwasher if used, place used towels in the tub, take trash to the outdoor bin, and lock all doors. You do not need to strip beds or clean — that's on us.

The time is a number a guest can acknowledge. The list is short enough to actually be read and done. And telling them what they don't have to do makes the list they do have to do feel reasonable — which means it's more likely to happen.

Why per-line wording is the point

Notice what all five rewrites have in common. Each one resolves to something concrete — a number, a clock time, a named fee, a yes-or-no — that a guest can read on its own and genuinely agree to. That's not a style choice. It's what makes a packet do its job after something goes wrong.

A packet acknowledged as one bulk "I agree to the house rules" is a single blurry click over everything at once. Nobody can later say which rule the guest actually saw. A packet where the guest acknowledges each rule individually produces a record where you can point at one line — the 11:00 AM checkout, the $100 unregistered-guest fee — and say: the guest confirmed this specific term, on this date, before they arrived. That's the difference between a rule and an enforceable rule.

If you'd rather not rewrite all five from scratch, our Airbnb house rules template is built from this exact standard — concrete numbers, named fees, acknowledgeable line by line — and you can edit every line to fit your property.

And when you're ready to actually send a packet to a guest and get each rule signed and timestamped before check-in, you can set yours up here.