Campaign Video

Https://youtu.be/zBxbnuPAazE

Friday, 21 August 2026

#447 Hemlock and St. Laurent - circle it

Two Gateways, One Fix: The Case for a Traffic Circle at St-Laurent and Hemlock

Two Gateways, One Fix: The Case for a Traffic Circle at St-Laurent and Hemlock

A bookend to the traffic circle already on the table for Vanier Parkway and Beechwood — and a sequencing question Wateridge Village's growth makes urgent.

The proposal

Two intersections mark the north and south gateways of the same green corridor running through the Beechwood/St-Laurent area: Vanier Parkway at Beechwood Avenue on the south end, and St-Laurent Boulevard at Hemlock Road on the north end. Both are places where a landscaped, parkway-style road meets a mainstreet-scale arterial. Both are places where the City's own planning documents have already recognized that the standard signalized intersection isn't the right tool. I'm proposing a traffic circle at each — treating the corridor's two gateways the same way, instead of fixing one and leaving the other as an afterthought.

This isn't a new idea — the City already floated half of it

The Vanier Parkway/Beechwood circle isn't something I invented. It came directly out of the City's Beechwood Avenue Transportation Corridor brainstorming process, which listed "adding a traffic circle at the Vanier Parkway intersection" alongside other corridor ideas. The City has known this intersection deserved special treatment for years. It just never got built.

What's less noticed is that the City's own Beechwood Community Design Plan makes the identical argument for the Hemlock end of the corridor — just not about the St-Laurent intersection specifically. The plan's own language:

"Parkways — the Vanier Parkway, the Rockcliffe Parkway and, to a lesser extent, Hemlock Avenue — are sweeping, limited access roads surrounded by green landscapes… the place where Beechwood meets Hemlock is similar in nature to where the Rockcliffe Parkway meets Confederation Boulevard. It is at the latter location that the National Capital Commission and the City of Ottawa have built a roundabout."

In other words: the City has already built a roundabout on this exact logic — parkway meets mainstreet, treat it as a gateway — a few hundred metres away at Rockcliffe Parkway and Confederation Boulevard. The reasoning that justifies a circle at Beechwood/Vanier applies just as directly one intersection north, where Hemlock — the same "parkway-style" road named in the City's own plan — meets St-Laurent Boulevard. That's the corridor's other bookend, and it's the point where St-Laurent's speed limit steps down from 50 to 60 km/h zones into the slower, denser section that runs past Manor Park.

Why it matters more now: Wateridge

St-Laurent and Hemlock sits at the doorstep of Wateridge Village, the former CFB Rockcliffe lands now being built out as a new, still-growing neighbourhood. This isn't a hypothetical future traffic increase — Wateridge's own community association has already documented resident concerns about speeding on their internal streets, concerns serious enough that they pushed a council motion to improve transit service in the area. A neighbourhood that's still under construction is already generating enough traffic pressure to need council intervention. That pressure funnels toward St-Laurent at exactly the intersection this proposal targets, and Wateridge isn't finished growing.

That's the sequencing argument. We have a documented pattern in this ward of treating known problems as someone else's timeline — the St-Laurent LRT tunnel sat on an "urgent" 2020 inspection finding for over five years before repair funding moved. I don't want the north gateway of this corridor to become the next multi-year deferral, discovered only after Wateridge is fully built out and the intersection is already failing.

The safety case, on the City's own terms

The City of Ottawa's own roundabout guidance is explicit about why this matters for a corridor with a growing residential population on one end and a cemetery, seniors' community, and mixed-use towers on the other:

  • At a roundabout, a pedestrian crosses only two sections of one-way traffic moving at slow speed — not the multi-directional turning conflicts of a signalized intersection.
  • Roundabouts remove the risk of a driver running a red light through a crossing pedestrian, which signals can't design away.
  • Roundabouts keep traffic moving at lower, more consistent speeds through the intersection itself, rather than the stop-and-accelerate cycle of a signal.

None of this is me asserting national collision statistics onto a specific corner. It's the City's own published rationale for why it uses roundabouts at all — applied consistently to a corridor where the City has already used that rationale once, at Confederation Boulevard, and floated it once more, at Vanier/Beechwood, without ever closing the loop at the corridor's other end.

