#498 AI in the City

Rideau-Rockcliffe Civic Notes

Index: 311 and artificial intelligence

A chronological list of posts on this blog whose main subject is Ottawa 311 or artificial intelligence, with article numbers, short summaries, and links.

Compiled 7 September 2026 · Source: peterkarwacki.blogspot.com

Passing one-line mentions are omitted. Some early AI pieces also appeared on Unpublished; the blog URL is given when the same argument lives here. Related follow-ups are noted inside the summary.

Artificial intelligence

Unnumbered · 10 December 2023

Ottawa City Councillors need help

https://peterkarwacki.blogspot.com/2023/12/ottawa-city-zcouncillors-need-help.html

Councillors cannot absorb every brief, delegation, and meeting attached to a multi-billion-dollar city budget, and fatigue produces bad votes. The proposed remedy is an AI decision-support system loaded with source data plus explicit morals and ethics, used to augment rather than replace elected judgment. The historical model is Chile’s Project Cybersyn (1971–73), Stafford Beer’s operations-research network that let managers see economic data and send directives. The piece argues that no major city decision should proceed without an AI advisor’s recommendation. A version also ran on Unpublished as “It's time for AI in Ottawa City management.”

#114 · 17 February 2026

A musical interlude

https://peterkarwacki.blogspot.com/2026/02/a-musical-interlude.html

A short demonstration: lyrics by the author, music and vocals generated in Suno. The point is not the song. It is that generative tools already do work that used to require a studio, and that outside estimates put about half of entry-level white-collar jobs within reach of AI agents inside five years. Cultural production is treated as an early, visible example of a labour shift that will also hit administration, analysis, and municipal staff work.

#133 · 23 April 2026

Current Events forecast future trends

https://peterkarwacki.blogspot.com/2026/04/current-events-forecast-future-trends.html

Returns to municipal AI as an operating method, not a slogan. Road-safety and similar files are still decided on multi-year historical averages while current events move faster than the briefing cycle. Staff should be paired with better models so live data, not last year’s roll-up, informs the next intervention. Unused city data is the bottleneck: sensors and datasets already exist; the decision process does not use them in time.

#255 · 5 July 2026

The Yips in politics

https://peterkarwacki.blogspot.com/2026/07/the-yips-in-politics.html

Uses “the yips”—performance anxiety that wrecks a practiced skill—as a metaphor for council delay. AI is offered as the antidote because it does not freeze under political heat. Suggested uses include simulating thousands of municipal outcomes before a long debate, synthesizing briefing books, and allocating resources with an auditable rule instead of a closed-door bargain. Cybersyn appears again as proof that decision-support systems predate chatbots. The claim is not that software should vote. It is that fear and volume are currently doing the deciding.

Unnumbered · 20 July 2026

Robot Doggie PeeJayKay is going Canvasing

https://peterkarwacki.blogspot.com/2026/07/wake-up-robot-doggie-canvasing-is-just.html

A lighter AI piece. It distinguishes what language models can do—scripts, slogans, research—from what they cannot do: buy hardware, hold a bank account, or walk a street. It then compares 2026 quadruped options, including Sony Aibo, Unitree Go2, and cheaper wheeled companions, as a canvassing stunt. The serious thread is capability versus agency. AI is already useful for campaign content; physical presence still belongs to people and machines that someone has to purchase and operate.

#361 · 2 August 2026

AI Governance Issues

https://peterkarwacki.blogspot.com/2026/08/ai-goverance-issues.html

The main municipal-AI policy post. Ottawa is already using AI—staff prompts in the thousands, a résumé-screening tool, systems reading infrastructure footage—while the governance framework is still a promised 2026 document. The proposed standard is to publish an inventory of tools, disclose use by default, guarantee human appeal, test before deployment, and give the Auditor General an annual review. Adoption is ahead of oversight. A disclosure-and-audit rule has to exist before the tools outrun accountability.

#402 · 11 August 2026

Yes, Somebody is Looking

https://peterkarwacki.blogspot.com/2026/08/402-somebody-is-looking.html

A short traffic-and-audience note. Blog views are rising, and some “readers” may be AI bots rather than voters. Artificial intelligence is incidental here, but the post is one of the few that treats automated agents as part of the public information environment, not only as a city-hall tool.

#475 · 31 August 2026

Power to the people

https://peterkarwacki.blogspot.com/2026/08/power-to-people.html

AI appears as electricity demand, not software policy. Hydro Ottawa’s large-load queue includes data centres, some tied to generative AI, that would nearly double local draw if connected. The piece walks through unnamed projects, bill pressure, IESO unserved-energy forecasts, and the lack of a public day-ahead or ride-through standard. Related follow-up: #481 The Juice is worth the Squeeze.

311

#157 · 16 May 2026

PPP Pee Pee and Poo poo

https://peterkarwacki.blogspot.com/2026/05/ppp-pee-pee-and-poo-poo.html

A public-washroom and facilities post that treats 311 as the reporting channel that should make cleanliness and outages visible. Suggestions include QR codes in units that feed ratings and rapid-response tickets, plus integration with maps and 311 so complaints, usage, and surveys sit in one loop. 311 is the measurement system, not the headline topic.

#200 · 7 June 2026

FOIA to access Open Data?

