Recommendations

What would help

311 already closes requests equally fast in every group once a request is made. These twelve steps aim at the gap before a request exists: making sure every community is heard. Each one says what is missing today and what we propose. Most can be piloted within existing budgets.

Group A

Measure who 311 hears

The City tracks how fast 311 responds, but not which communities it isn't hearing from.

1

Make "reports per 1,000 residents" an official 311 measure

The gap today

311's dashboards show raw request counts by community, and the ward dashboard compares wards per household, dividing every year by 2021 Census households. That favours wards with large households and makes fast-growing wards look like they report more each year (see Ward 5). Raw counts favour big communities, and wards mix high- and low-reporting communities together. Neither shows which communities report less than similar ones. The City's quarterly performance report tracks only how quickly 311 calls are answered.

What we propose

Report infrastructure reports per 1,000 residents for every community, next to the rate expected for similar communities, in 311's quarterly performance reporting alongside response time. Flag communities reporting well below expected.

Lead
311 & Insights
Effort
Low
How we'd know it works
Within a year the measure appears in the quarterly report, and the City uses it to choose where to act.
2

Refresh the gap analysis every year

The gap today

No City report looks at which communities under-report. This study is a one-time outside snapshot, and its data stops at September 2026.

What we propose

Repeat the analysis each year with the City's own, more complete data, and share the list of low-reporting communities with ward offices and community associations.

Lead
311 & Insights
Effort
Low
How we'd know it works
A yearly list is published, and the gap between low-reporting communities and similar ones narrows year over year.
Group B

Make reporting easier

Many residents don't know 311 exists, or find it hard to use without English. Reporting should be visible, simple, and possible without English or typing.

3

Put 311 where people already are

The gap today

Many residents may not know 311 exists, or that they can use it to report a pothole or a broken streetlight. The gap is not only in the app: in the communities with the most non-English speakers, phone and other non-app requests are about 22% lower per resident (220 vs 283 per 1,000 a year), and app requests 42% lower.

What we propose

Put small, simple signs where people walk and wait: park entrances, transit shelters, community halls, libraries and streetlight poles. Each shows icons (pothole, light, tree, water), "Call, tap or scan 311", a QR code, and a line in the community's main languages. Give each community its own QR code so the City can count the reports each sign brings in. Repeat the message on utility bills, waste carts and community newsletters, and point to the app's new languages when they launch in 2026.

Lead
311 & Insights; Marketing & Communications; Parks; Mobility
Effort
Low
How we'd know it works
Reports from each community's QR code, and reports per 1,000 residents in signed communities against similar unsigned ones.
4

Add photo-first reporting

The gap today

Reporting online or in the app means choosing from a long list of request types and answering written questions. That is hard without strong English.

What we propose

Let residents snap a photo, drop a pin and tap a simple icon (pothole, light, water, tree). Staff route the request from the photo and location. No typing and no English needed.

Lead
311 & Insights
Effort
Medium
How we'd know it works
More first-time reporters in high-gap communities, and the share of requests made photo-first.
5

Accept reports by text or WhatsApp

The gap today

311 takes reports by phone, online and through the app. Many newcomers use messaging apps every day, but there is no way to report a problem by text or WhatsApp.

What we propose

Set up a number residents can message, in the most-spoken languages of high-gap communities, that feeds the same 311 queue.

Lead
311 & Insights
Effort
Medium
How we'd know it works
Messages received that become valid requests, by community.
6

Close the loop

The gap today

Residents can check a request's status, but "closed" does not always mean fixed, and there is rarely a photo or plain note showing what was done. People who don't see results stop reporting.

What we propose

When a problem is fixed, tell the reporter in plain language, with a photo where possible.

Lead
Service departments
Effort
Low
How we'd know it works
More residents report again, and satisfaction with 311 rises.
Group C

Reward and encourage reporting

Small, well-designed incentives and trusted local messengers can turn reporting into a habit in the communities that report least.