What I'm not claiming

I don't have site-specific collision or volume data for St-Laurent and Hemlock, and I won't pretend I do. That's exactly the kind of study the City should be running now, while the St-Laurent Boulevard Transit Priority Corridor EA — which already covers the Hemlock-to-Innes stretch — is active, rather than as a bolt-on after Wateridge's build-out is complete and retrofitting gets more expensive and more disruptive.

The ask

  • Fold a St-Laurent/Hemlock roundabout feasibility study into the live St-Laurent Transit Priority Corridor EA — the corridor boundary already starts at Hemlock, so the study scope doesn't need to be reopened, just extended to this intersection design.
  • Formally revisit the Vanier Parkway/Beechwood circle the City's own Beechwood corridor process already put on the table, instead of letting it stay a shelved brainstorming item.
  • Require Wateridge's projected build-out traffic volumes to be factored into both studies, not treated as a separate problem to be discovered later.
It's just not that hard
Peter Karwacki is running for Ward 13 (Rideau-Rockcliffe) in Ottawa's October 2026 municipal election.

#446 In broad daylight - still no question

St. Laurent Station: Managed Risk, Missing Questions

St. Laurent Station: Managed Risk, Missing Questions

Ottawa • August 21, 2026

A major LRT transfer hub carries a documented structural risk. The City of Ottawa is actively managing it. Yet in successive public forums devoted to service reliability and return-to-office readiness, that specific constraint has gone unexamined.

The known issue

St. Laurent Station’s underground structure, originally built in the mid-1980s as a bus transitway, suffers from chronic water infiltration, concrete delamination, and spalling. In a report prepared by Stantec Consulting Ltd. and attached to a City request for proposals, the engineering firm stated that deteriorated concrete falling from the soffit “poses a serious and ongoing risk to the travelling public.” Mesh netting and periodic scaling are in place as temporary measures. The City maintains the station remains safe under continuous inspection and monitoring, while advancing a multi-million-dollar rehabilitation expected to require five to six weeks of full double-track closure plus additional single-tracking periods, likely beginning in 2028.

The public-record pattern

In June 2026 Transit Committee and Audit Committee discussions of RTO readiness, questions stayed at the system-wide level—fleet availability, downtown delivery, overall capacity. Specific operational bottlenecks at St. Laurent Station and its primary arterial feeders (King Edward Avenue / Route 7 / Route 12) were not raised.

The same pattern held on Friday, August 21, 2026, during the City’s technical briefing on the Transportation and Mobility Action Plan. Staff presented on fall ridership expectations, new express routes, schedule adjustments, and network reliability. When the floor opened for questions, Councillor Rawlson King (Rideau-Rockcliffe) used the opportunity to raise ward-level concerns about road reliability and alignments. He did not inquire about the structural condition of St. Laurent Station, the Stantec risk assessment, or the reliability of the King Edward and Montreal Road feeders under increased federal RTO loads.

Why it matters

St. Laurent is a multi-level transfer point where bus feeders meet the LRT. Increased morning peak demand from federal workers returning four days a week will concentrate additional riders at exactly this junction. Feeder reliability gaps or cancellations along King Edward and Montreal Road would compound platform crowding. Corridor-specific performance data for these routes under RTO stress has not been placed on the public record in the forums designed to examine readiness.

The City is not ignoring the asset. Inspections continue, temporary protections are in place, and permanent repairs are being scoped. The question is narrower and more procedural: when public briefings focus on service reliability and RTO preparedness, why does a known constraint at a high-volume transfer hub remain outside the discussion—even when a councillor whose ward is directly connected has the floor?

What remains open

  • How will reliability metrics for Routes 7 and 12 be tracked and reported as RTO volumes rise?
  • What contingency planning exists for transfer surges at St. Laurent if feeder service fluctuates?
  • When will the full operational implications of the planned multi-week track closures be detailed for riders and Council?

