Owen Sound: A Four-Year City Business Plan

Home › Implementation › Chapter 39

Implementation

Chapter 39The First 100 Days: Turn the Baseline Into Action

10,807 words · Mike Seiler · Owen Sound, Ontario

Open in the reader →

Vote on the proposals, hear the audio, read the reviews, search the whole plan.

In this chapter

The first 30 days establish the operating system.

The next 70 days should prove that the operating system can produce results.

By Day 100, residents should not expect every four-year promise to be complete.

They should expect something much more important:

The City should be measurably easier to understand, easier to deal with and harder to manage by political improvisation.

The first 100 days should produce the first:

The principle is:

Move quickly on things that are lawful, affordable, reversible and understood. Move carefully on things that are expensive, coercive, technically complex or difficult to reverse.

Speed and discipline are not opposites.

Good government needs both.

39.1What Changes After Day 30

The first month is dominated by:

Days 31 through 100 should begin converting that work into four types of action.

Approve

Council makes decisions where the evidence is ready.

Pilot

Test uncertain ideas at limited scale.

Improve

Fix obvious operating problems using existing authority.

Escalate

Take properly prepared requests to:

Not everything should advance.

Some initiatives may remain:

Hold

because the evidence is not ready.

That is acceptable.

39.2The 100-Day Standard

Every initiative selected for first-100-day action should answer:

Problem

What are we fixing?

Authority

Who can decide?

Evidence

What did the first 30 days reveal?

Action

What exactly happens by Day 100?

Cost

What does it cost?

Funding

Where does the money come from?

Staff

Who does the work?

Partner

Who else must agree?

What review is required?

Measure

How will the public know whether it worked?

Exit

What happens if it does not work?

This becomes the implementation template for the rest of the term.

39.3No 100-Day Stunt Government

A first-100-day plan can create bad incentives.

Politicians may rush:

simply to claim:

100 promises in 100 days.

That is not the objective.

One sound change is worth more than ten rushed announcements.

39.4Day 100 Is a Checkpoint, Not an Expiry Date

Some decisions will not be ready by Day 100.

Examples may include:

Do not force them through because the symbolic deadline arrived.

The Day-100 report can legitimately say:

Not ready. Here is what remains unresolved.

39.5The First 100-Day Council Work Plan

The Council agenda should concentrate on a manageable number of decisions.

Likely priority categories include:

  1. Open Government framework.
  2. Service standards.
  3. Start-Up Desk.
  4. First to Action.
  5. procurement improvements.
  6. road-transfer preparation.
  7. planning-service model.
  8. downtown quick fixes.
  9. housing navigation.
  10. seniors transit decision.
  11. Community Safety framework.
  12. Civic Corps pilot.
  13. Shop Local pilots.
  14. community partnership standards.
  15. digital governance.
  16. SON relationship framework.
  17. harbour federal file.
  18. crossing Year One study scope.
  19. first public scorecard.

That is already substantial.

39.6Protect the Regular City Agenda

Council must still deal with:

The first 100 days should not turn every Council meeting into a campaign-platform workshop.

Implementation has to fit inside actual municipal government.

39.7First Public Commitments Register

By Day 100, the Four-Year Commitments Register should be public.

Every significant commitment should show:

Not Started

Baseline Complete

Under Review

Council Decision Scheduled

Partner Discussion

Pilot

Active

Completed

Stopped

Missed

A resident should be able to locate any major campaign promise and see its status.

39.8Every Commitment Has an Owner

By Day 100, every active commitment should identify:

No initiative should remain:

Everybody is working on it.

That usually means nobody owns it.

39.9Public Authority Map

The Authority Map should also be live.

Every major commitment receives:

City

Can act locally.

County

Requires Grey County.

Ontario

Requires provincial authority, funding or action.

Canada

Requires federal authority, funding or action.

SON

Requires a distinct Indigenous-government relationship or may engage rights and consultation processes.

Community

Requires another organization or private partner.

This is one of the simplest ways to make campaign promises honest.

39.10First Public Financial Baseline

By Day 100, residents should have a plain-language picture of:

Not every accounting detail needs a dashboard.

The major financial picture should be understandable.

39.11Financial Dashboard Version One

Version One can be simple.

Possible fields:

Approved Budget

What Council authorized.

Actual to Date

What has been spent.

Variance

Difference.

Capital Project Status

Approved, spent, forecast.

Major Grants

Approved and received.

Debt

Outstanding and forecast.

Reserves

Current position.

Accuracy is more important than graphics.

39.12Complete Cost Starts Now

Every new report requesting significant spending should begin using the Financial Standard.

Show:

A proposal is not inexpensive merely because another government pays the first invoice.

39.13First Efficiency Review

Select a small number of processes for initial efficiency work.

Possible examples:

Do not start with frontline staffing cuts.

Start where waste can be reduced without weakening service.

39.14Efficiency Dividend Verification Standard

Before any first Efficiency Dividend is declared:

Finance should verify:

Baseline

What did the City spend before?

Change

What was actually changed?

New Cost

What does the replacement cost?

Net Saving

What is left after all costs?

Recurring or One-Time

Which is it?

Service Impact

Did quality decline?

Only then does the saving enter the Dividend calculation.

39.15No Fake Saving From Deferral

If the City postpones:

that is generally not an efficiency saving.

It may simply be:

a future liability.

Do not pay an Efficiency Dividend out of neglected maintenance.

39.16No Saving From Vacant Position Unless Work Disappears

A position being vacant does not automatically prove the City no longer needs the work.

Ask:

Only a true net saving counts.

39.17First Procurement Improvements

By Day 100, Council should be able to consider the first procurement improvements.

Possible early actions:

The objective is:

Open the opportunity without weakening procurement discipline.

39.18Local Vendor Gateway Version One

The first version does not need complex software.

It can provide:

A local small business should understand how to compete.

39.19No Guaranteed Local Contract

The Gateway must say clearly:

Registration does not guarantee work.

Procurement remains:

39.20Procurement Forecast

Publish a forward-looking list of significant purchasing opportunities where legally and operationally appropriate.

Examples:

Advance notice allows businesses to prepare.

39.21First Digital Exit Reviews

Choose several major technology contracts nearing renewal.

For each:

Cost

Data held

Export capability

Contract expiry

Alternative supplier

Criticality

Migration difficulty

This begins digital-sovereignty reform with actual municipal systems.

39.22Cancel Unused Licences

If the first inventory identifies software licences that are genuinely:

and cancellation creates no operational harm:

Stop paying.

That may become one of the first verified efficiencies.

39.23Do Not Cancel Before Export

If an old system contains required municipal records:

Preserve or migrate them before cancellation.

Saving a licence fee is not worth losing the public record.

39.24Service Catalogue Version One

By Day 100, publish the first plain-language Service Catalogue.

Start with the most common services.

Each entry should answer:

What do I need?

Who handles it?

How do I contact them?

