Home › Appendices › Appendix F

Appendices

Appendix FMunicipal Assets and Public Ownership

8,772 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

F.1 Purpose
F.2 The Municipal Asset Register
F.3 One Register, Multiple Systems
F.4 Asset Register Versus Infrastructure Index
F.5 Asset Register Is Broader
F.6 Asset Categories
F.7 Asset ID
F.8 Stable ID
F.9 Ownership Field
F.10 Ownership Is Not Operation
F.11 Operation Is Not Ownership
F.12 Funding Is Not Ownership
F.13 Regulation Is Not Ownership
F.14 Asset Record
F.15 Public Versus Protected Fields
F.16 Public Layer
F.17 Protected Layer
F.18 Open Government Does Not Mean Open Vulnerability
F.19 Security Is Not Excuse for Secrecy
F.20 Public Ownership Principle
F.21 Mayor Does Not Own Them
F.22 Council Does Not Own Them Personally
F.23 Department Does Not Own Them Personally
F.24 Institutional Ownership
F.25 Custodianship
F.26 Custodian Is Not Free to Dispose
F.27 Lifecycle
F.28 Acquisition Is Not End
F.29 Asset Acceptance Gate
F.30 Free Asset
F.31 Donated Asset
F.32 Asset Transfer
F.33 Transfer Payment
F.34 Acceptance Cost
F.35 Condition Assessment
F.36 Professional Inspection
F.37 Unknown Condition
F.38 Condition Confidence
F.39 Example
F.40 Condition Categories
F.41 Condition Is Not Risk
F.42 Criticality
F.43 Criticality Factors
F.44 Risk
F.45 Unknown High-Criticality Asset
F.46 Inspection Priority
F.47 First Asset Question
F.48 Maintenance
F.49 Preventive Maintenance
F.50 Reactive Maintenance
F.51 Not All Assets Need Same Strategy
F.52 Maintenance Standard
F.53 Maintenance Completion
F.54 Asset Reliability
F.55 Maintenance Backlog
F.56 Backlog Age
F.57 Oldest High-Risk Deferred Work
F.58 No Invisible Deferral
F.59 Maintenance Saving Myth
F.60 Deferred Liability
F.61 Asset Renewal
F.62 Repair Before Replace
F.63 Refurbish
F.64 Repurpose
F.65 Replace
F.66 Retire
F.67 Renewal Business Case
F.68 No Automatic Like-for-Like Replacement
F.69 No Automatic Upgrade
F.70 Scope Creep
F.71 Replacement Cost
F.72 Market Value
F.73 Insured Value
F.74 Four Different Values
F.75 Strategic Public Value
F.76 Low Market Value Can Still Mean High Public Value
F.77 High Market Value Can Still Be Surplus
F.78 Asset Decision Should Not Use One Number
F.79 Land Register
F.80 Land Record
F.81 Title
F.82 Mapping Is Not Title
F.83 Survey
F.84 Easements
F.85 Rights-of-Way
F.86 Covenants
F.87 Utility Rights
F.88 Access Rights
F.89 Environmental Liability
F.90 Contamination
F.91 Brownfield Opportunity
F.92 Heritage
F.93 Archaeology
F.94 SON Relationship
F.95 Do Not Treat Legal Ownership as Complete Answer
F.96 Waterfront
F.97 Public Access
F.98 Trail Connectivity
F.99 Utility Corridor
F.100 Future Crossing
F.101 Drainage
F.102 Emergency Access
F.103 Surplus Property
F.104 Surplus Test
F.105 Departmental Surplus Is Not Municipal Surplus
F.106 Example
F.107 Cross-Department Review
F.108 Strategic Hold
F.109 Strategic Hold Needs Reason
F.110 Surplus Decision
F.111 Sell
F.112 Lease
F.113 Licence
F.114 Partnership
F.115 Repurpose
F.116 Retain
F.117 Sale Is Irreversible
F.118 Lease Preserves Ownership
F.119 Lease Creates Obligations
F.120 Market Valuation
F.121 Book Value Is Not Sale Price
F.122 Assessment Value
F.123 Below-Market Transfer
F.124 Subsidy Must Be Visible
F.125 No Favourite Buyer
F.126 Conflict Review
F.127 Independent Valuation
F.128 Independent Process
F.129 No Mayoral Negotiated Giveaway
F.130 Sale Proceeds
F.131 Do Not Fund Permanent Operations Repeatedly by Selling Assets
F.132 Asset Sale Can Still Be Wise
F.133 Disposal Costs
F.134 Demolition
F.135 Demolition Before Sale
F.136 Building Register
F.137 Building Utilization
F.138 Underused Does Not Automatically Mean Surplus
F.139 Occupancy
F.140 Community Facility
F.141 Revenue Per Square Foot
F.142 Public Service Function
F.143 Accessibility
F.144 Accessible Entrance Alone
F.145 Full Route
F.146 Energy
F.147 Energy Retrofit
F.148 Avoided Energy Cost
F.149 Building Automation
F.150 Building Systems
F.151 Component-Level Planning
F.152 Avoid One Score Hiding Component Failure
F.153 Roads and Transportation Assets
F.154 Road Segment
F.155 Condition
F.156 Traffic Volume
F.157 Road Function
F.158 Underground Assets
F.159 One Street, One Plan
F.160 Do Not Pave Twice
F.161 Utility Coordination
F.162 Road Transfer
F.163 Road Transfer Due Diligence
F.164 Transfer Funding
F.165 No Free Roads
F.166 Bridge Register
F.167 Culverts
F.168 Small Structure
F.169 Water Assets
F.170 Critical Water Information
F.171 Public Water Information
F.172 Redundancy
F.173 Backup Power
F.174 Spare Parts
F.175 Single Point of Failure
F.176 Do Not Publish Exploit Map
F.177 Wastewater Assets
F.178 Stormwater Assets
F.179 Natural Systems
F.180 Natural Asset
F.181 Do Not Claim Another Owner's Wetland as City Asset
F.182 Natural Assets Can Have Service Value
F.183 Valuation
F.184 Trees
F.185 Tree Planting Is Acquisition
F.186 Tree Survival
F.187 Dead Tree
F.188 Tree Liability
F.189 Parks
F.190 Playground Inspection
F.191 Recreation Assets
F.192 Use Before Build
F.193 Utilization Is Not Value Alone
F.194 Public Realm
F.195 Grouped Assets
F.196 Public Art
F.197 Memorials
F.198 Fleet
F.199 Fleet Record
F.200 Vehicle Age Alone
F.201 Mileage Alone
F.202 Maintenance Cost
F.203 Downtime
F.204 Reliability
F.205 Safety
F.206 Parts Availability
F.207 Electrification
F.208 No Prestige Fleet
F.209 Telematics
F.210 Purpose-Limited Use
F.211 Equipment
F.212 Theft Risk
F.213 Tools
F.214 Materiality
F.215 Specialized Equipment
F.216 Emergency Equipment
F.217 Spares
F.218 "Unused"
F.219 Standby
F.220 Abandoned Asset
F.221 Dormant Asset Review
F.222 Leased-In Assets
F.223 Leased-Out Assets
F.224 Below-Market Lease
F.225 Public-Purpose Lease
F.226 Expiring Lease
F.227 Lease Register
F.228 Licence
F.229 Shared Facility
F.230 Partnership Asset
F.231 Joint Ownership
F.232 Ownership Percentage
F.233 Decision Rights
F.234 Capital Contribution
F.235 Dissolution
F.236 Shared Asset Exit
F.237 Easements and Strategic Rights
F.238 Examples
F.239 Register Them
F.240 Expiry
F.241 Conditions
F.242 Release
F.243 Small Strip, Big Consequence
F.244 Future Infrastructure
F.245 No Permanent Hold Without Reason
F.246 Digital Assets
F.247 Digital Asset Categories
F.248 Domain Ownership
F.249 Registrar
F.250 Not Employee Personal Account
F.251 Recovery Access
F.252 Software Account
F.253 Cloud Tenant
F.254 Source Repository
F.255 Administrative Credentials
F.256 Privileged Access
F.257 Credential Inventory
F.258 Digital Ownership Question
F.259 Licence Is Not Ownership
F.260 Subscription Is Not Ownership
F.261 Cloud Is Not Ownership
F.262 Control Matters
F.263 Digital Exit Score
F.264 Data Export
F.265 PDF Dump
F.266 Proprietary Format
F.267 Documentation
F.268 Undocumented System
F.269 Key-Person Dependency
F.270 Vendor-Only Knowledge
F.271 Source Code Escrow
F.272 Open Source
F.273 Digital Asset Register
F.274 Data as Asset and Liability
F.275 More Data Is Not More Value Automatically
F.276 Data Minimization
F.277 Data Owner
F.278 Data Steward
F.279 Source of Truth
F.280 Duplicate Data
F.281 Stale Data
F.282 Records Retention
F.283 Deletion
F.284 Do Not Keep Everything Forever
F.285 Do Not Delete to Avoid Disclosure
F.286 Intellectual Property
F.287 Contractor Work
F.288 Licence Rights
F.289 Future Reuse
F.290 Open Licensing
F.291 Not All IP Should Be Open
F.292 Public Playbook
F.293 Map.ca Public Infrastructure
F.294 Private Founder Interest
F.295 No Founder Veto
F.296 Independent Review
F.297 Public Standard First
F.298 Transfer or Licence Structure
F.299 Independent Valuation
F.300 No Windfall
F.301 RealMap
F.302 RealMap Data
F.303 City Data
F.304 Private Platform Data
F.305 Separation
F.306 Contracts as Assets and Obligations
F.307 Contract Register
F.308 Major Contract Fields
F.309 Warranty
F.310 Guarantee
F.311 Maintenance Agreement
F.312 Service-Level Agreement
F.313 Renewal Date
F.314 Automatic Renewal
F.315 Unused Warranty
F.316 Insurance
F.317 Insured
F.318 Deductible
F.319 Exclusions
F.320 Replacement Value
F.321 Business Continuity
F.322 Disaster Recovery
F.323 Critical Spares
F.324 Asset Dependency Map
F.325 Example
F.326 Single Asset View Is Not Enough
F.327 Critical Service Chain
F.328 Public Version
F.329 Resilience
F.330 Redundancy Has Cost
F.331 Resilience Investment
F.332 Backup Asset
F.333 Utilization Metrics Need Context
F.334 Asset Dependency on External Supplier
F.335 Sole Supplier
F.336 Parts Obsolescence
F.337 End-of-Life Support
F.338 Digital End-of-Life
F.339 Fleet Parts
F.340 Infrastructure Materials
F.341 Canadian Capacity
F.342 Not Absolute
F.343 Foreign Supplier
F.344 Asset Acquisition
F.345 No Grant-Driven Asset
F.346 No Donor-Driven Asset
F.347 No Prestige Asset
F.348 Acquisition Alternatives
F.349 Buy Versus Lease
F.350 Lease Can Cost More Long Term
F.351 Buy Can Lock Capital
F.352 Shared Asset
F.353 Shared Asset Can Complicate Governance
F.354 Rental
F.355 Purchase
F.356 Donated Property
F.357 Federal or Provincial Asset Transfer
F.358 Harbour Example
F.359 Harbour Asset Due Diligence
F.360 Transfer Price
F.361 Liability First
F.362 Asset Acquisition Approval
F.363 Acceptance Documentation
F.364 Departmental Gifts
F.365 Asset Disposal
F.366 Disposal Does Not Always Mean Sale
F.367 Data-Bearing Equipment
F.368 Reuse
F.369 Device Reuse
F.370 E-Waste
F.371 Vehicle Sale
F.372 Asset Retirement
F.373 Ghost Assets
F.374 Missing Assets
F.375 Asset Reconciliation
F.376 Accounting Register Versus Operational Register
F.377 Fully Depreciated Asset
F.378 Zero Book Value
F.379 Conversely
F.380 Finance and Operations Need Both Views
F.381 Asset Utilization
F.382 Utilization Formula
F.383 Arena Utilization
F.384 Do Not Create Universal Utilization Metric
F.385 Low Utilization
F.386 Or Required Reserve Capacity
F.387 High Utilization
F.388 Or overuse and insufficient maintenance windows.
F.389 Asset Accessibility
F.390 Barrier Register
F.391 Capital Project
F.392 Do Not Rebuild Barrier
F.393 New Asset
F.394 Digital Asset Accessibility
F.395 Environmental Stewardship
F.396 Environmental Risk Is Financial Risk
F.397 Contaminated Land
F.398 Flood-Prone Asset
F.399 Climate Context
F.400 Do Not Use Climate as Generic Explanation
F.401 Records and Asset History
F.402 History Can Include
F.403 Knowledge Should Survive Retirement
F.404 Photograph
F.405 Drawings
F.406 As-Built Records
F.407 Maintenance Manuals
F.408 Digital Documentation
F.409 Vendor Documentation
F.410 No Knowledge in One Employee's Inbox
F.411 Institutional Repository
F.412 Sensitive Documents
F.413 Asset Ownership Map
F.414 Public Map Is Not Legal Survey
F.415 Public Map Should Be Dated
F.416 Ownership Confidence
F.417 Asset Change Log
F.418 Public Asset Dashboard
F.419 Inventory Completion
F.420 Condition Coverage
F.421 Confidence Coverage
F.422 Unknown Critical Assets
F.423 Maintenance Completion
F.424 Deferred Maintenance Cost
F.425 Deferred Maintenance Age
F.426 Accessibility Barrier Age
F.427 Lease Expiry Risk
F.428 Digital Exit Coverage
F.429 Backup Coverage
F.430 Restore-Test Coverage
F.431 Asset Insurance Review
F.432 Title Review
F.433 Environmental Review
F.434 Traffic Lights
F.435 Grey Is Important
F.436 No One Asset Score
F.437 Public Asset Card
F.438 Protected Card
F.439 Anti-Gaming Rule One
F.440 Rule Two
F.441 Rule Three
F.442 Rule Four
F.443 Rule Five
F.444 Rule Six
F.445 Rule Seven
F.446 Rule Eight
F.447 Rule Nine
F.448 Rule Ten
F.449 Rule Eleven
F.450 Rule Twelve
F.451 Rule Thirteen
F.452 Rule Fourteen
F.453 Rule Fifteen
F.454 Rule Sixteen
F.455 Rule Seventeen
F.456 Rule Eighteen
F.457 Rule Nineteen
F.458 Rule Twenty
F.459 Rule Twenty-One
F.460 Rule Twenty-Two
F.461 Rule Twenty-Three
F.462 Rule Twenty-Four
F.463 Rule Twenty-Five
F.464 Rule Twenty-Six
F.465 Rule Twenty-Seven
F.466 Rule Twenty-Eight
F.467 Rule Twenty-Nine
F.468 Rule Thirty
F.469 Rule Thirty-One
F.470 Rule Thirty-Two
F.471 Rule Thirty-Three
F.472 Rule Thirty-Four
F.473 Rule Thirty-Five
F.474 Rule Thirty-Six
F.475 Rule Thirty-Seven
F.476 Rule Thirty-Eight
F.477 Rule Thirty-Nine
F.478 Rule Forty
F.479 Rule Forty-One
F.480 Rule Forty-Two
F.481 Rule Forty-Three
F.482 Rule Forty-Four
F.483 Rule Forty-Five
F.484 Rule Forty-Six
F.485 Rule Forty-Seven
F.486 Rule Forty-Eight
F.487 Rule Forty-Nine
F.488 Rule Fifty
F.489 The Ownership Test
F.490 The Control Test
F.491 The Operation Test
F.492 The Regulation Test
F.493 The Condition Test
F.494 The Confidence Test
F.495 The Criticality Test
F.496 The Maintenance Test
F.497 The Complete Cost Test
F.498 The Replacement Test
F.499 The Repair Test
F.500 The Utilization Test
F.501 The Resilience Test
F.502 The Accessibility Test
F.503 The Environmental Test
F.504 The Legal Test
F.505 The Digital Test
F.506 The Exit Test
F.507 The Surplus Test
F.508 The Future Test
F.509 The One-Taxpayer Test
F.510 The Conflict Test
F.511 The Reverse Test
F.512 The Stewardship Test
F.513 First 30 Days
F.514 First 30 Days Should Not Attempt Full Inspection
F.515 First 60 Days
F.516 Gap Report
F.517 First 100 Days
F.518 Year One
F.519 Year One Property Review
F.520 Do Not Sell During Inventory Panic
F.521 Year Two
F.522 Year Two Surplus Review
F.523 Year Three
F.524 Year Four
F.525 Four-Year Asset Audit
F.526 Name the Most Important Asset Newly Inventoried
F.527 Name the Largest Condition Unknown Resolved
F.528 Name the Largest Remaining Condition Unknown
F.529 Name the Highest-Risk Deferred Asset
F.530 Name the Largest Maintenance Backlog Reduced
F.531 Name the Largest New Maintenance Backlog Created
F.532 Name the Most Important Repair-Before-Replace Decision
F.533 Name the Most Important Asset Replacement
F.534 Name the Most Important Asset the City Chose Not to Build
F.535 Name the Most Important Strategic Property Retained
F.536 Name the Largest Property Disposition
F.537 Show the Public Reason
F.538 Name the Largest Below-Market Public Contribution
F.539 Name the Largest Asset Acquisition
F.540 Name the Largest Liability Accepted With an Asset
F.541 Name the Most Important Easement or Strategic Right Preserved
F.542 Name the Major Asset Transfer With the Largest Long-Term Municipal Impact
F.543 Name the Digital System With the Strongest Municipal Control
F.544 Name the Digital System With the Highest Remaining Lock-In Risk
F.545 Name a System Successfully Exited
F.546 Name an Asset Where Accessibility Was Improved During Renewal
F.547 Name an Asset Where Environmental Risk Changed the Decision
F.548 Name a Donated or Low-Cost Asset the City Declined Because Complete Cost Was Too High
F.549 Name a Surplus Asset the City Decided to Retain for Strategic reasons
F.550 Asset Handoff
F.551 No Asset Surprise
F.552 Or
F.553 Or
F.554 Or
F.555 Asset Knowledge Is Government Knowledge
F.556 The Municipal Assets and Public Ownership Commitment

