Home › The Town at Work › Chapter 9

The Town at Work

Chapter 9Municipal Service Reform

3,791 words · Mike Seiler · Owen Sound, Ontario

In this chapter

• 9.1 The Municipal Service Catalogue
• 9.2 Published Service Standards
• 9.3 First to Action
• 9.4 The First to Action Workflow
• 9.5 One Request, One File Number
• 9.6 The Standing Work List
• 9.7 Emergency Work
• 9.8 Professional and Regulated Work
• 9.9 Local Trades
• 9.10 Community Tasks
• 9.11 Seasonal Civic Work Days
• 9.12 Duplicate Reports
• 9.13 Requests Outside City Jurisdiction
• 9.14 Service Requests From Councillors
• 9.15 Telephone Service
• 9.16 In-Person Service
• 9.17 Digital Service
• 9.18 Multilingual Service
• 9.19 Accessibility
• 9.20 The Service Recovery Standard
• 9.21 Complaints as Information
• 9.22 Service Backlogs
• 9.23 Root Cause Review
• 9.24 Performance Measures
• 9.25 Privacy
• 9.26 Public Status Categories
• 9.27 Service Transparency Without Public Shaming
• 9.28 The First-Year Service Review
• 9.29 The New Service Rule
• 9.30 What Success Looks Like

Most residents experience municipal government through ordinary things.

A pothole.

A sidewalk that has not been cleared.

A broken sign.

A building permit.

A recreation registration.

A tree problem.

A missed collection.

A question about a property.

A damaged trail.

A parking issue.

A leaking municipal fixture.

A business licence.

A call to City Hall.

These interactions may seem small compared with major capital projects, but they shape public trust every day.

A resident should not need to understand the City's internal structure before reporting a problem.

They should not need to know which department owns the issue.

They should not need to repeat the same information to several people.

They should not wonder whether anyone received the request.

They should not need a personal contact at City Hall to find out what happened.

Municipal service should be organized around the problem being solved, not around the organizational chart.

The existing plan introduced First to Action, where residents report problems through a public map, professional matters are routed to the appropriate service, small paid jobs can be directed to qualified local trades, and suitable community tasks can involve neighbours and supervised youth.

It also proposed a permanent standing work list covering recurring issues such as lighting, trails, graffiti and litter so that these problems are reported, grouped, scheduled and measured rather than repeatedly rediscovered.

Those ideas become the foundation of a broader municipal service system.

The operating principle is:

Report it once. Route it properly. Track it publicly where appropriate. Finish the work. Close the loop.

9.1The Municipal Service Catalogue

Before improving service, the City should clearly identify what services it actually provides.

Create a public Municipal Service Catalogue.

This should not be another large internal manual.

It should be a resident-facing guide explaining the services available through the City and the basic standard residents can expect.

Each Service Should Identify

Service

What does the City provide?

Responsible Area

Which department or municipal partner is responsible?

How to Access It

Online, telephone, in person, mail or another method.

Eligibility

Who can use the service?

Information Required

What does the resident need to provide?

Expected Response

How quickly should the City acknowledge the request?

Expected Completion

What is the normal service target where a reasonable target can be established?

Emergency Route

What should a resident do if the problem presents immediate danger?

Cost

Is there a fee?

Other Government

Does Grey County, Ontario, Canada or another organization actually control the matter?

Review or Appeal

What can a resident do if they disagree with the outcome?

The catalogue should be written in plain language.

A resident should be able to search:

"Tree"

and discover the appropriate municipal process.

Or:

"Pothole"

"Fence"

"Noise"

"Sidewalk"

"Business"

"Building permit"

"Water bill"

"Park rental"

"Snow"

Government should become easier to navigate.

9.2Published Service Standards

A service standard is a public promise concerning how the City intends to respond.

Not every municipal issue can have the same timeline.

A dangerous water-main break is different from a faded park sign.

A building permit is different from a request for historical information.

