Owen Sound: A Four-Year City Business Plan

Home › The Public Scorecard › Chapter 47

The Public Scorecard

Chapter 47Infrastructure: The Public Infrastructure Scorecard

10,469 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

Residents experience municipal infrastructure every day.

They drive on it.

Walk on it.

Drink through it.

Flush into it.

Cross it.

Play in it.

Depend upon it during storms, fires and emergencies.

Much of it is invisible until it fails.

That creates one of the central problems in municipal government:

Political attention naturally goes to new things. Good asset management often means spending money on things residents cannot see.

A new building gets a ribbon cutting.

A replaced underground valve usually does not.

A new park feature gets photographs.

A repaired sewer may disappear under pavement before anyone sees it.

The Infrastructure Scorecard should make responsible maintenance visible.

The principle is:

Know what we own. Know its condition. Know what can fail. Maintain before failure where practical. Show what we are postponing. Never make infrastructure look healthy by refusing to inspect it.

The City's original Town at Work framework already calls for an infrastructure index, standing work lists, measurable maintenance and a more systematic approach to municipal assets.

The Scorecard turns that philosophy into public evidence.

47.1Purpose

The Infrastructure Scorecard should answer:

What does Owen Sound own?

What condition is it in?

How confident are we in that assessment?

What requires repair?

What can wait?

What is being maintained preventively?

What keeps failing reactively?

What has been deliberately deferred?

What is unfunded?

What major projects are underway?

Are projects on budget?

Are projects on schedule?

What new infrastructure are we adding?

What future operating costs come with it?

What responsibilities have been transferred from another government?

What liabilities will future Councils inherit?

Those are the questions residents need answered before discussing another major capital project.

47.2Infrastructure Is More Than Roads

The public scorecard should recognize major asset classes such as:

The exact inventory should follow professional municipal asset-management practice.

47.3Not Every Asset Belongs on the Public Map

Some infrastructure information may create:

risk.

The City can publish:

without exposing sensitive details such as:

Open Government is not open vulnerability.

47.4Public Layer and Professional Layer

The Infrastructure Index should have at least two conceptual levels.

Public Layer

Residents see:

Professional Layer

Staff maintain:

information.

Residents need accountability.

Operators need detail.

47.5Asset Ownership

Every major asset should have a known owner.

Possible:

City

Grey County

Ontario

Canada

Utility

Private

Shared or Agreement-Based

The public should not have to guess who maintains:

47.6Ownership Is Not Maintenance Responsibility

Sometimes one body owns an asset while another maintains it.

Where that occurs:

Show both.

47.7Infrastructure Register

The City should maintain an authoritative infrastructure register.

For major assets it should identify:

Asset

Asset class

Owner

Responsible department

Condition

Condition date

Confidence

Expected lifecycle stage

Planned work

Major financial exposure

The professional system can contain much more detail.

47.8Asset Count Is Not the Goal

The City should not celebrate:

We catalogued 48,237 assets.

The purpose is better decisions.

The important question is:

Does the inventory cover the assets that could create major service, safety or financial consequences if they fail?

47.9Criticality

Each important asset class should use an appropriate criticality framework.

A small park bench and a major water component do not have equal consequences.

Possible factors:

47.10Condition

Condition should be reported using a consistent scale where appropriate.

For example:

Very Good

Good

Fair

Poor

Very Poor

Unknown

Professional asset classes may require different technical systems.

Do not force everything into one rating if it reduces accuracy.

47.11Condition Is Not Age

An old asset may be:

A newer asset may fail early.

Report actual condition where known.

47.12Age Still Matters

Age helps inform:

It is one input.

Not the final conclusion.

47.13Condition Date

Every condition assessment should have:

A "Good" rating from 14 years ago may no longer be useful.

47.14Assessment Method

Where meaningful, identify whether condition comes from:

Not all condition ratings have equal certainty.

47.15Condition Confidence

The scorecard should report confidence.

Possible:

High

Recent professional evidence.

Moderate

Useful information with some uncertainty.

Low

Older or incomplete information.

Unknown

No reliable current assessment.

47.16Confidence Matters

The difference between:

Bridge condition: Fair, high confidence

and

Bridge condition: Fair, low confidence

is important.

The second may mean:

inspect before deciding.

47.17Unknown Is a Real Status

Do not guess.

Use:

Unknown

when condition is not adequately known.

An honest unknown is better than false precision.

47.18Unknown Reduction

A major four-year scorecard measure should be:

percentage of critical infrastructure with sufficiently reliable condition information.

Desired direction:

47.19Critical Condition Coverage

Possible measure:

Critical Asset Condition Coverage = Critical Assets With Current Sufficient Condition Information ÷ Total Critical Assets × 100

Professional staff should define:

47.20Do Not Improve Coverage by Redefining Critical

Do not remove difficult assets from the denominator simply to improve the score.

Publish methodology changes.

47.21Inspection Backlog

Track overdue critical inspections.

Possible measure:

Overdue Critical Inspections = Required Critical Asset Inspections Past Their Scheduled Date

This is often more important than the total number of inspections completed.

47.22Inspection Completion Rate

Possible:

Scheduled Inspection Completion Rate = Scheduled Inspections Completed Within Required Period ÷ Scheduled Inspections Due × 100

Use by asset class where appropriate.

47.23Inspection Is Not Maintenance

Inspecting a failing asset does not fix it.

Track both.

47.24Maintenance

The scorecard should distinguish:

Preventive Maintenance

Work completed before failure according to condition, cycle or professional judgement.

Reactive Maintenance

Work required because something failed or became deficient.

Emergency Repair

Urgent response to service or safety failure.

47.25Preventive Maintenance Ratio

Where meaningful:

Preventive Maintenance Share = Preventive Maintenance Expenditure or Work Hours ÷ Total Comparable Maintenance Activity × 100

Use the denominator most appropriate to each service.

Do not create one City-wide ratio if the data is not comparable.

47.26Preventive Is Not Always Better

Some low-cost, low-risk assets may rationally be:

Professional asset management decides.

The scorecard should not turn:

100% preventive maintenance

into a universal goal.

47.27Emergency Repair Trend

Track emergency repair frequency and cost for important asset classes.

A rising emergency trend can indicate:

Investigate.

47.28Emergency Repair Is Not Automatically Failure

Severe weather or unpredictable component failure can happen even in a well-managed system.

Use trend and context.

47.29Reactive Work Share

Where useful:

Compare planned versus reactive work.

If reactive work dominates a major asset class year after year:

Ask why.

47.30The Pothole Example

A pothole report should not only produce:

patch completed.

Repeated failure may indicate:

Service data should feed asset management.

47.31Repeat Repair

Track locations or assets receiving repeated repair.

Possible measure:

Repeat Repair Rate = Assets Requiring Repeat Corrective Work Within a Defined Period ÷ Assets Repaired

Use only where technically meaningful.

47.32Repeat Repair Trigger

A recurring issue should trigger:

where appropriate.

47.33Do Not Reward Cheap Repeated Patches

A scorecard based only on:

can create the wrong behaviour.

Measure recurrence.

47.34Deferred Maintenance

Deferred maintenance means known work is postponed beyond the preferred timing.

This should be visible.

47.35Deferred Maintenance Ledger

For significant deferred work, show:

Asset

Work needed

Reason deferred

Risk

Estimated future timing

Current estimated cost

Potential consequence

Do not bury known deferral in staff notes.

47.36Deferral Can Be Legitimate

