Kamloops is a thin market of 97,902 people, 12th of 24 in British Columbia and about 2.7% of the provincial roster. Feasibility work in Kamloops behaves differently from work in Vancouver: fewer precedents, slower comparables, and a Kamloops bylaw often written for a smaller city than the one standing today.

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

Bracketing Kamloops by population: Nanaimo (99,863) sits directly above and Chilliwack (93,203) directly below. Those two markets are the most defensible sanity check available for a Kamloops assumption, because they share British Columbia's statutes and its approval culture.

The nearest national peers to Kamloops by size and tier are Saint-Jean-sur-Richelieu, QC, Lethbridge, AB, Pickering, ON. Saint-Jean-sur-Richelieu in particular, at 98,036, is close enough in scale that its approval timelines are a reasonable prior for Kamloops — a prior, not evidence.

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

The Kamloops 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. Kamloops is tier 3, which restricts Kamloops to anchor products.

Corrections on Kamloops are welcome and fast. If a figure here is stale, send the City of Kamloops — Development and Engineering Services page and it gets re-read; the observation date on each Kamloops row states exactly how old the reading is, which is more than most zoning summaries will admit.

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

Zoning exists in Kamloops because the Local Government Act (the Vancouver Charter in Vancouver) delegates the power to City of Kamloops — Development and Engineering Services. That delegation is conditional: the Kamloops instrument, the Zoning Bylaw, must conform to the Official Community Plan, and where the two conflict the policy document wins. It is why an FSR read off a Kamloops zoning map can sit below what the plan contemplates — the plan is the ceiling of ambition, the bylaw the ceiling of right.

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

A caution specific to older Kamloops parcels: exceptions accumulate. Decades of site-specific amendments mean the code shown on the Kamloops zoning map is frequently modified by a schedule elsewhere in the same document. Anything here describes the Kamloops base zone; the parcel governs.

Kamloops does not control the whole stack. Changes at the British Columbia level flow through the Local Government Act (the Vancouver Charter in Vancouver) into what City of Kamloops — Development and Engineering Services may or must permit, and the Kamloops bylaw text often lags the statute. That lag is exactly where a stale Kamloops feasibility gets expensive.

Two ceilings compete on every Kamloops 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 Kamloops applicant if it lifts the constraint that is actually binding.

Worked through on a reference 26,000 sf Kamloops lot at 2.5 FSR — an illustration, not a Kamloops figure — the density ceiling is 65,000 sf of gross floor area, roughly 69 units at an 85% efficiency and 800 sf average. Whether Kamloops 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 Kamloops applicant negotiates for a concession that changes nothing. A height-bound Kamloops site gains nothing from density bonusing; an FSR-bound one gains nothing from two more metres. Aiming the Kamloops ask correctly is worth more than optimising the plate.

Parking quietly kills more Kamloops projects than density does. From GFA and unit size the calculator derives Kamloops units, applies your ratio and reports the stall count. Each Kamloops stall implies excavation, structure and ventilation, and in a market of 97,902 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 Kamloops relationship — permitted floor area divided by lot area — and City of Kamloops — Development and Engineering Services may use any of them in the Zoning Bylaw.

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

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

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

Maximum density is not the Kamloops objective. City of Kamloops — Development and Engineering Services may permit a plate the Kamloops market cannot absorb, and building to the ceiling in a 97,902-person market is how a compliant project becomes an unsellable one.

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

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

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

Scale changes the risk profile too. In a market of 97,902, a single mispriced Kamloops 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 Kamloops is correspondingly smaller.

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

The method behind the Kamloops page is deliberately boring. Population and rank come from the census roster shared by all 134 markets; the statutory chain comes from the Local Government Act (the Vancouver Charter in Vancouver); and the Kamloops regulatory figures, when any exist, come from a reviewer reading an City of Kamloops — Development and Engineering Services page and stamping the date.

The Kamloops gate is binary and unsentimental: reviewed and dated, or absent. There is no partially trusted middle state, which is why a Kamloops figure you see here can be traced to a document in one click.

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