A road emergency is different from a suggestion for next year's budget.

The City should establish reasonable categories.

Example Service Categories

Emergency

Immediate threat to:

• life;
• public safety;
• essential infrastructure;
• significant property;
• environmental protection.

Response begins immediately through the appropriate emergency process.

Urgent

A problem requiring timely attention but not an immediate emergency.

Examples might include:

• serious sidewalk hazards;
• damaged traffic signs;
• significant road defects;
• unsafe public equipment.

Routine Service

Normal municipal work that can be scheduled.

Examples might include:

• minor sign repair;
• graffiti;
• litter;
• non-urgent park maintenance;
• routine road or trail concerns.

Application or Approval

Services requiring:

• professional review;
• inspection;
• statutory notice;
• outside-agency comment;
• applicant information.

These should have published processing standards appropriate to the service.

Information Request

Ordinary questions that should generally be resolved quickly or routed immediately.

Standards Are Targets, Not Fiction

A published standard should reflect what the City can reasonably deliver.

There is no value in promising a five-day service standard if residents routinely wait thirty days.

Where the City cannot meet its standard, the system should record:

• that the standard was missed;
• why;
• what the revised expected date is.

The purpose is improvement, not pretending delays do not happen.

9.3First to Action

First to Action should become the City's common service-request system.

A resident reports a problem once.

From there, the City determines where it belongs.

The resident should not have to route the issue themselves.

Residents Could Report

• potholes;
• damaged signs;
• blocked sidewalks;
• litter;
• graffiti;
• streetlight problems;
• trail damage;
• park equipment;
• drainage concerns;
• fallen branches;
• damaged public property;
• accessibility barriers;
• snow and ice concerns;
• public washroom issues;
• waterfront conditions;
• other routine municipal matters.

Each Request Receives

• a reference number;
• date received;
• category;
• location;
• status;
• responsible service;
• expected next step.

Where appropriate, the public-facing system should show the issue on a map.

Personal information should not be displayed.

The person who reported the issue should not become part of the public record simply because they helped identify a municipal problem.

9.4The First to Action Workflow

Every service request should move through the same basic sequence.

Step 1: Receive

The issue enters through:

• website;
• map;
• telephone;
• City Hall;
• staff report;
• councillor referral;
• paper submission;
• another approved route.

Step 2: Confirm

The resident receives confirmation.

Step 3: Triage

Determine:

• emergency;
• urgent;
• routine;
• duplicate;
• another jurisdiction;
• insufficient information;
• non-municipal issue.

Step 4: Route

The request moves to:

• City crew;
• professional municipal staff;
• local contracted service;
• approved local trade;
• community program;
• Grey County;
• another government;
• another public agency.

Step 5: Schedule

The work is:

• dispatched immediately;
• scheduled individually;
• grouped with similar work;
• assigned to a seasonal work program;
• referred externally.

Step 6: Complete

The responsible party records completion.

Step 7: Verify

Where appropriate, confirm that the problem was actually resolved.

Step 8: Close the Loop

The resident receives the result.

The final message should be understandable:

Completed.

or:

Scheduled for September.

or:

This is a Grey County responsibility. It was referred on August 14. Here is the appropriate contact.

or:

No municipal action is being taken because the condition meets the City's current standard. Here is that standard.

A closed service ticket should mean the question was resolved, not merely removed from someone's inbox.

9.5One Request, One File Number

Residents should not need multiple case numbers for one municipal problem.

Where a matter touches several departments, create one public-facing file number.

Internally, the City may have:

• engineering tasks;
• inspection files;
• financial entries;
• legal records;
• work orders.

That internal complexity should remain inside the organization wherever practical.

For the resident:

One problem. One reference number. One place to check.

This is particularly important for complex matters such as:

• business openings;
• building projects;
• accessibility issues;
• neighbourhood drainage;
• events;
• permits requiring several municipal departments.

A person trying to invest in Owen Sound should not become the project manager for City Hall.