The City cannot repair everything simultaneously.

Deferral may be reasonable because of:

The important point is:

We know we deferred it.

47.37Deferral Is Not Saving

If a $300,000 repair is postponed:

The City did not:

save $300,000

unless the need legitimately disappeared.

47.38Deferral Cost Escalation

Where professional estimates support it:

Show whether delay is likely to:

Do not invent precise future escalation where uncertain.

47.39Deferred Maintenance Trend

At least annually show whether the known deferred-maintenance exposure is:

Increasing

Stable

Decreasing

with explanation.

47.40Backlog Dollars Need Context

A large dollar backlog does not automatically mean:

Some work may be planned over decades.

Separate:

47.41Infrastructure Risk

A useful framework combines:

Probability of failure

and

Consequence of failure

This should guide priority more than political visibility.

47.42High-Risk Asset

A high-risk asset may be:

if failure consequences are very severe.

Condition alone is not risk.

47.43Low-Risk Poor Asset

A poor-condition low-consequence asset may reasonably wait while higher-consequence assets receive funding first.

Explain the priority framework.

47.44Risk Categories

Possible public categories:

Critical

High

Moderate

Low

Under Assessment

The technical methodology should be professional.

47.45Do Not Publish Exploitable Risk Details

A public "Critical" label should not expose:

sensitive infrastructure.

Provide accountability without operational vulnerability.

47.46High-Risk Asset Count

A headline measure can show:

number or value of high and critical infrastructure risks with funded mitigation plans.

47.47Mitigation Plan

A high-risk asset may be addressed through:

Not every risk requires immediate replacement.

47.48Unfunded Risk

The Scorecard should distinguish:

Risk identified and funded

from

risk identified but unfunded.

47.49Unfunded Infrastructure Exposure

Finance can report the dollar exposure.

Infrastructure should report:

These two scorecards should align.

47.50Lifecycle

For major asset classes:

Show expected lifecycle planning.

Do not imply an exact replacement date when actual life depends on condition.

47.51Remaining Service Life

Where professionally estimated:

Use a range.

Example:

Estimated remaining service life: 5 to 10 years.

Better than false certainty.

47.52Replacement Is Not Automatic at Age Limit

Condition may justify:

Use engineering judgement.

47.53Rehabilitation Versus Replacement

Track whether the City is choosing:

Lifecycle value matters.

47.54Lowest Capital Cost Is Not Always Lowest Lifecycle Cost

A cheaper replacement may cost more over:

Use complete cost.

47.55Infrastructure Funding Gap

The asset plan should estimate how much long-term renewal need exists compared with planned funding.

The Scorecard can summarize this.

47.56Funding Gap Is Not Tomorrow's Bill

A 20-year infrastructure funding gap does not mean:

Council needs to raise that amount next year.

Explain the planning horizon.

47.57Annual Renewal Need

Where professionally supportable:

Show estimated average annual lifecycle renewal requirement.

Compare with:

47.58Renewal Funding Ratio

Possible planning measure:

Renewal Funding Ratio = Planned Long-Term Renewal Funding ÷ Estimated Long-Term Renewal Need × 100

Use cautiously.

This is a planning indicator.

Not a precise engineering truth.

47.59Capital Reserve Contributions

Show whether major asset classes are building sufficient reserves over time.

Cross-reference Section 44.

47.60Infrastructure Debt

Where major asset renewal uses debt:

Show:

Debt should not outlive the useful asset without justification.

47.61Grants

Show grant-supported infrastructure with:

A grant-funded asset is still a City asset after construction if the City owns it.

47.62Grant Readiness

Maintain a shelf of professionally justified, sufficiently mature projects.

Do not invent projects when a grant program opens.

47.63Project Readiness Categories

Possible:

Need Identified

Business Case

Preliminary Design

Approvals

Tender Ready

Construction

This helps residents understand where a project actually sits.

47.64Approved Is Not Construction Ready

A Council priority may still need:

Use accurate status.

47.65Major Capital Project Cards

Every material active capital project should have a public card.

47.66Project Card Fields

Project

Public purpose

Asset

Approved budget

Outside funding

City share

Amount committed

Amount spent

Forecast final cost

Start

Current stage

Forecast completion

Major risk

Last update

47.67Original Budget

Preserve the original approved budget.

47.68Current Approved Budget

If Council increases budget:

Show that separately.

47.69Forecast Final Cost

Residents should see where management currently expects the project to finish.

47.70Original Versus Current

Example:

Original approved budget: $8 million

Current approved budget: $9.3 million

Forecast final cost: $9.1 million

That tells the story.

47.71Do Not Rewrite the Original Budget

Never replace the old number in history after Council approves more money.

Keep the trail.

47.72Project Schedule

Likewise show:

Original forecast completion

Current forecast completion

Actual completion

when finished.

47.73Schedule Variance

Possible:

Schedule Variance = Current Forecast Completion Date - Original Approved Forecast Completion Date

Use appropriate units.

47.74Schedule Delay Needs Reason

Possible causes:

Explain material delays.

47.75Delay Is Not Automatically Failure

A project delayed to correct:

may be responsible management.

47.76Early Is Not Automatically Success

A project finished early but poorly is not good infrastructure.

Quality matters.

47.77Scope

Maintain a clear project scope.

47.78Scope Added

If Council adds:

work:

Show that the budget increased partly because scope increased.

47.79Scope Removed

If work is removed to stay under budget:

Disclose it.

Do not call the project:

under budget

without noting reduced scope.

47.80Change Orders

Publish cumulative material change orders.

Not every minor field adjustment needs a public headline.

Materiality matters.

47.81Change Order Cause

Possible:

Unknown condition

design error

owner-requested scope change

regulatory

market

other

Over time this can improve project management.

47.82Design Error Trend

If repeated design errors create significant change orders:

Investigate consultant or internal process.

Do not use one incident to condemn an entire profession.

47.83Unknown Underground Conditions

Municipal infrastructure often involves uncertainty below ground.

Contingency exists for a reason.

47.84Contingency

Show whether project contingency is:

at a high level for significant projects.

Do not make every small draw a political event.

47.85Contingency Is Not Free Money

Unused contingency should not automatically finance unrelated extras.

Follow project and financial governance.

47.86Project Quality

After completion:

Conduct appropriate:

work.

47.87Substantial Completion Versus Final Completion

Where construction contracts use different completion stages:

Explain them.

Do not call a project fully complete while major deficiencies remain.

47.88Deficiency List

A public project can open with minor deficiencies.

Report material unresolved items appropriately.

47.89Warranty Issues

Track significant early failures.

This can inform future procurement.

47.90Project Post-Mortem

For major projects:

Ask:

Budget accurate?

Schedule accurate?

Scope stable?

Procurement worked?

What surprised us?

What should change next time?

Institutional learning.

47.91Roads

Road reporting should go beyond:

47.92Road Condition

Publish road-condition information using the City's professional pavement-management methodology.

47.93Do Not Invent a Universal Road Score

If the City uses a recognized index or internal system:

Explain it.

Do not replace it with an arbitrary political grade.

47.94Road Condition Distribution

Show percentage of road network in:

or the appropriate professional categories.

47.95Lane-Kilometres or Centreline Kilometres

Use the correct road-length measure consistently.

Do not switch between them without explanation.

47.96Road Renewal

Track:

where meaningful.

47.97Kilometres Alone Can Mislead

One kilometre of full reconstruction can cost far more and create more value than one kilometre of surface treatment.