These are not speculative concerns. They follow directly from the engineering assessment already on file and from the geography of the network. Putting them on the public record in reliability and readiness forums would strengthen both accountability and confidence in the system Ottawa is asking thousands of additional daily riders to trust this fall.

Primary sources: Stantec report (quoted in Ottawa Citizen, CBC, CTV News, late July 2026); City of Ottawa Infrastructure Services statements; June 2026 Transit and Audit Committee proceedings; August 21, 2026 technical briefing recording.

#445 Rideau Rockcliffe Must Show Leadership for the East End Crossing

 


It is a definitive difference in policies between the King and I.


https://www.ctvnews.ca/ottawa/article/testing-underway-for-proposed-eastern-ottawa-gatineau-bridge/


The bridge is coming whether you like it or not.

Reality Check: Manor Park NIMBYIsm fails primarily because like sidewalks, the rest of the city will over rule them 16-9 no matter who they elect for their ward.

The solution is a work around. Engage now, ask for what you need now, show leadership, a willingness to cooperate and jettison the attitude for the good of the city.


Blog Posts on the Proposed East End Crossing

Blog Posts on the Proposed East End Crossing

peterkarwacki.blogspot.com — chronological order
March 20, 2019
Tunnels and Bridges, Pas de problem!
Written during Peter's 2019 council candidacy, this early post tackles the NCC's proposed sixth interprovincial bridge for Ottawa's east end. It opens with the traffic problem driving the debate: semi-trucks making dangerous turns at Rideau and King Edward, with roughly 3,500 trucks crossing the river daily and 72% routing through the Macdonald-Cartier Bridge into Lowertown. Peter contrasts Mayor Watson's description of the Kettle Island bridge option as an "evisceration" of communities against the NCC's preference for that same site, while noting Montfort Hospital's warnings that added traffic could delay emergency services. Rather than picking a side in the bridge-vs-tunnel debate, he argues for combining both — a hybrid approach — and pushes back on treating a billion-dollar price tag as an abstraction. He flags the Kettle Island, Lower Duck Island, and McLaurin Bay corridors then under NCC study.
Read the full post →
February 2026 · #110
Ward 13 – what's your lucky number?
References a Ward 13 candidates' debate that Rogers later removed from its video library, and reiterates the case for finally getting 18-wheelers off downtown streets like King Edward and Rideau via a new east-end crossing. Frames the upcoming election as a clear choice between NIMBY obstruction and positive progress, urging planners to start engaging with the community now rather than waiting for the file to resurface on its own.
Read the full post →
April 2026 · #142
East end crossing
A detailed, directly-titled comparison of Peter's and Councillor King's approaches to the long-debated east-end river crossing. Cites King's promise-fulfillment record (43% versus a 12% city-wide average), his No vote on Lansdowne 2.0, and his firm opposition to the bridge grounded in a 2021 study showing it would divert only about 15% of King Edward Ave. truck traffic. Peter argues the city-wide congestion-relief case outweighs King's ward-level NIMBY framing, positioning the crossing as a project that serves the whole region rather than just Ward 13's immediate streetscape.
Read the full post →
May 2026 · #144
2026 Issues and Stances – The Bridge!
An extensive, table-formatted platform document covering positions on climate change, free transit for students and seniors funded by bridge tolls, affordable housing, campaign-finance reform, and a lengthy critique of King's record — including his 2022 OPS Board resignation. The East End Crossing (Kettle Island Bridge) anchors the transportation section, framed as one of Peter's clearest points of departure from King's platform going into the campaign.
Read the full post →
May 2026 · #168
Madou..objects but Kettle Island Rules
Commentary on planning or development objections raised in relation to the Kettle Island corridor and the broader east-end crossing file. Peter weighs the specific local objections against the region's longstanding transportation needs, reiterating that the crossing's benefits for downtown truck traffic and congestion outweigh site-specific pushback.
Read the full post →
May 2026 · #175
Aviation Parkway – site of the new east end crossing
An examination of the Aviation Parkway corridor — by this point the federally confirmed Montée Paiement–Aviation Parkway alignment — as the site of the new interprovincial crossing. Peter weighs the technical and community factors at play along the corridor, including its proximity to Montfort Hospital and Manor Park, as planning moves from a multi-decade debate toward a specific, funded route.
Read the full post →
June 2026 · #207
Getting Trucks Out of Downtown: Why Rideau-Rockcliffe Must Lead on the East End Crossing
A strong, dedicated advocacy piece for the east-end river crossing as a way to remove heavy truck traffic from downtown and residential corridors. Peter details the safety, noise, air-quality, and economic benefits, and argues that Ward 13 — sitting closest to the proposed corridor — has a particular obligation to lead on the file rather than resist it, given its position to shape design and mitigation terms if it engages early.
Read the full post →
June 2026 · #230
The Bridge is Coming
An update-and-advocacy post following the federal government's 2024 decision to advance the Montée Paiement–Aviation Parkway corridor. Peter frames the crossing as no longer hypothetical after decades of studies, and calls for the ward to shift from resistance to active engagement in shaping how the project is built.
Read the full post →
June 2026 · #231
The Bridge – What must be done…now
A direct follow-up laying out the specific next steps Peter says are required to keep the crossing moving: funding commitments, environmental assessment milestones, and clear political commitment from Ward 13's representative, rather than the "selective silence" he attributes to King on the file.
Read the full post →
July 2026 · #317
A bridge for which its time has come
A summary case for the crossing after years of study, reviewing the traffic, economic, and environmental arguments in favour and calling for decisive movement now that the federal government has settled on a preferred corridor. Reiterates that continued delay simply prolongs the truck-traffic and safety problems on King Edward and Rideau that the project is meant to solve.
Read the full post →
August 21, 2026 (today)
Rideau Rockcliffe Must Show Leadership for the East End Crossing
Peter's newest post on the file, published this morning. Framed as "a definitive difference in policies between King and I," it links to CTV News coverage confirming testing is now underway for the proposed eastern Ottawa–Gatineau bridge. His argument: the bridge is coming whether Manor Park residents like it or not — council votes 16-9 against ward-level NIMBYism no matter who Ward 13 elects. The way forward, he says, is not resistance but a workaround: engage now, ask for what the ward needs now, show leadership and a willingness to cooperate, and drop the obstructionist posture for the good of the city.
Read the full post →
This list covers every post found addressing the East End Crossing across the full run of peterkarwacki.blogspot.com, cross-referenced against the blog's own "#397 Blog Post Summary #100–#396" index. Exact publication dates for the 2026 posts are approximate (month-level, matching the blog's own archive folders) except where a full date was available. If any other posts on this topic aren't showing up here, send the link and this summary can be updated.

