When the Building Says No Before the City Does

A private building rule can end a short-let plan long before a city does. It's the approval layer most hosts never check first.

Last updated: October 5, 2026

A city licence isn't the whole picture. Before a city gets involved, a private building can already decide whether your short-let plan is allowed. A deed, a set of house rules or a tenancy can restrict how a unit is used, and a management board can act on them. This is the approval layer most hosts check last, when they should check it first. Here's how the layers stack, and what to keep on file.

Key Takeaways

• A building can say no before a city does. A deed or a set of house rules can restrict short stays without any city action.
• The layers stack, and each one can bind. Title, building rules and a tenancy each carry their own limits, and any one can stop you.
• A board can enforce what a city doesn't. A management body acts on its own rules, often long before a regulator gets involved.
• Written permission is the thing that counts. What you need on file is the written word, not a neighbour's memory of a conversation.
• Keep the personal data tight too. Guest names, phone numbers and ID numbers need protecting as much as the paperwork.

The approval layers above a city licence

Think of the approvals as a stack. At the top sits the city licence, the one hosts check first. Below it sit the layers that decide a case long before a regulator gets involved: the property's title, the building's own rules, and any tenancy that covers the unit.

The title comes first. A deed can carry a covenant that limits how a unit is used, and that limit travels with the property, not with the owner. A restriction written into the title binds whoever holds it next, which is why it belongs at the start of any check.

Then come the building rules. A managed building often has house rules that speak to short stays directly. Those rules sit between you and the city, and a board can enforce them on its own schedule, without waiting for a licence decision.

Finally, there's the tenancy. If you rent the unit, your own lease can ban subletting in its own words. That ban binds whoever signed it, and it can end a short-let plan faster than any municipal process. Read the document you signed.

So the order to check is title first, building rules second, tenancy third. Most hosts run that order backwards, starting with the city because it feels like the official answer. The official answer is often the last one to matter.

Skipping that order is how a host finds out about a restriction after the first guest has already arrived. The cost isn't just the booking. It's the awkward conversation with a board that was never asked.

What a building rule can and cannot do

A building rule can restrict what happens inside the building. It can limit short stays, require registration with the board, set quiet hours or cap how often a unit turns over. Within its scope, it carries real weight, because the board can act on it without a city's help.

A building rule can't override a law, and it can't invent a power the board doesn't have. It also can't rewrite your title. So the layers don't cancel each other, they add up, and the strictest one in the stack is the one that governs your plan.

That's why "the city allows it" isn't an answer on its own. A city permission doesn't dissolve a private restriction. A host who lists on city approval alone can still be stopped by a rule they never read.

The honest position is that the interaction between these layers is a matter for your own documents and, if needed, your adviser. What this guide can do is tell you where to look and what to keep. The reading itself belongs to your title, your building rules and your local authority's current position.

One useful habit is to note which layer each limit comes from. When someone quotes a rule at you, you want to know instantly whether they mean the deed, the house rules or the lease. The source decides who can enforce it.

When two layers disagree, the stricter one usually wins in practice. A title restriction that bans nightly use doesn't get softer because the house rules stay silent. Read for the tightest limit, not the friendliest one.

Diagnosing a complaint before it escalates

A complaint usually arrives in one of two forms: a message from a neighbour, or a notice from the board. Both feel personal. Neither has to become a dispute if you diagnose it early and answer it in writing.

Start by naming the rule that's cited. Is it a house rule, a title restriction or a tenancy clause? The answer tells you who can enforce it and what they can ask for. A vague complaint that names no rule is often a conversation, not a case.

Then check your own permission. If you have written approval, read what it actually covers. An approval for a long stay doesn't automatically cover a short one, and a nod from one board member isn't a board decision.

Write down the facts while they're fresh: dates, notices, what you were allowed to do and when. A timeline you build in the first week is worth more than a statement you try to reconstruct months later.

A first reply sets the tone. If you answer with the facts and the documents, the exchange tends to stay procedural. If you answer with an argument, it tends to become one. Keep the first reply short, specific and written.

Building the file that answers a board

The file that answers a board is short and specific. It holds your written permission, the rule being cited, your timeline of facts, and any correspondence. A board that receives a tidy file tends to resolve a question faster than one that has to chase you for basics.

Keep it next to the operating records, not in a drawer of its own. When a question arrives, the host who can answer it the same day is the host who keeps the listing live. A file that takes three days to assemble reads like a problem, even when there isn't one.

Protect the personal data in that file as carefully as the permission. LOCALSBNB keeps credentials stored only on your device, masks guest names, phone numbers and ID numbers automatically, and grants access by area, so a shared document doesn't become a shared risk. localsbnb.com keeps that protection alongside the records, so the file you hand over is the file you can defend.

A board file also protects you later. If the building changes hands or the board changes its mind, the written record shows what was agreed and when. Paper beats memory, especially in a building where memories differ.

Finally, revisit the file when anything changes. A new tenancy, a board election or a title transfer can all move your position. A file that's a year out of date can mislead you as easily as no file at all.

FAQ

Can a building stop me if the city allows short lets?

Yes, in many cases. A city permission doesn't dissolve a private restriction. A deed, a house rule or a tenancy can each limit short stays, and the strictest layer in the stack is the one that governs your plan.

What should I read first?

Start with your title, then the building's rules, then your tenancy if you rent the unit. Those three documents decide more cases than any general guide. If they conflict, take advice on your own situation.

What if a neighbour complains?

Answer in writing, and name the rule being cited. Check whether your written permission covers the claim, and keep a timeline of the facts. A calm, documented reply resolves more complaints than a debate does.

The layers above a city licence are easy to skip and costly to miss. Read your documents, keep your written permission close, and protect the data inside your records. When you want the file and its safeguards in one place, start from localsbnb.com and keep it current.

---

This is general guidance for hosts, not legal, tax or insurance advice. Local rules, thresholds and platform terms differ by place and change over time; check the current position with your local authority and the current terms of each platform you use.