Know what the City owns before deciding what it needs to buy, sell, transfer or build

A municipality cannot manage its future responsibly if it does not know:

what it owns;
what it leases;
what it operates;
what it is responsible for maintaining;
what condition those assets are in;
what rights are attached to them;
what obligations travel with them;
what they cost to keep;
what they would cost to replace;
what information about them must remain protected.

Municipal assets are not limited to:

buildings;
roads;
vehicles.

They can include:

land;
easements;
bridges;
culverts;
sidewalks;
water infrastructure;
wastewater infrastructure;
stormwater systems;
parks;
trails;
trees;
public art;
equipment;
fleet;
software;
municipal data;
domains;
digital identities;
intellectual property;
contracts;
access rights;
licences;
utility corridors;
strategic rights-of-way.

Some assets are visible.

Some are underground.

Some exist only as:

legal rights;
data;
software;
contractual control.

Some are valuable because of what they do today.

Others may be valuable because they preserve:

access;
resilience;
future infrastructure options;
public ownership;
strategic independence.

The central principle is:

The City should know what it owns before deciding what it needs to buy, sell or build.

A second principle follows:

Public ownership is not an argument for keeping everything forever. It is an obligation to make deliberate decisions about assets held in trust for the public.

The standard should be:

Own what should remain public. Maintain what we own. Protect strategic rights. Share or lease when that creates better public value. Sell only when an asset is genuinely surplus. Never accept an asset without understanding the liability attached to it.

F.1Purpose

This appendix establishes the framework for identifying, managing, protecting, maintaining, acquiring, transferring and disposing of municipal assets.

F.2The Municipal Asset Register

Owen Sound should maintain one authoritative:

Municipal Asset Register.

