Owen Sound: A Four-Year City Business Plan

Home › Infrastructure and Resilience › Chapter 12

Infrastructure and Resilience

Chapter 12The Infrastructure and Systems Index

6,057 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

Before Owen Sound builds more, it should understand what it already owns.

Roads, bridges, pipes, buildings, parks, vehicles, pumps, computers, docks, lights and public facilities represent generations of investment.

Some are visible every day.

Others remain underground or behind locked doors until something fails.

Every one of them eventually requires:

Infrastructure is therefore not simply a capital-budget issue.

It is one of the City's largest long-term responsibilities.

The original proposal called for every road, pipe, pump, building and municipal system to be indexed with its age, condition and cost so that residents, tradespeople, engineers and students could better understand the physical systems supporting their community.

That idea should become the Owen Sound Infrastructure and Systems Index.

The Index would not replace the City's professional asset-management work.

It would make that work easier for residents to understand and use.

Ontario already requires municipalities to maintain formal asset-management planning under Ontario Regulation 588/17. The regulation requires municipal asset-management plans, proposed service levels, financial strategies, Council approval and annual review of progress.

Owen Sound completed a comprehensive 2025 Asset Management Plan incorporating both core and non-core infrastructure, proposed levels of service and a long-term financing strategy.

That professional work gives us the foundation.

The next step is to make municipal infrastructure understandable enough that the entire community can see the challenge.

Know what we own. Know what condition it is in. Maintain it before it fails. Plan its replacement before the bill arrives.

12.1Two Levels of Asset Information

Municipal infrastructure information should operate at two levels.

Level One: Professional Asset Management

This is the detailed technical record required for:

Professional records may contain information that is:

Those records should remain managed by qualified staff.

Level Two: The Public Infrastructure Index

The public should receive an understandable version showing enough information to answer basic questions such as:

The public Index should explain the infrastructure without publishing information that creates a security or operational risk.

The principle is:

Public understanding without compromising public safety.

12.2What Belongs in the Index

The Infrastructure and Systems Index should eventually include all major municipal asset classes.

These should include, at minimum:

  1. Roads
  2. Bridges and culverts
  3. Sidewalks and pedestrian infrastructure
  4. Water
  5. Wastewater
  6. Stormwater
  7. Municipal buildings
  8. Parks and open spaces
  9. Recreation facilities
  10. Fleet and equipment
  11. Street lighting and traffic infrastructure
  12. Municipal technology
  13. Fire and emergency infrastructure
  14. Waterfront assets
  15. Trails
  16. Public parking assets
  17. Municipal land
  18. Other major systems or facilities owned or operated by the City

Owen Sound's current asset-management work already covers both core infrastructure and non-core assets, including areas such as roads, facilities, parks and other municipal systems.

The public Index should organize that information around the way residents experience the City.

12.3Every Asset Needs a Record

For appropriate assets, the public record should eventually contain a consistent set of information.

Asset

What is it?

Location

Where is it?

Asset Class

Road, building, park, water system or another category.

Ownership

Does Owen Sound own it?

Is it leased?

Is another government involved?

Age

When was it built, installed or substantially renewed?

Condition

What is its current condition?

Service

What public service does the asset support?

Inspection

When was it last assessed where applicable?

Maintenance

What routine work is required?

Planned Work

What is currently scheduled?

Expected Major Renewal

When is significant rehabilitation likely to be required?

Replacement

When will replacement likely become necessary?

Replacement Cost

What is the current planning estimate?

Funding

Is funding:

Risk

What happens if the asset fails?

Project Status

Where major work is underway:

Not every field will make sense for every asset.

The format should remain consistent enough that residents can learn how to read it.

12.4A Simple Condition Scale

Technical asset condition assessments can become complicated.

The professional system should preserve whatever level of technical detail is required.

The public system should translate that into a simple condition scale.

Very Good

New or nearly new.

Only normal maintenance expected.

Good

Functioning well.

Routine maintenance required.

No significant near-term intervention expected.

Fair

Functioning but showing deterioration.

Increased maintenance or rehabilitation should be planned.

Poor

Significant deterioration.

Major rehabilitation or replacement planning is required.

Very Poor

High likelihood of failure, unacceptable service condition or major renewal required.

Unknown

The City does not currently possess sufficient reliable information.

That final category matters.

We should never invent a condition rating simply because an empty field looks uncomfortable.

If we do not know, say:

Unknown. Assessment required.

Unknown infrastructure is itself a risk worth identifying.

12.5Confidence in the Information

Asset information is not equally precise.

A road may have been professionally assessed last month.

A buried pipe may have an age record but limited direct condition information.

A building may have a recent facility-condition assessment.

An older asset may have incomplete historical records.

The public Index should therefore indicate the confidence level of significant information.

High Confidence

Recent professional inspection or strong records.

Moderate Confidence

Reliable records and indirect evidence.

Low Confidence

Limited or older information.

Unknown

Assessment required.

This prevents planning estimates from being presented as certainties.

12.6Roads

Roads are among the most visible municipal assets.

Residents experience their condition directly.

The road index should eventually identify:

Coordinate Before Digging

One of the simplest principles of infrastructure management should be:

Do not pave a road today if we know we need to dig it up tomorrow.

Before significant road reconstruction, the City should review:

Where practical, underground and surface work should be coordinated.

This may occasionally delay one project slightly.

It can also prevent residents from watching a newly reconstructed street get excavated shortly afterwards.

12.7Road Maintenance Versus Reconstruction

Residents should be able to understand the difference between:

A patched road is not necessarily a neglected road.

Sometimes patching is the financially responsible intervention.

In other circumstances, repeated patching may indicate that reconstruction has been delayed too long.

Publish the Strategy

For significant road segments, the City should be able to explain:

We are maintaining this road for another five years because that is currently the lowest lifecycle cost.

or:

This road has reached the point where continued patching no longer represents good value, so reconstruction has been scheduled.

That explanation gives residents more useful information than simply rating every rough road as a failure.

12.8Potholes as Asset Information

The proposed Pot Hole Day and First to Action systems should feed directly into asset management.

A pothole is not only a maintenance request.

Repeated potholes can become data.

If one road segment produces:

the asset system should flag it for deeper review.

Report

For recurring road locations:

At some point, repair becomes more expensive than renewal.

The Index should help identify when that point is approaching.

12.9Bridges and Culverts

Bridges and major culverts have a different risk profile.

Failure can:

The public Index should identify:

Detailed structural or security information that should not be public must remain protected.

The purpose is to tell residents whether a major connection is:

healthy, being monitored, scheduled for work or approaching renewal.

12.10Sidewalks and Pedestrian Infrastructure

Sidewalks deserve their own asset category.

They are essential infrastructure for:

The Index should eventually record:

This connects directly with the future Safe Routes and Local Knowledge programs.

Accessibility Layer

Residents should eventually be able to see practical information such as:

Those layers should be built with people who actually experience accessibility barriers.

12.11Drinking Water

Drinking-water systems are critical infrastructure.

They require a higher level of technical, regulatory and operational management than an ordinary municipal asset.

The public Index should provide understandable information such as:

Sensitive operational details should remain restricted.

The objective is not to create a public engineering manual for the water system.

It is to allow residents to understand the scale of the infrastructure required every time they turn on a tap.

12.12Wastewater

Wastewater infrastructure is equally important and usually much less visible.

Residents rarely think about a sanitary sewer when it is working.

They think about it immediately when it fails.

The public Index should summarize:

Where repeated problems occur in a neighbourhood, the City should identify whether the issue relates to:

Residents need clear responsibility rather than simply being told there is a sewer problem.

12.13Stormwater

Stormwater management is becoming increasingly important as communities deal with:

Owen Sound has undertaken a Stormwater Management Master Plan focused on the long-term management of stormwater runoff on public lands and the coordination of improvements with roads, bridges, sanitary infrastructure, water mains and other municipal work.

That approach should become part of the Infrastructure Index.

Stormwater Assets May Include

Public Reporting Should Explain

Stormwater should not become something residents hear about only after a basement floods or a road washes out.

12.14Municipal Buildings

Every municipal building should eventually have a basic public asset profile.

Examples include:

Building Record

Include:

Use Before Building

Before proposing a new municipal building, ask:

Are we fully using what we already own?

A building operating at low utilization may represent an opportunity for:

Conversely, an overcrowded or deteriorating facility may justify investment.

The asset record gives Council the evidence required to distinguish the two.

12.15Public Facility Utilization

Condition is only one part of asset value.

We should also understand use.

For appropriate facilities, measure:

A building may be in excellent physical condition but poorly used.

Another may be heavily used and approaching the end of its life.

Those are different investment questions.

Share Before Duplicating

