Brantford is a mid-depth market of 104,688 people, 26th of 46 in Ontario and about 1% of the provincial roster. Feasibility work in Brantford behaves differently from work in Toronto: fewer precedents, slower comparables, and a Brantford bylaw often written for a smaller city than the one standing today.

Across the 134-market Canadian roster, Brantford is 53rd by population and shares tier 2 with 39 other markets. Its 0.04× ratio to Toronto is the number to apply before importing any Toronto rent or velocity assumption into a Brantford model.

Bracketing Brantford by population: Thunder Bay (108,843) sits directly above and Chatham-Kent (103,988) directly below. Those two markets are the most defensible sanity check available for a Brantford assumption, because they share Ontario's statutes and its approval culture.

Nationally, Brantford reads most like Delta, BC, Red Deer, AB, St. John's, NL — same tier, similar population, different statutes. Use them to sanity-check what density Brantford 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.

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

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

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

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

Zoning exists in Brantford because the Planning Act delegates the power to City of Brantford — Planning and Development. That delegation is conditional: the Brantford instrument, the Zoning By-law, must conform to the Official Plan, and where the two conflict the policy document wins. It is why an FSR read off a Brantford zoning map can sit below what the plan contemplates — the plan is the ceiling of ambition, the bylaw the ceiling of right.

Where the Zoning By-law does not permit the massing a Brantford site can physically hold, the paths are a minor variance to the Committee of Adjustment or a full rezoning, and disputes land at the Ontario Land Tribunal. Treat the Brantford approval route as a line item rather than a footnote: it drives interest carry, option length and the credibility of the exit.

Within Brantford, 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 Brantford lots under the same code can support materially different buildings. Confirm the parcel with City of Brantford — Planning and Development, not the colour on the map.

Above City of Brantford — Planning and Development sits Ontario, and above the Brantford bylaw sits the Planning Act. When the province moves, Brantford follows on its own schedule; assume the printed Brantford text is the current law only after checking the date on it.

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

Worked through on a reference 27,000 sf Brantford lot at 2.5 FSR — an illustration, not a Brantford figure — the density ceiling is 67,500 sf of gross floor area, roughly 72 units at an 85% efficiency and 800 sf average. Whether Brantford 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 Brantford team what to ask for: storeys and floor-to-floor where height governs, density where FSR governs. In Brantford, where approvals run through City of Brantford — Planning and Development and contested outcomes reach the Ontario Land Tribunal, a misaimed request costs a cycle.

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

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

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

Brantford 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 Brantford lots more often than most owners expect.

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

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

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

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

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

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

This is a Brantford screening instrument, not an entitlement opinion. Every figure should be re-read against the Zoning By-law and confirmed with City of Brantford — Planning and Development before money moves.

The method behind the Brantford 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 Brantford regulatory figures, when any exist, come from a reviewer reading an City of Brantford — Planning and Development page and stamping the date.

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

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