Sarnia is a thin market of 72,047 people, 34th of 46 in Ontario and about 0.7% of the provincial roster. Feasibility work in Sarnia behaves differently from work in Toronto: fewer precedents, slower comparables, and a Sarnia bylaw often written for a smaller city than the one standing today.

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

The nearest Ontario neighbours by size are Sault Ste. Marie above Sarnia and Norfolk County below it. When Sarnia comparables run thin — and in a market of 72,047 they usually do — those are the files to pull first, since the governing statute is identical.

Outside Ontario, the closest tier-3 analogues to Sarnia are Airdrie, AB, Saint John, NB, Granby, QC. Comparing Sarnia 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.

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

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

We would rather withdraw a Sarnia row than defend it. Each Sarnia 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.

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

Sarnia — Planning and Development zones Sarnia under authority granted by the Planning Act. The Zoning By-law must sit inside the Official Plan, so a Sarnia 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 Sarnia shortfall — a minor variance to the Committee of Adjustment where the miss is marginal, a rezoning where it is structural — with the Ontario Land Tribunal as the forum for a contested outcome. Price the difference explicitly, because the same Sarnia envelope achieved by variance and by rezoning are not the same asset.

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

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

Two ceilings compete on every Sarnia parcel: lot area × FSR, and footprint × storeys after setbacks and coverage. The calculator resolves both from your inputs and reports the binding one, because relief only helps a Sarnia applicant if it lifts the constraint that is actually binding.

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

Get the bind backwards and a Sarnia applicant negotiates for a concession that changes nothing. A height-bound Sarnia site gains nothing from density bonusing; an FSR-bound one gains nothing from two more metres. Aiming the Sarnia ask correctly is worth more than optimising the plate.

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

Terminology trips up out-of-province teams working in Sarnia. FSR, FAR and density index are interchangeable descriptions of the same Sarnia ratio, and what Sarnia — Planning and Development calls it matters less than how it measures the floor area it applies to.

Height is equally slippery in Sarnia. A limit expressed in metres, in storeys, or as a geometric envelope produces different buildings on the same Sarnia lot, and the calculator here converts between them using the floor-to-floor figure you supply rather than assuming one.

On small Sarnia parcels the setback set usually governs the footprint outright, and the coverage percentage in the Zoning By-law becomes decorative. The calculator shows both so a Sarnia user can see which is doing the work.

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

The permitted Sarnia envelope and the sellable Sarnia envelope are different objects. With 72,047 residents and a 0.03× ratio to Toronto, the Sarnia question is rarely how much the bylaw allows — it is how much the market clears in a reasonable delivery window.

Phasing is the usual answer in a market the size of Sarnia. Splitting an envelope across stages keeps Sarnia exposure proportional to demonstrated absorption, at the cost of losing some efficiency Toronto projects can rely on.

Peers listed for Sarnia are chosen by tier and population, not proximity. They are the fastest available check on whether a Sarnia density assumption is ordinary or ambitious.

The most common way a Sarnia feasibility goes wrong is not arithmetic, it is staleness. the Zoning By-law is amended on Sarnia — Planning and Development's schedule, not yours, so a Sarnia figure carried from a file six months old may already be void. The printed summary from this page carries its own date for exactly that reason.

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

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

The method behind the Sarnia page is deliberately boring. Population and rank come from the census roster shared by all 134 markets; the statutory chain comes from the Planning Act; and the Sarnia regulatory figures, when any exist, come from a reviewer reading an Sarnia — Planning and Development page and stamping the date.

Under the gate, Sarnia either has a cited figure or it has none. Half-verified Sarnia data is treated as no data, and the page carries a noindex directive rather than a hedge.

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