How we check Nova Scotia short-term rental rules
Written by Casa Scotia, a Nova Scotia short-term rental manager. Not affiliated with any municipality or the Province. How we keep our interest out of it →
We research and write these guides ourselves. Because we manage short-term rentals, we have an interest in what the rules say: how we keep it out.
Where the rules come from. By-laws, plans, council decisions and municipal web pages; the Province's Act, Regulations, application form and guide; the Canada Revenue Agency; and each booking platform's Canada tax page. Each rule sits in one public dataset with its source and the date we read it.
Three reads. A first read records each rule's exact wording, source and date. A second, separate read reopens every source and tests each part alone; what it can't match to the text is graded down. If the reads disagree on a rate or status, a third review decides.
AI models do this reading under fixed written rules, and a separate check tests each guide against the data.
Check it yourself. Every rate, reading and verdict links to the source it comes from, with the date we read it. Read the source before you rely on a guide, and ask the municipal office when it matters: the office has the final word, not us.
When a municipality gets its own guide. Only once we've read its land-use rule in the by-law's own text. A web page, notice, search result or news report isn't enough; a by-law read in full that doesn't mention short-term rentals counts. Until then, it's a "Guide coming" row on the rules by municipality page.
Gaps. A scanned by-law or a page we can't load is a gap, never a guess: we read the page images, find another official copy, or ask the office. Where a guide can't yet answer something, such as which municipal document a registration needs, it tells you which office to ask, and what.
When a municipality's own documents disagree. If its by-law and web page differ, the guide shows neither: it tells you which office to ask, and what. We send the office the same question and publish its answer once it squares with the by-law. If it concerns its main land-use rule, it stays a "Guide coming" row.
Outside sources. News is never stated as fact; the guide names the publication. Where two outside sources differ, the guide names both and states neither. If a platform's tax page doesn't list a municipality, the guide says so, with the date, and who is then liable for the levy.
One reading everywhere. A by-law or levy program several municipalities share is read once, and every guide it covers shows that reading. HST on a municipal levy is answered once, from the federal tax rules; a municipality's own statement may sit beside it, never replace it.
None, none found, not named. "None": an official source says there isn't one. "None found": we read the published by-laws and found nothing, which isn't a guarantee. "Not named in the by-law": the land-use by-law doesn't mention short-term rentals, so the development officer decides how a rental is classified.
Dates and re-checks. "Checked" is when we last re-read a guide's sources: the oldest date, where its rules differ. "Changed" moves only when a rule or the wording changes in substance. Rules are re-read each quarter, oldest first; anything unsettled, and who collects each levy, about monthly; a new levy, before it starts. How often we re-check
What we never publish. Names of people: contacts are offices. Anything about the homes Casa Scotia manages. A verdict on a particular property, which only the municipality can give. Legal, tax or planning advice, or ways around a rule. To report a mistake, see Corrections.
How we keep our interest out of it
- Every guide says who wrote it, under its heading: Casa Scotia, a Nova Scotia short-term rental manager, not affiliated with any municipality or the Province.
- The verdict, the chips, the costs and the levy lines come from the data, never from a writer’s choice; a person signs off every levy rate and every “allowed” before a guide publishes.
- No guide says whether a particular property may be used as a short-term rental, and none suggests a way around a rule.
- Where the rules don’t show a rental is permitted, the guide offers no earnings estimate.
- Nothing about the homes Casa Scotia manages appears in any guide or in the data.
What the labels mean
| Label | Grade in the data | What it means |
|---|---|---|
| Confirmed in source | VERIFIED, VERIFIED-CANONICAL, VERIFIED-DATA | Read in the official document on the date shown. Not a legal opinion. |
| Reported by <publication> | REPORTED, INFERENCE | Rests on a secondary source, which the guide names. Never stated as fact. |
| Under review | UNVERIFIED, SPECULATIVE, UNRESOLVED | Not confirmed; the value is withheld. |
| being re-checked | Last read more than 120 days ago; still shown, and due a re-read. | |
| Not current | Last read more than 365 days ago; withheld until re-read. | |
| Ask <office> … | The office hasn’t answered a question we sent it; the guide says whom to ask, and what, until it does. | |
| None | An official source says there isn’t one. | |
| None found | A full read of the published by-laws found none. Not a guarantee. | |
| Not named in the by-law | The land-use by-law doesn’t mention short-term rentals; the development officer decides how a rental is classified. |
On a phone, swipe the table sideways to see every column.
How often we re-check
| What | When |
|---|---|
| Every rule | Each quarter, oldest first, in the first week of January, April, July and October |
| The provincial rules | Also each March, before the renewal deadline (April 1 each year) |
| Anything unsettled, and who collects each levy | About monthly |
| A levy adopted to start later | Before it starts |
| A reported change | Within five business days of the report |
On a phone, swipe the table sideways to see both columns.
Corrections
If something in a guide looks wrong or out of date, tell us which municipality and which line, with a source if you have one. We re-check it within five business days. A confirmed error is corrected in the guide and the data, and logged with its date on the change log.