Report treatment type.

47.98Road Maintenance

Track major categories such as:

according to City practice.

47.99Preventive Pavement Work

Measure whether the City is intervening before roads reach expensive failure.

47.100Worst-First Is Not Always Best

Always rebuilding the worst road can be poor asset management if lower-cost preventive work on several fair roads avoids future failures.

Explain prioritization.

47.101Road Priority

Possible factors:

47.102Political Street Selection

Do not select road projects because:

Use the published priority framework.

47.103Sidewalks

Track:

47.104Sidewalk Hazard Response

Measure appropriate response to:

under professional and legal standards.

47.105Sidewalk Network Gaps

Not every street requires identical infrastructure.

Identify gaps according to:

47.106Accessibility Priority

A short missing sidewalk link may be more important than a longer cosmetic reconstruction.

Public benefit matters.

47.107Curb Ramps

Track important accessibility upgrades.

Do not count:

without checking whether the resulting route is usable.

47.108Crossings

Track selected:

safety improvements.

Public safety metrics belong with Section 51 as well.

47.109Bridges

Every City-controlled bridge should have:

according to applicable professional and legal requirements.

47.110Bridge Inspection Status

Publicly show:

Current

Inspection due

Under review

without exposing sensitive technical vulnerabilities.

47.111Bridge Condition

Use professional categories.

47.112Load Restrictions

Where lawful and public:

Make active restrictions easy to find.

47.113Bridge Rehabilitation

Track:

47.114East-West Crossing Is Not Existing-Asset Maintenance

If a new crossing advances:

Keep it separate from:

Residents should see how new capital competes with existing asset needs.

47.115Culverts

Major culverts can create significant:

risk.

Include critical ones in asset planning.

47.116Small Asset, Large Consequence

Physical size does not equal importance.

A failed culvert can close a road.

47.117Stormwater

Stormwater infrastructure deserves its own public view.

47.118Stormwater Assets

Potential categories:

Do not publish sensitive operational details unnecessarily.

47.119Flooding Complaints

Aggregate recurring flood or drainage reports can help identify infrastructure priorities.

Protect household information.

47.120Repeat Flooding

Repeated complaints at an area should trigger professional analysis.

Do not publish a map that labels individual homes:

flood-prone

without careful legal, privacy and accuracy review.

47.121Storm Event Context

Severe rainfall can exceed design capacity.

Distinguish:

47.122Climate and Weather Design

Use current professional design information for:

where relevant.

Infrastructure should be designed for credible future conditions.

47.123Water Infrastructure

Water infrastructure should be managed under its applicable regulatory and professional framework.

The public Scorecard should summarize:

without publishing sensitive security information.

47.124Water Quality Is Separate From Asset Condition

A system can meet water-quality standards while some infrastructure needs renewal.

Do not combine the two.

47.125Watermain Breaks

A useful operational measure may be:

Trend matters.

47.126Break Trend Context

More breaks can indicate:

Investigate cause.

47.127Water Loss

If the City professionally measures non-revenue water or system loss:

Use it carefully.

Not every apparent loss is a physical leak.

47.128Water Infrastructure Funding

Where water is funded through user rates:

Keep funding distinctions clear.

Property-tax scorecards should not imply all water capital comes from taxes.

47.129Wastewater

Similarly, report:

47.130Wastewater Capacity

Where growth depends upon treatment or collection capacity:

Make high-level capacity information available.

Do not publish sensitive system vulnerabilities.

47.131Sewer Backups

Track municipal-system-related incidents in aggregate where meaningful.

Protect individual households.

47.132Inflow and Infiltration

Where this is a significant system issue:

Track professional improvement measures.

Avoid making technical claims without adequate measurement.

47.133Combined Street Work

Whenever road reconstruction is planned:

Review underground:

needs first.

47.134One Street, One Plan

This becomes a headline coordination measure.

47.135Coordination Rate

Possible measure:

Percentage of major road reconstruction projects that completed documented underground and related asset coordination before final design.

This may be more meaningful than trying to calculate speculative avoided excavation.

47.136Avoided Repeat Excavation

Where actual cases exist:

Report them.

Do not invent savings for hypothetical future road cuts.

47.137Utility Coordination

Coordinate where practical with:

47.138Utility Delay

If outside utility work delays a project:

Show the cause accurately.

Do not blame City crews.

47.139Utility Cut After Resurfacing

Track significant cases where newly improved streets are cut soon after construction.

Ask why.

Some may be unavoidable.

47.140Street Cut Policy

Use appropriate permit and restoration standards.

Do not create a financial punishment unrelated to actual public cost.

47.141Streetlights

Track:

where useful.

47.142Streetlight Repeated Failure

Repeated outages at the same asset should trigger deeper review.

47.143Lighting Quality

More light is not always better.

Consider:

47.144Traffic Signals

Critical traffic-control assets should have:

plans.

47.145Signal Downtime

Track significant unplanned outages.

47.146Signage

Municipal traffic and wayfinding signs require maintenance too.

Do not confuse this with the separate real-estate sign policy.

47.147Trails

Track municipal trail:

47.148Trail Closure

Make closures current and easy to find.

An outdated "open" status can create safety problems.

47.149River Infrastructure

For public river-related assets such as:

include condition and maintenance.

If Owen Sound owns or assumes harbour-related infrastructure:

Add those assets only when ownership and responsibility are clear.

Do not include federally owned assets as City assets.

47.151Federal Port Assets

The City may track federal harbour issues in the intergovernmental file.

It should not report those assets as though City Hall controls their maintenance.

47.152Buildings

Municipal facilities should have a public high-level condition view.

47.153Building Categories

Possible:

Use actual City portfolio categories.

47.154Facility Condition

Track:

needs at an appropriate summary level.

47.155Facility Condition Index

If staff use a professional Facility Condition Index or another methodology:

Explain it.

Do not invent a new political index.

47.156Building Maintenance

Separate:

47.157Roof Example

A roof may still function while replacement is foreseeable.

The Scorecard should allow:

Good today, major replacement forecast within five years.

Condition and capital timing can both be true.

47.158Facility Utilization

Before adding new space:

Measure use of existing facilities where practical.

47.159Use Before Building

A low-utilization building may represent:

rather than need for another facility.

47.160Utilization Is Not the Only Test

A fire hall or emergency facility may be essential even if conventional utilization metrics appear low.

Use the right measure.

47.161Recreation Facilities

Track:

Participation belongs in Section 52.

47.162Pool or Arena Example

A facility may have strong participation but poor physical condition.

Both scorecards matter.

47.163Parks

Parks contain many assets.

Do not attempt to individually score every:

Focus on:

47.164Playground Inspections

Track applicable inspection completion.

47.165Park Accessibility

Measure significant access improvements.

47.166Park Renewal

Show major scheduled:

renewal.

47.167Trees

Trees can be both:

Track through the appropriate forestry program.

47.168Tree Inventory

If a public inventory exists:

Do not publish sensitive private-property or risk information improperly.

47.169Tree Maintenance

Possible measures:

47.170Planting Count Is Not Enough

A dead newly planted tree is not successful infrastructure.

Track establishment or survival where feasible.

47.171Fleet

Municipal fleet is infrastructure too.

47.172Fleet Asset Register

Track:

47.173Fleet Replacement

Do not replace vehicles simply because they reach a fixed age.

Use:

47.174Maintenance Cost Trend

A vehicle with rising repair cost may still be cheaper to keep.

Use lifecycle analysis.