9.6The Standing Work List

Some municipal problems are predictable.

Every spring there will be road repairs.

Every year there will be graffiti.

Trees require maintenance.

Trails require inspection.

Streetlights fail.

Signs become damaged.

Snow and ice create recurring accessibility concerns.

Litter accumulates.

Instead of treating every occurrence as a completely new event, maintain a permanent Standing Work List.

The original initiative identified low lighting, trail management, graffiti and litter as examples of work that should operate as managed streams rather than disconnected complaints.

Standing Work Streams Could Include

• potholes;
• road-edge repairs;
• sidewalks;
• curb problems;
• streetlights;
• signs;
• graffiti;
• litter;
• parks;
• playgrounds;
• trails;
• benches;
• public washrooms;
• drainage;
• trees;
• accessibility barriers;
• winter maintenance;
• riverfront conditions.

Each Stream Should Have

• responsible department;
• seasonal schedule;
• backlog;
• service standard;
• work completed;
• average completion time;
• cost;
• recurring problem areas.

This turns complaints into operating information.

If the same problem appears repeatedly in the same location, the City should eventually ask:

Why does this keep happening?

The answer may reveal a larger repair that is cheaper than treating the symptom forever.

9.7Emergency Work

The public reporting system must never slow down emergency response.

Residents need clear direction.

Examples of Potential Emergencies

• downed power or utility hazards;
• major water-main failure;
• dangerous road obstruction;
• fire;
• serious flooding;
• immediate threat to public safety;
• critical infrastructure failure.

The public map should clearly state when residents should call:

• 911;
• the appropriate emergency line;
• another emergency service;

rather than submitting an ordinary service request.

Emergency Information Should Be Simple

Residents should not be expected to determine jurisdiction during an emergency.

The City should make it easy to identify the correct contact.

9.8Professional and Regulated Work

Some jobs cannot appropriately be crowdsourced.

They require:

• licensed trades;
• professional engineers;
• certified operators;
• qualified inspectors;
• trained municipal employees;
• specialized equipment;
• regulated procedures.

First to Action should distinguish these immediately.

Examples may include:

• electrical work;
• drinking-water operations;
• major road work;
• structural inspection;
• hazardous-material handling;
• fire systems;
• major tree hazards;
• regulated building work.

The objective is not to turn municipal infrastructure into a volunteer project.

It is to ensure that each job reaches the right person quickly.

9.9Local Trades

Some municipal work is small enough that a full traditional tender process may be unnecessarily cumbersome, while still requiring qualified paid workers.

The original proposal called for overflow, smaller jobs and peak-season work to be offered through a standing quick-quote list of local trades while City crews retain safety-critical and emergency work.

Subject to applicable procurement rules, the City should develop a roster for suitable work.

Potential Categories

• carpentry;
• plumbing;
• electrical;
• painting;
• fencing;
• minor concrete;
• landscaping;
• equipment repair;
• small excavation;
• signage;
• welding;
• seasonal work;
• specialized maintenance.

The Objective

Make municipal opportunity accessible to smaller qualified businesses.

That requires:

• clear qualification standards;
• reasonable insurance requirements;
• straightforward registration;
• transparent selection;
• prompt payment;
• fair rotation or quotation rules where appropriate.

A local trades strategy should increase competition.

It should never become a way to steer work to political friends.

9.10Community Tasks

Some tasks can appropriately involve residents, service clubs, neighbourhood groups and supervised students.

Examples may include:

• litter collection;
• community planting;
• event support;
• trail observation;
• non-technical mapping;
• neighbourhood cleanups;
• approved beautification;
• community information;
• public-space stewardship.

These tasks should meet four tests.

Safe

The work is suitable for volunteers.

Additive

It does not replace paid municipal employment.

Supervised

The City or partner provides the level of oversight appropriate to the activity.

Useful

The task creates a genuine public benefit.

