Population 20,499 puts Cranbrook 24th of 24 in British Columbia and at 0.6% of the rostered provincial total. Every downstream assumption in Cranbrook — absorption pace, achievable rent, lender appetite — tracks that scale more closely than it tracks the zone code printed on the Cranbrook map.

Cranbrook ranks 124th nationally out of 134 rostered markets, in a tier-3 cohort of 79. It is 0.03× the size of Vancouver; ignore that gap and a Cranbrook pro forma inherits demand it does not have.

The nearest British Columbia neighbours by size are Courtenay above Cranbrook and no smaller provincial peer below it. When Cranbrook comparables run thin — and in a market of 20,499 they usually do — those are the files to pull first, since the governing statute is identical.

Outside British Columbia, the closest tier-3 analogues to Cranbrook are Yellowknife, NT, Owen Sound, ON, Corner Brook, NL. Comparing Cranbrook to those markets is usually more instructive than comparing it to the nearest city by driving distance, because bylaw generosity follows market size and provincial statute far more reliably than geography.

Cranbrook has zero promoted zone rows today. The page stays fully usable — calculator, printable summary and deal handoff all work — but Cranbrook is marked noindex and excluded from the sitemap, because a page with no verified local figure has no business competing in search.

The Cranbrook rule is identical in all 134 markets: a page is indexable only when the tier gate allows the pair and at least one promoted row backs it. Cranbrook is tier 3, which restricts Cranbrook to anchor products.

We would rather withdraw a Cranbrook row than defend it. Each Cranbrook figure shows its source and observation date so the work can be checked, and a correction arriving with a bylaw citation is actioned rather than argued.

Reviewing Cranbrook is sequenced, not exhaustive. The Cranbrook zones that see actual development activity get read first, and the long tail of specialised districts waits, because a shallow pass over every Cranbrook code would be worth less than a careful pass over the ones that matter.

Cranbrook — Planning and Development zones Cranbrook under authority granted by the Local Government Act (the Vancouver Charter in Vancouver). The Zoning Bylaw must sit inside the Official Community Plan, so a Cranbrook site's real ceiling is the more restrictive of the two — the distinction between an as-of-right build and a policy amendment with a multi-year tail.

Two mechanisms cover a Cranbrook shortfall — a development variance permit where the miss is marginal, a rezoning where it is structural — with council itself — British Columbia has no provincial zoning appeal tribunal as the forum for a contested outcome. Price the difference explicitly, because the same Cranbrook envelope achieved by variance and by rezoning are not the same asset.

None of this is uniform inside Cranbrook. Heritage designations, site-specific exceptions, holding provisions and area overlays sit on top of the base zone and routinely change the answer for one Cranbrook parcel while leaving its neighbours untouched. Every figure published here is a base-zone figure unless the Cranbrook source note says otherwise.

Above Cranbrook — Planning and Development sits British Columbia, and above the Cranbrook bylaw sits the Local Government Act (the Vancouver Charter in Vancouver). When the province moves, Cranbrook follows on its own schedule; assume the printed Cranbrook text is the current law only after checking the date on it.

Feasibility in Cranbrook reduces to arithmetic that is easy to state and easy to get wrong. FSR gives one ceiling on a Cranbrook lot; geometry gives another, from the setback-and-coverage footprint multiplied by the permitted storey count. Whichever is lower is the Cranbrook building, and knowing which one it is tells you what to negotiate with Cranbrook — Planning and Development.

Worked through on a reference 34,000 sf Cranbrook lot at 2 FSR — an illustration, not a Cranbrook figure — the density ceiling is 68,000 sf of gross floor area, roughly 72 units at an 85% efficiency and 800 sf average. Whether Cranbrook height and setbacks actually allow that plate is the second half of the question, and the answer is parcel-specific.

Knowing what binds tells a Cranbrook team what to ask for: storeys and floor-to-floor where height governs, density where FSR governs. In Cranbrook, where approvals run through Cranbrook — Planning and Development and contested outcomes reach council itself — British Columbia has no provincial zoning appeal tribunal, a misaimed request costs a cycle.

Parking quietly kills more Cranbrook projects than density does. From GFA and unit size the calculator derives Cranbrook units, applies your ratio and reports the stall count. Each Cranbrook stall implies excavation, structure and ventilation, and in a market of 20,499 the revenue available to absorb that is thinner than in Vancouver.

A note on vocabulary, because British Columbia does not use the same words as every province. Floor space ratio, floor area ratio and density index all describe the same Cranbrook relationship — permitted floor area divided by lot area — and Cranbrook — Planning and Development may use any of them in the Zoning Bylaw.

Whether Cranbrook — Planning and Development caps Cranbrook height by metres, storeys, or an angular envelope changes the achievable count. Enter the Cranbrook limit as the bylaw states it and set floor-to-floor to match the construction type you actually intend.

Setbacks and coverage interact in ways that surprise people new to Cranbrook. On a narrow Cranbrook lot, side yards can consume enough width that coverage never binds at all; on a deep one, coverage binds long before the setbacks do.

Unit size is the last input and the one most often left at a default. Average unit size drives the Cranbrook unit count, which drives the parking obligation, which drives excavation — so a 100 sf change in the Cranbrook assumption can move the whole feasibility.

Zoning sets the ceiling in Cranbrook; absorption decides whether reaching it is wise. A Cranbrook envelope that pencils at full permitted density still has to sell or lease into a market of 20,499, and that constraint is not written in any bylaw Cranbrook — Planning and Development publishes.

Because Cranbrook sits 24th of 24 in British Columbia, delivery risk deserves as much attention as entitlement risk. Phasing, pre-leasing and conservative unit mixes are the standard Cranbrook responses.

The comparison table gives Cranbrook a reference set that is not simply the nearest city. Similar-sized markets are the better analogue, because Cranbrook demand tracks scale more closely than geography.

Risk in Cranbrook concentrates at the edges of the data. A base-zone figure that is correct citywide can be wrong on the specific Cranbrook parcel, and the difference usually shows up as a schedule or an overlay rather than a change to the Cranbrook zone code itself.

A Cranbrook error is harder to unwind than a Vancouver error. At 20,499 people and 0.03× the provincial leader, the Cranbrook buyer pool for a compromised entitlement is small enough that pricing is set by whoever shows up.

Treat Cranbrook output here as a screening tool. Verification with Cranbrook — Planning and Development — and, where the file warrants it, a British Columbia planning professional — remains the step that carries legal weight.

Three kinds of information appear on the Cranbrook page and they are kept apart on purpose: roster facts common to all 134 markets, British Columbia statutory structure, and reviewed Cranbrook bylaw readings. Only the third is ever presented as a local regulatory figure.

That separation is what keeps Cranbrook honest under the publishability gate. A crawled candidate can sit in staging indefinitely without ever appearing on the Cranbrook page, and the page simply stays unindexed until a human vouches for a Cranbrook number.

Every Cranbrook figure is tagged observed or modelled. The distinction is not cosmetic: an observed Cranbrook value can be checked against Cranbrook — Planning and Development, while a modelled one is only as good as the inputs behind it.