47.175Downtime

For critical fleet:

Track days unavailable where meaningful.

47.176Spare Capacity

Emergency and winter fleets may need redundancy.

A vehicle sitting unused some days is not automatically waste.

Reliability has value.

47.177Utilization

Track usage for appropriate non-critical fleet.

Low utilization may indicate:

Investigate.

47.178Fleet Pooling

Where departments can share vehicles:

Evaluate.

Do not impair emergency readiness.

47.179Electric or Alternative Vehicles

Evaluate on:

Do not purchase for symbolism.

Do not reject for symbolism either.

47.180Equipment

Large equipment should follow the same:

logic.

47.181Rental Versus Ownership

For rarely used equipment:

Compare:

Use the lowest complete-cost model that meets operational need.

47.182Local Repair

Track whether major equipment can be serviced:

This can support the Canadian-resilience framework.

47.183Parts Availability

For critical purchases:

Consider expected spare-part availability.

A cheaper asset that cannot be repaired may be poor value.

47.184Winter Infrastructure

Snow and winter operations deserve specific performance reporting.

47.185Winter Road Responsibility

Public maps should clearly show which roads are:

responsibility where applicable.

47.186Winter Service Standard

Publish applicable:

in understandable terms.

47.187Storm Severity

Winter performance should be interpreted against:

Do not compare a mild winter and severe winter without context.

47.188Route Completion

Where professionally measured:

Track route performance.

47.189Accessibility in Winter

Include significant:

barriers in winter review.

47.190Snow Complaint Volume

Useful as one indicator.

Not the sole indicator.

47.191Snow Complaints Can Rise With Better Reporting

Again:

Use multiple measures.

47.192Salt and Material Use

Track use and cost.

Normalize by:

before claiming efficiency.

47.193Material Reduction Is Not Automatically Good

Using less salt while roads become less safe is not success.

47.194Winter Fleet Downtime

Critical during severe weather.

Track major availability issues.

47.195Road Transfer Infrastructure Score

Where Grey County road transfers occur, create a dedicated subsection.

47.196Transfer Baseline

At transfer, record:

47.197Transfer Condition Confidence

Do not accept an asset-condition assumption without noting:

47.198Transition Funding

Cross-reference Section 44.

Infrastructure should show:

what physical liabilities the transition funding is intended to support.

47.199Transfer Performance

Track:

47.200Forecast Versus Actual

Compare original transfer assumptions with real cost and physical condition.

47.201Year Eleven

Continue showing long-term cost after temporary transition support ends.

Infrastructure decisions outlive funding agreements.

47.202One Taxpayer

If a road moved from County to City:

The public report should show whether:

changed.

No political double counting.

47.203Transfer Benefit

Local ownership may create benefits such as:

Track actual examples.

47.204Transfer Risk

It may also create:

pressure.

Track both.

47.205Infrastructure Service Interruptions

Track significant failures such as:

at the appropriate aggregate level.

47.206Failure Duration

Measure:

47.207Residents Affected

Where reasonably estimable:

Report scale.

Do not create false precision.

47.208Failure Cause

Possible:

47.209Repeat Failure

Repeated failure at the same asset should affect capital priority.

47.210After-Action Review

Significant infrastructure failure should produce:

cause

response

permanent correction

remaining risk

47.211Emergency Repair Cost

Track separately from planned maintenance where material.

47.212Insurance Recovery

If applicable:

Show whether major repair costs are:

in Finance.

47.213Public Communication

Residents affected by a major infrastructure failure need:

Infrastructure management includes communication.

47.214Asset Failure Is Not Always Preventable

Do not promise:

zero failures.

Aim for:

47.215Resilience

Critical infrastructure should be reviewed for:

47.216Redundancy Has Cost

A backup system that rarely operates may still be valuable.

Do not label all redundancy waste.

47.217Critical Single Point of Failure

Identify major single points of failure internally.

Publicly report mitigation progress at a safe level.

47.218Backup Power

Track whether critical facilities have:

backup systems.

Do not publish sensitive technical detail.

47.219Generator Testing

Critical backup equipment should be tested according to professional standards.

47.220Fuel Continuity

Emergency planning should consider prolonged outages.

Again:

No sensitive public operational detail.

47.221Critical Spare Parts

Maintain selected strategic spares where:

justify them.

47.222Spare Inventory Review

Do not overstock everything.

Review:

47.223Canadian Supply Resilience

For critical infrastructure categories:

Know whether alternatives exist:

The purpose is risk awareness.

47.224Foreign Supplier Is Not Automatically Risk

Assess:

No nationality panic.

47.225Domestic Supplier Is Not Automatically Safe

Canadian vendors can fail too.

Maintain procurement discipline.

47.226Infrastructure Cybersecurity

Modern infrastructure increasingly depends on:

That creates physical infrastructure risk.

47.227Public Reporting Boundary

Report:

at a high level.

Do not publish:

47.228Unsupported Operational Technology

Critical unsupported systems need:

plans.

47.229Manual Continuity

Where feasible:

Critical operators should know how to continue essential service during digital failure.

47.230Technology Vendor Exit

If an infrastructure system depends on one proprietary vendor:

Track exit and continuity planning.

47.231Sensors

Sensors can improve maintenance.

They should not replace:

without evidence.

47.232Sensor Accuracy

Maintain calibration or validation where required.

Bad data can create bad asset decisions.

47.233Digital Twin Claims

Do not describe an ordinary GIS layer as:

digital twin

for marketing.

Use technically accurate terminology.

47.234GIS

Infrastructure mapping should become a reliable institutional asset.

47.235Public GIS

Publish safe:

information.

47.236Sensitive GIS

Keep critical infrastructure details protected appropriately.

47.237Map Accuracy

A map should show:

where practical.

47.238Field Verification

Important infrastructure data should be field-verified over time.

Do not assume legacy records are perfect.

47.239Data Correction

Staff should be able to correct:

records.

47.240Resident Correction

Residents may identify obvious public-map errors.

Provide a correction path.

They do not become infrastructure inspectors.

47.241Infrastructure Index Public Use

The public index should help residents answer:

Why is this road being rebuilt before that road?

The answer should connect to:

47.242No Promise of Exact Rank

Capital priorities can change because of:

Explain changes.

47.243Priority Change Log

When a major project moves substantially in the capital plan:

Record the reason.

47.244Political Change Is a Reason Too

If Council deliberately changes a capital priority:

Say so.

That is a legitimate democratic choice.

Do not pretend the engineering ranking changed if Council made a policy choice.

47.245Capital Plan Versus Approved Project

The ten-year capital plan is:

It is not the same as:

Make that distinction clear.

47.246Forecast Years

Projects several years out may have:

estimates.

Use appropriate precision.

47.247Class of Estimate

For major projects:

Where professional practice uses estimate classes or maturity levels:

Report enough information to explain uncertainty.

47.248Do Not Present Early Estimate as Tender Price

A concept-stage estimate is not a promise.

47.249Contingency Range

Earlier projects need more uncertainty allowance.

Do not strip contingency to make an early project look affordable.

47.250Inflation

Capital estimates should state:

where material.

47.251Escalation

A 2033 project priced in 2026 dollars should not be presented as its likely future tender cost without explanation.

47.252Capital Completion Rate

A possible measure:

Capital Completion Rate = Planned Major Capital Projects Reaching Their Defined Annual Milestone ÷ Major Projects Scheduled for That Milestone

This may be more meaningful than simply:

47.253Spending Is Not Progress by Itself

