A Quiet-Hours Policy Guests Actually Follow

A quiet-hours rule that lives only in the house rules is a rule nobody reads. What guests follow is what they were told at the right moment, in the right place.

Last updated: September 27, 2026

Everybody has quiet hours in the house rules, and almost nobody has a quiet evening. That gap isn't a discipline problem. The rule is in a document a guest reads once, usually before they've arrived and long before the moment it applies. By the time the music goes on, the rule is a memory from a scroll, and memory is a weak enforcement mechanism.

Key Takeaways

• The house rules page is read once, at the wrong time. Nobody re-opens it at midnight, so it can't be where the rule lives.
• Timing beats wording. The same sentence lands at booking and vanishes at check-in, because context changes what a guest absorbs.
• Two rulebooks apply, and you enforce the tighter one. Building rules and local rules set the actual hours, not a template you copied.
• A short reminder beats a long policy. One line at the right moment does more than a paragraph nobody reaches.
• Resolve the complaint at the door. A noise complaint handled in the moment doesn't become the one you read about later.

Why the house rules page is read too late to matter

House rules get read in two states, and neither helps you. The first is before booking, when a guest skims a wall of text looking for the things that would make them choose another place — parking, pets, cleaning fee. The second is at check-in, after a flight, when they're scrolling for the door code and nothing else. In both cases the quiet-hours line is background noise.

Neither reading happens anywhere near the behaviour the rule is about. A guest isn't deciding whether to turn the music down while they read your house rules; they're deciding it at midnight with friends over, at which point the rule is competing with a mood. Rules that only exist in a document lose that contest every time.

So the honest diagnosis isn't that the rule is wrong. It's that the rule is stored in a place designed for reference, and it needs to be delivered in a place designed for the moment. Those are two different jobs, and the house rules page only does the first.

The moments where a quiet-hours reminder actually lands

A reminder doesn't need to be repeated constantly to work. It needs to arrive at a small number of moments where the guest is already thinking about the stay and can act on what you say. Miss those and no amount of repetition recovers it.

At booking. When a guest confirms, they're reading. A single line — that this is a residential building, that noise carries, that quiet hours apply and where they're set — sets the frame before they've packed. This is the moment the expectation is created, and it's the cheapest one to use.

The day before arrival. A short pre-arrival message that covers the practical things is the natural home for the reminder, because the guest is now thinking about the building they're about to walk into. One line, in the same message as the arrival details, is enough.

At check-in. This is where the reminder has the most chance of sticking, but only if it's specific to the building rather than a repeat of the policy. If the neighbour's bedroom shares a wall, say so. Concrete beats general, every time.

When the group is larger than usual. A booking for two and a booking for eight need different reminders. The moment a group confirms is the moment to name what the building expects, because a group is the situation quiet hours exist for.

The moment something starts to slip. If a guest messages about inviting people over, that's your cue to restate the expectation in one friendly line — not as a warning, but as a reminder that the neighbours are real. This one is optional, and it works when it's light.

Building rules, local rules and which one you enforce

By the time you're setting quiet hours, you're usually not the one who decides them. There are two rulebooks above yours, and both can bind you harder than the terms you wrote yourself.

The first is the building. If the unit sits in a block with a management agreement, a strata scheme or a residents' committee, that document governs noise inside the building, and it applies to your guests whether or not they've read it. It can set hours, restrict gatherings and impose penalties on the owner rather than the guest. When the building's rule is tighter than yours, the building's rule is the one that binds.

The second is the local authority. Councils and municipalities set noise limits that apply to a dwelling regardless of what the building or the host says, and they're the ones a neighbour will call first. The specific hours that apply — when quiet time starts, when it ends, and whether weekends differ — are set by that authority and by the building's management agreement, not by any number you can lift from a guide. Those are the sources to check, and they're the ones that settle the question.

So your job isn't to invent the hours. It's to find out which rule is tightest where the unit sits, write that into the listing, and deliver it at the moments above. If the building bans something the local rules allow, follow the building. If the local rules are tighter, follow those. Your own house rules should never be the most permissive of the three.

The delivery is easier when the guest, the stay and the messages sit together. A reminder that arrives in the same thread as the booking is read; a reminder sent from somewhere else competes with everything else on a guest's phone. With the inbox connected to Airbnb, the conversation stays with the booking it belongs to. The order detail at localsbnb.com keeps the guest, the dates and the building notes on one screen as you draft what to send.

Handling the complaint without turning it into a review

A noise complaint is a timing problem before it's anything else. Handled in the moment, it's a quiet word to a guest who turns the music down and never thinks about it again. Handled a day later, it's a confrontation about something that already ended, which is where the bad outcomes start.

When a neighbour tells you there's noise, act now. Message or knock, once, and make a specific request rather than a general complaint — asking a guest to move the speakers off the shared wall is something they can do; telling them they're being inconsiderate is something they'll argue with. Give them the reason, briefly, because "the neighbour's bedroom is on the other side of that wall" is far more persuasive than "please respect the rules".

If the guest doesn't respond or doesn't comply, your next step is the building's process and the platform's terms rather than an escalating argument in a message thread. Those processes exist for exactly this, and they'll want a record: the time, what the neighbour reported, when you raised it with the guest and what was said. Keep that, and keep it factual, because the version that matters later is the written one.

What you're trying to avoid is the complaint that arrives late in another form — as a poor rating, or as a message from the neighbour that goes straight past you to the building. Resolving it at the door is cheaper than resolving it later, and every part of it is easier when the guest can be reached quickly in a thread they're already reading.

FAQ

What hours should I set for quiet time?

The honest answer is that you don't set them. The permitted hours come from the local authority and from the building's management agreement, so check both and use whichever is tighter where the unit sits. Adopting a number from another host or another city is how a rule ends up unenforceable.

Should quiet hours go in the house rules anyway?

Yes, but don't rely on them there. The house rules page is a reference document, and a reference document doesn't change behaviour at midnight. Put the rule in the house rules for completeness, then deliver it at booking, before arrival and at check-in, where a guest is actually reading.

A neighbour complains about my guest. Who do I tell first?

Tell the guest, right away, with a specific request. Then follow the building's process if it doesn't resolve, and keep a factual note of the time, the report and what you said. Telling the neighbour you'll handle it and then not handling it is what turns a small noise complaint into a standing problem.

Quiet hours mostly fail as a delivery problem, not a policy one. Find out which rule binds at the unit, write it plainly, and say it at the handful of moments a guest will actually hear it — booking, the day before, check-in, and the moment a group books. Then handle the first complaint in the moment it happens. Keeping the guest, the stay and the messages in one thread at localsbnb.com is what makes that quick enough to work.

---

This article is general guidance for hosts and is not legal or platform policy advice; the permitted quiet hours and any noise limits are set by the local authority and the building's management agreement, and current platform terms prevail.