What happens next?

What is the normal response expectation?

Who do I contact if something goes wrong?

The Catalogue can expand continuously.

39.25Service Standards Version One

A reasonable first set may include selected services such as:

Do not publish unrealistic standards merely because:

fast sounds good.

The standard has to be deliverable.

39.26Service Standard Means a Meaningful Answer

A department should not satisfy a response standard by sending:

We received your email.

A meaningful response might be:

39.27Publish Exceptions

Service standards should explain situations involving:

A transparent exception is better than a hidden missed target.

39.28No Wrong Door Version One

By Day 100, frontline City staff should have a simple referral guide for common:

services.

Residents should increasingly hear:

That is handled by Grey County. Here is exactly where you go.

Not:

Not us.

39.29Measure Wrong-Door Problems

Create a simple staff mechanism to record recurring:

people keep calling us about this other service

issues.

That reveals where public information is failing.

39.30Start-Up Desk Launch

The original source proposes one City Hall window for someone starting a business, with a published ten-business-day answer standard or eligible fee waiver.

By Day 100, the Start-Up Desk should be operational in at least its first practical version.

39.31One Start-Up Contact

The first version should offer:

It does not require a new storefront or department.

39.32Before You Sign Service

Launch the Before You Sign guidance.

A prospective business can ask about a location before committing financially.

The response should identify known municipal considerations such as:

The response is preliminary.

It is not final approval.

39.33Ten-Business-Day Standard

If staff review confirms it is lawful and operationally realistic, Council should consider the promised ten-business-day standard for eligible Start-Up Desk matters.

The source promise is clear.

The refined rule should mean:

Within ten business days, receive the decision, a consolidated list of municipal requirements or a formal status explaining what remains outstanding.

39.34The Clock Must Be Honest

The public file should distinguish:

City Time

Time under municipal control.

Applicant Time

Waiting for applicant information.

Outside Time

Waiting for another authority.

Do not stop the clock invisibly.

39.35Fee-Waiver Rule

If Council adopts the fee guarantee:

Define exactly which:

qualifies.

Do not promise to waive:

The City cannot waive money it does not collect.

39.36Start-Up Scorecard

By Day 100 establish:

Do not count:

businesses contacted

as:

businesses created.

39.37Business Red-Tape Log

Start recording recurring complaints such as:

Every item should be classified:

City rule

City practice

County

Ontario

Canada

Fix the right layer.

39.38Shop Local Payment Pilot

The original source proposes a debit-first campaign based on the idea that payment costs can differ materially between card types.

By Day 100, Owen Sound should have current local evidence before launching any public claim about:

39.39Merchant Payment Report

Using voluntary, privacy-respecting merchant participation:

Publish aggregate findings such as:

Do not publish one merchant's confidential contract.

39.40Debit-First Pilot

If evidence supports it:

Launch a small voluntary education pilot.

Possible message:

Ask your local merchant which payment method they prefer.

Not:

Credit cards are bad.

Not:

Everyone must use debit.

Choice stays with the customer.

39.41City Payment Review

The City should review its own payment-processing costs too.

If City Hall asks merchants to understand payment costs:

It should understand its own.

39.42Owen Sound Penny Design

The original source proposes the Owen Sound Penny as a $1 cross-business reward funded from value retained locally rather than as currency.

By Day 100, the concept should still be in:

design or pilot approval

unless a genuine funding source and operating model have been established.

39.43Penny Funding Must Be Explicit

Potential funding must identify an actual payer, such as:

Do not say:

payment savings fund the Penny

unless those savings are actually contributed.

All public material should continue to say:

promotional reward

or

local loyalty reward.

Not:

39.45Penny Pilot Gate

Before Council authorizes a pilot:

Require:

If those are not ready:

Delay it.

39.46Shop Local Directory Version One

If the directory gap identified in the first month is real:

Launch a simple neutral listing.

Basic fields:

No paid basic ranking.

39.47Existing Directories Remain

The City directory should not require businesses to leave:

Public discovery can coexist with private platforms.

39.48Shop Local Delivery Feasibility Report

The source proposes using existing municipal movement through the city to help local deliveries, with local couriers first and union-agreed duties.

By Day 100:

Publish whether that approach appears:

39.49Private Delivery First

If local courier or cooperative delivery can solve the problem:

Prefer that to turning municipal vehicles into a retail-delivery fleet.

Government should fill a market gap only where a public case exists.

39.50Delivery Pilot Only if Evidence Supports It

If a pilot proceeds:

Define:

Measure the real cost per delivery.

39.51Community Pooling Test

The original plan proposes combining community purchasing demand, giving local merchants the first chance to fill demand, and eventually considering a purchasing cooperative.

By Day 100:

Test one or two narrow categories.

Do not launch a municipal warehouse.

39.52First Pooling Question

Ask:

What are households or businesses repeatedly buying outside Owen Sound that might be purchased more efficiently together?

Then:

Can existing local merchants supply it competitively?

Local supply gets a fair opportunity.

Not an automatic contract.

39.53Publish True Savings

If pooling saves money:

Include:

A cheaper unit cost is not always a cheaper final purchase.

39.54First to Action Pilot

By Day 100, the City should be capable of launching or approving a limited First to Action pilot.

The principle remains:

Report once. Route properly. Track appropriately. Finish the work. Close the loop.

39.55Start With a Few Categories

Do not put every municipal problem into the pilot.

Possible initial categories:

Choose categories with:

39.56Emergency Reports Stay Separate

The reporting tool must state prominently:

Do not use this for emergencies.

Emergency response continues through the proper emergency channels.

39.57Public Status

Where appropriate and privacy-safe:

Show simple status such as:

Received

Assigned

Scheduled

Completed

Not every internal work note belongs on the public map.

39.58Duplicate Reports

The pilot should recognize repeated reports of the same issue.

Residents should not need to submit a pothole fifty times to prove it matters.

39.59Councillors Use the Same System

A councillor reporting an ordinary maintenance issue should use the same operating workflow where practical.

Political access should not silently push one pothole ahead of another.

39.60Standing Work List

By Day 100, recurring work categories should be visible internally and, where useful, publicly summarized.

The original plan specifically proposes a standing work list for work such as potholes and low lighting.

This allows work to be:

39.61First Root-Cause Review

Choose at least one recurring municipal complaint and ask:

Why does this keep happening?

Examples:

Fixing cause can be more valuable than improving response speed.

39.62Employee Improvement Pilot

Select several staff-generated improvement ideas.

For each:

Problem

Idea

Cost

Trial

Result

This demonstrates that labour partnership creates operational value.

39.63Labour Partnership Table

By Day 100, establish the practical labour-partnership mechanism with appropriate employee representatives.

It should not replace:

Its focus is:

39.64No Layoff Dividend

The original Safety Dividend specifically says no officer is laid off to create the saving.

The same underlying integrity should guide the broader Efficiency Dividend:

Do not manufacture savings by removing people while leaving the work undone.

39.65Infrastructure Index Version One

By Day 100, publish the first understandable Infrastructure and Systems Index summary.

It does not need every asset.

It should show the structure.

Possible first categories:

39.66Public Condition Categories

Use simple public categories:

Very Good

Good

Fair

Poor

Very Poor

Unknown

Where information is professional or technical:

Link to the source where appropriate.

39.67Unknown Assets Get an Assessment Plan

An unknown should receive:

Do not leave:

Unknown

forever.

39.68First Five-Year Capital Look-Ahead

Publish a high-level five-year view of major known infrastructure requirements.

Label:

Approved

Planned

Forecast

Under Study

Unfunded

This prevents residents from assuming:

planned

means:

already funded.

39.69One Street, One Plan Pilot

Choose one upcoming corridor where multiple infrastructure needs overlap.

Coordinate:

Use it as a demonstration of integrated capital planning.

39.70Road-Transfer Decision Readiness

By Day 100, the road-transfer file with Grey County should include:

If information is missing:

Identify it publicly.

39.71No Road-Transfer Victory Claim Yet

Transfer money received from Grey County should not be described as:

profit

or:

savings.

It is part of a larger asset and liability transfer.

The real result will take years to measure.

39.72Hybrid Planning Decision

If Grey County's planning-service decision requires action within the first 100 days:

Council should receive a complete business case.

It should compare:

Current model

Proposed hybrid model

Cost

service time

local knowledge

staffing

governance

exit

Then Council decides.

39.73Applicant Experience Is the Test

The planning question is not:

Which government employs the planner?

It is:

Does the applicant get a faster, clearer and professionally sound answer?

39.74Downtown Quick Fix Program

By Day 100, obvious low-cost maintenance issues identified in the downtown baseline should begin moving.

Possible examples after staff review:

Fix the things that do not require a master plan.

39.75Quick Does Not Mean Sloppy

Even a small improvement may require:

consideration.

Fast government still follows rules.

39.76Downtown Operating Plan Version One

Publish a simple seasonal operating plan covering:

Downtown management should be operational.

Not only visionary.

39.77Vacancy Baseline

Create a factual vacancy inventory where information can be lawfully and reliably established.

Do not create:

bad landlord list.

The purpose is understanding:

39.78Downtown Development Desk

Designate a clear contact for significant downtown:

navigation.

Again:

One contact.

Not necessarily one new employee.

39.79Civic Square Temporary Pilot

If the baseline supports it and Council/staff approvals are in place:

Test temporary:

Then observe ordinary use.

39.80Tuesday Test Begins

The Civic Square should be measured on:

an ordinary Tuesday

as well as an event day.

A place needing constant programming to feel alive may be poorly designed for ordinary life.

39.812nd Avenue East Pilot Decision

By Day 100, Council should ideally know whether the seasonal pilot is:

Ready

Needs Modification

Not Ready

based on:

Do not schedule closure before those questions are answered.

39.82Pilot Success Criteria Before Launch

If approved:

Publish in advance:

Pedestrian activity

Business experience

accessibility

traffic

parking

safety

cost

resident feedback

Then compare after the pilot.

By Day 100, publish the first public version showing:

Do not map private land as though public access exists.

For each gap:

City-controlled

Other public owner

Private

Unknown

This keeps future proposals realistic.

39.85Owen Sound Outside Version One

Launch a simple Where Do I Start? guide for selected outdoor activities.

Possible activities:

For each:

Where

Beginner option

Equipment source

Club or business

accessibility information

seasonal safety information

The City connects.

Others provide depth.

39.86Equipment Library Decision

Do not buy a large City recreation inventory automatically.

By Day 100, identify whether:

already provide equipment access.

Fill a proven gap only.

39.87Enthusiast Map Version One

The first Enthusiast Map can organize:

No paid ranking.

No claim that the City endorses each provider.

39.88Enthusiast Gap List

Ask participants:

What do you routinely leave Owen Sound to buy, repair, learn or rent?

Publish aggregate opportunity categories.

That can feed the Start-Up Desk.

39.89Housing Navigation Desk Launch

By Day 100, launch the first practical Housing Navigation service.

It should help residents understand:

39.90Housing Desk Is Not a Promise of Approval

Every guide should say:

Property-specific approval depends on applicable law, site conditions and complete review.

Navigation is not pre-approval.

39.91Current Program Verification

All federal or provincial housing incentives included in the guide should show:

Do not repeat campaign-era program assumptions indefinitely.

39.92Housing Options Guide Version One

Publish plain-language information on:

Show which questions need:

39.93Approved Is Not Built Dashboard

Begin separating:

This protects housing statistics from political inflation.

39.94Municipal Land Inventory

By Day 100, identify City-owned land potentially relevant to:

This is an inventory.

Not a promise to sell or develop each parcel.

39.95Use Before Sell

Before disposing of City land:

Ask:

Does the City need this asset for a foreseeable public purpose?

Public land should not be treated as an easy one-time revenue source without long-term analysis.

39.96Family-Friendly Neighbourhood Pilot

Choose one neighbourhood walk-through or planning exercise using the Family Impact and Neighbourhood tests.

Look at:

This turns the principle into practical planning.

39.97Do Not Create a Family Score for Residents

The Family-Friendly framework evaluates:

It does not judge which households count as:

good families.

Public service remains equal.

39.98Seniors Independence Review Results

By Day 100, publish the first findings from the Seniors Independence Review.

Possible categories:

Focus on barriers.

Not stereotypes.

39.99Free Senior Transit Decision

The source proposes free bus fares for seniors.

By Day 100, Council should ideally receive the business case.

It should show:

Eligibility

Current ridership

Fare revenue

Capacity

Administrative cost

Estimated additional trips

Pilot term

Measure

Then Council decides.

39.100Pilot Before Permanent Fare Change

If approved:

Use a defined pilot where practical.

Measure:

Do not treat:

free

as the measure of success.

Independence is the outcome.

39.101Senior Ride Feasibility

The source also proposes scheduled rides with a nurse or community paramedic aboard.

By Day 100, Owen Sound should know whether Grey County or another appropriate health partner sees a viable role.

The transportation model should be evaluated even if no clinician participates.

39.102No Medical Requirement to Ride

Any future senior community ride should not require a resident to disclose private medical information merely to access transportation unless a specific clinical service legitimately requires it.

Transport first.

Medical participation optional and properly governed.

39.103Snow Brigade Pilot

If winter timing makes it relevant, launch a limited snow-help program only after:

rules are established.

The source proposal specifically contemplates snow brigades for seniors' private walks.

39.104Snow Brigade Boundaries

Appropriate work might include:

Not:

High-risk work remains professional.

39.105No Public Senior Vulnerability List

Requests can be managed privately.

Public mapping should show:

Not the homes of residents needing help.

39.106Community Safety Baseline Report