#4 Four FOUR!!! ! Hooks, Slices and Duffs

Why Your Local Councillor Is Basically a Weekend Golfer (And Why That Should Terrify You)

Why Your Local Councillor Is Basically a Weekend Golfer (And Why That Should Terrify You)

A slightly unfair but disturbingly accurate comparison between municipal politics and the world’s most optimistic sport.

There’s something exactly right about comparing local politics to weekend golf. Both involve grown adults who talk a big game, swing with great confidence, and somehow still end up in the weeds. The difference? In golf you only embarrass yourself. In municipal politics you can embarrass an entire transit system.

The Single Pristine Shot Is the Incumbency Mechanism

Golf doesn’t reward you for consistency. It rewards you for one glorious, pure, “did-you-see-that?” shot that erases the memory of the previous eleven disasters. Municipal politics runs on exactly the same psychology.

A councillor can spend years never sitting on the committee that actually oversees the file they keep name-dropping, but one well-timed community-event selfie, one newsletter line that begins “a position I have long championed,” and suddenly the topped drives are forgotten. Voters, like golfers, remember the shot that felt good, not the shot that was actually good.

Democracy, it turns out, has a very short-term memory and an unhealthy obsession with highlight reels.

The Duffs Are Structural, Not Personal

A weekend golfer’s slice isn’t really a character flaw. It’s grip, stance, swing plane, and the stubborn refusal to take a lesson, repeated until it becomes muscle memory. Same with council.

