Committee decision guide

Parking is a scenario, not a single number

For an institution or landowner, the parking question is usually a continuity question: how do you keep the site working today while testing what the land could support tomorrow? Compare the operational tradeoffs before the committee gets stuck debating a single stall count.

Talk through a site →Compare the scenarios

01 — SCENARIO COMPARISON

Four ways to frame the parking conversation

The right comparison depends on the site, the use, and the local bylaw. These prompts help a council, vestry, or board decide what needs to be verified next.

Keep parking on site

Preserve the current arrangement or add stalls within the property boundary. This can be the simplest operational story, but it may consume the land that creates the project in the first place.

Committee question: What land and budget does parking take away from the build?
Next check: Confirm the bylaw requirement, stall geometry, access, drainage, and servicing constraints.

Reconfigure or share existing parking

Use the site more efficiently, coordinate with a nearby lot, or share spaces across uses where the local rules and operating agreements allow it.

Committee question: Can a shared arrangement protect both daily operations and peak-period demand?
Next check: Validate ownership, hours, accessible spaces, agreements, and the approval path with a local professional.

Phase parking with the build

Treat parking as a sequence: keep enough capacity for current programming, then change the arrangement as a later phase comes online.

Committee question: What must remain available during construction and what can move later?
Next check: Map temporary access, construction staging, accessible routes, and the point at which each phase becomes usable.

Test a reduced-parking scenario

Explore a smaller parking footprint only where the rules, actual travel patterns, and committee priorities support it. A reduced count is a scenario to test, not an approval promise.

Committee question: What evidence would make a lower parking count credible to the council and the people who use the site?
Next check: Compare the rule, demand, transit or walkability context, overflow risk, and any variance or policy process required.

02 — KEEP THE USES VISIBLE

Start with what the site cannot lose

Before asking how many stalls a future project needs, list the worship rhythm, school day, food program, community events, accessible routes, deliveries, and peak moments that parking currently supports. That continuity list is the brief a professional needs to test a real option.

See the institutions brief →

Parking is a scenario, not a single number

Four ways to frame the parking conversation

The right comparison depends on the site, the use, and the local bylaw. These prompts help a council, vestry, or board decide what needs to be verified next.

Keep parking on site

Preserve the current arrangement or add stalls within the property boundary. This can be the simplest operational story, but it may consume the land that creates the project in the first place.

Committee question: What land and budget does parking take away from the build?
Next check: Confirm the bylaw requirement, stall geometry, access, drainage, and servicing constraints.

Reconfigure or share existing parking

Use the site more efficiently, coordinate with a nearby lot, or share spaces across uses where the local rules and operating agreements allow it.

Committee question: Can a shared arrangement protect both daily operations and peak-period demand?
Next check: Validate ownership, hours, accessible spaces, agreements, and the approval path with a local professional.

Phase parking with the build

Treat parking as a sequence: keep enough capacity for current programming, then change the arrangement as a later phase comes online.

Committee question: What must remain available during construction and what can move later?
Next check: Map temporary access, construction staging, accessible routes, and the point at which each phase becomes usable.

Test a reduced-parking scenario

Explore a smaller parking footprint only where the rules, actual travel patterns, and committee priorities support it. A reduced count is a scenario to test, not an approval promise.

Committee question: What evidence would make a lower parking count credible to the council and the people who use the site?
Next check: Compare the rule, demand, transit or walkability context, overflow risk, and any variance or policy process required.

Parking is a scenario, not a single number

Four ways to frame the parking conversation

Keep parking on site

Reconfigure or share existing parking

Phase parking with the build

Test a reduced-parking scenario

Start with what the site cannot lose

Ready to put a real site on the table?

Parking is a scenario, not a single number

Four ways to frame the parking conversation

Keep parking on site

Reconfigure or share existing parking

Phase parking with the build

Test a reduced-parking scenario

Start with what the site cannot lose

Ready to put a real site on the table?