Volunteer work should not become make-work created to produce a photograph.

Residents who offer their time deserve meaningful work.

9.11Seasonal Civic Work Days

The existing plan proposes organized work days in every season involving City crews, local businesses and residents, with costs and savings reported publicly.

These should become an extension of the Standing Work List.

Spring

Repair and Reconnect

Possible activities:

• litter;
• trail cleanup;
• public-space preparation;
• neighbourhood observation;
• approved planting;
• winter damage identification.

Summer

River and Parks Day

Possible activities:

• shoreline cleanup;
• park beautification;
• trail stewardship;
• public-space improvements;
• community recreation.

Autumn

Prepare Owen Sound

Possible activities:

• winter readiness;
• drainage observation;
• trail preparation;
• public-space cleanup;
• community emergency information.

Winter

Neighbour Day

Possible activities:

• snow support;
• neighbourhood rinks;
• safe recreation support;
• accessibility observations;
• community connection.

The City should publish:

• work completed;
• City cost;
• employee contribution;
• business contribution;
• volunteer contribution;
• verified savings where legitimate;
• issues identified for future work.

9.12Duplicate Reports

A good public system will produce duplicates.

Ten residents may report the same pothole.

That is not necessarily a problem.

It tells the City something about visibility and urgency.

The system should combine duplicate reports into one work item while showing how many people have reported or followed the issue.

Do Not Make Residents Compete for Attention

A service issue should not automatically move ahead simply because it received more online clicks.

Priority should be based primarily on:

• safety;
• service standard;
• professional assessment;
• severity;
• operational efficiency.

Public interest can be useful information.

It should not replace sound municipal judgment.

9.13Requests Outside City Jurisdiction

Residents frequently do not know whether something belongs to:

• Owen Sound;
• Grey County;
• Ontario;
• Canada;
• a utility;
• a private property owner;
• another agency.

They should not be expected to know.

The No Wrong Government Principle

If the City receives a reasonable request outside its jurisdiction:

1. identify the responsible body;
2. provide the correct contact;
3. transfer or refer the request where a lawful and practical process exists;
4. tell the resident what happened.

The City's service catalogue should eventually explain common jurisdictional questions.

Examples might include:

• County roads;
• social housing;
• paramedic services;
• provincial highways;
• federal navigation matters;
• utility infrastructure.

The answer should not end at:

"Not ours."

It should end at:

"Here is where it belongs."

9.14Service Requests From Councillors

Councillors will naturally receive resident concerns.

That is part of representative government.

The system should allow councillors to submit those issues into the same service process used by residents.

A councillor referral should not automatically move a routine request ahead of another resident's request.

Political access should not determine service priority.

Councillors Should Be Able to See

• whether the issue was received;
• where it was routed;
• current status;
• expected next step.

This allows councillors to advocate for residents without becoming informal dispatchers.

9.15Telephone Service

Not everyone wants to use an online portal.

Not everyone can.

Telephone access should remain part of normal City service.

The existing plan proposes modern multilingual telephone support for routine questions while preserving access to a person when judgment or assistance is needed.

The principle should be:

Technology handles repetition. People handle judgment, complexity and care.

Residents should be able to:

• report a problem;
• ask a question;
• receive a reference number;
• check status;
• reach an employee when needed.

No resident should become trapped in an automated telephone loop.

9.16In-Person Service

City Hall should remain accessible to people who need or prefer face-to-face service.

This is particularly important for:

• complex permits;
• seniors;
• residents with disabilities;
• residents without reliable internet;
• people facing language barriers;
• residents dealing with an unusual problem;
• people who simply need help understanding the process.

In-person service should increasingly function as a navigation service.

The resident should not be sent from counter to counter if the City can reasonably coordinate the response internally.

9.17Digital Service

Online service should be:

• mobile-friendly;
• accessible;
• simple;
• secure;
• easy to search;
• understandable without technical knowledge.

A resident should not need to create a permanent account merely to report litter.

