Home › Implementation › Chapter 38
Implementation
Chapter 38The First 30 Days: Establish the Operating System
Vote on the proposals, hear the audio, read the reviews, search the whole plan.
In this chapter
- 38.1 The First-Month Rule
- 38.2 No Fake First-30-Day Accomplishments
- 38.3 Continue What Is Working
- 38.4 No Purge
- 38.5 Candidate Work Ends at the Municipal Door
- 38.6 No Campaign Database Transfer
- 38.7 Private Platform Firewall
- 38.8 No Municipal Endorsement by Transition
- 38.9 Day One Disclosure
- 38.10 Independent Conflict Advice
- 38.11 Confirm the Law in Force
- 38.12 The Mayor's First Administrative Relationship
- 38.13 Mayor-City Manager Weekly Review
- 38.14 No Backroom Council
- 38.15 Council Orientation
- 38.16 Council Does Not Have to Adopt My Whole Plan
- 38.17 Campaign Mandate Is Evidence, Not Automatic Authority
- 38.18 Establish the Commitments Register
- 38.19 Keep "Stopped" Visible
- 38.20 Keep "Missed" Visible
- 38.21 Establish the Authority Register
- 38.22 Establish the Decision Gate
- 38.23 No New Permanent Implementation Department
- 38.24 Implementation Coordination
- 38.25 One Owner Per Commitment
- 38.26 Outside Partners Do Not Own City Follow-Up
- 38.27 Financial Baseline First
- 38.28 No Efficiency Dividend Yet
- 38.29 Efficiency Baseline
- 38.30 No Tax Promise From Unverified Savings
- 38.31 Contract Register Baseline
- 38.32 Renewal Alert
- 38.33 Asset Register Baseline
- 38.34 Unknown Is a Valid Answer
- 38.35 Ten-Year Capital Snapshot
- 38.36 Establish the Unfunded Infrastructure List
- 38.37 Establish the Grant Dependency List
- 38.38 Establish the Unfunded Mandate Baseline
- 38.39 Open Books Roadmap
- 38.40 Use Before Building
- 38.41 Public Decision Register
- 38.42 Correction Log
- 38.43 Quarterly Scorecard Baseline
- 38.44 Measure Before Improving
- 38.45 Never Invent a Baseline
- 38.46 Service Catalogue
- 38.47 Do Not Promise Ten Days for Everything
- 38.48 Start-Up Desk First-Month Version
- 38.49 Before You Sign
- 38.50 Ten-Day Guarantee Needs a Baseline
- 38.51 One Business File
- 38.52 Grey County Business Handoff
- 38.53 Shop Local Listening Begins
- 38.54 Payment-Cost Evidence
- 38.55 No Penny Until Funding Is Real
- 38.56 Shop Local Directory Baseline
- 38.57 Delivery Feasibility Only
- 38.58 Community Pooling Demand Test
- 38.59 Labour Relationship Starts Immediately
- 38.60 Labour Listening Questions
- 38.61 No Workforce Restructuring in the First Month
- 38.62 New Position Freeze Is Not the Policy
- 38.63 Vacancy Review
- 38.64 Employee Better-Way Channel
- 38.65 No Suggestion Theatre
- 38.66 Local Trades Inventory
- 38.67 Procurement Forecast
- 38.68 No Local-Favourite List
- 38.69 Digital Procurement Review
- 38.70 Digital Systems Baseline
- 38.71 AI Use Baseline
- 38.72 Interim AI Rule
- 38.73 Backup and Recovery Questions
- 38.74 Emergency Preparedness Briefing
- 38.75 Emergency Contact Validation
- 38.76 Local Knowledge Map Baseline
- 38.77 Public Versus Protected Information
- 38.78 No Vulnerable-Person Map
- 38.79 Infrastructure Walk
- 38.80 Staff Explain the Asset
- 38.81 Pothole Day Is Not Day Two
- 38.82 Standing Work List Starts Immediately
- 38.83 First to Action Requirements
- 38.84 Existing Reporting Comes First
- 38.85 Housing Navigation Baseline
- 38.86 Update Federal Funding Claims
- 38.87 Home Options Guide Outline
- 38.88 Housing Approval Baseline
- 38.89 Downtown Baseline Walk
- 38.90 Downtown Quick-Fix List
- 38.91 Do Not Launch a Downtown Megaproject
- 38.92 2nd Avenue East Pilot Is Not Yet a Closure
- 38.93 Civic Square Baseline
- 38.94 Temporary First
- 38.95 River Spine Baseline
- 38.96 Owen Sound Outside Inventory
- 38.97 Enthusiast Economy Baseline
- 38.98 No Fake Enthusiast Cluster
- 38.99 RealMap Disclosure Comes Before RealMap Awareness
- 38.100 Real Estate Sign Rules Stay in Place
- 38.101 No RealMap-Driven Sign Policy
- 38.102 Seniors Independence Review
- 38.103 Free Senior Transit Business Case
- 38.104 Community Ride Partnership Request
- 38.105 Snow Brigade Design
- 38.106 Community Safety Baseline
- 38.107 No Safety Dividend Yet
- 38.108 No Pre-Set Police Headcount
- 38.109 Police Operational Independence
- 38.110 Meet Police Leadership and Governance Body
- 38.111 Fire Service Briefing
- 38.112 Fire Capital Baseline
- 38.113 Community Safety Walks
- 38.114 Report, Do Not Confront
- 38.115 Crisis Response Map
- 38.116 Grey County Supportive Services
- 38.117 Community Partner Inventory
- 38.118 Partnership Rules Before Partnership Favourites
- 38.119 Faith Partners
- 38.120 Civic Corps Design Begins
- 38.121 Youth Do Not Become Free Municipal Labour
- 38.122 Student Mapping Pilot Design
- 38.123 Youth Opportunity Map Baseline
- 38.124 Safe Information Baseline
- 38.125 Public Wi-Fi Security Review
- 38.126 Phone Reuse Feasibility
- 38.127 No Universal 911 Claim Without Verification
- 38.128 Library Partnership
- 38.129 Responsible Data Education
- 38.130 No Resident Data Locker in Month One
- 38.131 map.ca Public Infrastructure Review
- 38.132 No "Email for Life" Municipal Launch
- 38.133 Community Calendar Can Be Evaluated Separately
- 38.134 AgriHome Governance First
- 38.135 Saugeen Ojibway Nation First Contact
- 38.136 Inventory Existing SON Relationships
- 38.137 Harbour Questions Begin Immediately
- 38.138 No Harbour Acquisition Commitment
- 38.139 Grey County First-Month Meeting
- 38.140 Road Transfer Audit Starts Immediately
- 38.141 One Taxpayer Baseline
- 38.142 Hybrid Planning Decision File
- 38.143 Regional Transit Briefing
- 38.144 Ontario Authority Audit
- 38.145 Ontario Issues Register
- 38.146 Strong-Mayor Briefing
- 38.147 No Strong-Mayor Surprise
- 38.148 Federal Issues Register
- 38.149 Transport Canada Harbour Request
- 38.150 Federal Housing Verification
- 38.151 Broadband Baseline
- 38.152 East-West Crossing: Scope, Not Shovel
- 38.153 Crossing Problem Statement
- 38.154 Preserve the Option
- 38.155 No Bridge Cost Claim From Old Numbers
- 38.156 Crossing Partner Map
- 38.157 No Hospital Promise
- 38.158 Public Participation Infrastructure
- 38.159 Resident Pulse
- 38.160 Strong Vote Legal Review
- 38.161 No VoteMap Municipal Adoption by Default
- 38.162 Petition Process Review
- 38.163 Community Assembly Planning
- 38.164 Open Government Baseline Report
- 38.165 State of the City Is Not Campaign Advertising
- 38.166 Credit Existing Strengths
- 38.167 Name Problems Without Blame Theatre
- 38.168 First 30-Day Public Calendar
- 38.169 Week One: Listen and Establish Authority
- 38.170 Week Two: Establish the Baselines
- 38.171 Week Three: Build the Relationships
- 38.172 Week Four: Publish and Decide
- 38.173 The 30-Day Action Register
- 38.174 Cost Category A: Existing Work
- 38.175 Cost Category B: Small Implementation
- 38.176 Cost Category C: Study
- 38.177 Cost Category D: Pilot
- 38.178 Cost Category E: Capital
- 38.179 Legal Review Priority
- 38.180 Privacy Review Priority
- 38.181 Accessibility Review Priority
- 38.182 Consultation Is Not One Giant Town Hall
- 38.183 Do Not Ask Residents Questions Government Has Already Decided
- 38.184 Do Not Ask Everything at Once
- 38.185 Advisory Committee Review
- 38.186 Project Tables Instead of Permanent Committees
- 38.187 Public Appointments
- 38.188 Lobbying and Influence Baseline
- 38.189 Gifts and Benefits Review
- 38.190 Closed Meeting Discipline
- 38.191 Records Discipline
- 38.192 Cyber Hygiene for Council
- 38.193 No Personal Password Sharing
- 38.194 Public Communications Standard
- 38.195 No "City Is Doing" Before Council Acts
- 38.196 Proposal Status
- 38.197 Mayor's Personal Social Media
- 38.198 Public Questions
- 38.199 First 30-Day Scorecard
- 38.200 What Should Be Visible by Day 30
- 38.201 What Should Not Be Judged by Day 30
- 38.202 What Should Definitely Not Happen in the First 30 Days
- 38.203 The First Visible Wins
- 38.204 Do Not Manufacture Quick Wins
- 38.205 The First Hard Truths
- 38.206 Campaign Promise Correction Standard
- 38.207 No Shame in Removing a Bad Idea
- 38.208 But Do Not Quietly Remove It
- 38.209 The First Council Work Plan
- 38.210 Protect Council Capacity
- 38.211 Protect Staff Capacity
- 38.212 Group Related Reports
- 38.213 Use Existing Reports
- 38.214 Update Rather Than Restart
- 38.215 Professional Independence
- 38.216 Mayor Must Hear Bad News
- 38.217 No Retaliation for Evidence
- 38.218 Public Does Not Need Internal Drama
- 38.219 First 30-Day Community Tone
- 38.220 Goodwill Compact Becomes Conduct, Not Campaign Branding
- 38.221 The First-Month Public Promise
- 38.222 Day-30 Deliverables
- 38.223 Responsible Departments
- 38.224 Council Approvals
- 38.225 Outside Partners
- 38.226 Cost
- 38.227 Funding
- 38.228 Staff
- 38.229 Consultation
- 38.230 Legal Review
- 38.231 Target Date
- 38.232 Measurement
- 38.233 The Month-One Exit Test
- 38.234 No Sunk-Cost Government
- 38.235 The Month-One Rights Test
- 38.236 The Month-One Freedom Test
- 38.237 The Month-One Family Test
- 38.238 The Month-One Local Test
- 38.239 The Month-One Jurisdiction Test
- 38.240 The Month-One Evidence Test
- 38.241 The Month-One Honesty Test
- 38.242 The First 30 Days Are a Baseline, Not a Victory Lap
A four-year plan can fail in its first month.
Not because the ideas are wrong.
Because a new administration can try to begin everything at once.
Thirty-seven sections of policy should not produce thirty-seven hurried announcements.
The first month should establish the operating system that makes the next four years possible.
The objective is:
Know the authority. Know the money. Know the assets. Know the people. Know the commitments. Know the baseline. Then begin.
The first 30 days are therefore not primarily about launching programs.
They are about establishing:
- governance;
- responsibility;
- measurement;
- financial baselines;
- legal authority;
- staff relationships;
- intergovernmental relationships;
- public reporting;
- conflict safeguards;
- implementation sequencing.
Some visible improvements should happen quickly.
Many larger initiatives should deliberately not begin until their:
- business case;
- legal review;
- financial model;
- consultation;
- professional analysis;
are complete.
That restraint is part of the plan.
38.1The First-Month Rule
Every major campaign commitment should enter one of five categories.
1. Act Now
The City already has the authority, resources and evidence.
2. Prepare
The idea is sound but requires design or baseline work.
3. Ask
Another government or organization must participate.
4. Pilot
The idea needs a limited, measurable test.
5. Hold
Do not proceed until an identified legal, financial, technical or public-interest question has been answered.
This classification should be published.
Residents should be able to see:
Why isn't this promise happening yet?
and receive a real answer.
38.2No Fake First-30-Day Accomplishments
The administration should not take:
- existing staff work;
- previously approved projects;
- grants secured by an earlier Council;
and rebrand them as:
Day 12 accomplishment of the new Mayor.
If the work began previously:
Say so.
The City is one institution across elections.
38.3Continue What Is Working
The transition should begin by asking:
What good work is already underway?
Not:
What can we cancel because it belongs to the previous administration?
Existing projects should be reviewed on:
- purpose;
- cost;
- status;
- obligation;
- performance.
Continue good work.
Correct weak work.
Stop only where evidence justifies it.
38.4No Purge
A municipal election does not mean:
- staff purge;
- consultant purge;
- committee purge;
- policy purge.
Every position and project should be judged according to:
- law;
- performance;
- public value.
Not political loyalty.
38.5Candidate Work Ends at the Municipal Door
The most important transition firewall is immediate.
Campaign resources remain separate from City resources.
That includes:
- campaign email;
- campaign volunteers;
- campaign donor information;
- voter information;
- campaign websites;
- campaign advertising accounts;
- private political analytics.
Nothing becomes municipal merely because the candidate became Mayor.
38.6No Campaign Database Transfer
There should be no transfer of:
- supporter lists;
- canvassing information;
- political opinions;
- voting-intention information;
into any City system.
Ever.
The City serves:
- supporters;
- opponents;
- people who did not vote;
- people who never followed the campaign;
equally.
38.7Private Platform Firewall
The same immediate rule applies to:
- map.ca;
- RealMap.ca;
- VoteMap;
- YouthMap;
- AgriHome;
- related private or foundation initiatives.
The City does not automatically adopt any of them.
Section 33 established:
Public standard first. Platform second. Founder last.
That rule begins on Day One.
38.8No Municipal Endorsement by Transition
No City:
- logo;
- staff account;
- public data feed;
- purchasing arrangement;
- official endorsement;
should be placed into a Mayor-related platform simply because the new Mayor controls both sides of the conversation.
Any future relationship follows:
- disclosure;
- independent review;
- lawful municipal process.
38.9Day One Disclosure
On or immediately after taking office, I would file and publish an appropriate statement identifying material private interests relevant to major proposals in this plan.
That would include interests relating to:
- map.ca;
- RealMap;
- associated entities;
to the extent legally and factually applicable at the time.
The purpose is not to prejudge the legal definition of a conflict in every future matter.
It is to make the relationship visible before any municipal evaluation begins.
38.10Independent Conflict Advice
The Clerk, Integrity Commissioner and appropriate legal professionals should establish the process for handling matters where:
- statutory conflict rules;
- code-of-conduct requirements;
- broader public-trust concerns;
may apply.
The Mayor should not decide:
I think I am sufficiently independent.
Independent advice exists for exactly that reason.
38.11Confirm the Law in Force
Municipal law changes.
The first week should include a legal briefing on the rules actually in force when the new Council takes office.
That includes current:
- Municipal Act requirements;
- strong-mayor provisions;
- municipal conflict rules;
- meeting rules;
- election-period carryover issues;
- planning changes;
- other significant provincial amendments.
Do not operate from campaign-period assumptions if the law changed.
38.12The Mayor's First Administrative Relationship
One of the first formal meetings should be with the City Manager.
Not to give a list of political commands.
To establish:
- responsibilities;
- communication;
- reporting;
- implementation process.
The Mayor leads politically.
The City Manager leads administration through the municipal organizational structure.
38.13Mayor-City Manager Weekly Review
Establish a regular weekly review.
Possible standing agenda:
Council Decisions
What needs implementation?
Service Issues
What requires political awareness?
Commitments
What is on track?
Financial Risks
What changed?
Intergovernmental Files
What needs escalation?
Public Information
What needs explanation?
Decisions Required
What must come to Council?
This meeting is for coordination.
It is not an informal substitute for Council.
38.14No Backroom Council
The Mayor-City Manager meeting should never become:
where the real decisions happen.
Where Council approval is required:
Bring the decision publicly to Council.
Administrative coordination belongs in administration.
Political authority remains where law places it.
38.15Council Orientation
Within the first weeks, Council should receive practical orientation covering:
- municipal authority;
- Council-staff roles;
- finance;
- procurement;
- conflicts;
- privacy;
- accessibility;
- Indigenous relations;
- strong-mayor powers;
- closed meetings;
- planning;
- County responsibilities.
The purpose is:
Give every Council member enough shared institutional knowledge to govern effectively.
38.16Council Does Not Have to Adopt My Whole Plan
This business plan is my proposed direction.
Council remains Council.
Each major initiative requiring Council authority must still:
- come forward;
- receive professional advice;
- be debated;
- be amended;
- be approved or rejected.
Winning an election does not eliminate representative government.
38.17Campaign Mandate Is Evidence, Not Automatic Authority
A clear election result matters politically.
It does not turn every campaign paragraph into a municipal by-law.
The administration should say:
Residents elected this direction. Now we will put each part through the proper public process.
38.18Establish the Commitments Register
Create the master Four-Year Commitments Register.
Every significant promise receives:
- number;
- title;
- section;
- current status;
- responsible department;
- Council authority required;
- outside partner;
- expected cost category;
- legal review required;
- target;
- measure.
Possible status:
Not Started
Baseline
Under Review
Council Decision Required
Partner Discussion
Pilot
Active
Completed
Stopped
Missed
No disappearing promises.
38.19Keep "Stopped" Visible
If an initiative is abandoned:
Do not remove it from the register.
Mark:
Stopped
and explain:
- why;
- when;
- who decided.
A transparent plan includes ideas that did not survive contact with evidence.
38.20Keep "Missed" Visible
If an administration fails to deliver something:
Mark it:
Missed
not:
Reimagined
unless it genuinely was.
Language should not erase failure.
38.21Establish the Authority Register
Each commitment should also receive an authority classification.
M
Municipal decision.
C
Grey County involvement.
O
Ontario involvement.
F
Federal involvement.
I
Indigenous governmental or rights relationship may be relevant.
P
Other public or community partner.
Many initiatives will have several.
This simple map prevents false promises.
38.22Establish the Decision Gate
No major initiative should advance from:
idea
to
implementation
without answering:
Authority?
Cost?
Funding?
Staff?
Legal review?
Public consultation?
Accessibility?
Privacy?
Partner?
Measure?
Exit?
This becomes the municipal implementation gate.
38.23No New Permanent Implementation Department
Do not respond to a large business plan by immediately creating:
Office of the Mayor's Four-Year Plan
with a new executive, assistants and permanent bureaucracy.
Use existing:
- Council;
- City Manager;
- senior staff;
- departments;
first.
If later evidence shows dedicated capacity is required:
Apply the New Position Business Case.
38.24Implementation Coordination
The City Manager should determine the best internal mechanism for coordinating cross-department commitments.
It could be:
- existing senior leadership;
- a temporary project structure;
- another efficient model.
The Mayor proposes the accountability requirement.
Administration determines the professional structure.
38.25One Owner Per Commitment
Every commitment needs one internal owner.
Not:
Planning/Public Works/Finance/Mayor/County
as a vague collective.
One person or department owns municipal coordination.
Other departments can participate.
Accountability requires a lead.
38.26Outside Partners Do Not Own City Follow-Up
If the initiative depends on:
- Grey County;
- Ontario;
- Canada;
- SON;
- business;
- nonprofit;
a City staff lead should still own:
- the municipal request;
- correspondence;
- follow-up;
- reporting.
Otherwise:
Waiting on partner
can become a permanent status.
38.27Financial Baseline First
Before promising tax savings or dividends:
Establish the real financial baseline.
The Treasurer should prepare a concise picture of:
- operating budget;
- capital program;
- debt;
- reserves;
- major contracts;
- grants;
- liabilities;
- approved but unfunded projects;
- emerging budget pressures.
The first financial promise is:
Know where we are.
38.28No Efficiency Dividend Yet
The Efficiency Dividend begins only after a saving is:
- real;
- measured;
- net;
- verified.
There is no:
Day Five Efficiency Dividend
created by estimating that future software might save money.
The source plan promises that every measured dollar saved receives the defined treatment and that positions are not cut merely to create those savings.
Measured means measured.
38.29Efficiency Baseline
For major departments or processes selected for review:
Record:
- current cost;
- staff time;
- service level;
- backlog;
- overtime where relevant.
Without baseline:
There is no credible saving.
38.30No Tax Promise From Unverified Savings
Do not announce:
Taxes will fall by X
because staff identified possible efficiencies.
First determine:
- actual savings;
- inflation;
- contractual changes;
- capital needs;
- County levy;
- assessment changes;
- provincial obligations.
Taxes are the result of the whole budget.
38.31Contract Register Baseline
Compile the information necessary for the public Contract Register.
At minimum for material contracts where disclosure is lawful:
- supplier;
- purpose;
- term;
- value;
- renewal date.
The first month is about assembling the baseline.
Not pretending every contract can be published instantly without:
- privacy;
- confidentiality;
- legal;
review.
38.32Renewal Alert
Identify major contracts renewing in the next:
- 6 months;
- 12 months;
- 24 months.
That gives procurement time to:
- review performance;
- test market;
- plan exit.
Avoid accidental renewals.
38.33Asset Register Baseline
Combine existing:
- asset-management;
- GIS;
- finance;
- facility;
- fleet;
information into the roadmap for the public Infrastructure and Systems Index.
Do not start by rebuilding professional databases.
Start with what the City already knows.
38.34Unknown Is a Valid Answer
Where condition information is incomplete:
Publish internally:
Unknown. Assessment required.
Do not invent a condition grade to make the Index look complete.
38.35Ten-Year Capital Snapshot
Ask Finance and asset staff for a plain-language snapshot of known major:
- road;
- water;
- wastewater;
- building;
- fleet;
- technology;
capital pressures.
The public needs to see what existing assets are already asking of future budgets.
38.36Establish the Unfunded Infrastructure List
Identify major known infrastructure requirements not currently fully funded.
Fields:
- asset;
- need;
- risk;
- estimated timing;
- estimated cost range;
- funding status.
Do not hide the future bill because it is outside the current budget year.
38.37Establish the Grant Dependency List
For each significant current grant-supported program:
Record:
- funder;
- amount;
- expiry;
- staff supported;
- operating obligation.
This creates early visibility around:
What happens when outside money ends?
38.38Establish the Unfunded Mandate Baseline
Begin the Ontario Unfunded Mandate Ledger.
Do not populate it with political grievances.
Ask Finance and department heads:
Which material operating or capital costs are directly connected to mandatory provincial requirements?
Document the authority.
38.39Open Books Roadmap
The first month should produce the plan for:
- public budget dashboard;
- contracts;
- commitments;
- decisions;
- capital;
- corrections.
Do not spend enormous money building a custom transparency portal before testing whether existing City systems can publish most of it.
38.40Use Before Building
This rule applies immediately.
Before commissioning:
- new app;
- new database;
- new facility;
- new department;
ask:
What do we already own?
38.41Public Decision Register
Beginning with the new Council term, create a clear mechanism for tracking important Council decisions.
Fields can include:
- decision;
- date;
- vote where recorded;
- cost;
- responsible department;
- implementation status.
Council minutes remain the legal record.
The register makes them understandable.
38.42Correction Log
Establish the public correction standard.
If a City document materially misstates:
- fact;
- number;
- program status;
correct it visibly.
The purpose is not to preserve every typo forever.
It is to normalize:
We were wrong. Here is the corrected information.
38.43Quarterly Scorecard Baseline
The source plan promises a quarterly scorecard showing:
- successes;
- misses;
and an open playbook for other communities.
The first 30 days should define:
- measures;
- data source;
- responsible department;
- baseline date.
Do not wait until quarter end to decide what success means.
38.44Measure Before Improving
For each major initiative:
Ask:
What is the current number?
If we want:
- faster service;
- fewer pothole complaints;
- lower payment costs;
- better transit use;
we need a baseline.
38.45Never Invent a Baseline
If the City did not previously measure something:
Say:
No reliable baseline currently exists. Baseline collection begins now.
That is more credible than reconstructing an unsupported number.
38.46Service Catalogue
Within the first month, begin building the plain-language municipal Service Catalogue.
For each common service:
What is it?
Who handles it?
How do I request it?
What information is needed?
What is a reasonable response expectation?
What if it is urgent?
This becomes the foundation of Respectful City Hall and No Wrong Door.
38.47Do Not Promise Ten Days for Everything
The Start-Up Desk proposal includes a ten-business-day standard for eligible municipal business responses.
That does not mean every City service receives a ten-day deadline.
Different services require different standards.
Set them based on:
- risk;
- complexity;
- law;
- capacity.
38.48Start-Up Desk First-Month Version
The Start-Up Desk does not need a new office renovation on Day One.
Start with:
- named municipal contact;
- current process map;
- common business requirements;
- Grey County referral pathways;
- response baseline.
Then build the stronger service standard.
38.49Before You Sign
One early Start-Up Desk deliverable should be the Before You Sign checklist.
Before a prospective business signs a lease or buys a property, help them identify possible:
- zoning;
- occupancy;
- building;
- licensing;
- accessibility;
- fire;
- signage;
issues.
Make clear:
Preliminary guidance is not final legal approval.
38.50Ten-Day Guarantee Needs a Baseline
Before introducing:
answer in ten business days or eligible fee waived,
staff should identify:
- which applications qualify;
- current processing time;
- outside-agency delays;
- incomplete-application rules;
- fee authority.
Then bring the standard to Council.
38.51One Business File
Begin designing a single applicant-facing business file.
It does not require one giant database.
It requires the resident to receive:
- one clear checklist;
- coordinated responses.
38.52Grey County Business Handoff
Within the first month, meet the Grey County Business Enterprise Centre and relevant economic-development staff.
Clarify:
City
Municipal approvals.
County
Business coaching and regional support.
Other Partners
Training and specialized services.
Do not duplicate them.
38.53Shop Local Listening Begins
Do not launch the Owen Sound Penny during the first month.
First:
Meet merchants.
Ask:
- payment methods;
- payment costs;
- customer behaviour;
- delivery challenges;
- local sourcing;
- platform frustrations.
The merchant should help define the problem.
38.54Payment-Cost Evidence
The original Shop Local concept assumed significant differences between card and debit payment costs.
The first month should collect current local evidence from willing businesses.
No merchant should be required to disclose confidential commercial information publicly.
Aggregate where appropriate.
38.55No Penny Until Funding Is Real
The Owen Sound Penny does not launch until the program identifies a lawful, explicit funding source.
A merchant keeping payment-cost savings does not automatically create a municipal reward pool.
That correction remains non-negotiable.
38.56Shop Local Directory Baseline
Inventory existing:
- City;
- County;
- BIA;
- Chamber;
- private;
business directories before building another.
Ask:
What is missing?
Then fill the gap.
38.57Delivery Feasibility Only
The Shop Local delivery proposal enters:
Prepare
not:
Act Now.
First review:
- municipal authority;
- insurance;
- collective agreements;
- custody;
- private courier competition;
- route economics.
The City does not begin placing private parcels into municipal vehicles because the idea sounds efficient.
38.58Community Pooling Demand Test
The first month can begin identifying a small number of categories where:
- households;
- businesses;
may benefit from pooled purchasing.
No City inventory.
No warehouse.
No municipal wholesale operation.
Measure demand first.
38.59Labour Relationship Starts Immediately
One of the first formal relationship-building actions should be to meet the City's bargaining units and employee representatives.
The source proposal explicitly calls for labour partnership, root-cause work and no replacement-worker approach.
The first meeting is for listening.
38.60Labour Listening Questions
Ask:
What wastes your time?
What process causes repeat frustration?
Where are staffing pressures highest?
What equipment is failing?
What creates unnecessary overtime?
What does management misunderstand?
What could make service better for residents?
Do not ask only:
Where can we cut?
38.61No Workforce Restructuring in the First Month
Except where an existing urgent operational matter requires lawful action:
Do not begin the term with:
- layoff list;
- outsourcing list;
- department elimination.
First understand the work.
38.62New Position Freeze Is Not the Policy
Likewise, do not announce:
No new positions for four years.
Some positions may be justified.
The policy is:
Every new position requires a complete business case.
38.63Vacancy Review
For significant current vacancies:
Ask:
- why position exists;
- workload;
- service impact;
- alternatives.
Do not automatically:
- fill;
- delete.
Review.
38.64Employee Better-Way Channel
Establish a simple route for staff to suggest:
- process improvements;
- cost savings;
- equipment changes;
- resident-service improvements.
Employees closest to the work often see problems first.
38.65No Suggestion Theatre
If employees submit ideas:
Respond.
Possible outcome:
Accepted
Testing
Not Practical
Already Planned
Requires Funding
Silence destroys participation.
38.66Local Trades Inventory
Begin building the requirements for the Local Vendor Gateway.
Before creating a Quick-Quote Roster:
Review current:
- procurement policy;
- trade obligations;
- insurance;
- qualification rules.
The objective is open access.
Not an insider contractor list.
38.67Procurement Forecast
Identify major purchasing opportunities expected in the next 12 months.
Where lawful:
Publish enough advance information that small businesses have time to prepare.
38.68No Local-Favourite List
A business does not receive municipal preference because:
- owner supported campaign;
- business is locally popular;
- Mayor knows them.
Local opportunity requires transparent rules.
38.69Digital Procurement Review
Ask IT, Finance and procurement staff:
Which major software contracts renew soon?
For each:
- cost;
- vendor;
- export capability;
- dependency;
- alternative;
- renewal date.
Begin the Digital Exit Test.
38.70Digital Systems Baseline
Start the Digital Systems Index.
Classify:
- critical;
- important;
- routine.
Do not publish cybersecurity details.
The first goal is knowing what the City relies upon.
38.71AI Use Baseline
Ask departments to identify meaningful current AI use.
Focus on systems affecting:
- resident information;
- decisions;
- sensitive records;
- operations.
Do not create bureaucracy around ordinary spelling tools.
38.72Interim AI Rule
Until a fuller policy is approved:
Employees should receive a clear interim reminder:
Do not place protected municipal or resident information into unapproved public AI systems.
The exact administrative policy should be developed professionally.
38.73Backup and Recovery Questions
For critical digital systems, the first month should establish:
Backup exists?
Restore tested?
Vendor dependency?
Manual continuity?
Do not run reckless tests on production systems merely to meet a campaign date.
Plan them.
38.74Emergency Preparedness Briefing
The Mayor and Council should receive a practical emergency-management briefing.
Cover:
- municipal emergency plan;
- roles;
- command;
- County relationships;
- provincial contacts;
- continuity.
The Mayor should know what not to do in an emergency as well as what to do.
38.75Emergency Contact Validation
Staff should verify that important:
- City;
- County;
- utility;
- provincial;
- federal;
emergency contacts are current.
A contact list from three years ago is not preparedness.
38.76Local Knowledge Map Baseline
Inventory existing public:
- GIS;
- trails;
- facilities;
- accessibility;
- emergency-information;
layers.
Do not create a new map until we understand what already exists.
38.77Public Versus Protected Information
During the first month, establish the principle:
Public
Information making residents more capable.
Protected
Information whose release could increase:
- security;
- privacy;
risk.
This determines how the Infrastructure Index and Local Knowledge Map develop.
38.78No Vulnerable-Person Map
Do not begin:
- senior registry;
- disability map;
- unhoused-person map;
- medically vulnerable household map;
as part of emergency planning.
Map services and resources.
Protect individuals.
38.79Infrastructure Walk
The Mayor should spend part of the first month outside City Hall with relevant staff.
Visit representative:
- roads;
- water facilities;
- parks;
- downtown assets;
- public buildings;
- waterfront;
- works facilities.
The purpose is learning.
Not staging a daily photo opportunity.
38.80Staff Explain the Asset
At each location ask:
What does this do?
What condition is it in?
What fails most often?
What does replacement cost?
What maintenance is deferred?
What would you fix first?
Frontline knowledge becomes part of leadership education.
38.81Pothole Day Is Not Day Two
The original initiative proposes organized civic work days and a standing work list.
Do not schedule a campaign-style Pothole Day before:
- safety;
- labour;
- insurance;
- task classification;
are established.
Build the framework first.
38.82Standing Work List Starts Immediately
What can begin quickly is the internal work-list structure.
Identify recurring categories:
- potholes;
- graffiti;
- litter;
- low lighting;
- trail issues;
- damaged signs;
- icy walks.
Then ask:
Which are professional work?
Which can be batched?
Which could safely involve community participation later?
38.83First to Action Requirements
Before launching a public issue map:
Define:
- intake;
- routing;
- privacy;
- duplicate reports;
- emergencies;
- status;
- closure.
A map with no backend process makes government look modern while making service worse.
38.84Existing Reporting Comes First
If the City already has an effective reporting mechanism:
Improve or integrate it.
Do not replace it solely because the campaign proposed a different interface.
38.85Housing Navigation Baseline
In the first month:
Map the current journey for someone asking:
Can I build a basement suite or garden suite?
Record:
- City steps;
- County steps;
- Ontario requirements;
- possible federal financing;
- common confusion.
This becomes the Housing Navigation Desk baseline.
38.86Update Federal Funding Claims
The housing guide should not repeat campaign funding claims without current verification.
If a federal suite-financing program is:
- active;
- delayed;
- changed;
- closed;
say so accurately.
The guide should carry a:
Last Verified
date.
38.87Home Options Guide Outline
Begin the public guide covering:
- secondary suites;
- garden homes;
- multigenerational options;
- downsizing;
- accessibility considerations;
- upper-floor housing.
Do not imply every property qualifies.
38.88Housing Approval Baseline
Record:
- applications;
- approvals;
- processing time;
- projects actually built;
where reliable data exists.
The four-year plan will measure:
Built
separately from:
Approved.
38.89Downtown Baseline Walk
In the first month, conduct a structured downtown walk involving appropriate:
- staff;
- businesses;
- residents;
- accessibility voices;
- safety partners.
Record:
- lighting;
- garbage;
- graffiti;
- sidewalks;
- vacant storefronts;
- washrooms;
- loading;
- accessibility;
- public-space conditions.
No shaming individual properties.
38.90Downtown Quick-Fix List
Separate:
Quick maintenance
from
Capital project
from
private-property issue
from
County/social-service issue
from
enforcement matter
This allows easy problems to move quickly.
38.91Do Not Launch a Downtown Megaproject
The first-month downtown priority is:
clean, maintain, understand, coordinate.
Not:
announce $25 million revitalization.
Maintenance before redesign.
38.922nd Avenue East Pilot Is Not Yet a Closure
During the first month:
Define the proposed pilot area.
Then begin:
- traffic review;
- business consultation;
- resident consultation;
- emergency access analysis;
- loading analysis;
- transit review;
- accessibility review.
No closure date should be announced before the pilot can pass those tests.
38.93Civic Square Baseline
Inventory what the existing public space already has:
- electricity;
- washrooms;
- seating;
- shade;
- stage capability;
- storage;
- booking;
- accessibility.
Use before building.
38.94Temporary First
If quick Civic Square improvements are appropriate:
Prefer temporary or modular:
- seating;
- planters;
- shade;
- games;
where budgets and operations permit.
Observe use.
Then design permanent investment.
38.95River Spine Baseline
Begin the Missing-Link Map.
Identify:
- public trail;
- private interruption;
- difficult crossing;
- accessibility issue;
- missing connection.
Do not promise continuous waterfront access across property the City does not own.
38.96Owen Sound Outside Inventory
Inventory:
- outdoor programs;
- equipment-rental opportunities;
- clubs;
- businesses;
- trails;
- beginner programs;
- adaptive opportunities.
Section 19 should begin with discovery.
Not municipal purchase of hundreds of pieces of recreation equipment.
38.97Enthusiast Economy Baseline
Identify local clusters around:
- cycling;
- paddling;
- fishing;
- marine activity;
- running;
- hiking;
- skating;
- hockey;
- makers;
- automotive;
- music;
- photography;
- gardening;
- other real communities.
Then invite people to tell us what is missing.
38.98No Fake Enthusiast Cluster
Do not declare:
Owen Sound is Canada's capital of X
because someone made a logo.
Find the communities that already exist.
Build around authenticity.
38.99RealMap Disclosure Comes Before RealMap Awareness
No official City RealMap promotion in the first 30 days.
First:
- ownership disclosure;
- legal advice;
- conflict review;
- privacy review;
- accessibility review;
- technical review;
- independent valuation if transfer is proposed.
Public standard first.
38.100Real Estate Sign Rules Stay in Place
The first month should not change residential sign sizes.
Instead:
- review existing by-law enforcement;
- establish sign baseline;
- identify stale or non-compliant signs;
- begin professional and public consultation planning.
The four-year transition remains evidence-gated.
38.101No RealMap-Driven Sign Policy
The City should record formally:
No future sign regulation may require use of RealMap or any other proprietary platform.
The sign policy must make sense if RealMap disappears.
38.102Seniors Independence Review
Begin the Seniors Independence Review.
Ask about:
- transit;
- walking;
- benches;
- winter;
- housing;
- technology;
- recreation;
- information.
Do not begin with:
What services can government give seniors?
Begin:
What prevents independence?
38.103Free Senior Transit Business Case
Immediately obtain the transit baseline needed to assess:
- current senior ridership;
- fare revenue;
- spare capacity;
- operating implications.
No permanent free-fare announcement until Council sees the cost.
38.104Community Ride Partnership Request
Bring the seniors' scheduled-ride concept to:
- Grey County;
- community-paramedicine or relevant health partners;
for feasibility discussion.
The source proposal envisions free senior fares and scheduled rides with a nurse or community paramedic aboard.
The City cannot assign those professionals itself.
38.105Snow Brigade Design
Because winter may arrive near the beginning of the term, the Snow Brigade concept may require quicker work.
Define:
- eligible tasks;
- private-property limits;
- volunteer safety;
- youth rules;
- insurance;
- request process.
Do not create a public map of seniors needing assistance.
38.106Community Safety Baseline
Before discussing police savings:
Establish a multi-year public-safety baseline.
With the appropriate services and governance bodies, gather:
- calls for service;
- priority response performance;
- overtime;
- vacancies;
- major incident trends;
- repeat locations;
- collisions;
- public perceptions;
- fire demand;
- by-law demand.
Use professionally appropriate measures.
38.107No Safety Dividend Yet
The original proposal states:
As prevention lowers police calls, officers shift toward community and youth work, and savings come only through voluntary retirement with the payback published. Built with the chief and the association; no officer is ever laid off.
That means the Safety Dividend cannot begin with:
We need to cut police staffing.
It begins with prevention and workload evidence.
38.108No Pre-Set Police Headcount
The administration should make no first-month announcement that:
- X officers;
- X positions;
will disappear.
First evaluate:
- service demand;
- legal obligations;
- safety;
- workload;
- overtime;
- vacancies;
- alternative-response opportunities.
38.109Police Operational Independence
Council and Mayor must respect the statutory governance of policing.
The Mayor does not direct:
- investigations;
- arrests;
- individual deployment decisions.
The municipal role is:
- governance;
- budget;
- public policy;
within the applicable legal structure.
38.110Meet Police Leadership and Governance Body
The first month should include briefings with the appropriate:
- police leadership;
- police governance representatives.
Ask:
What is driving workload?
What calls are growing?
Which calls could another service handle better?
Where are repeat problems?
What prevention work is already occurring?
Listen before proposing staffing changes.
38.111Fire Service Briefing
Meet fire leadership.
Review:
- service demand;
- prevention;
- inspections;
- staffing;
- training;
- apparatus;
- facility;
- capital replacement;
- mutual aid.
Fire is not merely another budget line.
It is professional emergency capacity.
38.112Fire Capital Baseline
Identify major known future requirements:
- apparatus;
- station;
- equipment;
- training.
Include them in the Infrastructure Index.
Do not discover a major replacement the year the vehicle fails.
38.113Community Safety Walks
Conduct structured safety walks in:
- downtown;
- selected neighbourhoods;
with appropriate:
- residents;
- business;
- police;
- fire;
- by-law;
- engineering;
- accessibility;
participants.
Focus on:
- lighting;
- sightlines;
- crossings;
- maintenance;
- public-space function.
No vigilantism.
38.114Report, Do Not Confront
Any neighbourhood participation program should explicitly say:
Observe and report. Do not confront.
Residents are not auxiliary police unless formally appointed within a lawful professional structure.
38.115Crisis Response Map
Identify which organizations currently handle:
- mental-health crisis;
- homelessness outreach;
- addiction;
- emergency shelter;
- paramedic care;
- police;
- by-law.
The goal is:
right response, right service.
Do not create a new crisis team before understanding current services.
38.116Grey County Supportive Services
Meet the County teams whose work intersects with:
- homelessness;
- outreach;
- housing;
- paramedicine.
The City should understand what already exists before designing another response.
38.117Community Partner Inventory
Section 29 requires a complete view of community capacity.
Begin an inventory of:
- charities;
- faith communities;
- service clubs;
- sports organizations;
- cultural groups;
- neighbourhood groups;
- volunteer organizations;
- institutions.
Do not turn the list into City endorsement.
It is a relationship map.
38.118Partnership Rules Before Partnership Favourites
Before awarding special access or funding:
Establish common principles concerning:
- eligibility;
- public purpose;
- cost;
- insurance;
- accountability;
- accessibility;
- exit.
The new Mayor should not begin by favouring organizations they already know.
38.119Faith Partners
Meet faith communities as community partners where relevant.
Maintain the rule:
Same public criteria regardless of faith.
A church does not receive municipal preference because the Mayor shares its beliefs.
A secular organization is not excluded because it does not.
38.120Civic Corps Design Begins
The Civic Corps should enter:
Prepare
during the first month.
Define:
- age groups;
- employment versus volunteer roles;
- supervision;
- insurance;
- police checks where legally or practically required;
- workplace safety;
- school/co-op possibilities;
- privacy;
- task limits.
38.121Youth Do Not Become Free Municipal Labour
The Civic Corps must not become:
City work performed by teenagers for exposure.
Appropriate paid work should be paid.
Volunteer work should be genuinely voluntary and suitable.
Professional work remains professional.
38.122Student Mapping Pilot Design
One early Civic Corps pilot may involve public-information mapping.
The rule remains:
Students Gather. Staff Validate. Public Uses.
Students do not certify:
- infrastructure;
- accessibility;
- safety;
- property condition.
38.123Youth Opportunity Map Baseline
Inventory current:
- jobs;
- co-op;
- clubs;
- recreation;
- volunteering;
- training.
Do not create youth profiles.
Map opportunities.
38.124Safe Information Baseline
Before promising universal public connectivity:
Inventory current:
- municipal Wi-Fi;
- library access;
- public computers;
- broadband availability;
- affordability programs;
- device-support organizations.
Define the gap first.
38.125Public Wi-Fi Security Review
Any expansion of public Wi-Fi should include professional review of:
- network separation;
- acceptable use;
- privacy;
- security;
- operating cost.
Free does not mean unmanaged.
38.126Phone Reuse Feasibility
The source proposal suggests recycled phones for residents without one.
Before launching:
Determine:
- device availability;
- battery safety;
- factory reset;
- account removal;
- e-waste;
- distribution;
- support;
- emergency-calling functionality.
Do not promise technical behaviour that has not been tested.
38.127No Universal 911 Claim Without Verification
A public safety claim concerning:
every charged handset reaches 911
must be technically and legally verified for the actual devices and network conditions before the City publishes it.
Emergency communication is not a place for assumptions.
38.128Library Partnership
Meet the public library regarding:
- digital literacy;
- responsible data stewardship;
- device support;
- public access.
Use existing trusted community capacity before creating a new municipal digital-literacy office.
38.129Responsible Data Education
Begin designing plain-language workshops around:
- backups;
- passwords;
- scams;
- photo preservation;
- document organization;
- privacy.
The original proposal specifically emphasizes helping families preserve photos, records and history.
That can begin without a complicated data locker.
38.130No Resident Data Locker in Month One
The data-locker concept enters:
Hold / Study.
It requires substantially more:
- privacy;
- cybersecurity;
- governance;
- financial;
work.
Teach people to control their information before asking them to place more of it into a new system.
38.131map.ca Public Infrastructure Review
The first 30 days should implement the Section 33 sequence.
1. Disclosure
Ownership and interests.
2. Public Problem
What civic-information problem are we solving?
3. Open Standard
What requirements should any solution meet?
4. Independent Review
Legal, financial, technical, privacy and accessibility.
5. Alternatives
What else could solve the same problem?
No municipal adoption before those steps.
38.132No "Email for Life" Municipal Launch
Do not launch a municipal lifetime-email promise.
First determine whether a sustainable:
- civic alias;
- portable identity;
model is technically, financially and legally viable.
Ambition does not substitute for continuity.
38.133Community Calendar Can Be Evaluated Separately
The calendar concept may be much lower risk than:
- civic identity;
- resident data locker.
Therefore:
Assess it as a separate module.
Do not require adoption of the entire map.ca ecosystem to test one useful public standard.
38.134AgriHome Governance First
The source proposes AgriHome Canada as free, open and bilingual.
During the first month:
Determine:
- ownership;
- public purpose;
- content authority;
- translation process;
- conflict;
- operating model.
No municipal national platform launch.
38.135Saugeen Ojibway Nation First Contact
Within the first month:
Send an appropriate leadership request for a meeting with Saugeen Ojibway Nation.
The first communication should not say:
Here is our proposed agreement.
It should say:
We would like to strengthen the relationship and listen to what would be useful.
38.136Inventory Existing SON Relationships
Before the meeting:
Staff should brief Council on:
- existing contacts;
- joint projects;
- correspondence;
- current commitments.
Do not make SON repeat history City Hall already possesses.
38.137Harbour Questions Begin Immediately
Prepare the federal harbour question file.
Ask:
- what Canada owns;
- what is available for transfer;
- asset condition;
- liabilities;
- dredging;
- environmental issues;
- current users;
- revenue;
- transfer funding.
The source explicitly calls for pressing the federal government for harbour answers.
Now the questions become specific.
38.138No Harbour Acquisition Commitment
Day 30 should not end with:
Owen Sound will buy the harbour.
It should end with:
Owen Sound has asked the right questions and knows what information remains missing.
38.139Grey County First-Month Meeting
The Mayor, Deputy Mayor and appropriate senior City staff should receive a complete Grey County briefing.
Priority files include:
- road transfers;
- planning-service changes;
- housing;
- homelessness;
- paramedics;
- transit;
- economic development;
- shared infrastructure.
38.140Road Transfer Audit Starts Immediately
Because the road-transfer implementation may occur early in the term:
Confirm:
- legal transfer date;
- road segments;
- condition;
- funding;
- winter operations;
- fleet;
- permits;
- lifecycle costs.
This cannot wait until Year Two planning.
38.141One Taxpayer Baseline
For road transfers and other shared services:
Establish:
- current City cost;
- current County cost;
- expected future City cost;
- County levy effect where measurable.
No cost shifting disguised as saving.
38.142Hybrid Planning Decision File
Obtain the current Grey County planning proposal.
Evaluate:
- cost;
- staffing;
- local knowledge;
- applicant experience;
- accountability;
- exit.
Do not enter the term assuming:
- join;
- reject.
Evidence first.
38.143Regional Transit Briefing
Obtain the current status of regional transit planning.
Identify Owen Sound priorities:
- connection points;
- schedule integration;
- accessible transfers;
- employment;
- healthcare;
- senior travel.
Submit them early enough to matter.
38.144Ontario Authority Audit
For every major campaign commitment:
Ask:
Does Ontario need to act?
If yes:
Identify the exact:
- ministry;
- statute;
- regulation;
- approval;
- funding program.
38.145Ontario Issues Register
Launch the internal version immediately.
Priority areas may include:
- strong-mayor governance;
- planning;
- infrastructure;
- environmental processes;
- healthcare advocacy;
- municipal pilots.
Publish the public version once verified.
38.146Strong-Mayor Briefing
Because provincial law can change, the Clerk and solicitor should explain:
- current powers;
- current mandatory duties;
- delegation;
- written-record requirements;
- election-transition rules.
Then this administration can determine how the voluntary Strong Vote restraints operate inside the law.
38.147No Strong-Mayor Surprise
Before using a significant extraordinary mayoral power:
Publish or provide the legally required written record and explain:
- authority;
- purpose;
- reason.
Where advance public discussion is lawful and practical:
Use it.
38.148Federal Issues Register
Create the federal counterpart.
Initial major files:
- harbour;
- bridge navigation;
- infrastructure funding;
- housing programs;
- broadband;
- open public infrastructure.
38.149Transport Canada Harbour Request
Within the first month:
Request a formal working meeting concerning:
- current federal harbour ownership;
- Ports Asset Transfer Program status;
- due-diligence information.
This is one of the clearest direct federal responsibilities in the plan.
38.150Federal Housing Verification
Assign responsibility for ensuring the Housing Desk does not repeat stale federal financing claims.
Every federal program should have:
- official source;
- current status;
- last verified date.
38.151Broadband Baseline
Do not apply for broadband funding until the City knows whether the problem is:
- physical coverage;
- reliability;
- affordability;
- device access;
- digital literacy.
Different problem.
Different solution.
38.152East-West Crossing: Scope, Not Shovel
The original plan calls the proposed crossing the signature senior-government ask, with the numbers case built in Year One.
The first 30 days should therefore do only the groundwork.
38.153Crossing Problem Statement
Prepare a short scoping report answering:
What transportation problem are we trying to solve?
Which existing crossings already serve east-west travel?
What current corridor is protected?
Which past studies exist?
What information has become outdated?
Which agencies would be involved?
What Year One study is actually needed?
Do not begin with:
Where should we build the bridge?
Begin:
Is another connection required?
38.154Preserve the Option
Confirm that no immediate municipal decision inadvertently compromises currently protected potential crossing corridors without Council understanding the consequence.
Preservation is not construction approval.
It keeps future options open.
38.155No Bridge Cost Claim From Old Numbers
Past cost estimates are historical information.
Do not turn them into current construction budgets.
Any new feasibility work requires:
- current dollars;
- current engineering;
- current environmental process.
38.156Crossing Partner Map
Identify future roles for:
- Owen Sound;
- Grey County;
- Ontario;
- Transport Canada;
- Fisheries and Oceans Canada where applicable;
- conservation authority;
- SON;
- property owners.
This is a multi-jurisdiction project if it ever proceeds.
38.157No Hospital Promise
The first-month scope should explicitly separate:
- bridge case;
- any future hospital or medical-centre planning.
The City does not control hospital relocation.
38.158Public Participation Infrastructure
Begin designing the Resident Government system.
The first task is not launching hundreds of online polls.
It is defining:
- what residents can influence;
- verification;
- privacy;
- accessibility;
- paper/phone alternatives;
- legal effect.
38.159Resident Pulse
A low-risk first step may be a recurring Resident Pulse on ordinary municipal-service questions.
Before launch:
Define how results will be described.
A voluntary online response is:
input from participants
not necessarily:
the opinion of all Owen Sound residents.
38.160Strong Vote Legal Review
Before VoteMap or another voting tool is connected to mayoral decision rules:
Complete:
- election-law;
- privacy;
- identity;
- accessibility;
- statistical;
- governance;
review.
Do not treat an online poll as equivalent to a statutory ballot.
38.161No VoteMap Municipal Adoption by Default
The same private-platform firewall applies.
The City can adopt:
- Strong Vote principles;
- public-consultation standards;
without adopting VoteMap technology.
38.162Petition Process Review
Review current resident:
- petition;
- delegation;
- correspondence;
processes.
Ask:
Is there an unnecessary barrier?
Then improve within law.
38.163Community Assembly Planning
The annual Mayor's Community Assembly should be scheduled conceptually in the first 30 days.
Do not hold one before the administration possesses enough baseline information to answer useful questions.
Plan it for substance.
38.164Open Government Baseline Report
By approximately Day 30, publish a first State of the City Baseline.
Not a celebratory speech.
A factual starting point.
Possible headings:
Finance
Where we are.
Infrastructure
What we know.
Service
What residents currently experience.
Workforce
Key capacity issues.
Major Projects
Current status.
Intergovernmental
Major external files.
Risks
What requires attention.
Unknowns
What we still need to learn.
38.165State of the City Is Not Campaign Advertising
The baseline should not say:
The old administration left a disaster
unless the evidence actually supports that extraordinary statement.
Nor:
Everything is great
because criticism feels uncomfortable.
Describe the institution accurately.
38.166Credit Existing Strengths
If the City has:
- strong reserves;
- competent staff;
- successful projects;
- good services;
say so.
The business plan is about improvement.
Not manufacturing crisis.
38.167Name Problems Without Blame Theatre
If a system is failing:
Identify:
- problem;
- cause where known;
- action.
Do not automatically attach a person's name.
Focus on correction.
38.168First 30-Day Public Calendar
Publish a simple implementation calendar.
Residents should be able to see:
Week One
Governance and briefings.
Week Two
Baselines and partner meetings.
Week Three
Public walks, issue mapping and registers.
Week Four
First baseline report and Council implementation decisions.
The exact meeting calendar will depend on the actual Council schedule.
38.169Week One: Listen and Establish Authority
The first seven days should focus primarily on:
- oath and legal responsibilities;
- City Manager;
- Clerk;
- Treasurer;
- department heads;
- conflict disclosure;
- Council orientation;
- current emergencies;
- existing commitments.
Do not arrive pretending the campaign already taught us everything.
38.170Week Two: Establish the Baselines
The second week should focus on:
- finances;
- assets;
- contracts;
- workforce;
- services;
- safety;
- housing;
- downtown;
- digital systems.
This turns campaign problems into measurable municipal problems.
38.171Week Three: Build the Relationships
Priority external meetings:
- SON;
- Grey County;
- local MP;
- local MPP;
- Transport Canada harbour officials as scheduling allows;
- major community partners;
- business support partners;
- labour;
- police/fire governance and leadership.
Not every organization needs a Mayor meeting within 30 days.
Prioritize relationships tied directly to implementation.
38.172Week Four: Publish and Decide
By the fourth week:
Bring the first necessary governance and implementation reports to Council.
Publish:
- baseline;
- commitment register;
- authority map;
- intergovernmental registers;
- major unknowns;
- first 100-day priorities.
The public should know what happens next.
38.173The 30-Day Action Register
Every first-month action should receive the same implementation fields.
Commitment
What are we doing?
Lead
Who owns it?
Council
Does Council approval apply?
Partner
Who else is needed?
Cost
Existing staff, small operating cost, study cost or major future capital.
Funding
Known source or not yet identified.
Legal
Review required?
Consultation
Who needs to be heard?
Day-30 Evidence
What proves the action occurred?
This becomes the model for every later implementation section.
38.174Cost Category A: Existing Work
Some first-month activities should be possible largely through:
- existing staff;
- existing meeting structure.
Examples:
- briefings;
- registers;
- inventories.
That does not mean they cost nothing.
Staff time is still a public resource.
38.175Cost Category B: Small Implementation
Some actions may require modest amounts for:
- accessibility support;
- professional review;
- temporary equipment;
- public consultation.
Use existing approved authorities where lawful.
Otherwise bring the expense to Council.
38.176Cost Category C: Study
Large proposals may require professional studies.
Examples:
- crossing;
- harbour;
- major digital transfer;
- transit;
- road liabilities.
No study should be commissioned merely because it was mentioned in the campaign.
Define:
- question;
- deliverable;
- cost;
- decision it will inform.
38.177Cost Category D: Pilot
Pilot budgets should be:
- capped;
- time-limited;
- measured.
A pilot without a stopping rule is an early permanent program.
38.178Cost Category E: Capital
The first 30 days should authorize no new major capital solely because it appears in this plan unless:
- existing process;
- emergency;
- previous commitment;
- extraordinary evidence;
requires action.
Most large capital belongs in the normal capital-planning cycle.
38.179Legal Review Priority
Not every idea requires outside counsel.
Use legal resources proportionately.
Highest early priorities include:
- Mayor-related platform conflicts;
- strong-mayor rules;
- procurement;
- major property transfer;
- harbour;
- new regulatory proposals;
- rights-sensitive initiatives.
Routine work remains routine.
38.180Privacy Review Priority
Highest early privacy priorities include:
- VoteMap;
- map.ca;
- resident accounts;
- safety data;
- youth data;
- service-request maps;
- potential data locker.
A bench inventory is not a high-risk privacy project.
Apply proportionality.
38.181Accessibility Review Priority
Accessibility belongs in:
- public dashboards;
- maps;
- consultations;
- transit;
- trails;
- Civic Square;
- 2nd Avenue pilot;
- housing information.
Do not wait until Year Four to test whether the public can use what we built.
38.182Consultation Is Not One Giant Town Hall
Different initiatives need different people.
Downtown Street Pilot
Affected businesses and residents plus wider users.
Transit
Riders and non-riders.
Seniors
Older residents and caregivers.
Procurement
Vendors and staff.
Youth
Young people.
SON
Government-to-government relationship.
Use the right consultation.
38.183Do Not Ask Residents Questions Government Has Already Decided
If law requires:
- compliance;
do not hold a fake vote asking whether the City should comply.
Consult on:
- implementation;
- local choices.
Participation should be meaningful.
38.184Do Not Ask Everything at Once
A new administration can exhaust residents by launching:
- 20 surveys;
- 10 town halls;
- 8 committees;
in one month.
Sequence consultation.
Respect people's time.
38.185Advisory Committee Review
Inventory existing committees and boards.
Ask:
- statutory?
- useful?
- duplicative?
- inactive?
- missing representation?
Do not abolish or create committees simply to signal change.
38.186Project Tables Instead of Permanent Committees
For some initiatives:
A short-term working table may be better than another permanent advisory body.
Define:
- task;
- membership;
- end date.
When task is complete:
End the table.
38.187Public Appointments
Where Council makes appointments:
Use:
- transparent;
- lawful;
process.
No campaign reward appointments.
38.188Lobbying and Influence Baseline
Begin designing the Influence Register for major matters.
Government should know when major:
- developers;
- unions;
- corporations;
- advocacy organizations;
are seeking decisions.
Ordinary resident conversation should not become burdensome lobbying registration.
Design proportionately.
38.189Gifts and Benefits Review
Ensure Council understands current:
- gift;
- benefit;
- hospitality;
rules.
The new administration should begin with clarity.
Not after the first controversy.
38.190Closed Meeting Discipline
Review closed-meeting rules with Council.
The standard remains:
Closed because the law and subject require confidentiality, never because the conversation is politically uncomfortable.
38.191Records Discipline
Council members should understand that municipal business conducted through:
- email;
- messaging;
- documents;
may create municipal records.
Do not use private channels to evade public-record responsibilities.
38.192Cyber Hygiene for Council
Councillors and Mayor should receive practical security guidance covering:
- accounts;
- passwords;
- phishing;
- devices;
- protected documents.
Political officeholders can be attractive targets.
38.193No Personal Password Sharing
No City system should depend upon:
I gave my password to my assistant.
Use proper access.
Institutional accounts.
Role-based permissions.
38.194Public Communications Standard
Beginning immediately:
Official communications should distinguish:
City Fact
Council Decision
Mayor's Opinion
Proposal
Under Study
Approved
Do not blur them.
38.195No "City Is Doing" Before Council Acts
If I propose:
free senior transit,
official communications should not say:
The City is introducing free senior transit
before Council approves it.
Language matters.
38.196Proposal Status
Every major initiative page should show:
Campaign Proposal
Staff Review
Council Consideration
Approved
Pilot
Operating
Residents should not need to guess.
38.197Mayor's Personal Social Media
Personal political communication should remain distinguishable from official City communication.
The exact practical arrangement should comply with municipal policies and records obligations.
No use of public staff to operate a campaign channel.
38.198Public Questions
Create a visible route where residents can ask:
What happened to promise X?
The answer should point to the Commitment Register.
That may reduce the need for endless individual correspondence.
38.199First 30-Day Scorecard
At Day 30, report:
Governance
- Council orientation complete?
- authority register created?
- commitments register created?
Finance
- baseline complete?
- grant dependencies mapped?
- major renewals identified?
Service
- service catalogue underway?
- common handoff failures identified?
Workforce
- labour meetings held?
- vacancies reviewed?
Infrastructure
- asset baseline established?
- road-transfer audit underway?
Downtown
- baseline walk complete?
- quick-fix list produced?
Housing
- navigation process mapped?
Business
- Start-Up Desk baseline complete?
- merchant meetings started?
Safety
- workload baseline underway?
- no unsupported staffing cuts booked?
Seniors
- transit baseline complete?
- County ride discussion initiated?
Youth
- Civic Corps governance design underway?
Digital
- systems inventory started?
- Mayor-related platform firewall active?
SON
- leadership outreach completed?
Grey County
- major joint files reviewed?
Ontario
- authority and issues registers established?
Canada
- harbour request submitted?
Transparency
- State of City baseline published?
This is the first accountability checkpoint.
38.200What Should Be Visible by Day 30
A resident should be able to see:
- what the administration promised;
- which level of government controls each promise;
- which promises are being acted on;
- which require studies;
- which require outside partners;
- which have legal concerns;
- which are on hold;
- where the money stands;
- which large liabilities are emerging;
- what happens in the next 70 days.
That is a productive first month.
38.201What Should Not Be Judged by Day 30
It would be unreasonable to expect:
- lower crime;
- completed bridge;
- transformed downtown;
- major new housing supply;
- full digital sovereignty;
- harbour acquisition;
- City-wide broadband;
- national AgriHome adoption;
within 30 days.
Those are outcomes requiring time.
Judge the first month on whether the foundation for measuring them exists.
38.202What Should Definitely Not Happen in the First 30 Days
The administration should not:
- ban conventional real-estate signs;
- require RealMap;
- transfer map.ca into municipal ownership without independent process;
- launch a municipal social network;
- promise lifetime email accounts before governance exists;
- launch a resident data locker;
- establish a municipal currency;
- permanently close 2nd Avenue East;
- commit to building the east-west crossing;
- purchase the federal harbour;
- direct police operations;
- pre-select police staffing cuts;
- lay off staff to create an Efficiency or Safety Dividend;
- assign Grey County paramedics to City programs;
- promise federal or provincial funding not yet approved;
- build a City telecommunications company;
- create dozens of new permanent staff positions;
- create permanent committees for every initiative;
- use municipal data for campaign purposes;
- use the Mayor's office to advance a private platform.
If avoiding these things makes the first month look less dramatic:
Good.
38.203The First Visible Wins
Visible early action should focus on things that are:
- lawful;
- inexpensive;
- useful;
- reversible.
Possible examples after staff confirmation:
- correcting broken public information;
- fixing obvious maintenance problems;
- improving a confusing webpage;
- publishing responsibility guides;
- clearing a service backlog where resources already exist;
- improving signage or wayfinding;
- routing resident issues correctly.
Trust begins with small competence.
38.204Do Not Manufacture Quick Wins
If a problem is complicated:
Say so.
Do not create a superficial patch purely to produce:
Day 17 announcement.
Some problems deserve proper work.
38.205The First Hard Truths
The first month may reveal:
- project costs larger than expected;
- legal barriers;
- infrastructure liabilities;
- staffing shortages;
- weak data;
- campaign assumptions that were wrong.
Publish those discoveries.
The purpose of a business plan is not proving that every original idea was perfect.
It is making better decisions.
38.206Campaign Promise Correction Standard
If new evidence changes a campaign proposal:
Use this format:
What I Proposed
The original commitment.
What We Learned
The new evidence.
What Changes
The revised proposal.
Why
The reason.
What Happens Next
The decision path.
That is responsible leadership.
38.207No Shame in Removing a Bad Idea
If a policy cannot survive:
- legal;
- financial;
- evidence;
review:
Remove it.
Do not waste four years protecting the campaign document from reality.
38.208But Do Not Quietly Remove It
The Commitment Register remains.
Mark:
Stopped after review.
That lets residents judge whether the correction was reasonable.
38.209The First Council Work Plan
By Day 30, Council should have a manageable list of matters likely to require decisions during the next 70 days.
Not 200 motions.
Prioritize:
governance;
budget and financial standards;
service reform;
immediate road-transfer issues;
planning-service decision;
housing and business navigation;
first pilots;
intergovernmental asks.
38.210Protect Council Capacity
Council has regular statutory and municipal business beyond this plan.
Do not consume every meeting with:
Mayor's initiative number 47.
The implementation calendar must leave room for:
- planning;
- budgets;
- emergencies;
- resident matters;
- existing work.
38.211Protect Staff Capacity
Every new report request consumes staff time.
Before directing a report:
Ask:
What decision will this report allow Council to make?
If none:
Maybe we do not need it.
38.212Group Related Reports
Rather than requesting separate reports on:
- benches;
- lights;
- washrooms;
- trails;
combine them into appropriate:
- public-realm;
- infrastructure;
work.
Reduce reporting overhead.
38.213Use Existing Reports
Before ordering a study:
Ask:
Has this already been studied?
East-west crossing work is an obvious example.
So are:
- asset management;
- planning;
- transit;
- facilities.
Read first.
38.214Update Rather Than Restart
If a past report is still fundamentally sound:
Update the assumptions.
Do not hire another consultant to repeat:
- background;
- history;
already known.
38.215Professional Independence
Engineers, planners, treasurers, firefighters, police leaders and other professionals should be free to tell Council:
The evidence does not support the Mayor's idea.
That is not disloyalty.
That is why professionals are employed.
38.216Mayor Must Hear Bad News
One leadership rule should be explicit:
Bring me bad news early.
Do not create a culture where staff hide:
- cost overruns;
- legal risks;
- missed deadlines;
because the Mayor reacts badly.
38.217No Retaliation for Evidence
No employee should fear political retaliation for providing professional advice that contradicts a campaign promise.
Council can make the final policy decision within law.
Evidence remains evidence.
38.218Public Does Not Need Internal Drama
Professional disagreement can be reported as:
Staff recommends X. I prefer Y for these reasons. Council will decide.
No need to personalize.
38.219First 30-Day Community Tone
The new administration should communicate:
We are here to work with people who voted for us, voted against us or did not vote at all.
The election ended.
Municipal government begins.
38.220Goodwill Compact Becomes Conduct, Not Campaign Branding
The original campaign Goodwill Compact should translate into:
- fair meetings;
- respectful debate;
- correction of errors;
- no personal retaliation.
It does not need to remain a campaign-branded document inside City Hall.
The principle matters more than the label.
38.221The First-Month Public Promise
The most defensible first-month promise is not:
I will transform Owen Sound in 30 days.
It is:
Within 30 days, you will be able to see how this administration intends to transform Owen Sound, who is responsible, what it costs, what law applies, what evidence is missing and what happens next.
That is the foundation.
38.222Day-30 Deliverables
By the end of the first 30 days, the administration should aim to have the following either completed or formally underway:
Governance
- Council and legal orientation;
- Mayor-City Manager operating rhythm;
- Commitment Register;
- Authority Map;
- decision tracking;
- conflict firewall.
Finance
- financial baseline;
- contract-renewal list;
- grant-dependency list;
- unfunded-infrastructure list;
- initial unfunded-mandate ledger.
Service
- Service Catalogue structure;
- response-time baseline;
- Start-Up Desk workflow;
- No Wrong Government design.
Workforce
- labour listening meetings;
- vacancy review;
- employee improvement channel.
Procurement
- vendor-process review;
- upcoming procurement forecast;
- digital contract review.
Infrastructure
- Index roadmap;
- road-transfer audit;
- capital-risk baseline.
Downtown
- downtown walk;
- maintenance quick-fix list;
- Civic Square inventory;
- 2nd Avenue pilot requirements.
River and Recreation
- Missing-Link Map baseline;
- activity and club inventory.
Housing
- Housing Navigation process map;
- federal-program verification process.
Business
- merchant listening;
- payment-cost evidence plan;
- Shop Local directory inventory;
- delivery and pooling feasibility questions.
Real Estate
- sign baseline;
- no change yet;
- RealMap conflict and public-standard review.
Seniors
- independence review;
- transit financial baseline;
- Grey County ride-partnership request;
- winter assistance design.
Safety
- police/fire/by-law/service baseline;
- Safety Dividend held until evidence;
- community-safety walk planning.
Community
- partner inventory;
- neutral partnership framework.
Youth
- Civic Corps legal and operational design;
- youth opportunity inventory.
Information
- public Wi-Fi inventory;
- device-reuse feasibility;
- responsible-data education partnership.
Digital
- Digital Systems Index;
- AI inventory;
- interim information-use rule;
- map.ca independent-review process.
SON
- leadership outreach;
- existing-relationship inventory.
Grey County
- road, planning, housing, transit and paramedic review.
Ontario
- Ontario Issues Register;
- current-law briefing;
- authority audit.
Canada
- Federal Issues Register;
- Transport Canada harbour request;
- federal funding and housing-program verification.
Major Projects
- crossing problem statement;
- corridor preservation review;
- no construction commitment.
Transparency
- State of the City Baseline;
- first Scorecard methodology;
- first 100-day implementation calendar.
That is enough work for one month.
38.223Responsible Departments
The exact administrative assignment belongs to the City Manager.
Broadly, work will involve existing functions such as:
- Clerk;
- Finance;
- City Manager's Office;
- Public Works and Engineering;
- Planning;
- Building;
- Economic Development;
- Parks and Recreation;
- Transit;
- Fire;
- IT;
- Communications;
- Human Resources;
- procurement;
- legal and integrity resources.
No section of this plan should be treated as permission for the Mayor to bypass those professional structures.
38.224Council Approvals
Some first-month actions are simply administrative:
- briefings;
- inventories;
- relationship meetings;
- baseline preparation.
Others require Council approval before implementation.
Examples may include:
- new spending;
- pilot programs;
- policy changes;
- service standards with financial consequences;
- by-law changes;
- major studies;
- acquisitions;
- permanent organizational change.
Every initiative gets the correct route.
38.225Outside Partners
The first month should establish rather than presume partnerships involving:
- Saugeen Ojibway Nation;
- Grey County;
- Ontario;
- Government of Canada;
- police governance;
- health-system organizations;
- library;
- business organizations;
- community groups;
- education institutions.
An outside partner appears in the plan as:
proposed partner
until that partner agrees.
38.226Cost
The first-month goal is to use existing institutional capacity wherever practical.
Where professional review or new work requires money:
Identify it.
There is no virtue in claiming:
$0
when staff are spending hundreds of hours.
Public work has cost even when no new cheque is written.
38.227Funding
The first-month implementation budget should distinguish:
Existing Approved Budget
Already available.
Council Approval Required
New municipal expenditure.
Outside Funding Potential
Not yet committed.
Future Capital
No current expenditure.
Never put:
Grant
in the funding column as though a hoped-for application is cash.
38.228Staff
The first 30 days should not assume large additions to the workforce.
If implementation creates material workload:
Measure it.
Then decide whether the solution is:
- reprioritization;
- temporary project support;
- technology;
- contract;
- permanent position.
Use the New Position Rule.
38.229Consultation
Consultation should be scheduled according to decision need.
Some questions need:
- early listening.
Others need:
- technical work first.
Do not ask residents to choose between options nobody has costed.
38.230Legal Review
The first month should establish the legal work queue.
Priority should follow:
- consequence;
- rights;
- financial risk;
- conflict.
Do not send every ordinary operating idea to external counsel.
Use professional judgement.
38.231Target Date
The master implementation register should include:
- 30-day;
- 100-day;
- Year One;
- Year Two;
- Year Three;
- Year Four;
target categories.
Not every commitment needs an invented calendar date years in advance.
Use the level of precision evidence supports.
38.232Measurement
Every initiative needs a measure before major implementation.
Examples:
Start-Up Desk
Response time.
Roads
Condition and lifecycle cost.
Shop Local
Merchant cost and participation.
Seniors Transit
Rides, cost and access.
Safety
Workload and response.
Downtown
Maintenance and use.
Digital
Portability and operating cost.
Partnerships
Commitments completed.
Measures can change when better evidence appears.
Publish the change.
38.233The Month-One Exit Test
Every pilot being prepared should already answer:
How does it stop?
If the City begins something and it does not work:
We need an orderly way to end it.
38.234No Sunk-Cost Government
If we spend:
- $20,000;
studying something and discover it is a bad idea:
That study may have saved:
- millions.
Do not build the project merely to justify the study.
38.235The Month-One Rights Test
Before advancing major policy:
Ask:
Charter?
Human rights?
privacy?
accessibility?
procedural fairness?
Indigenous rights?
property rights and applicable statutory authority?
Rights questions belong at the beginning.
Not after public controversy.
38.236The Month-One Freedom Test
Ask:
Does this initiative require government to control more of ordinary life than necessary?
If a voluntary tool works:
Prefer it.
If regulation is required:
Use the least intrusive effective rule.
38.237The Month-One Family Test
Ask:
Does this make it easier or harder for families to care for one another?
This applies to:
- housing;
- transportation;
- recreation;
- information.
38.238The Month-One Local Test
Ask:
Can Owen Sound solve this ourselves?
If yes:
Stop waiting for senior government.
38.239The Month-One Jurisdiction Test
Then ask:
Are we trying to solve something another government actually controls?
If yes:
Change the action from:
Do
to:
Ask / Partner / Advocate.
38.240The Month-One Evidence Test
Ask:
What would prove this idea wrong?
If the answer is:
Nothing,
it is not an evidence-based policy.
38.241The Month-One Honesty Test
At Day 30, I should be able to tell residents:
One thing we learned is better than expected.
One thing is worse than expected.
One campaign assumption was wrong.
One idea looks stronger after review.
One idea may need to change.
That should become normal government communication.
38.242The First 30 Days Are a Baseline, Not a Victory Lap
There should be no:
MISSION ACCOMPLISHED
report.
There should be:
Here is where we started.
Here is what we learned.
Here is what is now underway.
Here is what needs Council.
Here is what requires another government.
Here is what we are not doing yet and why.
That is credible implementation.
The First 30 Days Commitment
The first month of a new administration should not be the loudest month.
It should be the month that makes every later month work.
The commitment is:
Separate campaign systems from municipal systems immediately.
Disclose private interests before related municipal decisions arise.
Obtain independent conflict and legal guidance.
Confirm the law actually in force when Council takes office.
Respect the City Manager's administrative role.
Create a regular Mayor-City Manager operating review without creating a backroom Council.
Orient Council properly.
Recognize that election does not automatically approve every campaign proposal.
Create a Four-Year Commitments Register.
Keep stopped and missed commitments visible.
Map the jurisdiction behind every major promise.
Give every commitment one municipal owner.
Do not create a new bureaucracy simply to administer the business plan.
Establish the real financial baseline before claiming savings.
Do not declare an Efficiency Dividend before savings exist.
Identify major contracts, renewals, assets, unfunded infrastructure and grant dependency.
Build transparency from existing systems before purchasing new systems.
Define Scorecard measures before implementation.
Say when a reliable baseline does not yet exist.
Begin the Service Catalogue and No Wrong Door system.
Build the Start-Up Desk from a real process map.
Do not promise ten-day business responses until eligible files and timing rules are defined.
Listen to merchants before launching Shop Local programs.
Do not launch the Penny until the funding mechanism is real.
Do not put private deliveries in City vehicles before legal, labour, insurance and market review.
Meet municipal employees and bargaining representatives early.
Do not begin the term with layoffs or politically driven restructuring.
Apply the New Position Business Case instead of an arbitrary hiring freeze.
Ask frontline employees how work can improve.
Open procurement opportunity without creating local favourites.
Identify major software dependencies and upcoming renewals.
Begin the Digital Systems Index.
Do not put protected City information into unapproved AI systems.
Review critical backup and recovery capability.
Receive an emergency-management briefing before an emergency occurs.
Map useful public information without mapping vulnerable residents.
Walk City infrastructure with the people who actually operate it.
Build the Standing Work List before staging civic work days.
Design the backend of First to Action before launching the map.
Map the housing journey before promising new navigation services.
Version-date outside funding information.
Walk downtown and separate maintenance problems from capital projects, private-property issues and social-service issues.
Do not announce a downtown megaproject in the first month.
Treat 2nd Avenue East as a proposed pilot requiring evidence and consultation.
Inventory the Civic Square before rebuilding it.
Map River Spine gaps before promising continuous access.
Inventory existing outdoor and enthusiast communities before creating new municipal recreation businesses.
Complete conflict, legal, privacy, accessibility, technical and valuation work before any official RealMap or map.ca adoption.
Do not change real-estate sign rules in the first month.
Do not use sign regulation to manufacture customers for a platform.
Begin the Seniors Independence Review.
Cost free senior transit before implementing it permanently.
Ask Grey County and health partners whether the scheduled-ride concept is professionally feasible.
Design winter assistance without creating a public list of vulnerable seniors.
Establish the Community Safety baseline before discussing police staffing savings.
Do not pre-set police headcount reductions.
Respect police operational independence.
Review fire capacity and future capital needs.
Use safety walks to improve infrastructure, not create vigilantes.
Map the existing crisis-response system before creating another one.
Inventory community partners before selecting favourites.
Use equal partnership rules for faith and secular organizations.
Design Civic Corps legally and safely before enrolling young people.
Do not use youth as free replacements for municipal employees.
Map youth opportunities rather than youth themselves.
Inventory current connectivity before chasing broadband funding.
Review recycled-phone safety and emergency-calling claims before making promises.
Use the library and existing institutions for responsible data education.
Do not launch a resident data locker in the first month.
Define the public map standard before evaluating map.ca.
Do not launch an unproven municipal lifetime-email service.
Treat the community calendar as a separable, lower-risk public-information module.
Contact Saugeen Ojibway Nation to listen, not to present a finished agreement.
Inventory existing SON work before claiming the relationship is beginning from zero.
Begin the federal harbour facts file.
Do not commit to acquiring the harbour before due diligence.
Meet Grey County on roads, planning, housing, transit and paramedic partnerships.
Audit transferred-road liabilities before taking ownership.
Measure the total taxpayer effect of City-County service changes.
Evaluate hybrid planning on evidence.
Enter regional transit planning early enough to influence it.
Map Ontario's actual role in every major commitment.
Confirm current strong-mayor law before exercising extraordinary authority.
Create Ontario and federal issues registers.
Ask Transport Canada directly for harbour information.
Verify federal housing and broadband program status before public advice.
Treat the east-west crossing as a Year One evidence project, not a first-month construction promise.
Preserve reasonable crossing options without prejudging construction.
Separate any bridge case from hospital relocation.
Build Resident Government rules before launching online voting tools.
Do not confuse voluntary online participation with a statutory election.
Publish a State of the City Baseline by approximately Day 30.
Give previous Councils and staff credit for work already completed.
Name problems without manufacturing blame.
Publish the first 100-day implementation calendar.
Do not exhaust residents with unnecessary consultation.
Do not exhaust staff with reports that lead to no decision.
Read existing studies before ordering new ones.
Allow professional staff to tell Council when the evidence contradicts the Mayor.
Bring bad news forward early.
Correct campaign assumptions openly when evidence changes.
Stop bad ideas rather than defending them for political pride.
Never quietly erase a stopped promise.
At the end of 30 days, Owen Sound should not look completely different.
City Hall should.
Not cosmetically.
Operationally.
The administration should know:
- what it promised;
- what it can legally do;
- what it costs;
- who owns the work;
- which government must participate;
- what information is missing;
- how success will be measured;
- when to stop if something fails.
That is the first month.
Listen first. Establish the baseline. Assign responsibility. Publish the commitments. Protect the public interest. Then begin the work.