With 20,340 residents, Yellowknife ranks 1st among the 1 Northwest Territories markets tracked here and holds about 100% of the province's rostered population. Density policy in Yellowknife scales with that number — the language of the Zoning By-law, the committees that review it, and the depth of the comparable set all shift as a market moves up or down the Northwest Territories order.

Across the 134-market Canadian roster, Yellowknife is 125th by population and shares tier 3 with 78 other markets. Its 1.00× ratio to Yellowknife is the number to apply before importing any Yellowknife rent or velocity assumption into a Yellowknife model.

Nationally, Yellowknife reads most like Cranbrook, BC, Corner Brook, NL, Owen Sound, ON — same tier, similar population, different statutes. Use them to sanity-check what density Yellowknife can absorb, never to cite a figure: every number in the Zoning By-law is jurisdiction-specific and none of it survives a provincial border.

No Yellowknife zone has cleared review yet, so this page publishes no Yellowknife regulatory figure at all. That is the publishability gate working rather than an oversight: with no reviewed row, the Yellowknife page stays out of the sitemap and carries a noindex directive.

Being in the roster does not publish Yellowknife. All 134 Canadian markets get a working page; only those clearing the tier gate with a cited, dated figure get indexed, and Yellowknife sits in tier 3 of that gate alongside 78 other markets.

Every published Yellowknife row is dated deliberately: bylaws change, and an undated figure is a rumour. Find a discrepancy against the current City of Yellowknife — Planning and Development text and the Yellowknife row gets re-read or pulled.

Coverage also has a ceiling in ambition, not just in law. There are more zone codes in Yellowknife than any small team can verify at once, so review is prioritised by the codes most likely to carry a real Yellowknife project — the mixed-use and multi-unit districts rather than the exhaustive tail.

City of Yellowknife — Planning and Development zones Yellowknife under authority granted by the Community Planning and Development Act. The Zoning By-law must sit inside the Community Plan, so a Yellowknife 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.

When the Yellowknife bylaw falls short of what a site needs, the ordinary routes are a variance from the development officer for marginal gaps and a rezoning for structural ones. A refusal or an unacceptable condition on a Yellowknife application is contested at the Development Appeal Board. In Yellowknife that choice is a scheduling question first: relief is measured in months, a rezoning in years, and carry does not pause for either.

Within Yellowknife, base zoning is only the first layer. Site-specific amendments, heritage controls, holding symbols and overlay districts attach to individual parcels, which is why two adjacent Yellowknife lots under the same code can support materially different buildings. Confirm the parcel with City of Yellowknife — Planning and Development, not the colour on the map.

Provincial policy also moves under Yellowknife's feet. Northwest Territories has been an active legislator on housing supply, and amendments to the Community Planning and Development Act reach Yellowknife whether or not City of Yellowknife — Planning and Development has updated its own text yet — so a bylaw figure and the current law can diverge for months at a time.

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

Take a 29,000 sf Yellowknife lot and apply 3 FSR purely as an illustration: 87,000 sf of GFA, about 92 units once 15% goes to circulation and services. That number is arithmetic, not entitlement — the Yellowknife height limit and setback set decide whether the plate exists to hold it.

The bind flag is the whole point of a Yellowknife run. If height binds a Yellowknife site, an FSR bonus buys nothing and the conversation with City of Yellowknife — Planning and Development is about storeys or floor-to-floor efficiency. If FSR binds, extra Yellowknife height buys nothing either — the same area lands on a smaller plate, usually at a higher cost per square foot.

The ratio is the third lever on a Yellowknife site. Entered here it becomes a visible Yellowknife stall count rather than a buried cost line. Many Northwest Territories bylaws still carry ratios written for a different era of car ownership, which makes the reduction request one of the highest-return conversations a Yellowknife applicant can have.

A note on vocabulary, because Northwest Territories does not use the same words as every province. Floor space ratio, floor area ratio and density index all describe the same Yellowknife relationship — permitted floor area divided by lot area — and City of Yellowknife — Planning and Development may use any of them in the Zoning By-law.

A Yellowknife height limit in metres and one in storeys are not equivalent. Floor-to-floor assumptions decide how many Yellowknife levels fit under the same cap, which is why the tool asks for that number instead of guessing it.

Yellowknife footprint is the smaller of the setback-derived area and the coverage cap. Which one governs depends on parcel geometry, not on policy, and it flips between neighbouring Yellowknife lots more often than most owners expect.

Set the Yellowknife average unit size to the product you actually intend to build. Everything downstream — Yellowknife unit count, stalls, excavation volume — is derived from it, and the default is a placeholder rather than a market figure.

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

Because Yellowknife sits 1st of 1 in Northwest Territories, delivery risk deserves as much attention as entitlement risk. Phasing, pre-leasing and conservative unit mixes are the standard Yellowknife responses.

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

Three failure modes recur in Yellowknife work: a superseded bylaw figure, a parcel-level exception nobody pulled, and a parking ratio priced as a footnote. All three are cheap to avoid in Yellowknife and expensive to discover after closing.

Because Yellowknife runs at 1.00× Yellowknife, its liquidity is thinner: an entitlement error in Yellowknife takes longer to trade out of, and the discount demanded is steeper than the Northwest Territories leader would face on the same file.

Nothing on this page is legal or planning advice for Yellowknife. It is a feasibility estimate built from figures you supply or from reviewed rows that cite their City of Yellowknife — Planning and Development source and date. Confirm anything material with City of Yellowknife — Planning and Development before it reaches a purchase agreement.

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

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

Yellowknife outputs carry a provenance label so a reader never has to guess. Observed Yellowknife values cite a document and a date; modelled values are arithmetic on the numbers you entered, and are presented as such.