Before constructing new public space, examine whether existing space could be shared with:

Shared use can sometimes provide better service without creating another permanent municipal asset.

12.16Parks and Open Spaces

Parks are infrastructure.

They contain assets such as:

Residents should be able to see the condition and planned renewal of major park assets.

The City's 2025 asset-management work specifically included parks and open spaces among the infrastructure areas examined for current and proposed levels of service.

Park Stewardship

For each major park, eventually provide:

This will become particularly useful as the Efficiency Dividend begins funding visible park improvements.

Residents will be able to see:

What needed work. What was selected. What it cost. What condition improved.

12.17Trails

Trails should be mapped as both recreation assets and transportation connections.

The Index should identify:

Trail Knowledge

Residents should eventually be able to understand:

That information will later feed directly into the Local Knowledge and Owen Sound Outside programs.

12.18Street Lighting

Street lighting affects:

The existing plan already identifies low lighting as one of the recurring municipal work streams that should be reported and managed.

The lighting index should eventually record:

Light Where Needed

More lighting is not automatically better.

Lighting decisions should consider:

The objective is the right light in the right place.

12.19Traffic Infrastructure

Traffic infrastructure can include:

The public Index should help identify:

Residents should be able to distinguish between:

12.20Fleet

The City depends on vehicles and mobile equipment.

Examples may include:

Each major fleet asset should have:

Replace by Evidence

A vehicle should not automatically be replaced because it reaches a particular birthday.

Nor should an unreliable vehicle remain in service simply because replacing it is politically difficult.

Use:

The objective is to replace at the financially responsible point in the lifecycle.

12.21Fleet Utilization

Before buying another municipal vehicle, ask:

Idle Assets Have a Cost

A vehicle sitting unused still creates:

The Index should help identify assets that are substantially underused.

That does not automatically mean they should be sold.

Emergency equipment, for example, may need to exist precisely because it is needed rarely but urgently.

Utilization must always be interpreted in the context of purpose.

12.22Fire and Emergency Assets

Emergency infrastructure requires special treatment.

The public should understand the general condition and long-term cost of:

Operational security and emergency-response details that should remain confidential must remain protected.

Reliability Before Visibility

Emergency assets should be prioritized based upon:

A fire truck does not become less important because residents see a park improvement more often.

Capital planning must resist the tendency to favour visible projects over critical ones.

12.23Waterfront Infrastructure

Owen Sound's waterfront creates its own asset-management responsibilities.

Municipal or municipally managed assets may include:

Waterfront assets may also involve:

The Infrastructure Index should identify ownership and responsibility clearly.

A resident should be able to tell the difference between:

City-owned

City-leased

County

Provincial

Federal

Private

Shared or subject to another interest

This will be especially important when we develop the River as Owen Sound's Civic Spine later in the plan.

12.24Municipal Technology Is Infrastructure

Modern municipalities depend on digital systems as surely as they depend on roads and pipes.

Technology assets should therefore be included in asset planning.

These can include:

The public Index should not disclose security-sensitive technical information.

It should provide enough information to understand:

A Software Contract Can Be an Infrastructure Liability

A subscription may not look like an asset.

But if the City cannot function without it, the dependency should be managed like infrastructure.

We should know:

This will connect directly to the later Canadian Digital Sovereignty section.

12.25Municipal Land

Land is also an asset.

The City should maintain an understandable inventory of appropriate municipal land categories.

For publicly disclosable properties, identify:

Surplus Land

Before municipal land is declared surplus, the City should ask:

Selling land produces one-time revenue.

Land can never be purchased back at yesterday's price.

That does not mean the City should keep every parcel forever.

It means disposal should be intentional.

12.26The Asset Map

Where appropriate, public infrastructure should eventually appear on a geographic map.

A resident could select:

Roads

Parks

Trails

Sidewalks

Buildings

Waterfront

and see public asset information.

Example

Select a road segment:

Condition: Fair

Last major work: 2014

Next planned intervention: 2028

Current estimated project cost: planning estimate

Water work coordinated: Yes

Project status: Capital planning

This turns infrastructure planning into something residents can understand visually.

Sensitive Assets

Not all assets belong on a public map.

Security and operational review should determine what information is appropriate.

The map should inform residents without creating unnecessary risk.

12.27Planned Work Layer

The public map should also show major planned infrastructure work.

Residents should be able to see:

Current Year

Work approved and scheduled.

Next Three Years