A bad vote or a five-year oversight gap rarely traces back to one person being lazy or corrupt. It traces back to the incentive structure: no relevant committee seat means no real accountability lever, acclamation means no one ever corrects the swing thought, and low-information elections mean nobody’s watching the follow-through. You can fix a slice with lessons. You can fix a governance gap with a seat on the right subcommittee. Neither fixes itself by hoping really hard and posting more photos of ribbon-cuttings.

The Scorecard Is the Part Everyone Skips

Golfers are world-class at creative accounting. They round down, forget the whiff in the rough, and remember the birdie like it was a religious experience. Governance has the same self-scoring problem.

A newsletter that leads with “meaningful progress” and quietly omits the file where the ceiling has been at risk for five years is just golf’s honor system applied to public office. The difference is a bad scorecard in golf costs you a beer with your foursome. A bad scorecard in municipal politics costs someone else the service cut, the missed inspection, or the fare hike nobody actually voted for at the ballot box.

In other words: the councillor gets the mulligan. You get the invoice.

Where the Metaphor Breaks (Usefully)

In golf, the flattering shot and the real skill level eventually converge. The course doesn’t lie forever, and your handicap will eventually rat you out. In municipal politics, without a scorekeeper, they never have to converge. Someone has to be the tedious person who insists on comparing the actual swing mechanics to the full round played, not just the highlight reel on the newsletter.

That’s a far less romantic hobby than golf. It involves reading agendas, tracking committee attendance, and noticing when the same problems keep reappearing under different names. It’s the political equivalent of standing in the rain with a clipboard while everyone else is inside having a beer and talking about that one pure 7-iron.

But it’s also the only hobby that stops the rest of us from quietly subsidizing someone else’s perpetual slice.

So next time your local representative posts another glowing update, ask yourself the only question that matters in both golf and government:

“Okay… but what was the actual score?”

#443 Lord, Give me a sign!





Why I Do It This Way

Every campaign has a platform. Fewer have a reason the platform is built the way it is. Here's mine.

I tell people the truth, not what they want to hear

"Constituent relations" in this city too often means managing how people feel about a decision, not telling them what it cost, who voted for it, and what it did or didn't fix. My assumption is the opposite: residents can handle the real numbers and the real gap between promise and delivery. They don't need protecting from it — they need it published.

An incumbent's livelihood depends on people feeling good about the last four years. Mine doesn't. That asymmetry is what lets me say the uncomfortable thing instead of the reassuring one.

Evidence first, conclusions second

Thirteen years at IBM and Cognos, then a PMP and a data analyst — that background shows up in how I work. I start with the data (311 tickets, audited financials, attendance records, Auditor General reports) and let it tell me the story, not the other way around.

Sometimes it surprises me. Pulling 311 data on flooding in West Rockcliffe didn't turn up a simple crisis narrative — it turned up 123,000 tickets bulk-closed in six days, a data-integrity problem bigger than any one flood. Not the story I went looking for. The one the evidence gave me.

Structures, not scapegoats

It would be easier to make this campaign about one councillor's failures. I've tried not to, and where I've slipped, the results told me why: pieces attacking individuals underperform pieces attacking the structure. Readers trust "this system produces bad outcomes regardless of who's in the seat" more than "this person is bad" — because it's usually true.

Urban wards get outvoted 16-9 by suburban ones. Incumbents win nearly every time; turnout hovers around 40%. Those are structural facts — true no matter who holds the seat. So my energy goes there: ward boundary reform, a consolidated liability statement, a funding source attached to every debt motion. Fixes outlast elections. Grievances don't.

Outcomes over outputs

Municipal politics runs on outputs — motions passed, statements made, committees struck. I care whether the thing the motion was supposed to fix actually got fixed. A councillor can call for transit oversight for years without sitting on the Transit Commission. A city can pass an Anti-Racism Strategy with no published way to measure it working. A safe-workplace program can lose 40% of its budget while the audit language stays just as vague.

None of it requires bad intentions — just someone willing to check output against outcome and publish the difference, even when it's inconvenient.

One term, said out loud