By Day 100, publish a public Community Safety baseline using appropriate aggregate data.

Potential areas:

Use professional definitions.

39.107Safety Dividend Framework

The source proposes that prevention could reduce police demand, allowing officers to shift toward youth/community work and savings to occur only through voluntary retirement or attrition, with no officer laid off.

By Day 100, Council should approve or consider the framework, not claim the savings already exist.

39.108Safety Dividend Preconditions

Before any financial dividend:

  1. baseline call demand established;
  2. service change identified;
  3. workload reduction demonstrated;
  4. public safety maintained;
  5. professional police planning supports staffing implications;
  6. collective agreements respected;
  7. savings verified by Finance.

No shortcut.

39.109Capacity Dividend Comes First

The first benefit may be:

That is valuable even if the budget does not immediately fall.

Do not force a financial saving where the real benefit is capacity.

39.110Right Responder Table

Establish the cross-service Community Safety Partnership Table if evidence shows value.

Possible participation depending on topic:

Do not discuss identifiable residents publicly.

39.111First Right-Responder Pilot

Choose one recurring non-emergency call type where another service may potentially handle part of the problem better.

Define:

Pilot carefully.

39.112No Police Dumping

A Right Responder model should not simply move:

calls to undertrained workers or volunteers.

The new responder must actually be appropriate.

39.113Downtown Safety Work Plan

Combine:

Do not treat downtown safety as only a policing problem.

39.114Lighting Audit

The original source identifies low lighting as a standing work item and notes that a lit street can contribute to safety.

By Day 100, complete the first targeted lighting audit.

Ask:

More light is not always better light.

39.115Fire Prevention Quick Wins

If fire leadership identifies inexpensive improvements involving:

move them.

Do not wait for the entire safety strategy.

39.116Community Partner Standard

By Day 100, adopt or present the Community Partnership Standard.

Every significant partnership should define:

39.117Grant Register

Create a public list of significant municipal grants and in-kind support to outside organizations.

Where lawful:

Show:

No hidden community funding.

39.118Grant Is Not Contract

The first-100-day framework should distinguish:

Grant

Support for an independent public-benefit activity.

Contract

City purchases a defined service.

Do not use grants to bypass procurement.

39.119Faith-Neutral Public Standard

Publicly supported service should not be conditioned upon:

Faith organizations may still participate under the same public-purpose rules as secular organizations.

39.120Community Resource Directory

If no adequate current system exists:

Launch or improve a basic resource directory.

Possible categories:

Map the resource.

Not the person using it.

39.121Community Calendar Version One

The source proposes a free community calendar with no advertising and no tracking.

A first version could be appropriate within 100 days if:

are ready.

39.122Calendar Before Platform

The City can establish the calendar standard even if it does not adopt:

If existing City software can perform the function:

Use it.

Public purpose first.

39.123No Paid Calendar Ranking

Basic event visibility should not be sold.

Use transparent sorting:

39.124Civic Corps Pilot Approval

By Day 100, Council should be able to consider a first Civic Corps pilot.

Potential areas:

All roles must be age and risk appropriate.

39.125Paid Versus Volunteer

Every Civic Corps role should be classified.

Paid

Where the City is receiving real recurring productive work that should be employment.

Volunteer

Where participation is genuinely civic and optional.

Co-op

Where an educational institution governs the placement framework.

Do not blur categories for convenience.

39.126Youth Safety

Before placement:

Define:

Youth participation should be real.

Not reckless.

39.127Youth Opportunity Directory

By Day 100, launch the first public list of:

Youth should be able to browse without creating a permanent behavioural profile.

39.128Student Mapping Pilot

An early pilot may collect public observations such as:

The rule remains:

Students Gather. Staff Validate. Public Uses.

39.129No Youth Inspection

Youth do not certify:

The City does not use a youth program to avoid professional work.

39.130Safe Information Workshops

By Day 100, begin or schedule plain-language community education through appropriate partners.

Topics may include:

The source specifically proposes plain-language information stewardship so families can preserve photos, records and history.

39.131Use Existing Institutions

Partner first with:

Do not create a municipal technology-training bureaucracy unnecessarily.

39.132Public Wi-Fi Decision

If the first-30-day baseline identifies obvious public connectivity gaps:

Council may consider limited expansion in appropriate public spaces.

Any expansion needs:

Do not confuse Wi-Fi with city-wide broadband.

39.133Recycled Phone Pilot Decision

If the device-reuse study finds a safe, useful model:

Consider a small pilot.

Requirements may include:

Do not promise emergency functionality beyond what is verified.

39.134Digital Systems Index Version One

By Day 100, the internal Digital Systems Index should be substantially established.

The public version can report safe high-level information such as:

Do not publish attack surfaces.

39.135AI Governance Version One

By Day 100, establish a practical municipal AI policy.

At minimum:

Approved uses

prohibited sensitive-data uses

human responsibility

verification

vendor review

records implications

Keep it understandable.

39.136AI Does Not Decide Rights

No high-consequence municipal decision should be delegated to an unaccountable AI system merely because the technology is available.

A responsible human remains accountable.

39.137map.ca Decision Gate One

By Day 100, the first map.ca public-infrastructure review should answer:

What public problem is being solved?

What assets actually exist?

Who owns them?

What interest does the Mayor retain?

What open standard could solve the problem?

What alternatives exist?

No predetermined municipal adoption.

39.138Independent Review Begins Before Municipal Use

Where the concept continues:

Start independent:

review.

The Mayor does not select the conclusion.

39.139No Municipal map.ca Transfer by Day 100 Unless Extraordinary Review Is Complete

The default assumption should be:

No transfer within 100 days.

A public infrastructure transaction is too consequential to rush for an implementation milestone.

39.140RealMap Public Standard Draft

By Day 100, publish or consider the first platform-neutral Public Property Information Standard.

It can define expectations such as:

The standard can exist without RealMap.

39.141No Sign-Rule Change Yet Unless Evidence Is Ready

The real-estate sign transition should still be primarily in baseline and consultation during the first 100 days.

No rushed ban.

Enforce existing rules first.

39.142Sign Consultation Plan

Prepare consultation with:

Ask:

What information does the sign currently provide that must not be lost?

39.143Sign Baseline

Measure:

Do not design the answer before measuring the current system.

39.144SON Leadership Relationship

By Day 100, the City should aim, subject to SON's willingness and scheduling, to have completed an initial leadership conversation.

The source commitment is to build a relationship with SON and listen first.

That principle should govern the meeting.

39.145No Prewritten Agreement

The first 100 days should not be judged by whether an MOU is signed.

A stronger result may be:

Relationship before document.

39.146SON Relationship Inventory

By Day 100, City staff should know:

Institutional memory should not depend on one person.

39.147Harbour Federal File

By Day 100, Owen Sound should have formally asked Canada for the key harbour information.

At minimum:

39.148Harbour Public Questions Report

Publish:

Answered

Partially Answered