Projects included in the capital forecast.

Longer Term

Major known renewal needs that have not yet reached final scheduling.

This distinction is important.

A long-term need should not be presented as though construction has been approved.

Use clear language:

Approved

Planned

Forecast

Under Study

Unfunded

Residents should know the difference.

12.28The Unfunded Infrastructure List

One of the most important things government can publish is the work it knows is required but has not yet funded.

Create an Unfunded Infrastructure List.

For significant needs, show:

This is not a failure list.

It is a reality list.

Municipal infrastructure needs often exceed the money available in a single year.

The honest response is to prioritize visibly.

Priority Should Be Based on Risk

A project should not move to the top merely because the neighbourhood is politically influential.

Consider:

12.29The Infrastructure Funding Gap

An asset plan becomes useful only when it connects infrastructure need to financial capacity.

Ontario's current asset-management framework requires municipalities to identify proposed levels of service, the activities required to achieve them and a strategy for financing those activities.

The public should therefore be shown the basic relationship between:

What We Own

What It Requires

What We Currently Fund

What Is Missing

If there is a long-term funding gap, show it.

If it improves, show it.

If a decision widens it, show that too.

Do Not Hide the Gap With Grants

A grant can help close an infrastructure gap.

Until it is approved, it is not funding.

The public dashboard should distinguish:

This protects long-term planning from wishful accounting.

12.30Service Levels

Infrastructure exists to provide a service.

A road is not valuable merely because asphalt exists.

It provides transportation.

A water main provides drinking water.

A park provides recreation and public space.

A building provides a municipal service.

Ontario's asset-management framework specifically requires municipalities to consider current and proposed levels of service.

That concept should be explained publicly.

A Service Level Answers

What result are residents paying for?

Examples might include:

Higher Service Has a Cost

Residents should be able to see the relationship.

For some asset classes:

Current Service Level

What does it cost?

Higher Service Level

What improvement would residents notice?

What would it cost?

Lower Service Level

What saving occurs?

What deterioration or inconvenience results?

This turns infrastructure discussions into choices rather than slogans.

12.31Maintenance First

New projects receive attention.

Maintenance rarely receives ribbon cuttings.

That creates a dangerous incentive.

A municipality can become politically rewarded for building something new while receiving little recognition for properly maintaining what already exists.

This plan should reverse that mentality.

The Maintenance Principle

Take care of what we have before expanding what we cannot afford to maintain.

Before approving a major new asset, Council should see:

Sometimes expansion will still be the correct choice.

It should be made with the complete picture visible.

12.32Preventive Maintenance

Preventive maintenance should be treated as investment.

Examples can include:

A small intervention performed at the right time can extend asset life substantially.

Measure Avoided Cost Conservatively

Where preventive maintenance is claimed to save money, use credible lifecycle information.

Do not exaggerate.

If the precise dollar saving cannot reasonably be established, report:

Expected lifecycle extension

rather than inventing a number.

12.33Coordinate the Capital Program

The Infrastructure Index should help departments work together.

Before significant work occurs at a location, the City should ask:

One Street, One Plan

Where practical, major reconstruction should consider the whole street at once.

Instead of separate plans for:

create one coordinated street project.

This reduces repeated disruption and can improve long-term value.

12.34Infrastructure and Development

New development can create new municipal assets.

New streets.

New pipes.

New sidewalks.

New lighting.

New parks.

Those assets eventually become maintenance responsibilities.

Before accepting new municipal infrastructure, Council and staff should understand:

Growth Should Pay Attention to Lifecycle Cost

Development can increase assessment and economic activity.

It can also increase long-term municipal obligations.

Both sides of the equation should be considered.

A new neighbourhood that produces revenue but creates infrastructure requiring more service than the revenue supports may place pressure on future taxpayers.

Long-term fiscal impact should therefore become part of major growth planning.

12.35Infrastructure and Accessibility

Every major renewal project creates an opportunity to remove existing barriers.

When a sidewalk is reconstructed, examine curb ramps.

When a park is renewed, examine access.

When a building is renovated, examine physical and sensory accessibility.

When signs are replaced, examine readability.

When a digital system is modernized, examine digital accessibility.

Fix Once

If a major asset is already being reconstructed, accessibility improvements are often less costly than returning later to retrofit the same area.

The Infrastructure Index should flag accessibility opportunities early enough to incorporate them into project planning.

12.36Infrastructure and Climate Resilience