I've committed publicly to a single term, and I think it matters more than it sounds. Most of what's wrong with this council isn't corruption — it's the caution that comes from needing re-election. Committee seats skipped because they're exposed. Audits not pushed because you'll sit across from that department again next year. One term removes that gravity from my decisions. Not a virtue — a structural fact about my incentives, and I'd rather you know it now than discover its absence later.

What this looks like in practice

It's why a post from me is as likely to be a liability-management plan or an LRT bearing-failure timeline as a stump speech. Why I file records requests instead of press releases. Why, when criticized, I check if the criticism is right before deciding how to respond — which is also why early pushback on one piece settled, once people read the underlying facts, into roughly two-to-one support.

I don't expect agreement on every conclusion. I do think you should be able to see how I got there, check the numbers yourself, and hold me to the standard I'm applying to everyone else. That's the approach. Everything else is the platform built on top of it.

#442 Gimmicks and Backslapping Endorsements

Endorsements Aren't a Position. They're a Substitute for One.
Ward 13 — AccountabilityRideau-Rockcliffe

Endorsements Aren't a Position. They're a Substitute for One.

Gimmicks and back-slapping fill the space where a debate should be. Policy is hard to formulate and hard to understand — which is exactly why it's so easy to trade it in for somebody's word for it.

Policy is hard. It's hard to formulate, hard to model the trade-offs of, and hard to explain in a way that doesn't put people to sleep. An endorsement, by contrast, is easy. It's a name, a photo, a quote about character. It costs the reader nothing to accept and the endorser nothing to give — and increasingly, that ease is doing the work that debate is supposed to do in this election.

There are two versions of this happening in Ottawa right now, and they're not the same problem, even though they produce the same emptiness.

The Challenger's Shortcut

The first is familiar: a candidate picks up a name-brand endorsement and lets it stand in for a platform. Vote for me, because someone you already trust says to. It's a real transaction — the endorser is putting something on the line for someone who hasn't held office yet — but it still isn't a substitute for a position on the St-Laurent tunnel, on OPS Board oversight, on where the city's off-balance-sheet liabilities are headed. An endorsement can open the door to a conversation. It's not the conversation.

The Incumbent's Closed Loop

The second version is quieter and, I'd argue, worse: incumbents endorsing incumbents. Colleague-to-colleague, council-to-council, the congratulatory back-slap dressed up as civic guidance. A great partner on council. Always fights for the ward. Proud to support. It's the political equivalent of "I'm OK, you're OK" — mutual validation between two people who already hold power, asking for four more years of the same.

What a challenger endorsement risks

The endorser is backing an unproven outcome. There's no guaranteed return — if the challenger loses, the endorser gets nothing back.

It's a bet, which means it's at least a claim. Someone is saying: I looked at this person and I think they're right for the job.

What an incumbent-incumbent endorsement risks

Nothing. Both parties already hold office. The "risk" is reciprocal and self-insuring — you back me this cycle, the goodwill compounds for next time.

It requires no engagement with either record. It's not a claim about performance at all. It's a relationship being described as a reason.

Ask what an incumbent-incumbent endorsement actually cites. Not in the abstract — read the next one you see. Does it name a vote? A motion? An outcome delivered versus one promised? Or does it stop at "great colleague" and "always in the community"? My prediction, based on everything I've read through King's own newsletters this cycle, is that you'll come up close to empty. That's not a coincidence. Content engineered to generate zero friction is content engineered to never be checked.

The tone you trust isn't the record you're voting on.

That's the mechanism underneath all of this, and it isn't limited to politics — it's a well-documented failure mode in how people extend trust to anything that stays consistently pleasant in tone, regardless of whether the underlying claims hold up. A newsletter that never mentions the tunnel closure sitting in its own ward reads exactly as trustworthy as one that does, if tone is the only thing being evaluated. Back-slapping endorsements work the same way: they borrow the warmth of an existing relationship and let it stand in for scrutiny nobody actually performed.

Where I Sit on This, Plainly

Disclosure

I have one endorsement — maybe two — and both were unsolicited. That's a thin list next to the reciprocal networks incumbents build over multiple terms in office, and I'm not going to pretend otherwise.