F.3One Register, Multiple Systems

This does not require all technical records to live in:

one software application.

It means the City should be able to reconcile its systems into:

one institutional understanding of what it owns and controls.

F.4Asset Register Versus Infrastructure Index

The Municipal Asset Register answers:

What do we own or control?

The Infrastructure Index answers:

What condition is it in, how confident are we, what risk does it create and what should happen next?

They should:

connect.

F.5Asset Register Is Broader

It should include assets beyond conventional infrastructure.

F.6Asset Categories

At minimum:

Land

Buildings

Roads and Transportation

Bridges and Structures

Water

Wastewater

Stormwater

Parks and Recreation

Natural Assets

Fleet

Equipment

Public Realm

Digital Systems

Data

Intellectual Property

Contracts and Legal Rights

Easements and Rights-of-Way

Leased Assets

Shared Assets

Strategic Future Assets

F.7Asset ID

Every material asset or logical asset group should have a stable:

Asset ID.

F.8Stable ID

Do not create a new identity every time:

department changes;
software changes;
asset is renamed.

F.9Ownership Field

Every asset should state:

Owned

Leased In

Leased Out

Licensed

Jointly Owned

Operated for Another Party

Third-Party Owned but City Dependent

Easement / Right

Other

F.10Ownership Is Not Operation

A City may own something another organization:

operates.

F.11Operation Is Not Ownership

A City may operate something it:

does not own.

F.12Funding Is Not Ownership

Another government may fund an asset without:

owning it.

F.13Regulation Is Not Ownership

Ontario or Canada may regulate an asset without:

owning it.

F.14Asset Record

Each material asset should identify:

Asset ID

Asset name

Owner

Operator

Custodian

Location

Service function

Condition

Condition confidence

Criticality

Last inspection

Next inspection

Maintenance status

Estimated remaining life

Replacement / renewal estimate

Insurance status

Legal restrictions

Easements / encumbrances

Funding restrictions

Accessibility status where relevant

Cybersecurity / digital status where relevant

Next major decision

F.15Public Versus Protected Fields

Not every field belongs on the public website.

F.16Public Layer

Residents should generally be able to see appropriate information about:

asset category;
ownership;
broad location;
service function;
condition category;
confidence;
planned work;
major costs;
public decisions.

F.17Protected Layer

Sensitive details may include:

security vulnerabilities;
critical infrastructure configurations;
access credentials;
precise control-system architecture;
sensitive utility information;
confidential legal information;
personal information.

F.18Open Government Does Not Mean Open Vulnerability

Do not publish information that unnecessarily helps someone:

disrupt;
attack;
sabotage;

critical infrastructure.

F.19Security Is Not Excuse for Secrecy

Protect only what genuinely requires:

protection.

F.20Public Ownership Principle

Municipal assets should be treated as:

public assets held by the municipal corporation for lawful public purposes.

F.21Mayor Does Not Own Them

F.22Council Does Not Own Them Personally

F.23Department Does Not Own Them Personally

F.24Institutional Ownership

Assets survive:

election;
retirement;
restructuring.

F.25Custodianship

Departments may be responsible for:

care;
use;
maintenance.

F.26Custodian Is Not Free to Dispose

No.

F.27Lifecycle

Every significant asset passes through a lifecycle:

Need

Business Case

Acquisition

Acceptance

Inventory

Operation

Inspection

Maintenance

Renewal

Repurpose

Transfer

Disposal

Archive / Record Retention

F.28Acquisition Is Not End

It is often:

beginning of obligation.

F.29Asset Acceptance Gate

Before Owen Sound accepts a significant new asset:

Ask:

Do we need it?

Who owns it?

What is its condition?

What liabilities come with it?

What does maintenance cost?

What will replacement cost?

Is insurance available?

Is contamination present?

Are accessibility upgrades required?

Are cyber or software dependencies involved?

Are warranties transferable?

Are there easements or restrictions?

What is the exit path?

F.30Free Asset

The phrase:

free asset

should trigger:

more questions.

F.31Donated Asset

May still create:

maintenance;
insurance;
storage;
repair;
staffing;
replacement;
disposal;

costs.

F.32Asset Transfer

Same.

F.33Transfer Payment

Does not erase:

lifecycle liability.

F.34Acceptance Cost

Include transition and onboarding costs.

F.35Condition Assessment

Do not accept significant infrastructure based only on:

visual impression.

F.36Professional Inspection

Use where warranted.

F.37Unknown Condition

Means:

Unknown.

Not:

Good.

F.38Condition Confidence

Every significant condition rating should also identify:

confidence.

F.39Example

An asset rated:

Fair, Low Confidence

is different from:

Fair, High Confidence.

F.40Condition Categories

Possible:

Very Good

Good

Fair

Poor

Very Poor

Unknown

Use definitions.

F.41Condition Is Not Risk

A poor-condition asset may be:

low consequence.

A fair-condition critical asset may create:

higher risk.

F.42Criticality

Measure:

What happens if this asset fails?

F.43Criticality Factors

Possible:

safety;
service interruption;
number of residents affected;
environmental impact;
legal obligation;
emergency role;
replacement difficulty;
financial consequence.

F.44Risk

A useful asset-risk view combines:

likelihood;
consequence;
confidence.

F.45Unknown High-Criticality Asset

Should receive:

attention.

F.46Inspection Priority

Unknown condition should not become a permanent:

category.

F.47First Asset Question

Do we know enough to make the decision?

F.48Maintenance

An asset should have a defined maintenance approach where material.

F.49Preventive Maintenance

Prefer where:

economically;
technically;

appropriate.

F.50Reactive Maintenance

Some assets can reasonably be:

run to failure.

F.51Not All Assets Need Same Strategy

Use:

risk;
cost;
criticality.

F.52Maintenance Standard

For critical assets ask:

Required maintenance?

Recommended maintenance?

Completed on time?

Deferred?

Why?

F.53Maintenance Completion

Activity metric.

F.54Asset Reliability

Outcome metric.

F.55Maintenance Backlog

Track where material.

F.56Backlog Age

Important.

F.57Oldest High-Risk Deferred Work

Publish.

F.58No Invisible Deferral

If maintenance is postponed:

Show.

F.59Maintenance Saving Myth

Skipping required maintenance is not:

efficiency.

F.60Deferred Liability

It may create:

future cost.

F.61Asset Renewal

Renew when lifecycle evidence supports it.

F.62Repair Before Replace

Always consider.

F.63Refurbish

Consider.

F.64Repurpose

Consider.

F.65Replace

Where justified.

F.66Retire

Where no longer needed.

F.67Renewal Business Case

For significant replacement:

Compare:

Repair

Refurbish

Replace Like-for-Like

Change Service Model

Share

Lease

Dispose

F.68No Automatic Like-for-Like Replacement

Needs may have changed.

F.69No Automatic Upgrade

A replacement project should not become:

expansion;

without clear decision.

F.70Scope Creep

Track.

F.71Replacement Cost

Book value is not:

replacement cost.

F.72Market Value

Also different.

F.73Insured Value

Also may differ.

F.74Four Different Values

An asset may have:

Accounting value

Market value

Replacement value

Strategic public value

They are not interchangeable.

F.75Strategic Public Value

May include:

waterfront access;
future road corridor;
utility access;
park connection;
emergency redundancy;
public gathering space.

F.76Low Market Value Can Still Mean High Public Value

Important.

F.77High Market Value Can Still Be Surplus

Also possible.

F.78Asset Decision Should Not Use One Number

No.

F.79Land Register

Municipal land deserves a dedicated:

inventory.

F.80Land Record

For each material parcel:

Ownership

Legal description

Current use

Department

Zoning

Official Plan designation where relevant

Easements

Encumbrances

Environmental status

Heritage status where relevant

Access

Servicing

Strategic importance

Lease status

Surplus status

F.81Title

Verify.

F.82Mapping Is Not Title

A GIS polygon is not:

legal title.

F.83Survey

Where boundaries matter:

Use qualified survey information.

F.84Easements

Can materially affect:

use;
value;
construction.

F.85Rights-of-Way

Same.

F.86Covenants

Same.

F.87Utility Rights

Same.

F.88Access Rights

Same.

F.89Environmental Liability

Before acquisition or disposition:

Understand where material.

F.90Contamination

Can turn cheap property into:

expensive liability.

F.91Brownfield Opportunity

Can also create:

public opportunity.

But complete cost.

F.92Heritage

May create:

public value;
legal obligations;
capital cost.

F.93Archaeology

May require:

specific review;
Indigenous engagement;
regulatory process.

F.94SON Relationship

Land and waterfront decisions should consider early whether:

SON rights;
shared interests;
archaeology;

may be relevant.

F.95Do Not Treat Legal Ownership as Complete Answer

Title does not erase:

rights;
regulation;
history.

F.96Waterfront

Strategic waterfront land deserves particularly careful:

long-term review.

F.97Public Access

Before selling waterfront or corridor land:

Ask:

Could this permanently affect public access?

F.98Trail Connectivity

Same.

F.99Utility Corridor

Same.

F.100Future Crossing

Same.

F.101Drainage

Same.

F.102Emergency Access

Same.

F.103Surplus Property

An asset should not be declared:

surplus

merely because:

no department currently uses it.

F.104Surplus Test

Ask:

Current operational need?

Future operational need?

Infrastructure need?

Housing opportunity?

Park or trail opportunity?

Public access value?

Environmental value?

Emergency value?

Strategic corridor value?

Revenue potential?

Partnership potential?

F.105Departmental Surplus Is Not Municipal Surplus

Critical.

F.106Example

Public Works may not need a strip of land.

But the City may need it later for:

trail;
pipe;
road widening;
drainage.

F.107Cross-Department Review

Before surplus designation.

F.108Strategic Hold

Some assets should be:

held deliberately

even without current use.

F.109Strategic Hold Needs Reason

Do not warehouse land indefinitely without:

purpose.

F.110Surplus Decision

Should identify:

reason;
alternatives;
value;
future implications.

F.111Sell

One option.

F.112Lease