A department spending 100% of its capital budget has not necessarily completed the intended work.

47.254Underspending Is Not Automatically Good

Capital underspending may indicate:

Explain.

47.255Overspending Is Not Automatically Bad

If Council approved expanded scope:

It may be deliberate.

Maintain history.

47.256Project Delivery Confidence

For major projects:

Consider a simple status:

On Track

At Risk

Off Track

Complete

with published definitions.

47.257At Risk

May mean:

could materially affect outcome.

47.258Off Track

Should trigger:

47.259No Permanent Green

A project can move:

when new information appears.

Good reporting changes with reality.

47.260Project Risk Disclosure

Do not hide:

risk because it might alarm residents.

Do not disclose information that harms negotiations or security.

Balance.

47.261Property Acquisition

For infrastructure requiring land:

Track acquisition stage at an appropriate level.

47.262Negotiation Confidentiality

Do not publish negotiating positions or confidential property information.

47.263Expropriation

Where lawful authority is considered:

Treat as extraordinary.

Public reporting should accurately describe process.

47.264Environmental Approval

Major infrastructure may require environmental processes.

Show:

not started

underway

complete

where applicable.

47.265Approval Is Not a Formality

Do not show:

environmental approval expected

as though it is guaranteed.

47.266Indigenous Rights and Relationships

Where infrastructure may affect Aboriginal or treaty rights:

The relevant Crown processes and the City's SON relationship must be respected.

Do not treat consultation as a project schedule checkbox.

47.267Infrastructure Index and Indigenous Information

Do not publish culturally sensitive locations merely because they intersect an infrastructure layer.

47.268Archaeology

Where archaeological requirements apply:

Include them in:

47.269Unexpected Find

A discovery during construction may legitimately delay work.

Plan contingency where appropriate.

47.270Accessibility

Infrastructure design should increasingly include accessibility at the beginning.

47.271Accessibility Retrofit Cost

Track major retrofit liabilities where known.

47.272Accessibility Priority

Where a lower-cost improvement removes a significant barrier:

It may deserve high priority.

47.273Accessibility Is Not Cosmetic

A route that cannot be used by some residents is an infrastructure issue.

47.274Universal Benefit

Good accessibility can also improve:

movement.

47.275Public Realm

Benches, washrooms, lighting and wayfinding are infrastructure too.

They need:

47.276New Public-Realm Asset Test

Before installing:

Who cleans it?

Who repairs it?

Who stores it?

What does replacement cost?

47.277Donation Is Not Free Infrastructure

A donated:

may create future maintenance cost.

Accept intentionally.

47.278Naming Does Not Fund Maintenance Forever

A naming or sponsorship agreement does not eliminate lifecycle responsibility.

47.279Sustainability

Environmental performance should be measured where it materially affects:

Avoid decorative green claims.

47.280Energy Use

For major facilities:

Track energy consumption where useful.

47.281Energy Reduction

Normalize for:

when making major claims.

47.282Energy Retrofit

A retrofit should report:

Not projected savings forever without verification.

47.283Water Efficiency

Likewise for significant municipal facilities.

47.284Maintenance Before Expansion

One of the Scorecard's most important public comparisons should be:

Existing infrastructure renewal need

versus

new infrastructure proposals.

47.285New Asset Burden

For every new major asset:

Show:

Annual operating cost added

and

future replacement responsibility.

47.286Net Asset Growth

If City infrastructure inventory expands substantially:

Show that future maintenance obligations also expanded.

47.287Asset Disposal

If the City disposes of an asset:

Remove it from future maintenance liability.

Explain the change.

47.288Asset Disposal Is Not Always Savings

If service must then be:

show the replacement cost.

47.289Infrastructure and Housing

Housing growth should be connected to:

47.290Growth Capacity

Public planning should show at a high level where infrastructure has:

Do not promise development rights from infrastructure capacity alone.

47.291Growth Infrastructure Cost

New housing may require:

Show who is expected to fund them under applicable law and agreements.

47.292Development Contributions

Use lawful development funding tools transparently.

Do not call developer-funded infrastructure:

free.

Costs ultimately enter project economics.

47.293Infrastructure and Business

Commercial growth may depend upon:

The Start-Up Desk should reflect infrastructure realities.

47.294No Promise Before Capacity Check

Do not tell a business:

this site can support the use

before infrastructure and regulatory requirements are understood.

47.295Infrastructure and Downtown

Downtown improvements should coordinate:

47.296Do Not Rebuild the Surface Twice

If underground work is imminent:

Coordinate before major streetscape investment where practical.

47.297Infrastructure and River

River access and recreation improvements should respect:

47.298Infrastructure and Safety

Section 51 should cross-reference:

47.299Infrastructure and Recreation

Section 52 should cross-reference facility:

47.300Infrastructure and Accessibility

Section 54 should cross-reference unresolved physical barriers.

47.301Infrastructure and Environment

Section 56 should cross-reference:

outcomes.

47.302Data Owner

Primary owners will vary.

Possible:

The Infrastructure Scorecard should have a central coordinating owner.

47.303Central Coordination

A senior administrative owner should ensure:

stay consistent across departments.

47.304Professional Authority

Engineering conclusions should come from qualified professionals.

A scorecard does not replace professional judgement.

47.305Mayor Does Not Rate Bridges

The Mayor should not declare:

bridge is safe

or

road is failing

against professional evidence.

Political leaders decide priorities.

Professionals assess technical condition.

47.306Council Does Not Rewrite Engineering Data

Council can disagree about:

It should not alter the technical condition rating for political convenience.

47.307Resident Observations Matter

Residents can identify:

problems.

Those reports improve situational awareness.

47.308Residents Are Not Engineers

A resident report:

bridge feels unsafe

should trigger appropriate review.

It does not itself establish structural failure.

47.309Public Correction

If an Infrastructure Index record is wrong:

Correct it.

Maintain the material correction history.

47.310Measurement Frequency

Different infrastructure metrics require different schedules.

Service requests

Quarterly.

Major capital

Quarterly.

Condition assessments

According to inspection cycle.

Long-term asset plan

Annual or as professionally required.

Failures

As they occur.

47.311Do Not Inspect Everything Annually

That would be inefficient.

Inspection frequency should follow:

47.312Stale Data Warning

When condition information exceeds its expected review period:

Flag it.

47.313Infrastructure Baseline

Year One should establish:

47.314Baseline Honesty

If the baseline is incomplete:

Say:

Inventory 74% complete for this asset class.

Do not pretend completeness.

47.315Year One Objective

Know what we own and where the largest information gaps are.

47.316Year Two Objective

Use the improved information to:

47.317Year Three Objective

Reduce critical unknowns and make larger lifecycle decisions.

47.318Year Four Objective

Leave the next Council:

47.319Four-Year Trend Measures

Strong candidates include:

47.320Four-Year Condition Trend

Do not expect every asset class to improve simultaneously.

The City may deliberately allow low-priority assets to age while investing elsewhere.

Explain.

47.321Portfolio Health

A useful public summary can show:

47.322Count Versus Value

Ten small poor-condition assets may be less significant financially than one major poor-condition facility.

Show both where useful.

47.323Replacement Value

Use professional estimates.

Do not present replacement value as:

They are different.

47.324Infrastructure Investment

Track annual:

capital.

47.325Investment per Resident

Possible contextual measure.

Use cautiously.

Higher spending is not automatically better.

47.326Investment Versus Need

More important:

Are we investing in the right assets at the right time?

47.327Project Completion Count

Do not celebrate:

42 projects completed

without scale.

One major bridge rehabilitation can matter more than dozens of small projects.

47.328Major Project Definition

Define a materiality threshold for the public major-project list.

Review periodically.

47.329Small Projects Still Matter

Routine small capital should remain in normal financial records even if not individually dashboarded.

47.330Public Scorecard Header

The first Infrastructure Scorecard page should show:

What We Own

Major asset classes.

What We Know

Condition coverage and critical unknowns.

What Is at Risk

High-priority assets.

What We Are Maintaining

Preventive versus reactive work.

What We Have Deferred

Known deferred maintenance.

What We Are Building

Major capital projects.

What Is Off Track

Major cost or schedule exceptions.

What We Cannot Yet Fund

Priority unfunded needs.

What Changed This Quarter

Simple public explanation.

MeasureBaselineCurrentTarget / StandardTrendStatusOwner

Possible rows:

47.332Project Table

ProjectOriginal BudgetCurrent BudgetForecast CostOriginal CompletionCurrent ForecastStatus

Residents should be able to see changes immediately.

47.333Condition Table

Asset ClassGood / BetterFairPoor / WorseUnknownLast Major Update

Use the actual professional categories.

47.334Risk Table

Risk CategoryNumber / ValueFunded MitigationUnfundedTrend

Avoid exposing security-sensitive asset identity.

47.335Deferred Maintenance Table

Asset ClassKnown Deferred WorkEstimated ExposureRiskPlanned Response

Use ranges where necessary.

47.336Road Transfer Table

MeasureTransfer BaselineCurrentForecastLong-Term Note

Possible:

47.337Anti-Gaming Rule One

Do not improve the infrastructure condition score by:

47.338Anti-Gaming Rule Two

Do not remove poor-condition assets from the denominator because they are inconvenient.

47.339Anti-Gaming Rule Three

Do not call deferred maintenance:

savings.

47.340Anti-Gaming Rule Four

Do not call a project:

under budget

after quietly reducing scope.

47.341Anti-Gaming Rule Five

Do not reset the original project budget after a budget increase.

Preserve history.

47.342Anti-Gaming Rule Six

Do not reset the original completion date after a delay.

Preserve history.

47.343Anti-Gaming Rule Seven

Do not classify resident complaints as:

merely to reduce issue counts.

47.344Anti-Gaming Rule Eight

Do not classify planned maintenance as emergency work to inflate emergency performance.

47.345Anti-Gaming Rule Nine

Do not classify emergency repair as preventive maintenance after the fact.

47.346Anti-Gaming Rule Ten

Do not claim a grant-funded project cost the City:

nothing.

Show local contribution and future operating cost.

47.347Anti-Gaming Rule Eleven

Do not call transferred infrastructure:

free asset.

Show liabilities.

47.348Anti-Gaming Rule Twelve

Do not call old condition data:

current.

47.349Anti-Gaming Rule Thirteen

Do not reduce the capital backlog merely by deleting projects without explaining why they were removed.

47.350Anti-Gaming Rule Fourteen

Do not add speculative projects to inflate the apparent infrastructure funding gap.

Use professionally identified need.

47.351Anti-Gaming Rule Fifteen

Do not rush construction late in the term to improve completion metrics.

47.352Infrastructure Traffic Lights

If using:

Green

Asset or project within the published standard.

Amber

Material attention required.

Red

Significant action or decision required.

Grey

Condition or data insufficient.

Publish exact definitions.

47.353Grey Is Important

A Grey condition may be more urgent than a known Fair condition if the asset is critical.

Unknown is information risk.

47.354Green Asset Can Still Need Planned Work

An asset may be healthy while scheduled preventive maintenance is still due.

Green does not mean:

spend nothing.

47.355Red Does Not Mean Immediate Closure

A Red financial or condition status can mean:

depending on professional assessment.

Avoid public panic.

47.356Scorecard Notes

Every major Red or Amber item should show:

Why

What is being done

Next decision date

47.357No Narrative Without Data

Do not say:

Our infrastructure has never been stronger

without evidence.

47.358No Data Without Context

Likewise:

$80 million infrastructure gap

requires:

47.359Infrastructure Comparisons

Peer comparison can help.

Use cautiously.

47.360Different Cities Own Different Things

One municipality may own:

Another may not.

Do not compare total capital per resident without context.

47.361Climate and Geography Differ

Snow, terrain and water systems affect cost.

47.362Benchmark Specific Functions

Compare:

only where definitions are similar.

47.363Infrastructure Open Data

Publish safe reusable data where valuable.

Examples:

47.364Do Not Publish Vulnerability Data

No release of detailed:

information simply to satisfy an open-data philosophy.

47.365Public Maps Need Dates

Every infrastructure map should show:

47.366Proposed Is Not Existing

Maps should clearly distinguish:

Existing

Under Construction

Approved

Proposed

Conceptual

47.367Property Rights

Do not map a future:

across private land as though it already exists.

47.368Corridor Preservation

A preserved corridor is not:

Label accurately.

47.369East-West Crossing Scorecard

If the crossing continues:

Track separately:

cumulative study cost

current stage

current capital range

municipal share assumption

approvals

major risks

next decision gate

47.370No Build Is a Valid Status

If the crossing stops:

The scorecard should say:

Stopped after business case

or the accurate reason.

That can be good infrastructure management.

47.371Harbour Scorecard

If harbour-related municipal capital advances:

Track:

Federal assets remain separately identified.

47.372No Liability Transfer by Map

Do not accidentally imply City responsibility by placing a federal asset in the municipal asset inventory.

Ownership matters.

47.373Civic Square Scorecard

If capital advances:

Track like any other major project.

No special political treatment.

47.3742nd Avenue Scorecard

Track permanent infrastructure separately from seasonal operating pilots.

Temporary furniture is not the same as:

47.375Accessibility Capital Scorecard

Cross-reference major accessibility projects.

Do not count minor cosmetic changes as major accessibility improvement.

47.376Infrastructure Complaints

Resident complaints should inform but not dictate condition ratings.

47.377Professional Override

If residents complain frequently about a road rated structurally good:

Investigate:

Do not automatically change the engineering rating.

47.378Complaint and Condition Together

The best picture combines:

47.379Public Infrastructure Walks

Occasional neighbourhood infrastructure walks can help identify:

issues.

They do not replace inspection.

47.380Civic Corps

Youth may assist with safe, non-technical:

under supervision.

They do not certify asset condition.

47.381Volunteer Limits

Volunteers should never be asked to inspect:

as substitutes for qualified professionals.

47.382Local Trades

Local trades may competitively provide:

Procurement rules continue.

47.383No Preferred Contractor Map

The Infrastructure Index should not become advertising for:

47.384Contractor Performance

Professional contract-performance records can inform future lawful procurement.

Do not create public political rankings without a proper reason.

47.385Infrastructure Staffing

The Scorecard should identify when major project delay is caused by:

47.386Staffing Is Infrastructure Capacity

A capital plan with no:

to deliver it is not a real plan.

47.387Capital Delivery Capacity

Track how many major projects the organization can reasonably manage simultaneously.

47.388Do Not Overload the Capital Program

Ten well-managed projects can be better than:

47.389Consultant Capacity

Outside professionals can add capacity.

Measure:

47.390No Consultant Dependency Without Review

If the City cannot manage ordinary asset planning without continual outside dependence:

Evaluate whether internal capacity should grow.

