Part 2: Why Village A Passed Unanimously and Where the Real Pressure Points Begin - 11/19/2025

The vote ended up unanimous, but the questions show you where the real pressure points are going to land as this moves from paper to pavement. Most councillors treated Village A as a rare case where a developer did the things councils keep asking for. They cited the volume of consultation, visible design changes, and the mix of housing forms as proof that this was not a standard subdivision playbook. That tone matters, because it frames how future Base 31 phases will be judged. The bar just got set.

© PEC Council (YouTube)

View the entire PEC Council Meeting; or view our recap >

The meeting also created a soft political reality. Even councillors who raised hard questions worked to separate “legitimate operational concern” from “anti Base 31 sentiment.” You can hear the committee actively policing misinformation, especially around taxpayer exposure.

The strongest advocates and what they emphasized

Councillor John Hirsch anchored his support in “consultation that actually changed the plan.” He singled out the laneway concept as something residents asked for that was delivered. His questions were focused and practical: how many secondary or laneway suites does this design realistically enable, and how exactly does that translate into affordability. He was essentially testing whether “housing diversity” is a slogan or a supply mechanism.

Councillor Kate MacNaughton backed the design on planning fundamentals. She praised connectivity and the move to a larger central park, and she framed this proposal as a direct contrast to a previous application earlier in the meeting that lacked density and housing variety. Her biggest policy concern was not aesthetics. It was transportation capacity and choke points, plus sustainability choices that may look fine on a slide deck but become costly in real life.

Councillor Roberts positioned themselves as pro Base 31 but focused on public narrative risk. They raised the rumor that ratepayers will be stuck paying for water and wastewater infrastructure and pushed for a clear correction on the record. They also asked for numbers on local jobs and pressed on housing definitions, wanting “affordable versus attainable” to be more than a vague pairing of words.

Mayor Ferguson delivered the most comprehensive endorsement, rooted in long exposure to the file. The core of his remarks was trust-building: he repeated the developer’s early promise to be respectful, learn the community, and contribute, then stated that Base 31 has lived up to those commitments since 2021. His emphasis was that this is “a neighborhood, not a subdivision,” meaning the standard suburban critique does not fit as easily.

The primary skeptics and what they were actually worried about

The sharpest friction did not come from opposition to growth. It came from fear of accumulating municipal obligations.

Councillor Phil St-Jean was the clearest voice on this, especially early in the laneway discussion. His first critique was about operations: plowing and maintaining laneways adds service area and cost. He framed it as a fairness question, meaning taxpayers paying more because a subdivision design chose an extra network to maintain. Later, he softened that concern and made the opposite argument: new assessment and tax base should pay for new services, and without development you get none of the benefits. That arc matters. It shows a councillor moving from “cost exposure” to “growth pays for itself,” while still insisting the costs are real and must be named.

His most persistent practical issue was parking. He basically predicted the future complaint cycle in one sentence: more units means more cars, cars overflow to streets, winter bans trigger towing, residents blame the municipality and the developer, and the operational headache becomes political. That is the kind of concern that does not block approvals. It becomes an accountability issue later when the first winter hits.

The key questions that shaped the debate

1) Affordable versus attainable

The committee pushed hard on what these terms mean in practice. Staff offered the County’s affordability definition: housing costing less than 30 percent of before tax household income. “Attainable” was treated as the broader category for people who do not qualify for subsidized housing but still cannot buy into high cost markets easily.

The applicant added a more specific and market oriented definition: attainable means smaller and more entry level product, multiple tenures, and units designed for different life stages. They also floated a starting price target of $399,000. The unresolved piece is enforcement. The discussion established intent, not mechanism. If the County wants “affordable” to be more than an aspiration, the tool is not the subdivision approval itself. It is agreements, program design, and what gets built in the rental and mid density phases.

2) The laneways experiment

This is the first publicly owned laneway system of this type in the County, and everyone understood that. Staff described the laneways as an operationally negotiated compromise with two travel lanes, space for lighting and snow storage, and prohibited parking.

The trade-off was explicitly stated: laneways can enable gentler density and secondary units, but they cost more to plow and maintain. Staff suggested one mitigation path that will matter later: a lower level of service for laneways than for standard local streets, similar to approaches used in larger cities. This becomes a future political decision. If residents expect identical plow timing everywhere, the laneways become a conflict zone. If expectations are set early, the County gets flexibility.

3) Secondary units and parking realities

Two planning facts shaped this discussion.

First, the plan allows a large number of potential additional units through laneway houses, garden suites, and internal suites. Second, recent provincial changes limit a municipality’s ability to require additional parking spaces solely because additional dwelling units are added.

