Richmond carries a census population of 209,937, the 5th largest of the 24 British Columbia markets on this site and roughly 5.8% of the rostered provincial population. That single figure shapes almost everything a Richmond pro forma depends on: the storey count a council will entertain, how far the parking standard has drifted from real car ownership in Richmond, and whether a site assembly has any local comparables at all.

Nationally Richmond sits 27th of the 134 Canadian markets in this roster and is one of 40 tier-2 markets. Against Vancouver, Richmond runs at 0.32× the population, which is the honest discount to apply when someone hands a Richmond file an absorption assumption borrowed from the provincial leader.

Richmond sits between Burnaby at 249,125 and Abbotsford at 153,524. Same province, same rules, different scale: the cleanest way to test whether a Richmond density assumption is ambitious or ordinary.

The nearest national peers to Richmond by size and tier are Oakville, ON, Richmond Hill, ON, Windsor, ON. Oakville in particular, at 213,759, is close enough in scale that its approval timelines are a reasonable prior for Richmond — a prior, not evidence.

Nothing in Richmond has been promoted yet. Candidate extractions may sit in the staging table, but they never render on a Richmond page, and this URL stays unindexed until a reviewer confirms a figure against an Richmond — Planning and Development source and dates it.

The Richmond 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. Richmond is tier 2, which admits tier-1 and tier-2 products only.

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

We do not claim complete Richmond coverage and will not fake it. Reviewed Richmond rows accumulate in order of practical relevance, and the absence of a Richmond code here means it has not been read yet — not that it does not exist.

The legal chain in British Columbia runs the Local Government Act (the Vancouver Charter in Vancouver) → the Official Community Plan → the Zoning Bylaw, administered in Richmond by Richmond — Planning and Development. Nothing can be permitted as of right in Richmond that the plan does not already contemplate, which is why the fastest feasibility read is the Richmond plan designation, not the zone code.

Two mechanisms cover a Richmond 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 Richmond envelope achieved by variance and by rezoning are not the same asset.

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

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

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

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

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

Parking is the third constraint and the most often mispriced in Richmond. The tool converts a Richmond parking ratio into stalls from the unit count implied by your GFA and unit size, then shows what those stalls displace. Excavation and below-grade structure are volatile line items in British Columbia, so a ratio that looks trivial can decide a Richmond site.

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

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

Setbacks and coverage interact in ways that surprise people new to Richmond. On a narrow Richmond 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 Richmond unit count, which drives the parking obligation, which drives excavation — so a 100 sf change in the Richmond assumption can move the whole feasibility.

Maximum density is not the Richmond objective. Richmond — Planning and Development may permit a plate the Richmond market cannot absorb, and building to the ceiling in a 209,937-person market is how a compliant project becomes an unsellable one.

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

Use the peer table below to test a Richmond assumption before committing to it. Markets of similar tier and population face similar absorption physics, even where their statutes differ from the Local Government Act (the Vancouver Charter in Vancouver).

The most common way a Richmond feasibility goes wrong is not arithmetic, it is staleness. the Zoning Bylaw is amended on Richmond — Planning and Development's schedule, not yours, so a Richmond 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.

Scale changes the risk profile too. In a market of 209,937, a single mispriced Richmond site is a larger share of the year than the same error would be in Vancouver, and the pool of buyers willing to absorb an entitlement mistake in Richmond is correspondingly smaller.

Treat Richmond output here as a screening tool. Verification with Richmond — 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 Richmond page and they are kept apart on purpose: roster facts common to all 134 markets, British Columbia statutory structure, and reviewed Richmond bylaw readings. Only the third is ever presented as a local regulatory figure.

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

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