47.391Infrastructure Knowledge Transfer

Critical asset knowledge should be documented before experienced employees retire.

47.392Field Knowledge

Capture practical knowledge such as:

47.393But Do Not Treat Memory as Engineering Record

Verify important information.

47.394Long-Term Capital Forecast

The Scorecard should link to at least a ten-year capital outlook.

47.395Ten-Year Is Still Not Long Enough for Every Asset

Water and buildings may require longer lifecycle analysis.

The public plan can summarize longer-term exposure.

47.396Election Cycle Is Not Asset Lifecycle

Do not manipulate replacement timing around four-year terms.

47.397The Next Council Test

Every major Year Four infrastructure file should answer:

What condition?

What cost?

What risk?

What contract?

What decision next?

When?

47.398Transition Package

The next Council should receive:

47.399No Hidden Capital Surprise

Known major future needs belong in the transition file.

47.400No Election-Year Maintenance Holiday

Year Four maintenance should continue normally.

47.401No Election-Year Capital Rush

Do not start a major project merely to move its status to:

under construction

before voting day.

47.402Same Reporting Method

Use the same project cost and schedule definitions in Year Four.

47.403Public Can Judge

Candidates may argue that the City:

The Scorecard provides the evidence.

47.404Four-Year Infrastructure Audit

At term end:

Publish:

What condition knowledge improved?

What major assets were renewed?

What new assets were added?

What failed?

What remained deferred?

What became more expensive?

What liabilities remain unfunded?

What transferred from County?

What major projects carry into the next term?

47.405Name the Biggest Infrastructure Improvement

Use evidence.

47.406Name the Biggest Infrastructure Failure

Use evidence.

47.407Name the Largest Deferred Need

Tell residents.

47.408Name the Largest Unknown

If one remains:

Explain why.

47.409Name the Most Successful Preventive Intervention

Show what failure or cost it helped avoid where evidence supports the claim.

47.410Name the Most Expensive Emergency Repair

Explain what was learned.

47.411Name a Project Delivered Well

Show:

47.412Name a Project That Went Off Track

Explain:

47.413Name a Project Stopped

If evidence led to stopping:

That belongs in the report.

47.414Name the Largest Future Capital Pressure

The next Council should know.

47.415Name the Biggest Road-Transfer Lesson

Especially important if new local road responsibilities materially changed the City's asset portfolio.

47.416Name the Biggest Data Improvement

Perhaps the term's most valuable infrastructure achievement is simply:

We now know what we own and what condition it is in.

That matters.

47.417Infrastructure Stewardship Test

Ask:

Did we leave the next Council better information and better assets than we inherited?

47.418Maintenance Test

Ask:

Did preventive maintenance become more intentional?

47.419Failure Test

Ask:

Did avoidable repeat failures decline?

47.420Deferred Maintenance Test

Ask:

Did we make known deferral more visible and more disciplined?

47.421Condition Test

Ask:

Did the number of critical Unknown assets decline?

47.422Capital Test

Ask:

Were major projects delivered with honest cost and schedule reporting?

47.423Scope Test

Ask:

Did we disclose material scope changes instead of manipulating project-performance claims?

47.424Road Test

Ask:

Did road investment follow lifecycle, coordination and risk rather than politics?

47.425Utility Coordination Test

Ask:

Did we reduce avoidable repeated excavation through One Street, One Plan?

47.426Facility Test

Ask:

Did the City use existing buildings intelligently before proposing more space?

47.427Fleet Test

Ask:

Did replacement decisions use lifecycle and operational need rather than age alone?

47.428Winter Test

Ask:

Did winter performance remain reliable as responsibilities changed?

47.429Road Transfer Test

Ask:

Do we now know the true service and lifecycle cost of the roads we assumed?

47.430Resilience Test

Ask:

Can critical infrastructure continue through foreseeable disruptions better than four years ago?

47.431Digital Infrastructure Test

Ask:

Are critical operational systems better supported, more recoverable and less dependent on single vendors?

47.432Accessibility Test

Ask:

Did accessibility become part of infrastructure design rather than a retrofit afterthought?

47.433Environment Test

Ask:

Did infrastructure planning better account for drainage, river conditions, trees and severe weather?

47.434One Taxpayer Test

Ask:

When responsibility moved between City and County, did we report the total public cost honestly?

47.435Future Council Test

Ask:

Can the next Council see the five or ten biggest infrastructure decisions it will have to make?

47.436What Success Looks Like

Infrastructure success does not mean:

every road is perfect.

No municipality can afford that.

Success means:

47.437What Failure Looks Like

Infrastructure failure includes:

47.438The Infrastructure Scorecard Commitment

Owen Sound should commit to:

Know what major infrastructure the City owns.

Know which assets are owned or controlled by Grey County, Ontario, Canada, utilities or private parties instead.

Distinguish ownership from maintenance responsibility.

Maintain a professional Infrastructure and Systems Index.

Publish a safe public layer and protect sensitive operational information.

Use professional condition ratings rather than political grades.

Date every major condition assessment.

Publish condition confidence so residents know where uncertainty remains.

Use Unknown when information is genuinely insufficient.

Reduce critical Unknown assets over the four-year term.

Track overdue critical inspections.

Never improve infrastructure statistics by inspecting fewer assets.

Distinguish preventive, reactive and emergency maintenance.

Track repeat repairs that may indicate deeper failure.

Do not reward cheap temporary patches over durable solutions.

Maintain a Deferred Maintenance Ledger.

Never call postponed maintenance an efficiency saving.

Explain why major work was deferred.

Show where deferral is expected to increase future cost.

Prioritize assets by risk as well as condition.

Recognize that a fair-condition critical asset can require more attention than a poor-condition low-risk asset.

Show whether high-risk assets have funded mitigation plans.

Publish major unfunded infrastructure exposure honestly.

Use lifecycle planning rather than age alone.

Compare rehabilitation and replacement before choosing the most expensive intervention.

Use complete lifecycle cost rather than lowest purchase price alone.

Show the long-term renewal funding gap with its time horizon.

Do not describe a multi-decade infrastructure gap as next year's tax bill.

Maintain reserves and capital planning consistent with long-term asset needs.

Use debt for long-lived assets only with clear affordability and lifecycle reasoning.

Show grants together with City contribution and future operating cost.

Keep professionally justified projects ready rather than inventing projects for grants.

Publish a clear readiness stage for every major proposed capital project.

Maintain a public project card for every material active capital project.

Preserve the original approved budget.

Preserve the original expected completion date.

Show the current approved budget and forecast final cost separately.

Show the current completion forecast separately from the original schedule.

Explain material delays.

Do not call early completion success if quality is poor.

Disclose material scope increases.

Disclose material scope reductions.

Never claim a project is under budget after quietly removing major scope.

Publish cumulative material change orders.

Track recurring causes of change orders so project delivery can improve.

Use contingency honestly.

Complete deficiency and warranty work before calling major projects financially closed.

Conduct post-project learning reviews.

Publish road-condition information using professional pavement-management methods.

Use consistent road-length measures.

Distinguish resurfacing, rehabilitation and reconstruction.

Use preventive pavement treatment where lifecycle evidence supports it.

Do not select roads solely through a worst-first approach when preventive work provides better lifecycle value.

Do not select road projects according to political support.

Track sidewalk condition, network gaps and important accessibility barriers.

Prioritize useful network connections rather than counting metres of new sidewalk alone.

Track bridge inspection and condition according to applicable professional requirements.