But thin and real is a better foundation than thick and free. Nobody backing a first-time or long-shot challenger is doing it to protect a future favour. There's nothing in it for them except agreeing with the argument. That's a higher bar than incumbents clear for each other by default, and it's worth saying plainly instead of padding the comparison to look symmetrical. It isn't.

What Would Actually Move This

Not fewer endorsements — better ones. An endorsement that means something says what it's actually backing:

  • Which specific votes, motions, or delivered outcomes the endorsement is based on — not just "a great colleague."
  • Whether the endorser has anything to gain from the relationship continuing, stated openly rather than left implicit.
  • What the endorser would point to if asked to defend the claim on the merits, not the friendship.

Held to that standard, most of what currently passes for endorsement in this race — mine included — would have to either get specific or go quiet. I'd take that trade. The alternative is an election decided by who has the warmest network, which is just incumbency with a friendlier name.

Rideau-Rockcliffe residents can find the full record — capital project oversight, OPS Board findings, transit accountability, and the rest — on this blog and on Unpublished.ca.
Ward 13 · October 2026


Thursday, 20 August 2026

#441 Future LRT Oriented rule mismatch - how ai could have helped

Orléans Parking Schlmozzle: Policy Ambition Meets the LRT That Still Isn’t There

Orléans Parking Schlmozzle: Policy Ambition Meets the LRT That Still Isn’t There

August 20, 2026

In Orléans, the gap between what Ottawa’s new zoning rules promise and what daily life actually delivers is widening in real time. The city’s 2026 zoning overhaul eliminated minimum resident parking requirements for new multi-unit buildings, banking hard on transit-oriented development. The theory is clean: build dense housing near future rapid transit, let the market and the train sort the rest, and free up land and construction costs for more homes. The practice, right now, looks messier.

The clearest example sits at 530 Brisebois Crescent and 265 Centrum Boulevard. Forum Asset Management’s proposal for roughly 1,500 units across five buildings (nine to 40 storeys) offers 136 visitor parking spaces and zero dedicated resident spots. It leans entirely on proximity to the planned Place d’Orléans station on the O-Train Line 1 East Extension. On August 19, the Planning and Housing Committee sent the application back to staff for further review after Councillor Matthew Luloff and local businesses flagged the obvious problem: Orléans is still a car-dependent suburban community, and the LRT that is supposed to change that equation is not yet running.

That LRT delay is not a minor footnote. The East Extension (Blair to Trim, five new stations including Place d’Orléans) reached substantial completion in early March 2026. Stations are finished, systems are largely commissioned, and informal testing has occurred. Yet formal 21-day trial running has not started. The bottleneck is train availability. Ongoing cartridge-bearing “spalling” issues have kept large parts of the fleet offline; officials need roughly 46–54 vehicles available before trial running can begin. As of mid-August, OC Transpo was still “ramping up final readiness activities,” targeting enough vehicles by the end of the month, with no firm public opening date announced. The extension will miss the August 30 fall service change. What began as a 2022 target, then 2024, then early or mid-2026, is now sliding later into 2026 at best—if the latest recovery holds.

This is the lived-experience side of the ledger. Residents of Orléans still transfer by bus to reach Blair or other Line 1 stations. Commutes remain among the city’s longest and most crowded. Meanwhile, the zoning framework treats the station as if it is already delivering reliable, high-frequency rail service. Visitor parking is retained and capped (0.1 spaces per unit after modest exemptions, with per-building limits). Loading spaces are not required for residential uses. Accessible, EV, and bicycle requirements remain. Only the general-purpose resident stall minimum was zeroed out. The policy is coherent on paper if the LRT opens on schedule and mode share shifts quickly. It is far less coherent when the train is still months away and car ownership patterns in the east end have not magically changed.

The consequences are predictable. Move-ins, trades, deliveries, overnight guests, and the many households that still need a vehicle for childcare, groceries, medical appointments, or shift work will compete for the limited visitor supply and surrounding streets. Existing residents and businesses already report pressure. Future occupants of these towers—who may have chosen the address partly because parking was never promised—will discover the friction only after they move in. That is the classic sequencing failure: housing policy races ahead of the infrastructure it depends on.