Another.

F.113Licence

Another.

F.114Partnership

Another.

F.115Repurpose

Another.

F.116Retain

Another.

F.117Sale Is Irreversible

Often.

F.118Lease Preserves Ownership

Could be better.

F.119Lease Creates Obligations

Also.

F.120Market Valuation

Use qualified valuation where material.

F.121Book Value Is Not Sale Price

No.

F.122Assessment Value

Not automatically:

market value.

F.123Below-Market Transfer

May create public subsidy and legal issues.

F.124Subsidy Must Be Visible

If lawful.

F.125No Favourite Buyer

Never.

F.126Conflict Review

Required where:

elected official;
staff;
family;
associated business;

has interest.

F.127Independent Valuation

Use where conflict risk is high.

F.128Independent Process

Use.

F.129No Mayoral Negotiated Giveaway

No.

F.130Sale Proceeds

One-time financial resource.

F.131Do Not Fund Permanent Operations Repeatedly by Selling Assets

That creates:

structural weakness.

F.132Asset Sale Can Still Be Wise

Where asset genuinely:

surplus.

F.133Disposal Costs

Consider:

legal;
survey;
remediation;
demolition;
transaction.

F.134Demolition

Is an asset decision.

F.135Demolition Before Sale

May change:

value;
liability.

F.136Building Register

Every City building should have:

Function

Ownership

Age where known

Condition

Structural status

Accessibility

Energy use where useful

Fire / life safety status

Major systems

Maintenance backlog

Annual operating cost

Utilization

Replacement / renewal plan

F.137Building Utilization

A building can be:

in good condition;
underused.

F.138Underused Does Not Automatically Mean Surplus

Could be:

strategic;
seasonal;
emergency;
specialized.

F.139Occupancy

Measure correctly.

F.140Community Facility

May create value beyond:

revenue.

F.141Revenue Per Square Foot

Not sole test.

F.142Public Service Function

Matters.

F.143Accessibility

Building condition should include:

accessible journey;

not merely structural condition.

F.144Accessible Entrance Alone

Not enough.

F.145Full Route

Consider:

arrival;
parking;
entrance;
interior;
washroom;
service point;
exit.

F.146Energy

Where useful track:

electricity;
gas;
water;
emissions;

using defensible methodology.

F.147Energy Retrofit

Measure:

actual performance.

F.148Avoided Energy Cost

Use proper baseline.

F.149Building Automation

Can improve efficiency.

But creates:

digital dependency;
cybersecurity;

risk.

F.150Building Systems

Include:

HVAC;
roofs;
electrical;
plumbing;
fire systems;
elevators;
controls.

F.151Component-Level Planning

A building can be:

Good

while roof is:

Poor.

F.152Avoid One Score Hiding Component Failure

F.153Roads and Transportation Assets

The register should include:

roads;
sidewalks;
bridges;
culverts;
traffic signals;
streetlights;
signs;
guardrails;
parking lots;
paths;
retaining structures.

F.154Road Segment

Use logical segmentation.

F.155Condition

Pavement condition should use:

consistent methodology.

F.156Traffic Volume

Useful context.

F.157Road Function

Local street and major corridor may have different:

consequences.

F.158Underground Assets

Coordinate.

F.159One Street, One Plan

Before reconstructing a street:

Review:

pavement;
water;
sewer;
stormwater;
sidewalks;
utilities;
accessibility;
trees;
cycling;
transit;
lighting.

F.160Do Not Pave Twice

Where reasonably avoidable.

F.161Utility Coordination

Critical.

F.162Road Transfer

When another government transfers road ownership:

Treat it as:

an asset acquisition.

F.163Road Transfer Due Diligence

Review:

Pavement

Structures

Culverts

Drainage

Signals

Signs

Lighting

Sidewalks

Land / right-of-way

Utilities

Maintenance history

Winter cost

Capital forecast

Deferred work

Transition funding

F.164Transfer Funding

Separate:

one-time;
temporary;
ongoing.

F.165No Free Roads

The question is:

What liability accompanies the kilometres?

F.166Bridge Register

Each bridge or major structure should identify:

inspection;
condition;
restrictions;
rehabilitation;
replacement;
criticality.

F.167Culverts

Do not ignore smaller structures.

F.168Small Structure

Can create major:

flooding;
road closure.

F.169Water Assets

The register should include appropriate classes such as:

treatment;
reservoirs;
mains;
valves;
hydrants;
pumps;
service connections where municipally owned.

F.170Critical Water Information

Detailed security-sensitive data may belong only in:

protected system.

F.171Public Water Information

Can still include:

age;
broad condition;
planned renewal;
investment.

F.172Redundancy

Critical systems should identify:

redundancy.

F.173Backup Power

Important.

F.174Spare Parts

Important.

F.175Single Point of Failure

Identify internally.

F.176Do Not Publish Exploit Map

No.

F.177Wastewater Assets

Include appropriate:

plants;
pumping;
sewers;
equipment;
outfalls;
controls.

F.178Stormwater Assets

Include:

sewers;
catch basins;
ponds;
channels;
culverts;
outlets;
other municipal controls.

F.179Natural Systems

Can be part of stormwater resilience.

F.180Natural Asset

A natural feature should only be listed as a municipal asset where the City has an actual:

ownership;
control;
stewardship;

basis appropriate to the record.

F.181Do Not Claim Another Owner's Wetland as City Asset

No.

F.182Natural Assets Can Have Service Value

Examples:

flood attenuation;
shade;
erosion control;
recreation.

F.183Valuation

Be cautious.

Not every ecosystem service needs:

artificial dollar figure.

F.184Trees

Municipal tree inventory can include:

location;
species;
condition;
maintenance;
replacement.

F.185Tree Planting Is Acquisition

F.186Tree Survival

Is outcome.

F.187Dead Tree

Not successful asset just because:

planted.

F.188Tree Liability

Old or hazardous trees may require:

risk management.

F.189Parks

Asset classes can include:

land;
playgrounds;
sports fields;
shelters;
lighting;
furniture;
paths;
washrooms.

F.190Playground Inspection

Separate from:

general park condition.

F.191Recreation Assets

Could include:

arenas;
pools where applicable;
courts;
fields;
equipment;
specialized facilities.

F.192Use Before Build

Track utilization before:

major expansion.

F.193Utilization Is Not Value Alone

A specialized emergency or accessibility asset may be rarely used but:

important.

F.194Public Realm

Benches, planters, public art, decorative lighting and similar assets should not disappear from the register simply because:

individually small.

F.195Grouped Assets

Can be managed as:

asset class.

F.196Public Art

Needs:

ownership;
artist rights;
maintenance;
insurance;
deaccession policy;

where relevant.

F.197Memorials

Same.

F.198Fleet

Fleet register should include:

vehicles;
heavy equipment;
transit vehicles;
fire apparatus;
trailers;
specialized machines.

F.199Fleet Record

Vehicle ID

Function

Age

Hours / kilometres

Condition

Maintenance

Downtime

Fuel / energy

Replacement forecast

Utilization

Criticality

F.200Vehicle Age Alone

Not replacement trigger.

F.201Mileage Alone

Not enough.

F.202Maintenance Cost

Relevant.

F.203Downtime

Relevant.

F.204Reliability

Relevant.

F.205Safety

Relevant.

F.206Parts Availability

Relevant.

F.207Electrification

Evaluate where appropriate through:

duty cycle;
charging;
climate;
lifecycle;
operating needs.

F.208No Prestige Fleet

Do not buy technology for:

image.

F.209Telematics

Can improve:

routing;
maintenance.

But creates:

employee privacy;
cybersecurity;

issues.

F.210Purpose-Limited Use

Required.

F.211Equipment

Smaller equipment should be grouped or individually tracked according to:

value;
risk;
portability.

F.212Theft Risk

Consider.

F.213Tools

Not every screwdriver needs:

public Asset ID.

F.214Materiality

Use common sense.

F.215Specialized Equipment

Track individually.

F.216Emergency Equipment

High priority.

F.217Spares

A spare asset may create resilience.

F.218"Unused"

Does not automatically mean:

waste.

F.219Standby

Different from:

abandoned.

F.220Abandoned Asset

Should be identified.

F.221Dormant Asset Review

At least periodically.

F.222Leased-In Assets

The City should know:

Lease term

Renewal

Rent

Maintenance

Insurance

Improvements

Exit

Restoration obligations

F.223Leased-Out Assets

Also.

F.224Below-Market Lease

May represent:

public subsidy.

F.225Public-Purpose Lease

Can be justified.

Show:

value;
purpose;
authority.

F.226Expiring Lease

Should not become:

surprise.

F.227Lease Register

Maintain.

F.228Licence

Distinguish from:

lease;
ownership.

F.229Shared Facility

Clarify:

ownership;
scheduling;
maintenance;
capital;
insurance;
exit.

F.230Partnership Asset

Same.

F.231Joint Ownership

Needs governance.

F.232Ownership Percentage

Where relevant.

F.233Decision Rights

Important.

F.234Capital Contribution

Important.

F.235Dissolution

Important.

F.236Shared Asset Exit

Plan.

F.237Easements and Strategic Rights

Some of the City's most important assets may be:

rights;

rather than land.

F.238Examples

utility easement;
drainage easement;
access easement;
trail easement;
right-of-way;
encroachment right;
licence;
restrictive covenant benefit;
development right.

F.239Register Them

Do not leave strategic rights buried in:

old paper files.

F.240Expiry

Track.

F.241Conditions

Track.

F.242Release

Do not release easement without:

cross-department review.

F.243Small Strip, Big Consequence

A narrow access strip may be worth more strategically than:

sale price suggests.

F.244Future Infrastructure

Preserve corridors where evidence supports it.

F.245No Permanent Hold Without Reason

Again.

F.246Digital Assets

Digital infrastructure should be treated as:

municipal assets and dependencies

not merely IT expenses.

F.247Digital Asset Categories

Include:

domains;
websites;
software licences;
cloud tenancies;
databases;
source code;
APIs;
digital certificates;
administrative accounts;
repositories;
GIS layers;
municipal data;
configuration;
automation;
models;
documentation.

F.248Domain Ownership

The City should know:

Who legally controls every critical municipal domain?

F.249Registrar

Institutional account.

F.250Not Employee Personal Account

Never.

F.251Recovery Access

Institutional.

F.252Software Account

Same.

F.253Cloud Tenant

Same.

F.254Source Repository

Same.

F.255Administrative Credentials

Not a personal asset of:

employee;
contractor;
vendor.

F.256Privileged Access

Controlled.

F.257Credential Inventory

Protected, not public.

F.258Digital Ownership Question

For every significant system ask:

Who owns the data?

Who owns the code?

Who owns configuration?

Can City export?

In what format?

Can another supplier use it?

What survives termination?

F.259Licence Is Not Ownership

Buying software does not necessarily mean:

owning software.

F.260Subscription Is Not Ownership

No.

F.261Cloud Is Not Ownership

No.

F.262Control Matters

The practical question:

Can the City continue serving residents if the vendor relationship ends?

F.263Digital Exit Score

Measure.

F.264Data Export

Should be:

usable.

F.265PDF Dump

May not be sufficient.

F.266Proprietary Format

Risk.

F.267Documentation

An asset.

F.268Undocumented System

Risk.

F.269Key-Person Dependency

Risk.

F.270Vendor-Only Knowledge

Risk.

F.271Source Code Escrow

May be relevant in specialized contracts.

Not automatically necessary.

F.272Open Source

Can improve portability.

But does not remove:

governance;
support;
security;

needs.

F.273Digital Asset Register

Should connect with:

Digital Systems Index;
privacy;
cybersecurity;
procurement;
records.

F.274Data as Asset and Liability

Municipal data can have:

operational value;
legal obligations;
privacy risk;
security risk.

F.275More Data Is Not More Value Automatically

No.

F.276Data Minimization

May improve:

asset quality;
risk.

F.277Data Owner

Identify institutional owner.

F.278Data Steward

Identify.

F.279Source of Truth

Identify.

F.280Duplicate Data

Review.

F.281Stale Data

Archive or correct according to lawful records practices.

F.282Records Retention

Applies.

F.283Deletion

Must follow:

law;
records schedules;
legal holds;
operational requirements.

F.284Do Not Keep Everything Forever

No.

F.285Do Not Delete to Avoid Disclosure

Never.

F.286Intellectual Property

The City may own or control:

reports;
designs;
software;
branding;
photographs;
datasets;
documentation;

depending on law and contract.

F.287Contractor Work

Do not assume City owns:

Check contract.

F.288Licence Rights

May be sufficient.

But know.

F.289Future Reuse

Consider before procurement.

F.290Open Licensing

May create public value for:

municipal templates;
standards;
non-sensitive code.

F.291Not All IP Should Be Open

Security, third-party rights and other legitimate restrictions may apply.

F.292Public Playbook

Municipal methods can be shared where:

lawful;
useful.

F.293Map.ca Public Infrastructure

If any map.ca component were ever considered for municipal use:

Public ownership and control must be resolved before adoption.

F.294Private Founder Interest

Must remain:

separate.

F.295No Founder Veto

No municipal infrastructure should depend upon a private founder retaining:

personal veto;
privileged access;
irreversible control.

F.296Independent Review

Required.

F.297Public Standard First

Define:

open standards;
data portability;
governance;
accessibility;
privacy;
security;

before platform.

F.298Transfer or Licence Structure

If private technology becomes municipal infrastructure:

The City must know exactly what is:

transferred;
licensed;
retained;
controlled.

F.299Independent Valuation

Where private intellectual property is transferred:

Use appropriate:

independent valuation;
procurement;
legal;
conflict;

review.

F.300No Windfall

Municipal adoption should not create an undisclosed private financial benefit for:

elected official;
founder;
related party.

F.301RealMap

Same firewall.

F.302RealMap Data

Property information should not become:

resident behavioural profile.

F.303City Data

Should not flow into private platform for unrelated commercial use without:

lawful basis;
contract;
appropriate authorization.

F.304Private Platform Data

Should not automatically become:

City data.

F.305Separation

Important.

F.306Contracts as Assets and Obligations

A contract may create:

rights;
obligations;
renewal options;
termination rights;
data rights.

F.307Contract Register

Connect with asset register.

F.308Major Contract Fields

Vendor

Purpose

Asset / service

Start

End

Renewal

Annual cost

Ownership

Data rights

Exit

Liability

F.309Warranty

A contractual asset.

Track.

F.310Guarantee

Track.

F.311Maintenance Agreement

Track.

F.312Service-Level Agreement

Track.

F.313Renewal Date

Track.

F.314Automatic Renewal

Flag.

F.315Unused Warranty

Can waste:

public value.

F.316Insurance

Assets should have appropriate insurance review.

F.317Insured

Does not mean:

fully protected.

F.318Deductible

Matters.

F.319Exclusions

Matter.

F.320Replacement Value

Matter.

F.321Business Continuity

Insurance does not replace:

continuity planning.

F.322Disaster Recovery

Same.

F.323Critical Spares

Same.

F.324Asset Dependency Map

For critical services ask:

What other assets must work for this asset to function?

F.325Example

Water system may depend on:

electricity;
communications;
controls;
chemicals;
roads;
trained staff.

F.326Single Asset View Is Not Enough

Need:

system view.

F.327Critical Service Chain

Map internally.

F.328Public Version

Can summarize without revealing:

security-sensitive detail.

F.329Resilience

Asset management should ask:

What happens in power outage?

Flood?

Cyber incident?

Supplier interruption?

Severe winter?

Key staff absence?

F.330Redundancy Has Cost

But so does:

failure.

F.331Resilience Investment

Should be:

risk-based.

F.332Backup Asset

May look underused.

That can be intentional.

F.333Utilization Metrics Need Context

Always.

F.334Asset Dependency on External Supplier

Track for critical systems.

F.335Sole Supplier

Risk.

F.336Parts Obsolescence

Risk.

F.337End-of-Life Support

Risk.

F.338Digital End-of-Life

Risk.

F.339Fleet Parts

Risk.

F.340Infrastructure Materials

Risk.

F.341Canadian Capacity

Can be one resilience factor.

F.342Not Absolute

A Canadian supplier can still be:

single point of failure.

F.343Foreign Supplier

Can still be:

reliable.

Use evidence.

F.344Asset Acquisition

Every material purchase or transfer should originate from:

service need;
business case.

F.345No Grant-Driven Asset

Again.

F.346No Donor-Driven Asset

Again.

F.347No Prestige Asset

Again.

F.348Acquisition Alternatives

Consider:

Buy

Lease

Share

Rent

Partner

Repair Existing

Do Nothing

F.349Buy Versus Lease

Use:

Complete Cost;
control;
flexibility;
asset life.

F.350Lease Can Cost More Long Term

Possible.

F.351Buy Can Lock Capital

Possible.

F.352Shared Asset

May improve utilization.

F.353Shared Asset Can Complicate Governance

Also.

F.354Rental

Good for:

occasional use.

F.355Purchase

Better for:

frequent critical use.

F.356Donated Property

Complete due diligence.

F.357Federal or Provincial Asset Transfer

Complete due diligence.

F.358Harbour Example

If Owen Sound ever considers acquiring harbour assets from Canada:

Treat the transaction as one of the most significant asset acquisitions the City could undertake.

F.359Harbour Asset Due Diligence

At minimum consider:

Exact land and water interests

Structures

Docks

Breakwalls

Environmental conditions

Dredging responsibilities

Existing leases

Utilities

Roads

Security

Insurance

Capital backlog

Revenue

Staffing

Regulatory responsibilities

SON relationship and rights issues

Exit / future transfer

F.360Transfer Price

Could be:

smallest number in the analysis.

F.361Liability First

Important.

F.362Asset Acquisition Approval

Major acquisitions should identify:

Council decision;
funding;
ownership;
operating owner;
inspection;
liability;
public purpose.

F.363Acceptance Documentation

Do not let assets enter City ownership informally.

F.364Departmental Gifts

No informal acceptance of significant property.

F.365Asset Disposal

Disposal should follow:

law;
policy;
procurement or sale process;
environmental;
records;

requirements.

F.366Disposal Does Not Always Mean Sale

Could mean:

recycling;
donation where lawful;
trade-in;
destruction;
decommissioning.

F.367Data-Bearing Equipment

Requires secure:

erasure;
destruction;

before disposal.

F.368Reuse

Prefer where:

safe;
economical.

F.369Device Reuse

If devices are transferred to residents:

Ensure:

secure wipe;
inspection;
ownership transfer;
battery safety;
privacy;
accessibility;
clear limitations.

F.370E-Waste

Use appropriate:

disposal;
recycling.

F.371Vehicle Sale

Remove:

municipal equipment;
data;
identifying technology;

appropriately.

F.372Asset Retirement

Update systems.

F.373Ghost Assets

Do not keep disposed assets listed as:

active.

F.374Missing Assets

Investigate.

F.375Asset Reconciliation

Finance, operations and physical inventory should:

reconcile periodically.

F.376Accounting Register Versus Operational Register

They may differ in granularity.

They should still:

reconcile.

F.377Fully Depreciated Asset

May still be:

operationally critical.

F.378Zero Book Value

Does not mean:

zero public value.

F.379Conversely

Accounting asset may no longer be:

useful.

F.380Finance and Operations Need Both Views

F.381Asset Utilization

Useful for:

facilities;
fleet;
equipment.

F.382Utilization Formula

Should be defined for each class.

F.383Arena Utilization

Different from:

snowplow utilization.

F.384Do Not Create Universal Utilization Metric

No.

F.385Low Utilization

May indicate:

excess capacity.

F.386Or Required Reserve Capacity

Context.

F.387High Utilization

May indicate:

efficiency.

F.388Or overuse and insufficient maintenance windows.

Context.

F.389Asset Accessibility

For public-facing assets track:

known barriers;
accommodation;
correction plan.