https://peterkarwacki.blogspot.com/2026/06/foia-to-access-open-data.html

Residents should not need a freedom-of-information request to learn who owns a dataset or what the city already measures. The published scorecard includes 311 call-resolution times by category and by ward, so neighbourhoods can see whether service is even. 311 is framed as an equity and management metric: if it is not published in readable form, it is not being managed.

#244 · 30 June 2026

The Satirical Interview with an Ottawa Mayor

https://peterkarwacki.blogspot.com/2026/06/the-satirical-interview-with-ottawa.html

Satire on city statistics. One exchange says satisfaction surveys ignore people who stopped calling 311 years earlier. The 311 point is methodological: official service scores can be survivorship bias if the sample is whoever still bothers to phone.

#345 · 27 July 2026

Third Party news, not mine, not the city, not main stream

https://peterkarwacki.blogspot.com/2026/07/third-party-news-not-mine-not-city-not.html

The first clear public write-up of the 311 finding. A review of Ottawa’s open 311 dataset showed more than 123,000 service tickets bulk-closed in a six-day window, presented as a data-integrity problem rather than a flood or pothole story. The surrounding argument is that thinner local newsrooms make resident analysis of open data, MFIPPA files, and 311 extracts a substitute watchdog. Residents are told to pull the portal datasets and publish what they find.

#387 · 6 August 2026

There is a duty to consult but an imperative to lead

https://peterkarwacki.blogspot.com/2026/08/there-is-duty-to-consult.html

Contains the operational 311 proposal, often summarized as “Modify 311. Don’t build another app.” Instead of a new resident app, 311 itself should become GPS-aware: near an active capital job, the system should show project status and ask whether the new ticket belongs to that file. Linking at creation is offered as the fix for orphaned tickets and for the 123,000 bulk-closures. Engagement reform—agendas, disposition logs—sits in the same post. 311 is the enforcement layer for “the city already knew.”

#415 · August 2026

Enforce those bylaws!

https://peterkarwacki.blogspot.com/2026/08/enforce-those-bylaws.html

Smoking and vaping rules already exist; enforcement is mostly 311-driven rather than patrol-driven. The post asks for published 311 complaint volume and bylaw response times so residents can see whether complaints close or pile up. 311 is the evidence trail for a law that looks present on paper and absent in parks.

#416 · 13 August 2026

Whistle blowers — do we support them enough?

https://peterkarwacki.blogspot.com/2026/08/whistle-blowers-do-we-support-them.html

Uses the 311 bulk-closure, police-database auditing, and St-Laurent inspection findings as cases where someone inside likely knew first. Internal disclosure channels should be tracked the same way 311 tickets and Auditor General findings should be tracked: volume and outcome, not a black box. 311 is the analog for making a hidden process countable.

#427 · 16 August 2026

For the “How” — I’m your man

https://peterkarwacki.blogspot.com/2026/08/for-how-i-m-your-man.html

Applies the ADKAR change sequence to ward files. Under “Ability,” the concrete tool is a 311 rebuild: GPS project lookup and ticket-to-project linking at creation, using the system residents already call, so 123,000 orphaned tickets are not a recurring bulk-close event. 311 is treated as delivery infrastructure, not a call-centre slogan.

#443 · 21 August 2026

Lord, Give me a sign!

https://peterkarwacki.blogspot.com/2026/08/lord-give-me-sign.html

A method post. Pulling 311 data on West Rockcliffe flooding did not produce a simple flood narrative; it produced the six-day bulk-closure of about 123,000 tickets. The lesson stated is “evidence first”: start with 311 extracts, audited financials, and Auditor General reports, and accept the story the file actually contains.

Unnumbered · 7 September 2026

How to search for City Information

https://peterkarwacki.blogspot.com/2026/09/how-to-search-for-city-information.html

Not a 311 exposé. It places 311 and service requests inside Ottawa’s fractured digital map: live tools live on siloed domains while ottawa.ca search ranks old PDFs. Residents are told to bookmark ServiceOttawa, geoOttawa, DevApps, Recreation, Engage, and Open Ottawa, and to use site:ottawa.ca when they must search policy. 311 belongs in the “my services” cluster that the front door currently fails to find.

How the two threads connect