Where identity is not necessary, do not require it.

Where a resident needs ongoing access to a complex file, an account may be useful.

The amount of information collected should match the service.

9.18Multilingual Service

Owen Sound serves residents and visitors with different language abilities.

The City should identify practical ways to make basic service navigation available beyond English where there is demonstrated need.

This does not require translating every internal municipal document into every language.

It may include:

• common service information;
• emergency directions;
• simple forms;
• translated web content;
• interpretation support;
• telephone assistance.

Official and statutory communication requirements must continue to be met.

The objective is simple:

A language barrier should not unnecessarily become a service barrier.

9.19Accessibility

Accessibility should be designed into municipal service from the beginning.

Residents may experience barriers involving:

• vision;
• hearing;
• mobility;
• cognition;
• language;
• literacy;
• technology;
• transportation.

Every Major Service Should Ask

Can someone complete this process:

• without a smartphone?
• without standing for a long period?
• with a screen reader?
• with limited dexterity?
• with hearing loss?
• with limited familiarity with municipal government?
• with help from a trusted support person where permitted?

Accessibility is not only about buildings.

A complicated form can be a barrier.

A telephone service with no alternative can be a barrier.

A map that cannot be read by assistive technology can be a barrier.

A meeting scheduled in an inaccessible location can be a barrier.

The service should be designed for the community that actually exists.

9.20The Service Recovery Standard

The City will sometimes make mistakes.

A request may be lost.

A deadline may be missed.

Incorrect information may be provided.

Work may be completed poorly.

When that happens, the goal should be to resolve the problem rather than defend the process.

Service Recovery Should Include

1. acknowledge the problem;
2. correct the information;
3. identify the responsible person or department;
4. provide a realistic next step;
5. record the failure where it reveals a broader service problem.

Repeated service failures should be analyzed.

If fifty people experience the same difficulty, the problem is probably not fifty residents.

It is probably the system.

9.21Complaints as Information

Complaints are operational data.

They tell the City where residents repeatedly experience friction.

The City should categorize complaints without identifying residents publicly.

Track Patterns Such As

• missed service standards;
• repeated transfer between departments;
• confusing forms;
• inconsistent information;
• repeated road locations;
• permit delays;
• inaccessible services;
• recurring billing problems.

The objective is not to create a league table of employees.

It is to identify systemic problems.

Complaint Reporting

Quarterly public reporting could include:

• number of service complaints;
• major categories;
• percentage resolved;
• average resolution time;
• systemic changes made.

9.22Service Backlogs

Backlogs should be visible internally and summarized publicly where appropriate.

A backlog that nobody measures can grow quietly for years.

For each significant work stream, management should know:

• requests awaiting action;
• oldest outstanding request;
• average age;
• normal service capacity;
• seasonal pressures;
• reasons for delay.

Backlog Reduction

Where a large backlog exists, the City should decide openly whether to:

• add temporary capacity;
• use local contractors;
• redesign the process;
• change the service standard;
• eliminate unnecessary steps;
• prioritize by risk.

A backlog is a management problem to solve, not simply a number to inherit.

9.23Root Cause Review

Repeated complaints should eventually trigger a deeper question.

For example:

If a certain section of road produces recurring potholes, repeated patching may not be the efficient answer.

If one municipal form produces constant errors, the form may be poorly designed.

If one intersection generates repeated concerns, a traffic review may be appropriate.

If the same permit issue repeatedly surprises applicants, the information provided beforehand may be inadequate.

Root Cause Standard

When a service issue exceeds a reasonable recurrence threshold, ask:

What is producing the problem?

Then determine whether fixing the cause costs less than repeatedly treating the symptom.

9.24Performance Measures

Municipal service performance should be measured carefully.

The goal is not to create numbers that encourage poor behaviour.

If staff are rewarded only for closing tickets quickly, difficult issues may be closed before they are resolved.

Use balanced measures.