F.390Barrier Register

Connect to:

Accessibility Scorecard.

F.391Capital Project

Should remove identified barriers where:

reasonably integrated.

F.392Do Not Rebuild Barrier

Never.

F.393New Asset

Accessibility review before:

acceptance.

F.394Digital Asset Accessibility

Same.

F.395Environmental Stewardship

Asset decisions should consider:

contamination;
drainage;
energy;
materials;
lifecycle;
natural systems.

F.396Environmental Risk Is Financial Risk

Often.

F.397Contaminated Land

Can affect:

value;
liability;
use.

F.398Flood-Prone Asset

Can affect:

insurance;
maintenance;
resilience.

F.399Climate Context

Asset planning should consider changing:

weather;
precipitation;
freeze-thaw;
heat;

where supported by evidence.

F.400Do Not Use Climate as Generic Explanation

Tie to:

actual asset risk.

F.401Records and Asset History

Every significant asset should have accessible institutional history.

F.402History Can Include

acquisition;
major repair;
inspection;
warranty;
incident;
ownership change;
disposal.

F.403Knowledge Should Survive Retirement

Yes.

F.404Photograph

Can be useful.

F.405Drawings

Important.

F.406As-Built Records

Important.

F.407Maintenance Manuals

Important.

F.408Digital Documentation

Important.

F.409Vendor Documentation

Important.

F.410No Knowledge in One Employee's Inbox

Avoid.

F.411Institutional Repository

Use.

F.412Sensitive Documents

Protected appropriately.

F.413Asset Ownership Map

A public map can identify appropriate:

City land;
facilities;
parks;
roads;
trails.

F.414Public Map Is Not Legal Survey

State.

F.415Public Map Should Be Dated

Yes.

F.416Ownership Confidence

If boundary uncertain:

Say.

F.417Asset Change Log

Major changes:

acquisition;
sale;
transfer;
lease;
demolition;
new build;

should appear.

F.418Public Asset Dashboard

Possible headline measures:

Assets inventoried

Assets with current condition assessment

High-criticality assets with unknown condition

Preventive maintenance completed

Deferred maintenance

Major assets acquired

Major assets disposed

Leases nearing expiry

Surplus properties

Digital systems with verified exit

Accessibility barriers outstanding

Major asset risks

F.419Inventory Completion

Possible:

Inventory Completion % = Material Assets Recorded ÷ Material Assets Expected

But denominator must be:

defensible.

F.420Condition Coverage

Condition Coverage % = Material Assets With Current Condition Rating ÷ Material Assets Requiring Condition Rating

F.421Confidence Coverage

Track.

F.422Unknown Critical Assets

Important.

F.423Maintenance Completion

Track by asset class.

F.424Deferred Maintenance Cost

Estimate cautiously.

F.425Deferred Maintenance Age

Important.

F.426Accessibility Barrier Age

Important.

F.427Lease Expiry Risk

Important.

F.428Digital Exit Coverage

Possible:

Exit-Tested Systems ÷ Critical Digital Systems

F.429Backup Coverage

Not enough alone.

F.430Restore-Test Coverage

Better.

F.431Asset Insurance Review

Track.

F.432Title Review

For strategic land.

F.433Environmental Review

For higher-risk land.

F.434Traffic Lights

Green

Condition, ownership, maintenance and next action sufficiently understood.

Amber

Known issue or upcoming intervention.

Red

High-risk deficiency or urgent unresolved obligation.

Grey

Ownership, condition or other essential information not sufficiently known.

F.435Grey Is Important

Unknown critical infrastructure should not appear:

Green.

F.436No One Asset Score

A single number can hide:

different risks.

F.437Public Asset Card

For significant assets:

Field	Information
Asset
Owner
Service
Condition
Confidence
Criticality
Last Review
Planned Work
Estimated Cost
Funding
Next Decision

F.438Protected Card

May contain additional:

technical;
security;
legal;

information.

F.439Anti-Gaming Rule One

Do not count an asset as known merely because:

it appears in accounting records.

F.440Rule Two

Do not count an asset as inspected because:

someone drove past it.

F.441Rule Three

Do not label condition Good because:

no complaint exists.

F.442Rule Four

Do not treat Unknown as Good.

F.443Rule Five

Do not remove poor assets from dashboard because:

embarrassing.

F.444Rule Six

Do not reduce maintenance backlog by:

deleting work orders.

F.445Rule Seven

Do not redefine required maintenance to make completion rate look higher.

F.446Rule Eight

Do not call deferred maintenance:

saving.

F.447Rule Nine

Do not call a transferred asset:

free.

F.448Rule Ten

Do not call a donated asset:

free.

F.449Rule Eleven

Do not count transition funding as:

permanent asset funding.

F.450Rule Twelve

Do not use book value as:

replacement value.

F.451Rule Thirteen

Do not use assessment value as:

market value automatically.

F.452Rule Fourteen

Do not use market value as:

strategic public value automatically.

F.453Rule Fifteen

Do not declare land surplus because:

one department has no use.

F.454Rule Sixteen

Do not sell strategic rights without:

cross-department review.

F.455Rule Seventeen

Do not use one favourable appraisal while ignoring:

material restrictions.

F.456Rule Eighteen

Do not hide public subsidy in:

below-market sale;
below-market lease.

F.457Rule Nineteen

Do not treat sale proceeds as:

recurring revenue.

F.458Rule Twenty

Do not build an asset simply because:

grant exists.

F.459Rule Twenty-One

Do not accept an asset simply because:

transfer price is low.

F.460Rule Twenty-Two

Do not acquire contaminated property without understanding:

liability.

F.461Rule Twenty-Three

Do not call City operation:

City ownership.

F.462Rule Twenty-Four

Do not call City ownership:

exclusive regulatory authority.

F.463Rule Twenty-Five

Do not call vendor-hosted data:

municipally controlled;

without knowing contract rights.

F.464Rule Twenty-Six

Do not call a software subscription:

owned technology.

F.465Rule Twenty-Seven

Do not call an export:

usable exit;

until tested.

F.466Rule Twenty-Eight

Do not call open source:

secure;

merely because source is open.

F.467Rule Twenty-Nine

Do not call Canadian hosting:

sovereignty;

without understanding ownership, control and exit.

F.468Rule Thirty

Do not let critical municipal domains or administrative accounts remain in:

employee;
contractor;
founder;

personal control.

F.469Rule Thirty-One

Do not let vendor retain sole administrative access to critical City system.

F.470Rule Thirty-Two

Do not publish security-sensitive asset details merely to appear transparent.

F.471Rule Thirty-Three

Do not use security as blanket excuse to hide:

ownership;
condition;
cost.

F.472Rule Thirty-Four

Do not count building accessibility complete because:

entrance has ramp.

F.473Rule Thirty-Five

Do not count tree planting as successful asset creation without:

survival.

F.474Rule Thirty-Six

Do not count a building as well-used based only on:

one busy event.

F.475Rule Thirty-Seven

Do not call standby equipment waste merely because:

rarely used.

F.476Rule Thirty-Eight

Do not call rarely used equipment resilient without proving:

need.

F.477Rule Thirty-Nine

Do not dispose of data-bearing equipment before:

secure erasure.

F.478Rule Forty

Do not remove an asset from records until:

disposal;
transfer;

is actually complete.

F.479Rule Forty-One

Do not leave disposed assets as:

active.

F.480Rule Forty-Two

Do not use GIS location as substitute for:

legal title.

F.481Rule Forty-Three

Do not release easements because:

they appear unused;

without future-needs review.

F.482Rule Forty-Four

Do not hide significant lease expiries.

F.483Rule Forty-Five

Do not allow automatic digital contract renewal to create:

accidental lock-in.

F.484Rule Forty-Six

Do not accept founder-associated technology into municipal infrastructure without:

independent conflict;
procurement;
valuation;
governance;

review.

F.485Rule Forty-Seven

Do not allow municipal adoption of private technology to create:

founder veto;
founder privileged access;
undisclosed founder windfall.

F.486Rule Forty-Eight

Do not combine private platform data and municipal data merely because:

technically possible.

F.487Rule Forty-Nine

Do not use a single asset-health percentage to conceal:

high-risk failures.

F.488Rule Fifty

Do not wait for catastrophic failure before learning what the City owns.

F.489The Ownership Test

Ask:

Who legally owns this?

F.490The Control Test

Who can make decisions about it?

F.491The Operation Test

Who operates it?

F.492The Regulation Test

Who regulates it?

F.493The Condition Test

What condition is it in?

F.494The Confidence Test

How sure are we?

F.495The Criticality Test

What happens if it fails?

F.496The Maintenance Test

Are we maintaining it deliberately?

F.497The Complete Cost Test

What does it cost to keep?

F.498The Replacement Test

What will it cost when its useful life ends?

F.499The Repair Test

Can we repair rather than replace?

F.500The Utilization Test

Are we using it enough for its purpose?

F.501The Resilience Test

What service depends on it and what happens during failure?

F.502The Accessibility Test

Can residents reasonably use it?

F.503The Environmental Test

What environmental liabilities or benefits travel with it?

F.504The Legal Test

What easements, covenants, leases, rights or obligations affect it?

F.505The Digital Test

If it is digital, what do we actually own?

F.506The Exit Test

Can we leave the vendor or dispose of the asset responsibly?

F.507The Surplus Test

Is it truly surplus to the whole municipality or only one department?

F.508The Future Test

Could disposing of this asset foreclose an important future public option?

F.509The One-Taxpayer Test

Would transferring ownership merely move the liability to another publicly funded institution?

F.510The Conflict Test

Who privately benefits from acquisition, sale, lease or transfer?

F.511The Reverse Test

Would we accept this transaction if a political opponent proposed the same deal for someone close to them?

F.512The Stewardship Test

Are we managing this asset as trustees for residents who will inherit the decision?

F.513First 30 Days

Begin an enterprise-wide review of:

asset registers;
land records;
leases;
major contracts;
digital systems;
major infrastructure classes;
strategic rights.