Keep existing bridge renewal separate from any new east-west crossing proposal.

Include major culverts and drainage structures in risk planning.

Treat stormwater as core infrastructure.

Use recurring drainage complaints to identify possible system issues while protecting household privacy.

Distinguish infrastructure failure from extraordinary weather events.

Use credible current design conditions for severe weather where relevant.

Report water and wastewater infrastructure condition without exposing security-sensitive system information.

Keep water quality performance separate from physical asset condition.

Track watermain-break trends where professionally useful.

Keep water and wastewater funding distinctions clear.

Review underground water, wastewater and stormwater needs before major road reconstruction.

Make One Street, One Plan standard practice for major corridors where practical.

Coordinate with utilities before major surface investment.

Track avoidable cuts into newly reconstructed streets.

Maintain streetlights and traffic controls as infrastructure rather than one-off complaints.

Keep trail status and closures current.

Include City-owned river and harbour-related assets only when responsibility is legally clear.

Never report a federal harbour asset as though it were City-owned.

Maintain a high-level condition plan for municipal buildings.

Use existing facility capacity before proposing new construction where appropriate.

Recognize that emergency facilities need different utilization measures than ordinary public buildings.

Maintain recreation facilities according to condition and lifecycle as well as participation.

Prioritize significant park and playground assets rather than attempting to score every bench.

Measure tree establishment, maintenance and risk where appropriate rather than planting counts alone.

Treat fleet and major equipment as infrastructure assets.

Replace fleet based on lifecycle and operational need rather than age alone.

Track critical fleet downtime.

Preserve appropriate redundancy for emergency and winter operations.

Compare ownership, rental and contracting for rarely used equipment.

Consider repairability and parts availability in major equipment procurement.

Publish clear winter road responsibilities.

Measure winter operations against storm conditions and adopted service standards.

Include winter accessibility in performance review.

Never claim lower salt use as efficiency if public safety worsens.

Create a dedicated road-transfer infrastructure baseline.

Record transferred asset condition before or at assumption as accurately as possible.

Track transfer operating, winter and capital costs against the original assumptions.

Continue modelling the cost after temporary transition funding ends.

Apply One Taxpayer reporting to transferred roads.

Report both the benefits and liabilities of local road control.

Track significant infrastructure service interruptions.

Measure restoration time and recurring failures.

Conduct after-action reviews after major infrastructure failures.

Build appropriate resilience through redundancy, backup power, spare parts and operating procedures.

Do not label necessary redundancy as waste solely because it is not used every day.

Maintain sensible strategic spares where failure consequence and lead time justify them.

Understand critical Canadian and international supply dependencies without turning resilience into isolationism.

Treat operational technology and cybersecurity as part of modern infrastructure risk.

Do not publish exploitable cyber or infrastructure-security information.

Maintain plans for unsupported critical systems.

Preserve manual or alternate operating capability for essential services where feasible.

Use sensors where they improve management, but validate the data.

Do not use fashionable technical terms such as digital twin inaccurately.

Maintain reliable GIS information as an institutional asset.

Publish safe public maps and protect sensitive layers.

Date maps and distinguish existing, approved, proposed and conceptual infrastructure.

Never show private land as public infrastructure without legal access.

Publish why major capital priorities change.

Distinguish the long-term capital plan from actual approved spending.

Use appropriate cost ranges for early-stage projects.

Do not present concept estimates as tender prices.

State the dollar year and inflation assumptions for long-range estimates where material.

Measure capital milestones, not simply dollars spent.

Treat capital underspending as something to explain rather than automatic success.

Use On Track, At Risk, Off Track and Complete only with published definitions.

Protect confidential property negotiations while keeping project status visible.

Treat environmental approvals as genuine decision processes rather than formalities.

Respect Aboriginal and treaty rights and the City's relationship with Saugeen Ojibway Nation throughout applicable infrastructure planning.

Protect culturally sensitive information.

Budget archaeological work where legally or professionally required.

Build accessibility into infrastructure design from the beginning.

Treat public-realm furniture, washrooms, lighting and wayfinding as assets that require maintenance.

Never accept new infrastructure without considering future operating and replacement costs.

Treat donated assets as future maintenance obligations.

Verify real energy savings after major retrofits rather than repeating projected savings forever.

Show existing-asset renewal needs beside new capital proposals.

Publish the annual operating tail created by major new assets.

Show when asset disposal actually reduces future cost and when the cost simply moves elsewhere.

Connect housing and business growth decisions to real servicing capacity.

Never promise development capacity before infrastructure has been checked.

Coordinate downtown public-realm investment with underground infrastructure.

Respect environmental, flood and property constraints along the river.

Cross-reference infrastructure with safety, recreation, accessibility and environmental scorecards.

Give every major infrastructure metric a professional administrative owner.

Never allow the Mayor or Council to rewrite technical condition assessments for political convenience.

Use resident observations to identify issues without pretending residents replace professional inspection.

Correct public infrastructure records when errors are found.

Use inspection cycles based on risk and professional requirements rather than inspecting everything annually.

Flag stale condition information.

Use Year One to establish the baseline.

Use Year Two to increase preventive work and manage transferred responsibilities.

Use Year Three to reduce critical unknowns and make major lifecycle decisions.

Use Year Four to leave a complete infrastructure handoff.

Publish four-year trends without expecting every asset class to improve simultaneously.

Show condition by both number and asset value where useful.

Do not equate higher capital spending with better asset management automatically.

Keep project count in context.

Publish safe underlying infrastructure data where it creates public value.

Never publish critical infrastructure vulnerabilities in the name of openness.

Track the east-west crossing through explicit decision gates if it continues.

Allow No Build or Corridor Preserved to remain valid crossing outcomes.

Track harbour capital only according to actual municipal ownership and responsibility.

Apply ordinary capital accountability to Civic Square and 2nd Avenue projects.

Use resident complaints alongside professional condition, not instead of it.

Allow Civic Corps to assist with safe non-technical mapping but never substitute youth or volunteers for professional infrastructure inspection.

Use local trades through fair procurement.

Recognize staffing and project-management capacity as part of capital-delivery capability.

Do not overload the organization with more capital projects than it can professionally manage.

Capture experienced staff knowledge before retirement while verifying important technical information.

Maintain a capital horizon longer than one election cycle.

Never manipulate infrastructure replacement around political timing.

Give the next Council a complete asset, risk, inspection, project and funding handoff.

Never create an election-year maintenance holiday.

Never create an election-year construction rush.

Use the same infrastructure reporting definitions throughout the term.

Publish the four-year infrastructure audit with successes, failures, deferrals, unknowns and future liabilities.

The Infrastructure Scorecard should make an important cultural change possible.

Instead of asking:

What new thing can we announce?

Council should increasingly ask:

What do we already own?

What condition is it in?

What could fail?

What should be maintained now?

What can responsibly wait?

What are we adding to future maintenance?

What does the next Council inherit?

That is stewardship.

A well-managed city does not wait for a pipe to break, a roof to leak or a road to collapse before infrastructure becomes politically important.

It knows.

It plans.

It maintains.

It measures.

It publishes the risk.

And when it cannot afford everything at once, it says so.

Know the asset. Know the condition. Know the confidence. Know the risk. Maintain deliberately. Build carefully. Show what is deferred. Leave fewer infrastructure surprises for the next generation.

← Chapter 46: Services: The Public Service ScorecardChapter 48: Downtown: The Public Downtown Scorecard →