So councillors were trying to square a circle. More units can mean more cars, but the County cannot fully solve that through parking requirements.

Staff and the applicant offered partial answers: one parking space per primary unit is required, garages exist, and removing front driveways can increase on-street parking opportunities. Councillors pushed back with real world winter constraints and likely overflow.

This is one of the biggest “watch this later” items, because it will not show up in a traffic report. It shows up in complaints, enforcement, and winter operations.

4) Traffic choke points and road widening anxiety

MacNaughton put her finger on a County wide pain point: York Union, Lake Street, and County Road 10 are already stressed. She signaled resistance to road widening due to established streetscapes, which hints at a future clash between growth and preserving character corridors.

The applicant response leaned heavily on the transportation study conclusion: Village A requires no external intersection improvements, and three external intersections tied to broader buildout will be developer funded. They did not fully answer the emotional core of the question, which is “even if the model says it works, what happens when 700 plus units arrive and everyone is still driving.”

That tension will resurface as other Base 31 villages come forward.

5) Sustainability and long-term operating costs inside homes

MacNaughton raised detailed sustainability critiques that were unusually granular for a subdivision discussion. She flagged heat pumps as preferable to natural gas furnaces, questioned tankless water heaters in a context where water waste can inflate bills, and suggested solar water heating as a pragmatic alternative. She also floated the idea that naturalized stormwater ponds could be designed with multi-zone function, including potential safe swimming, if engineered correctly.

This did not alter the approval, but it did something important. It put sustainability expectations on the record early, before site plan and building permit stages. That creates political permission later for councillors to push harder on building standard choices.

6) Health care as the missing sticky note solution

Roberts asked the most community grounded question: everyone wanted health care, so is it actually part of the plan. The developer said yes, described active conversations with clinic operators and a doctor from Alberta, and framed it as an aspiration that becomes easier once housing is real.

St-Jean then asked the follow-up the community will ask later: are you speaking to the doctors already here who are under pressure. The answer was essentially “not enough yet, work in progress,” and the developer reiterated the chicken and egg problem.

This is a credibility hinge point. If a clinic materializes, it reinforces the “complete community” narrative. If it does not, it becomes the easiest broken promise story, even if it was never a formal condition of approval.

The factual clarifications that mattered for public perception

The committee used the meeting to correct several common public claims. The most important one was infrastructure cost responsibility. Staff stated internal subdivision infrastructure is built by the developer, and future phases depend on available sewage capacity. The developer emphasized that the draft plan does not trigger costs onto ratepayers.

The developer also offered a direct counter narrative on economic spillover: they cited surveying visitors and claimed 65 percent patronize downtown, and they gave a back-of-envelope property tax projection tied to average home value and the tax rate. Even when numbers are debated later, getting these claims into the public record changes how residents argue about the project.

Why the vote was unanimous, even with concerns

The committee treated Village A as aligned with several non-negotiable planning goals at once: density that can be serviced, a wider housing mix, parks that are usable, and a street network designed for walkability. On top of that, Base 31 had already delivered visible benefits that speakers reinforced in real time.

So the concerns did not translate into “no.” They translated into “we are watching you.” The recorded vote passed with all members in favor.

What to watch next

• The issues most likely to return are not the broad vision items. They are the operational realities.

• Parking and winter enforcement will become a lived experience problem quickly if secondary units scale up.

• Laneway maintenance standards will become a policy debate once residents start comparing service levels.

• Traffic choke points will remain politically sensitive as other Base 31 villages stack on top of other County growth.

• Health care will stay the most emotionally potent expectation, because it was publicly framed as “in the game” even though it is not a subdivision condition.

Sustainability choices will reappear later at site plan, building design, and marketing stages, especially as energy costs and infrastructure constraints evolve.

---

Disclaimer: This article is based on a meeting with an approximate duration of 3:45:049. Due to the length of the meeting, our team was not able to independently review the full recording in its entirety. As a result, we relied on software-generated transcription, automated summarization, and automated recognition of speakers and participants, which may not be entirely accurate. All transcriptions, summaries, and related content are prepared by our team in good faith and on a reasonable best-efforts basis. The content is provided for general informational purposes only and is intended to support public understanding of the topics discussed. While reasonable efforts have been made to present the information accurately, automated processes may result in errors, omissions, or unintended misinterpretations. This article does not constitute an official, certified, or verbatim record of the meeting, and it should not be relied upon as such. Readers are encouraged to consult original source materials, official minutes, or recordings where available for confirmation or clarification. Questions, requests for clarification, or suggested corrections may be submitted to hello@pecconnect.ca for review and consideration.