F.514First 30 Days Should Not Attempt Full Inspection

The goal is:

know where the records are and where the gaps are.

F.515First 60 Days

Produce:

Asset Register Gap Report.

F.516Gap Report

Identify:

Missing ownership records

Unknown condition

High-criticality unknowns

Lease expiries

Digital ownership uncertainty

Strategic rights not centrally indexed

Major deferred maintenance

F.517First 100 Days

Prioritize:

high-criticality;
high-value;
high-liability;

unknowns.

F.518Year One

Create:

authoritative asset structure;
public layer;
protected layer;
Asset IDs;
condition-confidence standards.

F.519Year One Property Review

Identify:

Operational

Strategic Hold

Leased

Under Review

Potentially Surplus

F.520Do Not Sell During Inventory Panic

No.

F.521Year Two

Improve:

condition coverage;
preventive maintenance;
land strategy;
lease management;
digital ownership;
exit rights.

F.522Year Two Surplus Review

Only after:

cross-department analysis.

F.523Year Three

Focus on:

major renewals;
long-term capital;
strategic acquisitions;
high-risk disposals;
digital lock-in replacements.

F.524Year Four

Publish:

Four-Year Municipal Asset Audit.

F.525Four-Year Asset Audit

Should show:

Assets inventoried

Unknown assets resolved

High-risk unknowns remaining

Condition coverage

Preventive maintenance performance

Deferred maintenance

Major acquisitions

Major transfers

Major disposals

Surplus properties sold or retained

Strategic lands preserved

Accessibility improvements

Digital systems with tested exits

Critical vendor dependencies

Lease risks

Major environmental liabilities

Major next-term renewals

F.526Name the Most Important Asset Newly Inventoried

F.527Name the Largest Condition Unknown Resolved

F.528Name the Largest Remaining Condition Unknown

F.529Name the Highest-Risk Deferred Asset

F.530Name the Largest Maintenance Backlog Reduced

F.531Name the Largest New Maintenance Backlog Created

F.532Name the Most Important Repair-Before-Replace Decision

F.533Name the Most Important Asset Replacement

F.534Name the Most Important Asset the City Chose Not to Build

Where applicable.

F.535Name the Most Important Strategic Property Retained

F.536Name the Largest Property Disposition

F.537Show the Public Reason

F.538Name the Largest Below-Market Public Contribution

If any.

F.539Name the Largest Asset Acquisition

F.540Name the Largest Liability Accepted With an Asset

F.541Name the Most Important Easement or Strategic Right Preserved

Where appropriate without compromising sensitive information.

F.542Name the Major Asset Transfer With the Largest Long-Term Municipal Impact

F.543Name the Digital System With the Strongest Municipal Control

F.544Name the Digital System With the Highest Remaining Lock-In Risk

F.545Name a System Successfully Exited

F.546Name an Asset Where Accessibility Was Improved During Renewal

F.547Name an Asset Where Environmental Risk Changed the Decision

F.548Name a Donated or Low-Cost Asset the City Declined Because Complete Cost Was Too High

If applicable.

F.549Name a Surplus Asset the City Decided to Retain for Strategic reasons

If applicable.

F.550Asset Handoff

The next Council should receive:

Current register

Major risks

Major condition unknowns

Deferred maintenance

Planned renewals

Active property transactions

Lease expiries

Strategic land issues

Digital contract renewals

Environmental liabilities

Major transfer agreements

F.551No Asset Surprise

The next Council should not discover six months later:

Nobody realized the roof needed replacement.

F.552Or

Nobody knew the lease expired.

F.553Or

Nobody knew the City did not own the data.

F.554Or

Nobody knew the transfer included a major maintenance liability.

F.555Asset Knowledge Is Government Knowledge

Yes.

F.556The Municipal Assets and Public Ownership Commitment

Owen Sound should commit to:

Maintain one authoritative institutional understanding of the assets the City owns, leases, operates, controls or materially depends upon.

Connect the Municipal Asset Register to the Infrastructure Index rather than maintaining disconnected asset lists.

Use stable Asset IDs for material assets and logical asset groups.

Distinguish ownership, operation, regulation, funding and custodianship.

Never assume that operating an asset means owning it.

Never assume that owning an asset means the City has exclusive regulatory authority over it.

Record service function, condition, confidence, criticality, maintenance, replacement and next decision for material assets.

Maintain separate public and protected asset-information layers.

Publish enough information for residents to understand ownership, condition, cost and planned work without publishing security-sensitive vulnerabilities.

Do not use security as a blanket excuse for asset secrecy.

Treat municipal assets as institutional public property rather than possessions of elected officials, departments or individual employees.

Manage assets through a full lifecycle from need and acquisition through operation, renewal and disposal.

Require a formal acceptance gate before the City takes ownership of major assets.

Never call an asset free merely because the purchase or transfer price is low.

Include maintenance, insurance, staffing, accessibility, environmental, digital, replacement and disposal liabilities in asset acceptance.

Use qualified inspections where asset condition materially affects the decision.

Treat Unknown condition as Unknown rather than Good.

Publish condition confidence alongside condition where useful.

Distinguish asset condition from asset criticality.

Prioritize high-criticality assets with poor or unknown condition.

Use preventive, predictive, reactive or run-to-failure maintenance strategies according to asset risk rather than ideology.

Track deferred maintenance rather than making it disappear from the work list.

Never call skipped required maintenance a saving.

Apply Repair Before Replace to significant asset-renewal decisions.

Consider refurbishment, repurposing, sharing and retirement before automatic like-for-like replacement.

Distinguish accounting value, market value, replacement value and strategic public value.

Never use book value as a substitute for replacement cost.

Never use market value as the sole measure of an asset's public value.

Maintain a comprehensive municipal land inventory.

Verify title and legal interests where ownership boundaries matter.

Never treat a GIS parcel as a substitute for legal title or survey evidence.

Record easements, rights-of-way, covenants, utility rights and other material encumbrances.

Understand environmental liability before acquiring or disposing of higher-risk property.

Treat heritage and archaeological considerations as real asset-management factors.

Engage Saugeen Ojibway Nation early where land, water, archaeology, rights or shared interests may be affected.

Do not treat municipal title as the complete answer to every rights or jurisdiction question.

Review waterfront and strategic-corridor property carefully before irreversible disposition.

Preserve public access, trail, drainage, utility, emergency and future infrastructure options where evidence supports it.

Do not classify land as municipal surplus merely because one department has no current use for it.

Require cross-department review before declaring strategic property surplus.

Use the categories Operational, Strategic Hold, Leased, Under Review and Potentially Surplus.

Require reasons for Strategic Hold so the City does not warehouse property indefinitely without purpose.

Consider sale, lease, licence, partnership, repurpose and retention before disposition.

Recognize that sale is often the most irreversible option.

Use qualified valuation for material transactions.

Identify below-market transfers or leases as public subsidies where applicable.

Never provide a favoured buyer privileged access to municipal property.

Use independent valuation and process where conflicts are material.

Treat property-sale revenue as one-time money.

Do not fund permanent operating imbalance through repeated asset sales.

Maintain building records that include condition, accessibility, major components, operating cost, maintenance backlog and utilization.

Do not assume an underused building is automatically surplus.

Do not judge public facilities solely by revenue per square foot.

Use the complete accessible journey when evaluating public buildings.

Measure actual energy performance after major retrofits rather than relying only on forecasts.

Manage building components such as roofs, HVAC and electrical systems separately where component condition matters.

Maintain roads, sidewalks, bridges, culverts, signals, streetlights, signs and related transportation assets within an integrated register.

Use One Street, One Plan before major reconstruction.

Coordinate underground and surface renewal so the City does not repeatedly rebuild the same corridor unnecessarily.

Treat road transfers from another government as asset acquisitions requiring full due diligence.

Review pavement, structures, drainage, winter cost, rights-of-way, capital forecasts and deferred maintenance before accepting transferred roads.

Never describe transferred roads as free because transition funding accompanies them.

Maintain dedicated bridge and structural inspection records.

Do not ignore culverts and smaller structures capable of causing major failures.

Maintain water, wastewater and stormwater asset inventories at an appropriate level of technical detail.

Protect sensitive critical-infrastructure details while still reporting high-level asset condition and investment needs publicly.

Identify redundancy, backup power, critical spares and single points of failure internally for essential services.

Do not publish a vulnerability map merely to appear transparent.

Recognize natural features as municipal assets only where the City has a defensible ownership, control or stewardship basis.

Do not claim another government's or private owner's natural feature as a City asset.

Use natural-asset valuation carefully and do not force speculative dollar values where they add little decision value.

Measure tree survival rather than tree planting alone.

Manage parks, playgrounds, fields, washrooms, paths, furniture and public-realm assets according to their actual service roles.

Measure recreation-facility use before major expansion while recognizing that utilization is not the only public-value measure.

Maintain public art and memorial ownership, maintenance and rights information where appropriate.

Manage fleet according to age, condition, utilization, maintenance, reliability, safety and service criticality rather than age alone.

Evaluate fleet electrification through actual duty cycle, climate, charging, lifecycle and operational requirements.

Do not buy vehicles or equipment merely for technological prestige.

Use telematics only with clear operational purpose and appropriate privacy safeguards.

Apply materiality so asset management does not become an exercise in individually cataloguing every low-value object.

Distinguish standby assets from genuinely abandoned assets.

Review dormant assets periodically.

Maintain complete lease records for assets the City leases in and leases out.

Track lease expiry, renewal, maintenance, insurance, improvements and restoration obligations.

Disclose material public subsidy in below-market leases.

Define ownership, maintenance, capital, insurance and exit responsibilities for shared facilities.

Give jointly owned assets clear governance and dissolution rules.

Treat easements and strategic rights as municipal assets worthy of active management.

Do not release an easement simply because no current department appears to use it.

Treat narrow access corridors, drainage rights and utility rights according to their strategic public value rather than acreage alone.

Treat digital infrastructure as municipal assets and dependencies, not merely IT expenses.

