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.
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.
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
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
- Stand up a unified search index over the main public portals.
- Promote those portals as first-class destinations on the homepage and in search suggestions.
- Attach ward and address metadata to every new report and application.
- 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.
- Measure search success: top queries, zero-result queries, and whether the first hit is a live tool or an archive.
Longer term
- Use one address/parcel master across services.
- Expose domain systems through stable APIs rather than only through separate websites.
- Publish neighbourhood-level operational metrics in the same place residents already look for services.
- Only then add assistants or chat interfaces, and only if they retrieve current, sourced city records.
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
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.
Navigating Ottawa's Digital Sprawl: How Citizens Can Actually Extract Information from City Hall
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.
No comments:
Post a Comment