Possible Measures

Acknowledgement Time

How quickly did the City confirm receipt?

Routing Time

How quickly did the issue reach the responsible service?

Completion Time

How long until completion?

First-Contact Resolution

How often was the issue resolved without repeated transfers?

Reopened Requests

How often did a supposedly completed issue require further work?

Backlog

How much unresolved work remains?

Resident Satisfaction

Was the person satisfied with the process, regardless of whether the answer was yes?

Cost

What does the service cost?

Safety

Were required standards maintained?

No single measure should determine whether a service is successful.

9.25Privacy

Service systems should collect only the information needed to provide the service.

If someone reports a pothole, the City may need:

• location;
• description;
• optional contact information.

It does not need an extensive personal profile.

Public Mapping

Where an issue appears on a public map, display:

• location;
• issue;
• status;
• general update.

Do not display:

• reporter name;
• telephone number;
• email address;
• unnecessary property information;
• personal comments that identify someone.

Residents should be able to help improve their City without becoming the public subject of the report.

9.26Public Status Categories

Use the same plain-language status categories across City services where possible.

Received

The City has the request.

Reviewing

The issue is being assessed.

Assigned

Responsibility has been determined.

Scheduled

Work has been planned.

In Progress

Work has begun.

Referred

Another government or organization is responsible.

Completed

The work is finished.

No Action Required

The City reviewed the issue and determined that no municipal work is currently required.

The reason should be provided.

Closed

The matter is resolved.

Simple language makes the system easier to understand.

9.27Service Transparency Without Public Shaming

Public tracking should improve accountability.

It should not create a platform for targeting individual municipal employees.

Performance should normally be published by:

• service;
• department;
• project;
• work stream.

Not by individual employee.

Management remains responsible for individual employee performance through proper workplace processes.

Transparency should examine systems.

It should not become public personnel management.

9.28The First-Year Service Review

During the first year, every major resident-facing City service should be reviewed.

The review should ask:

What does the resident currently experience?

Map the actual process.

How many steps are required?

Every unnecessary step deserves examination.

How many departments touch the request?

Could coordination improve?

What information is requested twice?

Eliminate duplication.

What is the actual response time?

Use data rather than assumptions.

Where do complaints occur?

Identify recurring friction.

Can the process be simplified?

Reduce unnecessary administration.

Does the City need all information currently collected?

Reduce unnecessary data.

Is an in-person option available?

Preserve human access.

Is the service accessible?

Test it with residents who face barriers.

Can residents track progress?

Provide visibility where appropriate.

9.29The New Service Rule

A new municipal service should not be launched without answering:

• Who owns it?
• Who operates it?
• What is the service standard?
• How does a resident access it?
• What information does it collect?
• What does it cost?
• What happens when demand is higher than expected?
• What is the complaint process?
• How will results be measured?
• How does the City end or redesign it if it fails?

This prevents new programs from becoming permanent simply because they were once announced.

9.30What Success Looks Like

Municipal service reform should produce practical results.

A resident should increasingly be able to say:

"I knew where to report it."

"They confirmed they had it."

"I could see what was happening."

"They told me when it would be done."

"When it was not the City's responsibility, they told me whose it was."

"I did not need to know somebody."

"I did not need to call five times."

That is success.

It is not complicated.

It requires discipline.

The Municipal Service Commitment

The City of Owen Sound should become easier to deal with.

Not because every resident will receive the answer they want.

Not because every repair can happen immediately.

Not because government can eliminate every delay.

But because the process itself can become clear.

The standard is:

Report once.

Receive confirmation.

Route it properly.

Prioritize by need and safety.

Use the right worker for the right job.

Track progress.

Protect personal information.

Tell the resident what happened.

Measure repeated problems.

Fix the cause when possible.

A municipality earns trust in hundreds of ordinary interactions long before it earns trust through one major announcement.

Do the small things well, and residents will believe us when we say we are capable of doing the large things well too.