Inventory critical domains, websites, cloud tenancies, databases, software, code, APIs, certificates, GIS layers, digital configuration and documentation.

Ensure critical municipal domains and administrative accounts remain institutionally controlled rather than held in personal accounts.

Do not allow employees, contractors, vendors or founders to retain sole control over critical municipal accounts.

For every significant digital system, identify who owns the data, code, configuration and export rights.

Recognize that licences, subscriptions and cloud services are not the same as ownership.

Measure practical control by asking whether the City can continue serving residents after a vendor relationship ends.

Require usable data exports rather than assuming any export constitutes an exit.

Treat documentation as a municipal asset.

Reduce key-person and vendor-only knowledge dependencies.

Connect the Digital Asset Register to privacy, cybersecurity, procurement and records management.

Treat municipal data as both an asset and a potential liability.

Do not equate more data with more public value.

Identify institutional data owners, stewards and sources of truth.

Follow lawful records-retention and disposition rules.

Never delete records to avoid public access or accountability.

Never retain personal information forever merely because storage is inexpensive.

Clarify ownership and licence rights in contractor-created reports, software, designs, datasets and other intellectual property.

Consider future reuse before agreeing to restrictive intellectual-property terms.

Share non-sensitive municipal standards, templates and tools where doing so creates public value.

Do not make all municipal intellectual property public where security, privacy or third-party rights require restrictions.

If map.ca or RealMap is ever considered as municipal infrastructure, resolve public ownership, licensing, governance and control before adoption.

Apply independent legal, procurement, privacy, cybersecurity, accessibility, architecture, conflict and valuation review to founder-associated technology.

Use Public Standard First, Platform Second, Founder Last.

Never allow a private founder to retain personal veto, privileged access or irreversible control over municipal infrastructure.

Never create an undisclosed private windfall through municipal adoption of founder-associated technology.

Keep private platform data and municipal data legally and operationally distinct unless lawful integration has been specifically approved.

Do not allow private commercial use of City data merely because a platform hosts municipal functions.

Treat contracts, warranties, renewal options and termination rights as municipal assets and obligations.

Maintain a major contract register linked to relevant municipal assets.

Track warranty periods and do not allow public value to expire unused through poor records.

Review insurance coverage, deductibles and exclusions for material assets.

Recognize that insurance does not replace resilience or continuity planning.

Map critical service dependencies internally.

Identify where essential assets rely on electricity, communications, suppliers, specialized parts or key personnel.

Protect detailed dependency and vulnerability information while publishing safe high-level resilience information.

Use risk-based redundancy rather than assuming redundancy is always wasteful or always necessary.

Track sole-source and obsolete-parts risk for critical assets.

Use Canadian capacity as one resilience factor without assuming Canadian suppliers are automatically lower risk.

Require asset acquisitions to begin with a service need rather than a funding opportunity, donation or political desire for a visible project.

Compare buying, leasing, sharing, renting, partnering, repairing and doing nothing before significant acquisitions.

Use Complete Cost in buy-versus-lease decisions.

Perform complete due diligence before accepting federal, provincial, County or private asset transfers.

Treat any future harbour acquisition as a major asset transfer requiring exceptional financial, legal, environmental, operational and relationship due diligence.

Do not evaluate a harbour acquisition by transfer price alone.

Identify land, water interests, structures, dredging, environmental liability, leases, utilities, security, capital backlog and operating cost before acquisition.

Include Saugeen Ojibway Nation early in any harbour process where rights or shared interests may be engaged.

Document major asset acceptance formally.

Do not permit departments to accept significant property informally outside proper authority.

Dispose of assets using lawful and documented processes.

Use reuse, trade-in, recycling, sale, donation where lawful, destruction or decommissioning according to the asset and public purpose.

Securely erase data-bearing equipment before it leaves municipal control.

Use secure inspection, erasure and transfer practices for any public device-reuse initiative.

Reconcile financial and operational asset registers periodically.

Recognize that a fully depreciated asset can still be operationally critical.

Recognize that an accounting asset can remain on the books after its practical usefulness declines.

Use asset-class-specific utilization metrics rather than one universal measure.

Do not label low utilization waste without considering standby, emergency or specialized purpose.

Do not label high utilization efficient without considering wear, downtime and maintenance.

Connect public-facing assets to the Accessibility Barrier Register.

Use capital renewal as an opportunity to remove barriers rather than reconstruct them.

Review new physical and digital assets for accessibility before acceptance.

Treat environmental risk as part of asset risk and financial risk.

Consider contamination, flooding, weather exposure, drainage and lifecycle materials where relevant.

Do not use climate or environmental terminology as a generic explanation for every asset problem.

Maintain asset history, drawings, maintenance records, warranties, manuals and as-built information so institutional knowledge survives staff turnover.

Do not allow critical asset knowledge to exist only in one person's inbox.

Publish appropriate municipal ownership maps while making clear that a public GIS map is not a legal survey or title opinion.

Date public asset maps and disclose material ownership uncertainty.

Maintain a change log for major acquisitions, sales, transfers, demolitions and leases.

Publish a Public Asset Dashboard showing inventory coverage, condition coverage, high-risk unknowns, maintenance, acquisitions, disposals, leases, digital exit readiness and major risks.

Use Grey for significant ownership or condition information that is not yet known.

Do not assign one simplistic asset-health score to the entire municipal portfolio.

Never reduce maintenance backlog merely by deleting tasks from the system.

Never declare an asset healthy because nobody complained.

Never call a transfer, gift or grant-funded asset free.

Never use a single valuation type for every asset decision.

Never declare municipal property surplus without testing whole-City future needs.

Never hide public subsidy in below-market property transactions.

Never permit critical digital systems to remain dependent on personal accounts or sole-vendor administrator access.

Never confuse an export button with a tested digital exit.

Never publish sensitive infrastructure vulnerabilities for transparency theatre.

Never use security as an excuse to hide ordinary ownership, condition and spending information.

Never treat a ramp as proof of complete building accessibility.

Never treat planting as proof of a successful tree asset.

Never dispose of devices before secure data erasure.

Never release strategic access or easement rights without proper review.

Never allow automatic digital contract renewals to create accidental municipal lock-in.

Never allow founder-associated private technology to become public infrastructure without the strongest conflict and ownership safeguards.

Never hide major asset risks merely because they are expensive or politically inconvenient.

Use the first 30 days to locate and reconcile existing asset records.

Use the first 60 days to publish an Asset Register Gap Report.

Use the first 100 days to prioritize high-criticality and high-liability unknowns.

Use Year One to establish the authoritative register, public layer, protected layer and condition-confidence standards.

Use Year Two to strengthen condition assessments, preventive maintenance, digital ownership and land strategy.

Use Year Three to make major renewal, acquisition, disposition and lock-in decisions.

Use Year Four to publish a Four-Year Municipal Asset Audit and prepare a professional asset handoff.

Name the largest remaining risks rather than handing them silently to the next Council.

Apply the final stewardship test to every asset decision: Do we know what we own, do we know its condition, do we understand the obligation, and are we leaving the next generation a deliberate asset rather than an accidental liability?

The asset framework can ultimately be reduced to nine questions:

What do we own?

What rights do we hold?

What condition is it in?

How sure are we?

What happens if it fails?

What does it cost to maintain and replace?

Should we keep it?

If we acquire something new, what liability comes with it?

If we dispose of something, what public option disappears with it?

A City that does not know its assets will eventually:

replace things too early;
maintain things too late;
buy things it already has;
sell rights it later needs;
accept liabilities disguised as gifts;
become trapped in digital systems it does not control.

A City that knows its assets can make different decisions.

It can:

repair before replacing;
maintain before failure;
lease rather than sell where appropriate;
sell genuinely surplus assets;
preserve strategic corridors;
understand transfers before accepting them;
protect critical data;
escape vendor lock-in;
show residents exactly what public ownership means.

Know what we own. Know its condition. Know its purpose. Know its liability. Maintain deliberately. Transfer carefully. Sell only with reason. Keep public control where public control matters.

← Appendix E: Financial Framework and Reference Tables Appendix G: Scorecard Definitions and Measurement Standards →

Appendix FMunicipal Assets and Public Ownership

Know what the City owns before deciding what it needs to buy, sell, transfer or build

F.1Purpose

F.2The Municipal Asset Register

F.3One Register, Multiple Systems

F.4Asset Register Versus Infrastructure Index

F.5Asset Register Is Broader

F.6Asset Categories

F.7Asset ID

F.8Stable ID

F.9Ownership Field

F.10Ownership Is Not Operation

F.11Operation Is Not Ownership

F.12Funding Is Not Ownership

F.13Regulation Is Not Ownership

F.14Asset Record

Asset ID

Asset name

Category

Owner

Operator

Custodian

Location

Service function

Condition

Condition confidence

Criticality

Last inspection

Next inspection

Maintenance status

Estimated remaining life

Replacement / renewal estimate

Insurance status

Legal restrictions

Easements / encumbrances

Funding restrictions

Accessibility status where relevant

Cybersecurity / digital status where relevant

Next major decision

F.15Public Versus Protected Fields

F.16Public Layer

F.17Protected Layer

F.18Open Government Does Not Mean Open Vulnerability

F.19Security Is Not Excuse for Secrecy

F.20Public Ownership Principle

F.21Mayor Does Not Own Them

F.22Council Does Not Own Them Personally

F.23Department Does Not Own Them Personally

F.24Institutional Ownership

F.25Custodianship

F.26Custodian Is Not Free to Dispose

F.27Lifecycle

Need

Business Case

Acquisition

Acceptance

Inventory

Operation

Inspection

Maintenance

Renewal

Repurpose

Transfer

Disposal

Archive / Record Retention

F.28Acquisition Is Not End

F.29Asset Acceptance Gate

Do we need it?

Who owns it?

What is its condition?

What liabilities come with it?

What does maintenance cost?

What will replacement cost?

Is insurance available?

Is contamination present?

Are accessibility upgrades required?

Are cyber or software dependencies involved?

Are warranties transferable?

Are there easements or restrictions?

What is the exit path?