7

Fix-It Points

The gap today

Reporting takes time and effort, and residents get nothing back for it. The people least familiar with 311 have the least reason to start.

What we propose

Verified, non-duplicate infrastructure reports earn points that can be traded for City-owned rewards such as leisure centre drop-in passes or transit day passes. Points are capped each month and awarded only after the City verifies the report.

Lead
311 & Insights; Recreation
Effort
Medium
How we'd know it works
Verified reports per 1,000 residents rise in pilot communities, with no rise in duplicates.
8

Community Care Challenge

The gap today

Community associations are the City's closest local partners, but nothing links their work to 311 reporting.

What we propose

Associations in high-gap communities earn small grants for growth in verified reports per resident, with a public leaderboard by ward.

Lead
Community Services
Effort
Low to medium
How we'd know it works
Verified reports per resident grow in participating communities.
9

311 Community Ambassadors

The gap today

Newcomers often learn about City services from settlement agencies, faith centres and neighbours rather than City campaigns. No program trains these trusted people to help residents use 311.

What we propose

Train multilingual residents through those organisations to help neighbours report, and to lead seasonal walk-and-report audits with ward offices.

Lead
Community Services; ward offices
Effort
Medium
How we'd know it works
Residents helped, and reports made at walk-and-report audits.
10

Bring in young people

The gap today

Young people in newcomer families often help their parents with English and online services, but they aren't asked to help report neighbourhood problems.

What we propose

Run school and youth-group "map your block" projects that report real issues, recognised with volunteer certificates.

Lead
Community Services
Effort
Low
How we'd know it works
Schools and groups taking part, and valid reports they make.
Group D

Don't rely on reports alone

Even with better reporting, some problems will go unreported. The City can find them directly.

11

Inspect proactively where reporting is low

The gap today

Much day-to-day maintenance starts with a complaint. The City has tested camera-based road defect detection, but there is no plan to send inspections first to the communities that report least.

What we propose

Schedule proactive inspections, including camera-based detection, first in under-reporting communities.

Lead
Mobility; Water; Parks
Effort
Medium
How we'd know it works
Defects found by inspection in under-reporting communities, and a falling repair backlog there.
12

Measure "fixed", not just "closed"

The gap today

311 tracks how fast requests are closed, but not whether the same problem comes back.

What we propose

Track how often a closed request is followed by a new one for the same issue at the same place, by community, and report it next to response time.

Lead
311 & Insights
Effort
Low
How we'd know it works
The reopen rate is published and falls over time.

How Fix-It Points would work

Earn
Points for each infrastructure report the City verifies as real and not a duplicate. Bonus points for a first report from a new household in a high-gap community.
Redeem
City-owned rewards only: leisure centre drop-in passes, transit day passes, or a donation of points to the community association.
Safeguards
Points awarded only after verification; a monthly cap per person; no points for duplicates; a fixed annual reward budget.
Where first
High-gap communities only during the pilot, so rewards reach the people 311 hears from least.

Incentives carry risks: duplicate or trivial reports, and rewards flowing to residents who already report. Verification before points are awarded, monthly caps and a pilot limited to high-gap communities address most of these. The City's own data would show quickly whether verified reports per resident rise.

A 12-month pilot the City could run

Where
Two or three wards with large reporting gaps (for example Wards 3, 5 and 9), with similar communities elsewhere as a comparison group.
What
Local 311 signs with the 311 phone number and a QR code for each community, photo-first reporting, Fix-It Points, a Community Care Challenge and trained ambassadors.
Measures
Verified infrastructure reports per 1,000 residents; share of new reporters; duplicate rate; defects found by proactive inspection; awareness of 311.
Success test
Reporting in pilot communities closes at least half the gap with similar communities, with no rise in the duplicate rate.
Cost control
Rewards limited to City-owned passes within a fixed budget; ambassadors through existing settlement-agency partnerships.