Outstanding

Do not announce a municipal acquisition decision merely because the federal government responded.

39.149Harbour Due Diligence Scope

If transfer discussion appears serious:

Prepare the scope for:

due diligence.

Council should approve significant study cost where required.

39.150No Harbour Negotiation by Mayor Alone

Any major transfer process should be handled through:

The Mayor may advocate.

The institution negotiates.

39.151Grey County Road Transfer Readiness

By Day 100, both governments should have a working implementation list for the road transfer.

Fields:

No responsibility gaps.

39.152No Wrong Road

On transfer day, a resident should be able to report a road issue without hearing:

We're not sure whether that's still the County.

The public routing system must be updated in advance.

39.153Grey County Housing Protocol

By Day 100, establish a practical referral relationship between:

The City does not become a shadow County department.

39.154Paramedic Partnership Answer

The City should know by Day 100 whether Grey County is interested in further evaluation of:

If the answer is no:

Record it.

Do not continue publicly promising County participation.

39.155Regional Transit Submission

Submit Owen Sound's evidence and priorities into the regional transit process early enough to matter.

Key issues:

39.156Ontario Ask Book Version One

By Day 100, publish Owen Sound's first short Provincial Ask Book.

Avoid a long wish list.

Priority requests may include only matters that:

39.157Strong-Mayor Position

If Council wishes to request removal or reform of Owen Sound's strong-mayor designation:

By Day 100, send the precise request to Ontario.

Do not claim the designation has changed until Ontario changes it.

39.158Provincial Mandate Ledger Version One

Publish the first verified entries.

Each should identify:

Do not use the Ledger as partisan commentary.

39.159Ontario Pilot Candidates

Select at most a few municipal reform ideas that genuinely require provincial flexibility.

For each:

Do not ask for vague:

more municipal power.

39.160Federal Ask Book Version One

Likewise, publish the first federal priorities.

Likely early file:

Other issues should only appear if the federal role is clear.

39.161Federal Housing Information Correction

By Day 100, the Housing Desk should have corrected any outdated campaign description of federal financing programs.

Accuracy beats preserving wording from the campaign.

39.162Broadband Evidence

By Day 100, answer:

Does Owen Sound actually have a broadband infrastructure gap?

If the main barrier is:

do not propose a fibre network to solve the wrong problem.

39.163East-West Crossing Year One Scope

By Day 100, Council should be able to consider a scoped Year One business-case study.

The study question should remain:

Does Owen Sound need another major northern east-west connection across the inner harbour or Sydenham corridor, and if so, what alternative best solves the demonstrated problem?

Not:

How do we justify the bridge we already decided to build?

39.164Crossing Study Components

The first scope should include:

39.165No-Build Alternative

Every serious crossing study must include:

Do not build another crossing

as a real alternative.

If the study cannot recommend no project:

It is advocacy, not analysis.

39.166Corridor Preservation

Where existing planning protects possible routes:

Do not accidentally allow decisions that destroy them before the business case concludes.

Preservation is not approval.

39.167Community Input Before Route Commitment

Residents and affected businesses should understand:

Do not ask them only:

Which bridge location do you prefer?

if:

no bridge

remains a valid option.

39.168Resident Pulse Version One

Launch a limited Resident Pulse on ordinary municipal questions.

Use it to test:

Do not use an early voluntary poll to decide individual rights or substitute for statutory processes.

39.169Publish Who Participated

When reporting a Pulse:

Show:

Do not say:

Owen Sound believes...

when 312 self-selected respondents participated.

Say:

Among the people who responded...

39.170Phone and Paper Alternatives

For important public consultation:

Provide reasonable non-digital participation.

Resident Government cannot become:

smartphone democracy.

39.171Vote Verification Development

If the Strong Vote system continues toward digital verification:

By Day 100, publish the privacy and governance requirements before selecting technology.

Verify the person.

Protect the opinion.

39.172No Political Profile

Participation in one municipal consultation should not become part of a permanent political profile.

Consultation data should never become campaign data.

39.173Mayor's Community Assembly Date

Set the first Community Assembly date and publish its purpose.

It should include:

Not a campaign rally.

39.174Public Questions in Advance

Allow residents to submit questions before the assembly.

Group duplicates.

Do not exclude critical questions merely because they are uncomfortable.

39.175First State of the City Update

Around Day 100, publish the second operational update after the Day-30 baseline.

The structure should include:

What Changed

What Did Not Change

What We Learned

What Worked

What Did Not Work

What Is Late

What Needs Council

What Needs Another Government

This should become routine.

39.176First "I Was Wrong" Requirement

By Day 100, if a material campaign assumption has proven incorrect:

Say so.

Do not wait until Year Four.

A good administration should be able to say:

We expected X. The evidence shows Y. We are changing course.

39.177Do Not Manufacture an Error for Optics

Likewise, do not perform humility theatrically.

If a major assumption was not wrong:

Do not invent one.

Correction is valuable because it is truthful.

39.178First Public Scorecard

Day 100 should produce the first full public scorecard.

The goal is not to show many green boxes.

The goal is to establish the discipline that will govern the term.

39.179Scorecard Colours Are Not Enough

Every score should link to:

A green dot with no definition is decoration.

39.180Scorecard Categories

The first version should preview the permanent categories later developed in Part XVI.

Finance

Tax pressure

Services

Infrastructure

Downtown

Housing

Business

Safety

Recreation

Youth

Accessibility

Privacy and information

Environment

Partnerships

Resident satisfaction

Commitments completed

Commitments missed

The exact measures will mature.

39.181Completed Means Completed

A commitment is not completed because:

Completion must correspond to the promise.

If the promise was:

launch the Start-Up Desk

then:

studying a Start-Up Desk

is not completion.

39.182Progress Is Still Worth Reporting

The fact that an initiative is not complete does not mean nothing happened.

Report:

40 per cent

only if that percentage has a defensible meaning.

Otherwise use milestone status.

39.183Missed Means Missed

If a Day-100 target was:

publish the service catalogue

and it is not published:

Mark:

Missed

then explain:

No quiet deadline changes.

39.184Delayed by Another Government

If delay belongs partly to:

show:

City submitted

Partner response due

current status

Do not blame vaguely.

39.185Delayed by the City

If the City failed to submit information on time:

Say that.

Accountability only works when it applies inward.

39.186First 100-Day Public Meeting

Hold a public review near or after Day 100.

Structure:

  1. commitments;
  2. finance;
  3. service;
  4. major projects;
  5. failures;
  6. next steps;
  7. resident questions.

Keep presentation concise enough to leave time for residents.

39.187No Applause Requirement

Residents attending a public review do not need to:

Criticism is part of the exercise.

39.188What Day 100 Should Feel Like

A resident should begin noticing:

Not every resident will use every tool.

The institutional difference should be visible.

39.189What Day 100 Should Not Look Like

It should not look like:

The first 100 days establish momentum without sacrificing judgement.