Regardless of political disagreement around climate policy, municipalities must manage physical risks that affect municipal assets.

These may include:

Infrastructure planning should examine demonstrated local risk and design assets accordingly.

The question should remain practical:

What conditions must this asset reasonably withstand during its expected life?

Resilience is fundamentally an asset-management responsibility.

12.37Infrastructure and Emergency Planning

The Infrastructure Index should connect with emergency-management planning.

Critical assets should have appropriate internal classifications.

Examples may include:

The public does not need every operational detail.

Municipal leadership needs to know:

This information will help inform the later Local Knowledge and east-west transportation sections.

12.38Local Knowledge From Tradespeople

One of the most valuable aspects of the original Infrastructure Index idea is that professional municipal information can be reviewed by a community containing:

Public participation should never replace professional engineering or regulatory responsibility.

It can still generate useful questions.

Community Infrastructure Sessions

Once a year, invite residents with practical knowledge to review public asset information.

Ask:

Staff evaluate the ideas.

The public does not direct infrastructure work by popular vote.

The community becomes another source of observation and practical knowledge.

12.39Students and Infrastructure Education

The Index can also become an educational resource.

Students could learn:

Practical Canadian Civics

Understanding how a City actually works is civic education.

A student who understands:

where water comes from,

where wastewater goes,

how property taxes become a road,

why infrastructure must be replaced,

understands government differently.

This connects directly to the proposed paid student mapping and leadership opportunities already identified in the plan.

12.40Public Reporting Without Crowdsourcing Engineering

There must be a clear boundary.

Residents may:

Qualified professionals remain responsible for:

Public participation improves the information available.

It does not replace professional responsibility.

12.41Asset Identification

Major public assets could eventually receive simple identification numbers.

For example:

OS-ROAD-00428

OS-PARK-0017

OS-BLDG-0009

Residents would not need to memorize these numbers.

They would provide a consistent link between:

Scan Where Useful

At appropriate public facilities or equipment, a small code could allow residents to access:

The system should remain usable without scanning or owning a smartphone.

12.42Asset History

For significant assets, preserve the history.

Example

1968

Original construction.

1994

Major rehabilitation.

2016

Mechanical replacement.

2025

Condition assessment.

2029

Planned major renewal.

This gives future staff and residents context.

Municipal history should not disappear every time software changes.

12.43Photographic Records

Photographs can be useful for appropriate public assets.

Examples include:

Images should be dated.

They can help demonstrate:

Before and After

For significant visible community improvements, publish:

Before

Work Completed

Cost

After

This creates understandable accountability.

12.44Capital Project Pages

Every significant capital project should eventually have its own public page.

Project Page

Problem

Why is the project required?

Asset

What infrastructure is involved?

Condition

What is wrong?

Options

What alternatives were considered?

Approved Solution

What is being built?

Budget

Original approved budget.

Funding

Who pays?

Contract

Who is performing the work?

Schedule

Expected start and completion.

Current Status

Where is it today?

Changes

Significant changes or delays.

Final Cost

Published upon completion.

Outcome

What service improved?

This should connect directly to the Open Government contract and decision registers.

12.45Major Project Gateway

Large infrastructure projects should pass through defined stages.

Stage 1: Need

Do we have a real problem?

Stage 2: Options

What are the reasonable alternatives?

Stage 3: Preliminary Cost

What magnitude of investment are we considering?

Stage 4: Business Case

What is the public benefit?

Stage 5: Funding

How will it be paid for?

Stage 6: Design

What exactly are we building?

Stage 7: Procurement

Who will build it?

Stage 8: Construction

Is it on schedule and budget?

Stage 9: Commissioning

Does it work as intended?

Stage 10: Lifecycle

Who maintains and eventually replaces it?

The City should be able to stop or redesign a project at an early stage if evidence changes.

Money already spent studying an idea is not a reason to spend much more building a poor one.

12.46The Repair Versus Replace Test

For ageing assets, compare:

Repair

Rehabilitate

Replace

Retire

Does the City still need the asset?

The lowest immediate cost is not always the lowest lifecycle cost.

Neither is replacement always the answer.

12.47Asset Disposal

When the City no longer requires an asset, the decision should be intentional.

Ask:

The disposal should be recorded according to municipal policy.

A public asset should never simply disappear.

12.48The Infrastructure Scorecard

The quarterly and annual public scorecards should include infrastructure measures.

Condition