The 311 spine is: find the 123,000 bulk-closures in open data (#345); treat them as a data-integrity failure (#443); fix 311 in place with GPS project linking (#387, #427); publish resolution times by ward (#200).

The AI spine is: use AI as council decision support (2023, #255); use live data rather than stale averages (#133); put disclosure and audit rules on tools already in use (#361); watch the grid cost of AI compute (#475).

also see #387 (call 311 map) https://peterkarwacki.blogspot.com/2026/08/there-is-duty-to-consult.html?m=1

#387 There is a duty to consult but an imperative to lead

Ottawa Projects Near You

Prototype — illustrative sample data, not a live City feed. Click a pin, or a card, for the synopsis.

Slated

Ongoing

Open for consultation

Select a pin on the map to see the project synopsis, status, and how to weigh in.

Prototype for illustration only — pin locations and text are sample data, not sourced from the City of Ottawa.

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

1. City of Ottawa, Building stronger communities through Public Engagement (newsroom release, Jan. 2026) — ottawa.ca
2. City of Ottawa, Memo: 2025 Public Engagement Year in Review (Dec. 18, 2025) — ottawa.ca
3. Alayne McGregor, "Election 2026 analysis: How do we get Ottawa City Council to pay attention?" Centretown BUZZ, June 17, 2026 — centretownbuzz.ca
4. "City of Ottawa Public Engagement Strategy," Participedia case study (consultation findings behind the 2013 strategy) — participedia.net
5. 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.

Right now, a resident who notices a problem near an active project has no way to know the city is already aware of it. They file a ticket. That ticket has no link to the project record. Staff triaging it have no way to know it's a duplicate. Multiply that across a ward with several active files — the St-Laurent tunnel, sewer work in West Rockcliffe, an OC Transpo detour — and you get exactly the kind of untracked, disconnected ticket volume that made the bulk-closure incident possible in the first place.

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.

Peter Karwacki is a candidate for Ward 13 (Rideau-Rockcliffe) in Ottawa's October 2026 municipal election.

#502 Farenheit 311 - Ottawa's Funky Trouble System

Ward 13 · Rideau-Rockcliffe Civic accountability notes

What 311 Data Can (and Can't) Tell You About Ottawa

The system doesn't need a new app. It needs its own data to mean what it says.

Ottawa's 311 — Service Ottawa, run through myservice.ottawa.ca and the ServiceOttawa app — works fine as a way to file a complaint. Call, click, or tap, and a ticket gets created. What it doesn't do well is function as a record the public can actually trust. That distinction matters more than it sounds, because 311 isn't just a complaint line. It's supposed to be the city's most granular, most current dataset on where things are broken and how fast the city fixes them. Right now it can't reliably do that job.

The gap isn't a technology problem. It's an information management problem — the kind that gets missed because it's boring, and because "we have an open data portal" sounds like transparency even when the data inside it doesn't hold up.

The core problem

When a large batch of tickets closes on the same date without differentiated resolution codes, the closure timestamp stops meaning "this got fixed" and starts meaning "this got cleared." Anyone using that data to measure response time — a resident, a journalist, a councillor — gets a false read on how the city is actually performing.

Where the system breaks down

1. Status is binary when it shouldn't be My ServiceOttawa shows only "Open" or "Closed." There's no assigned, dispatched, or in-progress state — so a resident can't tell the difference between "nobody has looked at this yet" and "a crew is scheduled for next week." Cities running proper Open311 implementations expose that granularity because the backend already tracks it. Ottawa's doesn't surface it.
2. Closure codes don't distinguish outcomes "Resolved," "duplicate," "referred to another agency," and "administratively closed" all collapse into the same "Closed" flag. Without that distinction, every downstream metric built on the open data — average time-to-resolution, ward-level comparisons, SLA compliance — is unreliable at the source.
3. No link between a ticket and the project already addressing it File a pothole complaint on a street that's slated for reconstruction next year, and 311 has no way to tell you that. The resident gets a ticket instead of an answer, and the city gets a redundant complaint it has to process anyway.
4. Categories follow the org chart, not the problem A flooding complaint often touches roads, stormwater, and forestry root intrusion at once, but the intake taxonomy assumes one department owns it. The reassignment loops that follow don't show up anywhere in the public data — they just show up as delay.
5. Nobody publishes the accountability loop The raw monthly data dumps exist. A standing dashboard that turns them into resolution-time-by-category-by-ward — the thing that would let council or the public actually monitor performance — doesn't.

What would actually fix it

None of this requires a new platform. It requires the city to treat its own operational data with the same discipline it would demand of any other system of record — and most of it is a backend and API decision, not new infrastructure.

1. Fix closure-code granularity first The cheapest, highest-leverage change. It's a field-mapping problem, not a new build, and it's the one fix that restores trust in every dataset downstream of it.
2. Expose the intermediate status states The backend almost certainly already tracks assigned, dispatched, and in-progress. Show them.
3. Publish a standing resolution-time dashboard By category and by ward, refreshed on the same cadence as the existing monthly data, so there's a real feedback loop instead of a CSV nobody parses.
4. Link tickets to capital and maintenance project records geospatially Tell residents when their street is already scheduled, instead of silently collecting a duplicate complaint. This is the change that actually reduces call volume — it's an efficiency argument as much as a transparency one.
5. Audit the data the way you'd audit any CRM Bulk-closure incidents, category-reassignment rates, duplicate-ticket rates — publish it annually. Right now nothing forces the system's own data quality to be checked at all.

The fix here is backend data discipline applied to the system Ottawa already has — not a new app. That's a harder story to sell at a ribbon-cutting, and it's the one that would actually change what residents can trust when they file a ticket.

This is the same pattern that shows up across most of what I write about city hall: the gap is rarely a missing tool. It's a missing discipline around the tools that already exist — and no one's job is to close that gap unless a councillor makes it their job.

Peter Karwacki — Candidate, Ward 13 (Rideau-Rockcliffe)
peterkarwacki.blogspot.com

#497 How to search for City Information

Keep the specialist systems. They already hold the operational data. Put a citizen experience and integration layer in front of them.

Civic information design

Finding city information should not require a map of the website

Ottawa already publishes a lot of useful data. The harder problem is getting residents from a simple question to the live tool that answers it. Here is an information map and a practical architecture for that.

A working note on municipal search, silos, and service integration · September 2026

If you have tried to look up a green-bin schedule, drop-in swim hours, or a development file on your street, you have probably learned the unofficial rule of ottawa.ca: the homepage search is often the long way around.

In theory, a municipal website is a digital front door. In practice, Ottawa’s public information lives across siloed subdomains, PDF archives, and specialist databases. The live answer is frequently one or two clicks away from the page the search engine returns. Residents who learn the shortcuts get better service. Everyone else gets 2018 committee reports.

This post is not an argument for one vendor or one election platform. It is a design brief: what an information map and architecture would need to do if the goal is faster, more reliable public access to city information.

The real problem is not “too little information”

Ottawa already operates several capable systems:

• My ServiceOttawa for accounts, taxes, and many transactions
• geoOttawa for parcels, zoning, facilities, waste calendars, wards, and historic aerials
• DevApps for planning applications and rezoning files
• Recreation Ottawa for schedules and bookings
• Engage Ottawa for consultations
• Open Ottawa for datasets, dashboards, and downloadable GIS

Those tools are not the failure. The failure is that they do not present themselves as one city. The main search index treats archived staff reports and current service tools as the same kind of document. Subdomains are weakly deep-linked. Address is not a first-class filter. A resident has to know which door to open.

Three familiar mismatches:

• Waste pickup. Expected: an address lookup. Often received: old policy PDFs and news releases about waste diversion.
• Swimming or skating. Expected: hours at the nearest facility. Often received: recreation master plans, while the live schedule sits on recreation.ottawa.ca (https://ottawa.ca/en/recreation-and-parks) .
• Development next door. Expected: active applications on that street. Often received: decade-old minutes that happen to mention the street name, while the current file is in DevApps.

Until the official search works, the practical workaround remains external search with a site constraint, for example site:ottawa.ca green bin schedule, plus a short list of bookmarked portals. That is a symptom, not a strategy.

An information management map

A useful map starts with resident jobs, not department names. Most public lookups fall into four clusters.

My place

Address, ward, property, taxes, water, waste calendar, zoning, flood information, nearby parks and facilities.

My services

Recreation hours and bookings, 311 and service requests, permits, payments, account status.

What’s happening here

Active development files, construction, bylaw changes, committee items that affect a street or neighbourhood.

Evidence

Budgets, performance measures, open datasets, agendas and minutes, routine disclosure lists.

Today those jobs are split across systems that do not reliably share a common place key or a common search index.

Resident job	Primary system today	Typical failure
Taxes, bills, account	myservice.ottawa.ca	Not surfaced well by the main search box
Waste, zoning, parcels, facilities	geoOttawa	Powerful if you already know it exists
Planning files	devapps.ottawa.ca	Street-name search hits old minutes first
Pool and rink hours	https://ottawa.ca/en/recreation-and-parks	Isolated subdomain; seasonal PDFs outrank live hours
Consultations	engage.ottawa.ca	Separate engagement stack
Raw data and GIS	open.ottawa.ca	Catalogue exists, but is not the default answer path
Policy and history	ottawa.ca and PDF archives	Over-indexed relative to live tools

The map only becomes operational when every public artefact carries a short set of fields:

• Audience and task — pay a bill versus research a rezoning
• System of record — which application is authoritative
• Freshness — update cadence and last reviewed date
• Place — address, parcel, ward, or geometry
• Lifecycle — live service, current application, or archive
• Disclosure class — open, routine disclosure, or formal access request
• Canonical URL and API — where a machine or a search index should point

Without that inventory, neither staff nor search engines can tell a current pickup calendar from a staff report that happens to mention “green bin.”

A target architecture

Keep the specialist systems. They already hold the operational data. Put a citizen experience and integration layer in front of them.

Resident channels
  Web  ·  Mobile  ·  311  ·  later: constrained assistant
                 |
                 v
Discovery and experience layer
  Task navigation  ·  Federated search  ·  “My place” context
                 |
                 v
Shared platform services
  Identity   Address/parcel master   Notifications/cases
  Documents  GIS/API                 Content inventory
                 |
                 v
Domain systems
  ServiceOttawa  DevApps  Recreation  Engage  geoOttawa  Open Ottawa
                 |
                 v
Governed data
  Open datasets  Performance metrics  Agendas  Routine disclosure
      

Figure 1. Domain systems stay specialized. The missing municipal layer is discovery, shared place data, and governance.

1. Channel layer

One public front door organized by tasks and life events, not branch names. High-frequency actions — waste, recreation hours, “what is planned on my street,” pay a bill — should be reachable in two or three steps. If someone has to know which office owns the function, the information architecture is still an org chart.

2. Discovery layer

This is the gap that most residents feel. Replace a full-text dump of minutes with federated, ranked search:

• Index live service pages, DevApps records, recreation events, 311 request types, Engage items, Open Ottawa datasets, and geoOttawa feature types.
• Keep archives in a separate collection so historical PDFs do not outrank current tools.
• Make address and map location a first-class filter: “swimming near this address,” “active applications on this street.”
• Maintain the words residents actually type — garbage, green bin, waste collection — as synonyms.
• Return typed results: Service, Map layer, Application file, Dataset, Meeting item, Bylaw.

Commercial search works better than the internal box today because it ranks landing pages over buried attachments. A city search service should do that job on purpose, with deep links into the silos.

3. Shared platform services

These are the pieces that make separate systems feel like one government:

• Identity — one resident profile across accounts, recreation, and later planning comments.
• Master location — a single address and parcel service used by waste, taxes, planning, 311, and maps.
• Cases and notices — one view of my requests, my applications, and my consultations.
• Structured documents — agendas and reports published as objects with title, date, ward, topic, and attachments, not only PDFs dropped into a CMS.
• GIS as a service — geoOttawa and future digital-twin layers exposed by API so other pages can embed “this property” context instead of sending people to another site.

4. Domain systems stay specialized

DevApps can remain the planning file system. Recreation can remain the booking engine. Open Ottawa can remain the catalogue. The rule is API-first and metadata-first: each system publishes a contract for what a current application, pickup schedule, or dataset looks like, so the front door can assemble an answer.

5. Information governance

Access fails when no one owns the question, “Is this the current public answer?” The minimum controls are:

• A public information asset register: what exists, who owns it, how often it is refreshed.
• Routine disclosure plans wired into search, so residents are not sent to a formal access request to learn who manages a dataset.
• Open-by-default publication of non-personal operational measures on a fixed cadence.
• Quality rules: every resident-facing page has an owner, a review date, and a flag that says current or archival.

What better access would look like

A search for “when is my green bin picked up” should return the address lookup or the geoOttawa waste-calendar layer first, not a waste-diversion policy PDF. “Development on [street name]” should open current DevApps files pinned on a map, with committee items as secondary context. “Swim times” should deep-link into live hours for the nearest facility.

That is functional service integration: the same answer whether the person starts on ottawa.ca, in geoOttawa, or with 311.

Do this first, then this

Near term

1. Stand up a unified search index over the main public portals.
2. Promote those portals as first-class destinations on the homepage and in search suggestions.
3. Attach ward and address metadata to every new report and application.
4. Publish a versioned public inventory of “where to look for X.” The unofficial cheat sheet residents already keep is a manual version of that inventory.
5. Measure search success: top queries, zero-result queries, and whether the first hit is a live tool or an archive.

Longer term

1. Use one address/parcel master across services.
2. Expose domain systems through stable APIs rather than only through separate websites.
3. Publish neighbourhood-level operational metrics in the same place residents already look for services.
4. Only then add assistants or chat interfaces, and only if they retrieve current, sourced city records.

A chatbot on top of a fractured index will confidently retrieve the wrong PDF. Search quality and metadata come first.

A resident cheat sheet, until the architecture catches up ( *this is a fake link it is actually https://ottawa.ca/en/recreation-and-parks)

What you need	Go directly here
Property taxes and water bills	myservice.ottawa.ca
Zoning and land-use maps	maps.ottawa.ca/geoottawa
Planning applications and rezoning	devapps.ottawa.ca
Drop-in recreation, swimming, skating	*
Public consultations	engage.ottawa.ca
Raw datasets and civic GIS files	open.ottawa.ca

Those bookmarks are a reasonable stopgap but they should not be the permanent public interface.

The test

A municipal information architecture is working when a resident can ask a plain question, stay on one journey, and reach the current tool without knowing which department owns the file. Ottawa already has most of the source systems. The work that improves access is the layer that makes them findable, joinable by address, and clearly labelled as live or archival.

Navigating Ottawa's Digital Sprawl: How Citizens Can Actually Extract Information from City Hall

Published by Peter Karwacki • Rideau-Rockcliffe Civic Notes

If you have ever tried to look up a simple piece of municipal information on the City of Ottawa’s website and left feeling thoroughly frustrated, you are not alone. Whether you are looking for your green bin schedule, drop-in public swim hours, or active development notices in your neighborhood, navigating the city's main web footprint often feels like sifting through decades of digital archive clutter.

In theory, a municipal portal should serve as an efficient digital front door for residents. In practice, Ottawa's information architecture is fractured across siloed sub-domains, deep PDF archives, and independent databases. To get the answers you need, residents have to learn how to bypass the front page altogether.

The Internal Search Problem: Why Simple Queries Fail

The core barrier on ottawa.ca is its site search engine. Instead of prioritizing direct, user-facing tools or actionable services, the engine runs full-text queries across thousands of meeting minutes, staff reports, and historic committee documents.

Scenario 1: Searching for "Garbage Pick Up"

What you expect: An address lookup tool for your neighborhood's pickup schedule.

What you get: Downloadable PDFs of 2018 Committee Reports, news releases from three years ago, and high-level policy outlines explaining the concept of waste diversion.

Scenario 2: Searching for "Public Swimming" or "Skating"

What you expect: Drop-in pool or rink hours at your local community center.

What you get: High-level master plans for recreation, nested landing pages, or outdated seasonal PDFs. The actual scheduling engine lives on an isolated sub-domain ( https://ottawa.ca/en/recreation-and-parks ) that the main search bar rarely deep-links effectively.

Scenario 3: Searching for "Development Applications" or Street Names

What you expect: Active building proposals, rezoning notices, or variance requests down the street.

What you get: Agendas from a decade ago where the street name was mentioned in passing, completely missing active planning files hosted inside the separate devapps.ottawa.ca application.

A Citizen's Cheat Sheet for Extracting Municipal Data

Because the main portal tries to be everything at once, the key to getting fast, accurate information is skipping the homepage search bar and bookmarking the targeted portals directly:

What You Need	Direct Portal / Tool	Best Method
Property Taxes & Water Bills	My ServiceOttawa	https://myservice.ottawa.ca
Zoning & Land Use Maps	geoOttawa	https://maps.ottawa.ca/geottawa/
Planning Applications & Rezoning	DevApps Portal	https://devapps.ottawa.ca
Drop-in Rec, Swimming, Skating	Ottawa Recreation	https://ottawa.ca/en/recreation-and-parks
Public Consultations & Draft Plans	Engage Ottawa	https://engage.ottawa.ca
Raw Datasets & Civic GIS Files	Open Ottawa	https://open.ottawa.ca

Pro-Tip: Use External Search Syntax

When you must search for policy documents or specific city bylaws, bypass the site's internal search bar using Google or DuckDuckGo with the site constraint prefix:

site:ottawa.ca [your topic]

External search indexing far outpaces the site's internal keyword engine in ranking active, relevant landing pages over archived staff PDFs.

Building a More Accessible Civic Digital Front Door

Navigating municipal services should not require advanced internet search skills or prior knowledge of city hall's administrative divisions. Moving forward, municipal digital strategy must focus on functional service integration—unifying separate web tools like DevApps, Recreation, and ServiceOttawa into a cohesive, user-centric platform.

Until those structural improvements are made, keeping these direct tools and search strategies handy ensures you can extract the civic data and municipal services you pay for without unnecessary headaches.

Tags: #Ottawa #CivicTech #OpenData #MunicipalGovernance #OttawaServices #RideauRockcliffe

Navigating Ottawa's Digital Sprawl: How Citizens Can Actually Extract Information from City Hall

Published by Peter Karwacki • Rideau-Rockcliffe Civic Notes

If you have ever tried to look up a simple piece of municipal information on the City of Ottawa’s website and left feeling thoroughly frustrated, you are not alone. Whether you are looking for your green bin schedule, drop-in public swim hours, or active development notices in your neighborhood, navigating the city's main web footprint often feels like sifting through decades of digital archive clutter.

In theory, a municipal portal should serve as an efficient digital front door for residents. In practice, Ottawa's information architecture is fractured across siloed sub-domains, deep PDF archives, and independent databases. To get the answers you need, residents have to learn how to bypass the front page altogether.

The Internal Search Problem: Why Simple Queries Fail

The core barrier on ottawa.ca is its site search engine. Instead of prioritizing direct, user-facing tools or actionable services, the engine runs full-text queries across thousands of meeting minutes, staff reports, and historic committee documents.

Scenario 1: Searching for "Garbage Pick Up"

What you expect: An address lookup tool for your neighborhood's pickup schedule.

What you get: Downloadable PDFs of 2018 Committee Reports, news releases from three years ago, and high-level policy outlines explaining the concept of waste diversion.

Scenario 2: Searching for "Public Swimming" or "Skating"

What you expect: Drop-in pool or rink hours at your local community center.

What you get: High-level master plans for recreation, nested landing pages, or outdated seasonal PDFs. The actual scheduling engine lives on an isolated sub-domain ( https://ottawa.ca/en/recreation-and-parks ) that the main search bar rarely deep-links effectively.

Scenario 3: Searching for "Development Applications" or Street Names

What you expect: Active building proposals, rezoning notices, or variance requests down the street.

What you get: Agendas from a decade ago where the street name was mentioned in passing, completely missing active planning files hosted inside the separate devapps.ottawa.ca application.

A Citizen's Cheat Sheet for Extracting Municipal Data

Because the main portal tries to be everything at once, the key to getting fast, accurate information is skipping the homepage search bar and bookmarking the targeted portals directly:

What You Need	Direct Portal / Tool	Best Method
Property Taxes & Water Bills	My ServiceOttawa	https://myservice.ottawa.ca
Zoning & Land Use Maps	geoOttawa	https://maps.ottawa.ca/geoottawa/
Planning Applications & Rezoning	DevApps Portal	https://devapps.ottawa.ca
Drop-in Rec, Swimming, Skating	Ottawa Recreation	https://ottawa.ca/en/recreation-and-parks
Public Consultations & Draft Plans	Engage Ottawa	https://engage.ottawa.ca
Raw Datasets & Civic GIS Files	Open Ottawa	https://open.ottawa.ca

Pro-Tip: Use External Search Syntax

When you must search for policy documents or specific city bylaws, bypass the site's internal search bar using Google or DuckDuckGo with the site constraint prefix:

site:ottawa.ca [your topic]

External search indexing far outpaces the site's internal keyword engine in ranking active, relevant landing pages over archived staff PDFs.

Building a More Accessible Civic Digital Front Door

Navigating municipal services should not require advanced internet search skills or prior knowledge of city hall's administrative divisions. Moving forward, municipal digital strategy must focus on functional service integration—unifying separate web tools like DevApps, Recreation, and ServiceOttawa into a cohesive, user-centric platform.

Until those structural improvements are made, keeping these direct tools and search strategies handy ensures you can extract the civic data and municipal services you pay for without unnecessary headaches.

Tags: #Ottawa #CivicTech #OpenData #MunicipalGovernance #OttawaServices #RideauRockcliffe

#157 PPP Pee Pee and Poo poo

 

Review of other public restroom strategies offer a compelling model for Ottawa’s  own public washroom strategy emphasizinig flexible, tech-enabled portable units 

(like Throne Labs’ “Thrones”) alongside traditional pilots, business incentives,

accessible, gender-neutral, free facilities.

Full 24/7 is challenging (due to vandalism, maintenance, costs), but  nonetheless necessary.

Extended hours and heated units address winter needs. Public pressure pushes for more reliable access for people.


Challenges:

Funding volatility (tied to budgets/federal issues), temporary closures, and balancing tech with durability.

Success  needs  dedicated staffing and community input.

Ottawa Rollout

Adopt Modular/Portable Tech:

Ottawa should pilot Throne-style heated, sensor-equipped portables as a faster/cheaper complement to the Centretown standalone brick-and-mortar unit.

Portables are easier to place in parks, Bank Street corridors, ByWard Market, or LRT areas without full sewer/water infrastructure and are ideal for phased expansion toward a 10-minute walk network.


Establish a Hybrid Network:
Combine 5–10+ secure fixed units (heated, vandal-resistant, easy-clean like Centretown) with clusters of portables for flexibility/seasonal needs.

Add targeted public urinals in high-traffic male-dominant spots.

Governance & Funding: 

Create a dedicated public washroom coordinator. Secure multi-year budgets, partnerships for maintenance, and annual reporting.

Use GottaGo!

Ottawa's GottaGo advocacy for site selection via public input.

Operations for Heated/Clean/Extended Access:
Prioritize climate-controlled units, professional cleaning contracts with user feedback loop, and extended/24/7 in core areas with security (cameras, lighting, attendants ).

Business incentive programs to unlock private facilities.

Phased Vision: 2026–2027:
Centretown pilot +
2–4 portables. 2028+:
Scale to 10–20+ units city-wide,

Integrate with downtown revitalization for tourism/public health with tech-augmented, partnership-heavy model can delivering wins and scalability despite budget pressure which directly addresss Ottawa’s cold climate.

REF: dcpublicrestrooms.org

Other cities have grappled with similar challenges—limited standalone facilities, public health/sanitation issues, and equity needs.

PPP pee pee

Incorporating privately run washrooms and portables on public property is a cost-effective, scalable way to expand Ottawa’s public washroom network quickly.

They complement the Centretown standalone pilot and the 2027 city-wide strategy. This hybrid model draws from Ottawa’s own advocacy, DC’s Throne Labs approach, and practices in other cities.

Privately Run Washrooms (Business & Community Partnerships)

Ottawa’ must explicitly call for partnerships with local businesses to open private washrooms to the public.

This includes city-sponsored support for extra cleaning, monitoring, signage, and possibly small incentives (e.g., grants or tax relief) in high-need areas like downtown, ByWard Market, or Bank Street corridors.

Businesses (cafes, restaurants, retail, community centres) agree to public access during set hours.

• The city provides signage ("Public Washroom Available"), cleaning subsidies, sharps disposal, or liability protections.

• GottaGo! Ottawa and past discussions highlight this as key during COVID when private facilities were crucial.

Benefits: to PPP pee pee and poo poo

•  Low capital cost for the city; 

leverages existing infrastructure; builds community buy-in. 

Challenges include business reluctance (wear/tear, security) and inconsistent hours.
• Scale via an app or map (Ottawa explored this years ago) listing all participating spots.

• Aim for 50–100+ unlocked facilities downtown, reducing pressure on new builds. 

Models like Germany’s “Nette Toilette” (city pays businesses a fee for public access) or NYC’s public-private incentives could adapt well.

Portable toilets (standard or upgraded) placed on city-owned land (parks, plazas, sidewalks, transit areas) offer fast deployment without full construction. 

Ottawa already use them seasonally in parks, events, and fields; an extensive strategy would fund more year-round or semi-permanent clusters.

Privately operated model: 

The city contracts private companies (e.g., local sanitation firms or innovators like Throne Labs) to install, service, clean, and maintain units on public property. 

The operator handles daily/regular servicing, while the city provides the site, power/water hookups (if needed), and oversight.

• DC Throne Labs example: Thrones are privately manufactured and operated under city contract. Placed on public land (parks, plazas, near transit), they’re heated/AC-equipped, sensor-monitored, app/QR-accessible, with running water and daily professional cleaning.

• Ottawa pays for the service (~$1M in FY2026 for 10 units + manager); Throne manages everything. High usage, low vandalism.

Ottawa fit: 

Pilot Throne-style or similar heated, accessible portables on public sites (e.g., Dundonald Park, 

LRT stations, 

Bank Street) as a bridge to fixed units. 

Easier in winter with power connections.


Other options:

• Basic porta-potties: Low-cost, flexible for seasonal/high-demand spots.
• Upgraded units (e.g., Portland Loo-style single-occupancy, vandal-resistant): More durable, often privately supplied/installed.
• Restroom trailers: Larger, witih multiple stalls, for events or temporary hubs.

Advantages:

 Quick rollout (weeks vs. years for fixed builds); movable based on data (311 complaints, foot traffic); lower upfront costs; private operators absorb maintenance risks.


Challenges & Mitigations:
Permitting on public land (zoning, accessibility); servicing in winter; security (cameras, lighting); equity (full accessible units over urinals).

Address via contracts with performance standards, user feedback, and dedicated city coordinator ...like the Night Mare

Rollout

• Tiered Network: Fixed heated standalones (Centretown model) as anchors + dozens of privately run business facilities + clusters of operator-maintained portables on public property for coverage gaps. 

Goal: <10-minute walk in core areas.

• Phasing: 2026–27: Centretown pilot + business incentive program launch + 5–10 portable units (Throne-style pilots). 2028+: Scale based on 2027 report, with annual funding for contracts.

• Governance: 

Public-private agreements with clear roles; data-driven site selection; integration with GottaGo! advocacy for signage and equity.

• Heated/Clean/24x7 

Angle: Prioritize climate-controlled portables; professional cleaning via operators; extended hours where feasible (security via tech/monitoring).

This approach controls costs, accelerates access, and shares responsibility—proven in other cities. It directly supports Ottawa’s downtown revitalization while addressing public health. 

Education

A robust communications strategy is a critical missing piece for Ottawa’s public washroom rollout. Without proactive public education on safety, cleanliness, proper use, and community cooperation, new facilities (fixed, portables, or privately opened) risk quick degradation from vandalism, misuse, or public skepticism, undermining the entire effort.

Why Communications Matter Here

Past issues in Ottawa (and peer cities) — vandalism, drug use in facilities, public urination heat maps, and resident/business concerns about maintenance — show that infrastructure alone isn’t enough. Successful programs pair facilities with campaigns that build trust, encourage respectful use, and foster shared ownership.

What a Strong Ottawa Communications Strategy Could Look LikeBuild it into the 2027 city-wide report (or launch in parallel with the Centretown pilot). Partner with GottaGo! Ottawa, Coun. Ariel Troster’s office, Public Works, and community groups. 

Drawn from: 

DC’s awareness-raising, 

Seattle’s “Everybody Poos,” 

Vancouver’s signage/mapping focus, and PHLUSH advocacy toolkits.

1. Core Messaging Framework
• Safety: “Secure by design — well-lit, monitored, accessible for everyone. Report issues via 311/app.”

• Cleanliness: “We keep them clean — you help by using properly. Daily professional servicing + your feedback.”

• Cooperation & Respect: “This is for all of us — families, tourists, seniors, workers. Proper use keeps them available.” Emphasize dignity, public health, and downtown revitalization benefits.

• Equity & Inclusion: Highlight universal design, free access, and how it supports vulnerable populations without stigmatizing

2. Multi-Channel Campaign Tactics
• Signage & Wayfinding: Clear, universal symbols at every facility + digital/physical maps (expand Ott/pee app or integrate with Google Maps/311). “Public Washroom — Open & Maintained” signs at participating businesses and portables. Vancouver’s 2026 framework prioritizes this for better access.

• Public Education Campaigns:
• Humorous/positive visuals (e.g., “Everybody’s Gotta Go” ) via social media, bus shelters, parks, and LRT.
• Hygiene posters inside units (e.g., proper disposal, handwashing) — proven to shift behaviors.


• Videos/testimonials from users (tourists, families, businesses) shared on City channels and GottaGo!.
• Community Engagement:
• Open houses, pop-up events at pilots (e.g., Centretown), and neighborhood meetings.
• School/workplace programs and partnerships with BIDs (Business Improvement Areas) for private washroom participants.
• User feedback loops: QR codes in every unit for ratings/cleanliness reports + rapid response.
• Media & Storytelling: Proactive releases on milestones, success stories (e.g., “X fewer sanitation calls after launch”), and data (usage stats, reduced street issues). Counter NIMBY concerns with facts on safety/maintenance.

3. Integration with Private & Portable Elements
• Privately Run Business Washrooms: Train participating businesses on the program; provide co-branded signage and materials. Educate the public: “Support local spots that open their doors — they get city support for cleaning.” Address business fears with clear guidelines on expectations.
• Portables on Public Property (e.g., Throne-style or basic): Operator contracts include maintenance visibility (sensors/apps showing status). Public messaging: “Privately serviced for reliability — powered by [company] under city standards.” Highlight quick deployment and flexibility as wins.

4. Phasing & Governance
• Short-term (2026–2027): Pilot comms with Centretown opening — launch kit with signage, social push, and 311 integration. Dedicated budget line for outreach.
• Ongoing: Annual “State of Public Washrooms” report + campaign refresh. Dedicated coordinator (like DC’s DPW manager) handling education alongside operations.
• Metrics for Success: Track 311 complaints, usage data, user surveys, and public sentiment. Adjust based on feedback.

Proven Inspirations
• Build awareness of benefits for all (residents, tourists, equity) while advocating for funding/maintenance.

• Grassroots campaigns reduce stigma and build consensus through public meetings and outreach.

• Practical PR tools for engaging media, simplifying messaging, and community planning.

Incorporating this would make Ottawa’s hybrid network (fixed + private partnerships + operator-run portables) far more sustainable. It turns potential “problems” into community assets through education and cooperation. GottaGo! already has strong research and advocacy roots — looping them in formally would accelerate this. 

This time around, inform yourselves, vote differently, vote wisely. Vote for Peter Karwacki for Rideau Rockcliffe.