39.190Early Savings Should Be Small and Credible

If the first verified efficiency is:

$12,000 in cancelled duplicate software licences

publish it.

Do not feel pressure to claim:

millions saved

before evidence supports it.

Small real savings build credibility.

39.191Early Failures Should Be Small Too

That is one purpose of pilots.

If a $5,000 pilot fails:

We learned cheaply.

If a $5 million permanent program fails:

The lesson is much more expensive.

39.192Pilot Portfolio

By Day 100, the City may have several small pilots.

Possible examples:

Not every pilot needs to start simultaneously.

Staff capacity matters.

39.193Maximum Pilot Capacity

The City Manager should advise Council how many active pilots the organization can reasonably:

Too many experiments create no learning because nobody has time to evaluate them.

39.194Pilot Card

Every pilot should have a one-page public card.

Problem

Start

End

Cost

Partner

Population served

Measure

Stop conditions

Final decision date

Simple.

39.195Pilot Expiry

A pilot should expire unless:

deliberately extends or adopts it under the proper process.

No silent permanency.

39.196Stop Conditions

Examples may include:

Publish these before launch where practical.

39.197Modification Is Not Failure

A pilot may reveal:

The concept works, but the schedule is wrong.

Modify.

The choices are not only:

Learning is the purpose.

39.198Public Money Spent on Failed Pilot

If a pilot fails:

Publish the cost.

Do not hide it.

Then explain:

What larger cost did this test help us avoid?

If there was no useful learning:

Say that too.

39.199First 100-Day Accessibility Audit

Select key new public-facing tools and test them for accessibility.

Examples:

Do this before habits become entrenched.

39.200Accessibility Fix Log

Where issues are found:

Record:

Accessibility is ongoing maintenance.

39.201First Privacy Review Set

Complete privacy reviews for the highest-risk early tools:

Low-risk systems should not be burdened unnecessarily.

39.202Data Minimization Test

Every new form should be asked:

Do we actually need this field?

If not:

Remove it.

The safest personal data is data the City never collected.

39.203First Cybersecurity Executive Report

Council should receive a protected briefing at an appropriate level on:

The public should receive a safe summary.

39.204Publish Governance, Not Vulnerability

The public can know:

The City has identified three high-priority legacy-system risks.

It does not need:

Open government still uses judgement.

39.205First Canadian Capacity Review

Choose a small number of critical municipal supply categories.

Ask:

This begins Canadian-independence work in a measurable way.

39.206Do Not Create a Canadian-Only Procurement Rule Overnight

Any procurement change requires:

review.

The first 100 days build the evidence.

39.207Repair Before Replacement Pilot

Identify one asset class where repairability could produce savings.

Examples might include:

Compare:

39.208Open Playbook Starts Now

As the first systems are built, document:

Do not wait until Year Four to reconstruct how everything worked.

The open playbook should be built alongside the work.

39.209Publish Reusable Templates Early

Possible early reusable documents:

A small municipality elsewhere could use them immediately.

39.210No Branding Requirement

Another municipality should not need to call its program:

to reuse the method.

The process is what matters.

39.211First 100-Day Department Load Review

Ask:

Which departments are now overloaded because of implementation?

If staff capacity is becoming the bottleneck:

Slow down.

Do not sacrifice normal municipal service to prove the business plan is active.

39.212Prioritization Is Leadership

If ten projects compete for one department:

Council and administration need to rank them.

Saying:

Everything is priority one

is not leadership.

39.213No Staff Burnout Strategy

A four-year reform program cannot be built on:

Change needs to become normal work.

Not a 100-day sprint continuing for four years.

39.214Resident Workload Matters Too

Likewise:

Do not invite the same:

to fifteen different City consultations.

Coordinate engagement.

39.215Consultation Calendar

Publish a public consultation calendar.

Residents can see:

This makes participation easier.

39.216No Consultation After Decision

If the administration has already decided:

Do not call the meeting:

consultation.

Call it:

if that is what it is.

Words matter.

39.217Council Amendments Are Part of the Plan

Some initiatives will be:

by Council.

The Mayor should not treat amendments as sabotage.

Collective decision-making can make the plan better.

39.218Opposition Is Information

If residents strongly oppose a pilot:

Understand why.

Possible explanations:

Do not automatically conclude either:

critics are wrong

or:

critics must win.

Examine the evidence.

The Resident Government framework still applies.

No public poll determines:

Participation remains inside law.

39.220First 100-Day Rights Review

Every rights-sensitive pilot should have documented review.

Possible areas:

Do the review before enforcement.

39.221First 100-Day Conflict Review

Any initiative involving:

requires appropriate independent conflict process.

The new administration should set this precedent early.

39.222No Favour Economy

A supporter who says:

I helped elect you, now help my company

receives the same public process as everyone else.

The first 100 days should make that expectation unmistakable.

39.223No Punishment Economy

Likewise, an opponent does not receive:

because they opposed the Mayor.

Public authority is not electoral revenge.

39.224First Public Satisfaction Baseline

By Day 100, establish a simple baseline for resident experience with City Hall.

Possible questions:

Did you know where to start?

Was the answer clear?

Were you treated respectfully?

Did you understand the next step?

Was the response timely?

Keep surveys short enough that people answer them.

39.225Do Not Manipulate Satisfaction Surveys

Do not ask:

How satisfied are you with our excellent new service?

Use neutral wording.

39.226Complaint Data Is Improvement Data

Aggregate recurring complaints.

Ask:

What process produced this frustration?

Do not treat criticism merely as:

39.227Complaints About Staff

Individual employee concerns require appropriate:

process.

Do not publish personnel details to demonstrate transparency.

39.228Complaints About Mayor

Criticism of the Mayor is not a service risk.

Do not use:

to retaliate against ordinary political criticism.

39.229First Community Assembly

If timing and Council calendar allow, hold the first Mayor's Community Assembly around or soon after Day 100.

Agenda:

Baseline

First decisions

First pilots

First failures

Major unresolved files

Resident questions

Do not fill two hours with speeches.

39.230Mayor Answers Jurisdiction Questions Honestly

If asked:

Why haven't you fixed healthcare?

answer:

Here is what the City controls, here is what Ontario controls, and here is what we have asked Ontario to do.

That is the purpose of the Authority Map.

39.231First 100-Day Intergovernmental Report

Publish one combined page showing:

SON

Relationship status.

Grey County

Roads, planning, housing, transit.

Ontario

Current asks.

Canada

Harbour and federal files.

Residents should understand that outside-government work is still measurable work.

39.232Do Not Claim Partnership Before Agreement

Use status such as:

Requested

In Discussion

Partner Agreed

Under Development

Do not put another organization's logo on a proposal before permission.

39.233Day-100 Budget Impact

Publish the complete incremental cost of first-100-day implementation.

Possible categories:

Existing Staff Time

Estimated where useful.

New Operating Expenditure