Percentage of assets by condition category.

Knowledge

Percentage of major assets with reliable condition information.

Maintenance

Planned maintenance completed.

Capital

Projects:

Financial

Risk

Number of high-risk assets.

Funding

Service

Significant service interruptions.

Accessibility

Barriers removed through capital work.

The purpose is to show whether infrastructure stewardship is improving over time.

12.49The Infrastructure Warning List

A Mayor and Council should know which assets keep senior staff awake at night.

Once each year, administration should provide Council with a prioritized Infrastructure Warning List.

Where lawful to publish, identify:

Security-sensitive details can be handled appropriately.

The principle remains:

Bad news should reach Council early.

A problem becomes more expensive when political discomfort delays acknowledgement.

12.50The Five-Year Look Ahead

Residents should not learn about major capital needs only when the budget arrives.

Maintain a rolling five-year infrastructure outlook.

Show:

Year One

Approved projects.

Year Two

High-confidence planned projects.

Years Three to Five

Forecast renewal.

Beyond Five Years

Known major liabilities and expected investments.

The farther we look into the future, the less precise the numbers will be.

That is acceptable.

A forecast is not a promise.

It is preparation.

12.51The Twenty-Five-Year View

For major asset classes, the City should also maintain a long-range outlook.

Over twenty-five years:

These costs should not surprise us simply because they occur after the next election.

The twenty-five-year view should identify broad renewal requirements rather than pretending to predict an exact construction budget decades in advance.

12.52The Annual Infrastructure Walk

Once each year, hold a public Infrastructure Day.

Not as political theatre.

As civic education.

Residents, students, tradespeople and interested organizations could visit selected sites and learn:

Staff members who understand these systems should be given the opportunity to explain their work.

This builds appreciation for both the assets and the people maintaining them.

12.53Infrastructure Should Be Understandable to a Student

A useful test for the public Index is:

Could a high school student use it to understand how Owen Sound physically works?

If yes, we have probably made the information accessible.

If it can only be interpreted by:

then we have published professional information without yet creating public understanding.

Both are necessary.

12.54The First-Year Infrastructure Index Build

The first year should focus on bringing existing information together rather than commissioning an entirely new inventory from scratch.

Step 1: Use Existing Asset Information

Begin with the City's current asset-management plans, GIS information, financial asset records, facilities information and capital forecasts.

Owen Sound already has a comprehensive asset-management framework covering core and non-core infrastructure.

Step 2: Establish Public Asset Categories

Create consistent public categories.

Step 3: Identify Information Gaps

Determine where:

Step 4: Protect Sensitive Information

Establish clear security and privacy rules.

Step 5: Build the Public Map

Begin with low-risk, high-value information:

Step 6: Add Condition

Introduce simplified condition information.

Step 7: Add Cost

Show renewal and replacement planning estimates.

Step 8: Add Work History

Connect major maintenance and capital projects.

Step 9: Connect First to Action

Allow service reports to reference the appropriate public asset where useful.

Step 10: Publish the First Infrastructure Report

Show:

12.55Year Two

During Year Two:

12.56Year Three

During Year Three:

12.57Year Four

By Year Four, Owen Sound should have a public infrastructure system that allows an ordinary resident to understand:

That becomes one of the clearest measures of whether this business plan actually improved municipal stewardship.

12.58What This Is Not

The Infrastructure and Systems Index is not:

It is a public management system.

It connects:

asset

to

condition

to

service

to

maintenance

to

cost

to

decision

to

result.

The Infrastructure Commitment

Owen Sound inherited an enormous physical investment from the people who built this community before us.

Our responsibility is not simply to enjoy it.

Our responsibility is to maintain it and eventually pass it forward.

That requires us to know what we have.

To inspect it.

To maintain it.

To repair it at the right time.

To replace it when necessary.

To coordinate work before digging twice.

To distinguish true efficiency from deferred maintenance.

To understand the cost before adding another asset.

To explain the funding gap honestly.

And to allow residents to see the condition of the community they collectively own.

The principle is simple:

Know what we own.

Know what it does.

Know what condition it is in.

Know what it costs to maintain.

Know when it needs replacing.

Fund it honestly.

Show the work.

Infrastructure should not become visible for the first time when it fails.

Good stewardship means knowing what is beneath our feet before it becomes an emergency.

← Chapter 11: Local Trades and ProcurementChapter 13: Local Knowledge and Emergency Resilience →