None of this means the long-term direction is wrong. Dense housing near rapid transit is sound urban policy, and underground parking is expensive. The By-law’s more granular approach (keeping visitor, loading for non-residential, bike, EV, and accessible rules while dropping the blanket resident minimum) shows deliberate design rather than pure ideology. Staff studied visitor spillover and chose not to weaken those requirements further. But ambition without delivery creates exactly the schmozzle now visible in Orléans. The LRT’s repeated delays—construction, then fleet reliability—have turned a future-oriented rule into a present-day mismatch.

The committee’s referral of the Forum application is a small, useful pause. It forces a second look at whether a 1,500-unit project with zero resident parking can function in today’s Orléans rather than the Orléans that exists only on the transit map. Residents who end up cursing the lack of foresight will not be wrong if the gap between policy and reality continues to grow while the trains stay in the yard. The ambition is clear. The lived experience, today and for the foreseeable tomorrow, is still waiting for the train.

How AI Could Have Been a Game Changer in Orléans

How AI Could Have Been a Game Changer in Orléans

Catching the parking–LRT mismatch before it reached committee

The August 2026 referral of the 1,500-unit Forum proposal at Brisebois Crescent and Centrum Boulevard was predictable. Ottawa’s new zoning rules allowed zero resident parking on the assumption that the Place d’Orléans LRT station would deliver reliable service. Reality lagged: the East Extension reached substantial completion in March 2026 but still lacked a firm opening date by mid-August because of ongoing fleet issues. The result was last-minute political friction, staff rework, and uncertainty for the developer and future residents.

A properly deployed AI system could have surfaced this exact mismatch months earlier — turning a reactive crisis into a managed risk. Here’s how.

1. Continuous Reality Checking

AI excels at reconciling multiple live data streams that humans review only periodically:

  • OC Transpo progress memos, independent certifier reports, and fleet-availability numbers
  • Original versus revised LRT timelines (2022 → 2024 → early 2026 → sliding later)
  • Zoning assumptions embedded in By-law 2026-50 and the Secondary Plan
  • Current car-ownership and modal-split data for Orléans

When the probability of timely LRT revenue service dropped below a defined threshold while a zero-parking application was under review, the system would have generated an automatic, high-priority alert. No one would have needed to “notice” the gap in a committee report.

2. Forward-Looking Scenario Modeling

Instead of a single optimistic assumption, AI can run dozens of realistic futures in seconds:

  • “LRT opens Q4 2026 with full frequency”
  • “LRT opens mid-2027 with reduced initial service”
  • “Further fleet delays push reliable service into 2027”

For each scenario it would forecast on-street parking demand, visitor-stall overflow, trades and move-in pressure, and spillover onto neighbouring streets. Decision-makers would have seen quantified risk ranges rather than a binary “transit is coming” narrative.

The practical difference: Staff and the applicant could have adjusted parking ratios, phased requirements, or added temporary measures while the application was still in early review — avoiding the public referral and redesign cycle that is now underway.

3. Early Intervention During Policy Design

The same monitoring layer could have operated while By-law 2026-50 was being finalized. It would have tested the new zero-minimum parking rules against actual Stage 2 delivery risk across every major station area. Orléans would have been flagged as higher-risk than stations already in service, prompting either tighter interim rules or explicit contingency language. Preventing the mismatch at the policy stage is far cheaper than correcting it project by project.

4. What AI Would Not Have Done

AI does not replace political judgment. It cannot force council to slow housing targets or compel the LRT to open on schedule. What it does is remove plausible deniability. Once the mismatch is quantified, transparent, and repeatedly surfaced, the cost of ignoring it becomes visible to everyone — staff, councillors, the developer, and the public.

Bottom Line

The data needed to spot this sequencing failure was already public. An AI system focused on “policy assumptions versus infrastructure reality” would have made the gap impossible to overlook. The result would have been earlier course correction, less wasted staff time, lower redesign costs, and reduced risk of future resident frustration. That is the concrete, near-term value of AI in municipal decision-making: turning foreseeable mismatches into manageable ones before they reach the committee floor.