Approved amount.

Pilot Expenditure

Approved amount.

Professional Review

Legal, technical or consulting.

Future Capital Commitments

None unless separately approved.

Residents should know what reform costs.

39.234Reform Is Not Free

Open government can:

It also requires:

Do not market reform as costless.

The question is:

Does the value exceed the cost?

39.235Day-100 Staffing Impact

Report whether the plan caused:

If no new position was created:

Good.

If one was justified:

Explain the business case.

39.236First 100-Day External Consulting Register

Where consultants were retained for implementation:

Show:

Do not hide reform consulting inside broad professional-services accounts where disclosure is appropriate.

39.237Use Consultants for Expertise, Not Decisions

A consultant can:

Council and staff remain accountable for public decisions.

Do not outsource political judgement.

39.238First 100-Day Risk Register

Publish a high-level list of major implementation risks.

Possible examples:

The public should see what could derail the plan.

39.239Risk Has an Owner

Every significant risk needs:

Unowned risks become surprises.

39.240First 100-Day Unknowns Register

This may be equally important.

List major questions still unanswered.

Examples:

Harbour liability

Unknown until federal records received.

Crossing cost

Unknown until current study.

Penny economics

Unknown until pilot model.

map.ca public structure

Unknown until independent review.

Saying:

unknown

is not weakness.

Pretending certainty is.

39.241What Should Be Completed by Day 100

Reasonable completion targets may include:

These are institutional foundations.

39.242What May Be Piloting by Day 100

Depending on Council approval and staff capacity:

Not all need to launch.

39.243What Should Still Be Under Study

Likely examples:

This is deliberate.

39.244What Should Still Be Forbidden by Governance

By Day 100 there should still be no:

Some safeguards should never graduate from:

No.

39.245The 100-Day Public Report

The report should use the same format for every major commitment.

We Promised

Original commitment.

We Learned

Baseline and evidence.

We Did

Action.

It Cost

Actual amount.

Result

Measure.

Status

Complete, active, pilot, delayed, stopped.

Next

Year One action.

This prevents narrative-only reporting.

39.246Include the Source Promise

Where practical, the public report should show the original campaign wording beside the implemented version.

That lets residents see where an idea:

No rewriting campaign history.

39.247Explain Necessary Changes

If the implemented policy differs:

Explain:

legal review changed this

or

the numbers did not support this

or

the partner declined

or

Council chose another approach.

Every change should have a reason.

39.248The Day-100 Mayor Statement

The Mayor's public statement should answer five questions.

What are we proud of?

What did not work?

What surprised us?

What did we change?

What are the next three priorities?

Keep it grounded.

39.249No 100-Day Victory Video as Substitute for the Report

Communications can summarize.

The detailed public record remains.

A short video is not accountability.

39.250First Independent Public Check

Where practical, ask appropriate:

to validate the parts of the scorecard they legitimately own.

The Mayor should not certify their own savings.

39.251Finance Verifies Finance

Treasurer or appropriate financial staff verify:

39.252Department Verifies Service Data

The operational department confirms:

39.253Residents Verify Experience

Resident surveys provide:

Do not substitute one source for another.

39.254Professional Services Verify Technical Claims

Engineers, planners and other qualified professionals verify:

The Mayor does not certify bridge capacity from a spreadsheet.

39.255Public Trust Comes From Separation

The Mayor proposes.

Council decides where required.

Staff administer.

Professionals verify.

Residents judge.

That separation is healthy.

39.256First 100-Day Exit Decisions

At least one initiative may deserve:

Stop.

If so:

Stop it.

A first-100-day plan proving that City Hall can abandon a weak idea would be a sign of maturity.

39.257First 100-Day Expansion Decisions

Some pilots may show obvious benefit.

If so:

Do not expand automatically.

Bring:

to the proper approval process.

39.258First 100-Day Maintenance Decisions

Some pilots may simply continue at the same small scale for more evidence.

That is valid too.

Government does not need a dramatic answer to every question immediately.

39.259The 100-Day Principle of Reversibility

The less certain we are:

The more reversible the first action should be.

Temporary furniture before permanent plaza construction.

Pilot transit before permanent fare policy.

Open standard before platform transfer.

Study before bridge.

Due diligence before harbour ownership.

That is disciplined innovation.

39.260The 100-Day Principle of Proportionality

The greater the potential harm:

The stronger the review.

A public calendar can move faster than:

A bench pilot can move faster than:

A merchant survey can move faster than:

Good governance scales review to consequence.

39.261The 100-Day Principle of Independence

The Mayor should deliberately make parts of the system less dependent upon the Mayor.

By Day 100:

That is how a plan becomes institutional.

39.262The 100-Day Principle of Local Responsibility

Ask after every external-government meeting:

What can Owen Sound do now without waiting?

Do that.

39.263The 100-Day Principle of Honest Dependency

Then ask:

What truly cannot proceed without another government?

Put that into the appropriate:

register.

Do not pretend City Hall controls the answer.

39.264The 100-Day Principle of Public Choice

Where residents genuinely have meaningful alternatives to choose between:

Present them clearly.

Where professional or legal requirements constrain the choice:

Explain the constraint.

Participation improves when people know what is actually open for decision.

39.265The 100-Day Principle of Equal Service

Every new system must work for:

No political customer class.

39.266The 100-Day Principle of Family and Community

Early reforms should make it easier to:

These are practical ways municipal government can strengthen families and community without trying to control them.

39.267The 100-Day Principle of Canadian Capacity

Early Canadian-independence work should be modest and real.

Examples:

Not:

declare economic independence.

Capability first.

39.268The 100-Day Principle of Open Failure

By Day 100, the City should already have demonstrated:

A mistake can be acknowledged without a scandal being necessary.

If a pilot underperforms:

Report.

Adjust.

This lowers the political cost of learning.

39.269Day-100 Final Test

A resident should be able to ask:

What has changed since inauguration?

and receive a concrete answer.

Not merely:

The Mayor has been very busy.

The answer should include:

The First 100 Days Commitment

The first 100 days are where the four-year business plan begins proving whether it is a business plan or merely a campaign document.

The commitment is:

Publish every major promise and its status.

Assign every active commitment a responsible municipal owner.

Publish the authority behind each promise.

Make the first financial baseline understandable.

Use complete lifecycle costing for new proposals.

Verify savings before declaring an Efficiency Dividend.

Never call deferred maintenance a saving.

Open procurement information to small and local vendors without creating favourites.

Publish upcoming procurement opportunities where appropriate.

Begin testing technology exit before major renewals.

Cancel genuine duplicate technology costs only after records and continuity are protected.

Launch the first Service Catalogue.

Publish realistic service standards.

Make service standards mean a meaningful answer, not an automatic acknowledgement.

Implement No Wrong Door.

Launch the Start-Up Desk with one public contact and one coordinated municipal pathway.

Launch Before You Sign guidance for prospective businesses.

