Ottawa Projects Near You
Prototype — illustrative sample data, not a live City feed. Click a pin, or a card, for the synopsis.
Ottawa Doesn't Have a Consultation Problem. It Has an Enforcement Problem.
Ward 13 (Rideau-Rockcliffe) — Campaign Notes
Ottawa has had a written public engagement policy since 2003. It has a dedicated online platform, a strategy document, a workbook, an addendum with ten new sections, and a Public Information and Media Relations team whose job is partly to coordinate how the City talks to residents.[1][2] On paper, this is a mature system.
In practice, residents describe something closer to theatre: display boards instead of discussion, surveys with no room for nuance, meetings scheduled at hours that guarantee low turnout, and committee decisions that arrive with almost no warning. A Centretown BUZZ analysis of the 2026 municipal election laid out the gap between the policy and the experience in detail, drawing on a February 2026 public meeting where the City asked residents how to fix its own engagement process — and got told, repeatedly, that thirty years of nominal improvement hadn't changed much.[3]
The pattern that emerges isn't a lack of process. It's a lack of consequence when the process is skipped, rushed, or ignored. Below are the specific failure points, and what an actual fix looks like for each one.
1. Committee timing is a black hole
The problem: Reports typically land about a week before a standing committee hears them, and council ratifies the committee's recommendation roughly ten days after that. Residents often don't know when their issue will actually be scheduled — the Gladstone-Gilmour bikeway project didn't have a confirmed committee date even as the article went to print, and turned out not to be on the June agenda at all.[3] Since 2024, the City has also run fewer standing committee meetings, which means unrelated contentious items get bundled onto the same day — Manor Park sidewalks and the Bank Street bus lanes were both debated on March 30, 2026 — leaving residents an unpredictable wait to speak, with no accommodation for anyone who can't be present for the full window.[3]
The fix: A published, rolling 90-day forward agenda for every standing committee, updated at least monthly. The City already tracks this internally to build its own meeting schedules — publishing it costs nothing and removes the single biggest source of the "black hole" complaint. Pair it with a minimum notice-to-comment window (longer for reports tied to capital budgets or zoning changes) so residents aren't given a week to respond to a report staff spent months preparing.
2. Input gets collected but not answered
The problem: Table-format consultations can work — but only if what gets said is written down and acted on. The BUZZ piece points to the New Ways to Bus consultations, where useful rider suggestions were raised in the room and then absent from OC Transpo's final proposal, with no explanation of why.[3] The City's own 2025 year-in-review memo talks about "closing gaps in the engagement experience" and building staff capacity, but doesn't describe a mechanism for showing residents what happened to their specific input.[2]
The fix: A public disposition log for every consultation: each substantive point raised gets a one-line status — adopted, rejected with a stated reason, or deferred with a timeline. This is the same standard I've argued for on 311 data and OPS auditing: if the City is going to collect information from residents, the collection has to be auditable, not just performed.
3. The tools don't allow real input
The problem: Engage Ottawa is a genuinely useful repository for background documents and meeting notices, but its surveys are frequently described as too simplistic to capture what people actually think, and several people at the February 2026 meeting singled out the Lansdowne 2.0 consultation specifically for not being clear about what could still be changed in the agreement.[3] The City's own research into "what participants want" — going back to consultations that shaped the original 2013 strategy — found residents consistently asking for three things: enough time to get informed, a chance to weigh in before a decision is too far along to change, and input weighted the same as developer or business input.[4] Those three asks are, by the City's own account, largely the same ones being repeated in 2026.
The fix: Every major survey should include at least one open-response question reviewed by a human, not just multiple-choice options that pre-sort the answer. For any consultation tied to a binding agreement (like Lansdowne 2.0), the City should be required to publish, in plain language, exactly which terms are and aren't open to change before the consultation begins — not after residents ask.
4. Advisory committees — the low-cost fix that got cut
The problem: Ottawa used to run standing advisory committees of citizen volunteers on issues like cycling, accessibility, and French-language services. Most were eliminated during the Jim Watson era, and the few that remain meet only occasionally.[3] These committees let subject-matter volunteers work through policy problems with staff before an issue became politically charged — cheap, informed input, built in ahead of the decision rather than bolted on after.
The fix: Reinstate 2–3 advisory committees as a bounded pilot (accessibility, cycling, and infrastructure/housing are the obvious starting points) with a fixed review date, rather than either a permanent re-launch or continued neglect. Evaluate, then decide whether to expand.
5. Some voices carry more weight than others
The problem: The Bank Street bus lane debate pitted thousands of daily transit riders against roughly 18 parking spots defended by business owners — and the result was a weakened bus lane proposal. Bike parking requirements in the new zoning bylaw were similarly softened at the last moment "after discussions with industry."[3] Mayoral candidate Alex Lawson's formal lobbying complaint against Mayor Sutcliffe, alleging a "cozy relationship" with former campaign staff turned lobbyists, put a spotlight on whether the City's lobbyist registry is actually doing its job.[3]
The fix: Real-time, not retrospective, disclosure of lobbyist meetings with council members and senior staff. Candidates should publish their donor lists before election day, not rely on residents to cross-reference filings after the fact.
Where this leaves Ward 13
None of this requires reinventing how Ottawa consults residents. The 2026 strategy update itself acknowledges the goal is to make engagement "more predictable, clearer, remove barriers and easier to understand"[5] — which is the right diagnosis. But a strategy document with no enforcement mechanism is exactly what residents have already lived through since 2003. The difference between this round of updates and the last one will be whether any of these standards are binding on staff and council, or whether they're aspirational language that quietly erodes the way advisory committees did.
My own position: a Public Engagement Charter needs teeth. A report shouldn't be eligible to proceed to committee unless the notice period, accessible timing, and disposition-log requirements were actually met — the same standard I'd want applied to my own office if elected.
References
- City of Ottawa, Building stronger communities through Public Engagement (newsroom release, Jan. 2026) — ottawa.ca
- City of Ottawa, Memo: 2025 Public Engagement Year in Review (Dec. 18, 2025) — ottawa.ca
- Alayne McGregor, "Election 2026 analysis: How do we get Ottawa City Council to pay attention?" Centretown BUZZ, June 17, 2026 — centretownbuzz.ca
- "City of Ottawa Public Engagement Strategy," Participedia case study (consultation findings behind the 2013 strategy) — participedia.net
- City of Ottawa, Your input matters: public engagement strategy update, Engage Ottawa (Dec. 2025–Feb. 2026 consultation) — engage.ottawa.ca
Modify 311. Don't Build Another App.
Ottawa doesn't need a new civic tech project to tell residents what's happening where they're standing. It needs 311 to know where they're standing.
Stand outside a construction fence in Ottawa today and you'll get almost nothing from the city about what's happening behind it. No sign explaining the timeline. No easy way to check if the noise, the closure, or the mess is on schedule or six months behind. If something looks wrong, your options are to call 311 and describe your problem from scratch, or give up and post about it on a neighbourhood Facebook group.
That's not a technology gap. It's a design choice, and it's one the city can fix inside a system it already runs.
The idea
311 already knows what it is: a way for residents to report problems and look up information. What it doesn't do is use the one piece of information your phone already has the moment you open the app — where you are — to tell you what the city already knows about that spot.
The fix is simple to describe. A resident standing at or near an active capital project opens 311. Instead of typing a description and guessing at a category, the app recognizes the location and surfaces what's already on file: what the project is, what phase it's in, what the timeline says, and who's accountable for it.
Why this beats a duplicate ticket
I've written before about the 311 data integrity problem I found in Ottawa's open data — over 123,000 tickets bulk-closed in a six-day window, with no visible explanation. That story mattered because it showed the system losing track of its own workload. A GPS-aware project lookup attacks the same failure from the other end.
Location-aware lookup fixes this at the point of entry. If a resident's ticket originates within range of an active project, the system can prompt: is this related to Project X? If yes, the ticket gets linked instead of orphaned. That's not a UX nicety — it's a structural fix to a data integrity problem I've already shown is real.
Why 311, not a new app
It would be easy to pitch this as a shiny new civic tech product. I'd rather not. Ottawa doesn't need another app competing for space on residents' phones, another procurement cycle, another vendor contract to manage. 311 already has the users, the ticketing backend, and the budget line. The ask isn't "build something new." It's "make the system you already paid for smarter about location."
That's a cheaper, more credible ask for a council to say yes to than a net-new platform — and it's the kind of fix that survives past any one election, because it isn't tied to a person, it's tied to how the system works.
What this would take
- Project location data as a live layer — capital project boundaries (not just points) matched against device GPS, with a sensible radius so residents near the edge of a project still get a match.
- Plain-language project summaries — status, timeline, budget vs. actual spend where available, and a link to the underlying council or committee record, so the lookup doubles as an accountability tool, not just a status page.
- Ticket-to-project linking at creation — new 311 tickets filed near an active project get prompted to link, closing the gap that let 123,000 tickets disappear without explanation.
- Offline-tolerant data — a lot of active infrastructure sites, like the St-Laurent tunnel, are underground or in weak-signal areas. The project layer needs to work from a cached dataset, not just a live call at the moment someone needs it.
None of this requires new legislation or a new budget envelope of any real size. It requires treating 311 as core infrastructure — the same argument I've made about open data generally — and building the next feature into the system residents already use, instead of asking them to adopt one more thing.