Implement the ten-business-day business standard only with clear eligibility and honest clock rules.

Waive only eligible City-controlled fees where Council lawfully adopts that guarantee.

Begin the Business Red-Tape Log.

Measure current local merchant payment costs before making public savings claims.

Make Shop Local payment choices voluntary.

Do not launch the Owen Sound Penny until funding, accounting, fraud, privacy and redemption are real.

Keep the Penny a reward, not a currency.

Launch a neutral local business directory only if it fills a real gap.

No paid basic ranking.

Complete the Shop Local delivery feasibility work before municipal delivery begins.

Prefer existing local couriers where they can solve the problem.

Test Community Pooling narrowly before considering a cooperative.

Give local merchants a fair first opportunity to meet pooled demand.

Launch a small First to Action pilot only after the backend service workflow exists.

Keep emergencies out of the municipal issue-reporting system.

Let councillors use the same ordinary service workflow as residents where appropriate.

Use Standing Work Lists to batch recurring problems.

Complete at least one root-cause review.

Test employee-generated improvement ideas.

Build labour partnership without bypassing collective bargaining.

Do not manufacture savings through layoffs or disappearing work.

Publish Infrastructure Index version one.

Allow Unknown as an honest condition where information is incomplete.

Publish a five-year capital look-ahead.

Test One Street, One Plan on a real corridor.

Prepare thoroughly for Grey County road transfers.

Judge hybrid planning by applicant service, cost, local knowledge and accountability.

Begin obvious downtown maintenance improvements without waiting for a megaproject.

Publish a Downtown Operating Plan.

Use temporary Civic Square improvements before permanent construction.

Apply the Tuesday Test.

Approve a 2nd Avenue East pilot only after traffic, business, resident, accessibility and emergency requirements are ready.

Publish success criteria before the pilot begins.

Publish the first River Spine Missing-Link Map.

Launch an Owen Sound Outside beginner guide.

Inventory equipment access before purchasing municipal inventory.

Publish the first Enthusiast Map and opportunity gaps.

Launch Housing Navigation.

Keep housing navigation separate from guaranteed approval.

Version-date outside housing programs.

Separate housing approvals from units actually built.

Inventory municipal land without promising its disposal.

Apply the Family-Friendly Neighbourhood Test to at least one practical area.

Publish the first Seniors Independence findings.

Bring the free-senior-transit business case to Council.

Pilot before making a permanent fare commitment where practical.

Evaluate the scheduled senior ride with Grey County and health partners rather than assigning their staff.

Launch winter help only with clear safety and privacy boundaries.

Publish the Community Safety baseline before claiming a Safety Dividend.

Approve the Safety Dividend rules before claiming financial savings.

Recognize increased police capacity as a possible dividend before budget savings exist.

Pilot Right Responder approaches only where the alternative responder is genuinely qualified.

Treat downtown safety as an infrastructure, service and policing question together.

Complete the first targeted lighting audit.

Establish a neutral Community Partnership Standard.

Publish significant municipal grants and in-kind support.

Keep grants separate from procurement contracts.

Use the same public-service standard for faith and secular partners.

Launch or improve a community resource directory without mapping vulnerable residents.

Create a free community-calendar standard without paid ranking or behavioural tracking.

Approve a Civic Corps pilot only after employment, volunteer, co-op, safety and privacy roles are clear.

Pay young people when the work should be paid.

Never turn Civic Corps into free replacement labour.

Map youth opportunities, not youth.

Use students to gather public information only where staff can validate it.

Begin responsible-data education with existing community institutions.

Expand public Wi-Fi only where an actual access gap and sustainable operating model exist.

Launch a recycled-device pilot only if privacy, battery, security and support questions are solved.

Complete Digital Systems Index version one.

Adopt practical municipal AI rules.

Keep humans accountable for consequential municipal decisions.

Complete the first map.ca public-purpose and ownership review.

Do not rush a map.ca transfer to satisfy a 100-day deadline.

Publish the platform-neutral Public Property Information Standard before adopting a proprietary property platform.

Enforce existing sign rules before rewriting them.

Begin sign consultation without promising a predetermined ban.

Establish the first leadership relationship with Saugeen Ojibway Nation by listening first.

Do not measure reconciliation by whether a document is signed in 100 days.

Ask Canada specific questions concerning harbour ownership, transfer, assets, dredging, liabilities and funding.

Publish what Canada answered and what remains unanswered.

Do not acquire the harbour before complete due diligence.

Prepare Grey County road, planning, housing, paramedic and transit files for real decisions.

Bring Owen Sound's regional transit priorities forward early enough to matter.

Publish a short Ontario Ask Book.

Ask Ontario precisely for strong-mayor reform if Council wants it.

Publish verified provincial mandate costs.

Ask Ontario for specific municipal pilots rather than vague autonomy.

Publish a short Federal Ask Book.

Correct outdated federal housing claims.

Prove a broadband gap before asking for broadband infrastructure money.

Scope the east-west crossing as an evidence study, not a predetermined construction project.

Include the no-build alternative.

Preserve reasonable corridors while the evidence is gathered.

Launch Resident Pulse with honest limits on what self-selected participation represents.

Keep phone and paper options for important consultations.

Protect political opinion from permanent profiling.

Schedule the first Mayor's Community Assembly.

Publish the first full State of the City update.

Correct any material campaign assumption that evidence has disproved.

Publish the first complete public scorecard.

Define completed, delayed, stopped and missed honestly.

Publish the cost and result of every meaningful pilot.

Test accessibility before systems become entrenched.

Apply privacy review according to risk.

Publish cybersecurity governance without publishing vulnerabilities.

Begin Canadian supply-resilience work with a few critical systems rather than slogans.

Document reusable municipal tools as they are built.

Do not overload staff or residents in the name of speed.

Publish consultation dates and purposes.

Allow Council to amend the plan.

Treat opposition as information rather than disloyalty.

Keep rights outside popularity contests.

Apply the conflict firewall immediately and visibly.

Treat supporters and opponents equally at City Hall.

Establish a resident-service satisfaction baseline.

Publish the first 100-day implementation cost.

Publish material consulting and staffing impacts.

Publish the major implementation risks and unknowns.

Stop at least any initiative that evidence clearly shows should stop.

Expand pilots only after results are reviewed.

Prefer reversible first steps when uncertainty is high.

Make the operating system less dependent upon the Mayor as the term progresses.

At Day 100, residents should not be asked to trust that change is happening behind the scenes.

They should be able to see it.

Not through slogans.

Through:

The first 30 days answer:

Where are we?

The first 100 days answer:

Can this administration actually turn evidence into action?

That is the test.

Build the system. Make the first decisions. Test the uncertain ideas. Publish the results. Correct what is wrong. Then enter Year One with evidence rather than momentum alone.

← Chapter 38: The First 30 Days: Establish the Operating SystemChapter 40: Year One: Build the Foundation and Prove the Model →