Owen Sound: A Four-Year City Business Plan

Home › The Public Scorecard › Chapter 60

The Public Scorecard

Chapter 60Missed: The Public Missed Commitments Scorecard

9,754 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

A credible government should be able to publish a page titled:

What We Missed.

Not:

Challenges Encountered.

Not:

Priorities Still Advancing.

Not:

Transformational Work Continuing Into the Future.

If something was promised for the four-year term and it was not delivered:

Say so.

That does not mean every missed commitment represents:

A commitment can be missed because:

Those are very different situations.

They should not be hidden under one number.

The central principle is:

A government that can publicly name what it missed is more trustworthy than one that changes the definition of success.

Another principle is equally important:

A missed promise and a responsible decision can exist at the same time.

If government promised:

We will build X.

Then discovers that X would:

the responsible decision may be:

Do not build X.

The original commitment was still:

Both facts belong in the record.

The Missed Scorecard exists so government can say:

We said this.

It did not happen.

Here is why.

Here is what it cost.

Here is what we learned.

Here is what still needs to happen.

Here is what the next Council inherits.

That is not political weakness.

That is public stewardship.

60.1Purpose

The Missed Scorecard should answer:

What did the City say it would do?

What was due?

What was not delivered?

What part was completed?

What remains?

Why was it missed?

Was the cause inside City control?

Was another government responsible for the final action?

Did Council deliberately reject it?

Did evidence change?

Did the cost become unreasonable?

Was the commitment poorly designed from the beginning?

When did the City first know the commitment was at risk?

When did residents learn that?

How much money was spent?

What contractual or financial obligations remain?

Did anything useful result despite the miss?

Should the next Council continue it?

Should it be stopped permanently?

What will the City do differently next time?

Those are the questions.

60.2Missed Is a Factual Status

The word:

missed

should not automatically mean:

It means the original commitment or target was:

60.3Failure Is a Judgment

Failure should be used more carefully.

A failure may involve:

60.4Responsible Stop

A commitment may be:

Missed, Responsible Stop

if the original promise was not delivered but stopping became the better decision.

60.5External Block

A commitment may be:

Missed, External Block

where another required authority or party prevented completion.

60.6Democratic Rejection

A commitment may be:

Missed, Council Rejected

where Council lawfully decided:

60.7Evidence Changed

A commitment may be:

Missed, Evidence Changed

where the original idea no longer passed:

tests.

60.8City Execution Failure

A commitment may be:

Missed, City Execution

where the City had the authority and reasonable ability to deliver but did not.

60.9Shared Failure

A commitment may be:

Missed, Shared Responsibility

where City and partner failures both contributed.

60.10Unknown Cause

Sometimes:

Missed, Cause Under Review

is the honest status.

Do not invent certainty.

60.11Missed Commitment Register

The City should maintain a specific view of the Commitment Register showing:

commitments.

60.12No Separate Hidden List

The Missed Scorecard should use the same underlying public commitment dataset as Section 59.

60.13Original Promise

Preserve.

60.14Original Date

Preserve.

60.15Original Scope

Preserve.

60.16Original Cost Assumption

Preserve where one existed.

60.17Responsible Authority

Preserve.

60.18Miss Date

Record when the commitment actually became:

60.19Do Not Wait Until Year Four

A commitment becomes missed when its deadline passes without delivery.

Not when:

60.20Completed Late

If commitment is eventually finished:

Its final status may be:

Completed Late

while the original deadline miss remains visible.

60.21Late Does Not Become On Time

Never rewrite the original date.

60.22Revised Target

A legitimate revised date may be adopted.

60.23Original Miss Still Exists

If original deadline already passed:

The historical miss remains.

60.24Revision Before Deadline

A deadline may sometimes be revised before it is missed because:

changed.

60.25Revision Requires Governance

A revised deadline should identify:

60.26No Last-Minute Date Laundering

Do not move a deadline:

solely to avoid a Red status.

60.27Deadline Change Test

Ask:

Would we have approved this revised date if there were no public Scorecard?

60.28At Risk

Before a commitment is missed:

Use:

At Risk

where evidence shows significant delivery concern.

60.29At Risk Is Early Warning

It should encourage:

60.30At Risk Is Not Shame

Good project management identifies risk early.

60.31No "On Track" Without Evidence

A commitment with:

should not remain:

On Track

because its deadline is still months away.

60.32At-Risk Indicators

Possible:

60.33Early Warning Date

Track when risk was first formally identified.

60.34Public Disclosure Date

Track when material risk became public.

60.35Warning Gap

A useful accountability question:

How long did City Hall know before residents were told?

60.36Confidentiality

Some risk may initially require:

handling.

60.37Confidential Does Not Mean Forever

When lawful and practical:

Publish enough to explain the status.

60.38No Surprise Failure

Residents should not discover on the final day of the term that a major promise had been stalled for:

60.39Major Commitment Escalation

At-risk major commitments should receive:

60.40Council Notification

Where Council direction or budget decision is required:

Bring it forward.

60.41Mayor Notification

The Mayor should know major strategic risks.

60.42Mayor Is Not Project Manager

Administration manages:

60.43Escalation Is Not Micromanagement

Council may need to decide:

60.44Recovery Plan

An at-risk commitment may receive:

60.45Recovery Plan Fields

Problem

Cause

Corrective action

Cost

Revised schedule

Decision required

Risk if no action

60.46Recovery Has Limits

Do not throw:

at a commitment simply because it was promised.

60.47Stop Test

At each major recovery decision:

Ask:

Is completing the original commitment still the best use of public resources?

60.48Sunk Cost

Money already spent is:

60.49Sunk Cost Is Not Reason to Continue

A bad project does not become good because:

60.50Sunk Cost Still Matters

Report it.

60.51Financial Exposure

Every material missed commitment should show:

60.52Financial Exposure Categories

Possible:

Design

Consulting

Land

Procurement

Construction

Software

Legal

Staff

Grant Repayment

Termination

Operating

60.53Staff Time

Do not attempt to assign an invented dollar value to every staff conversation.

60.54Material Staff Cost

For major failed projects:

Staff time may be significant enough to estimate.

Label methodology.

60.55Sunk Cost Table

Possible:

CommitmentSpent to DateRecoverableRemaining ObligationStatus

60.56Grant Repayment

A failed or stopped project may trigger:

Show.

60.57No Grant Panic

Do not continue an irresponsible project solely because:

we might lose the grant.

Compare:

60.58Cancellation Cost

Sometimes paying:

is cheaper than continuing.

60.59Complete Cost Again

Use full lifecycle analysis.

60.60Operating Tail

A project may be affordable to build but unaffordable to:

60.61Maintenance Tail

Same.

60.62Replacement Tail

Same.

60.63Responsible Stop Example

A project with:

may still deserve cancellation if proceeding requires:

60.64Do Not Hide Sunk Cost to Make Stop Look Better

Publish.

60.65Do Not Continue to Hide Sunk Cost Either

Both choices require honesty.

60.66Resident Impact

A missed commitment should describe practical resident impact where known.

60.67Possible Resident Impacts

60.68No Invented Private Loss

Do not claim:

businesses lost $4 million

unless reliable evidence exists.

60.69Qualitative Impact

Sometimes:

Residents continue to use the temporary route

is enough.

60.70Safety Impact

If miss affects safety:

Give it higher priority.

60.71Accessibility Impact

Likewise.

60.72Financial Impact

Likewise.

60.73Rights Impact

Likewise.

60.74Temporary Mitigation

If full commitment was missed:

Show what temporary action exists.

60.75Mitigation Is Not Completion

Keep distinction.

60.76Root Cause Review

Material misses should receive:

60.77Cause Is Not Excuse

The purpose is improvement.

60.78Primary Cause

Identify where reasonably possible.

60.79Contributing Causes

Also record.

60.80Cause Categories

Possible:

Commitment Design

Jurisdiction

Legal

Scope

Estimate

Budget

Funding

Procurement

Staff Capacity

Contractor

Technology

Data

Land

Utility

Partner

Ontario

Canada

County

Market

Weather

Emergency

Demand

Evidence

Political Decision

60.81Do Not Overuse "Market Conditions"

Explain what changed.

60.82Do Not Overuse "Unforeseen Circumstances"

Name them where possible.

60.83Unknown Conditions

Sometimes real.

Example:

60.84Contingency

Ask whether such unknowns should reasonably have been anticipated.

60.85Planning Error

Say when:

60.86Estimating Error

Say when:

60.87Scope Error

Say when:

60.88Authority Error

Say when campaign or Council assumed:

60.89Capacity Error

Say when administration lacked:

60.90Procurement Error

Say when procurement approach:

60.91Vendor Error

Say when vendor failed.

60.92Partner Error

Say when partner failed.

60.93Council Choice

Say when Council changed direction.

60.94Mayor Choice

Say when mayoral leadership changed recommendation.

60.95Public Evidence

Say when public input or evidence changed:

60.96New Law

Say when legislation or regulation changed.

60.97Emergency Reprioritization

May be legitimate.

60.98Emergency Cannot Explain Everything Forever

After emergency:

Reassess.

60.99Root Cause Versus Trigger

A contractor bankruptcy may trigger failure.

Poor contract resilience may still be:

60.100Five Whys

A simple root-cause technique may help internally.

Do not make public reporting gimmicky.

60.101System Cause

Look beyond:

60.102Human Error

Ask why system allowed:

60.103Accountability Does Not Mean Scapegoating

A good Missed Scorecard should improve:

60.104Individual Misconduct

If serious misconduct occurred:

Handle through proper:

process.

60.105Public Scorecard

Do not turn into:

60.106Leadership Accountability

Elected and administrative leaders should still accept responsibility for:

60.107Authority Miss

Some campaign commitments may prove outside municipal jurisdiction.

60.108Not an Excuse

A candidate should have checked.

60.109Jurisdiction Correction

Publish:

Original assumption

Actual authority

What City could lawfully do

What it did

60.110Example

If Ontario controls the required statutory change:

City can:

It cannot claim:

60.111Federal Authority

Same.

60.112County Authority

Same.

60.113Shared Jurisdiction

Complexity should be mapped early.

60.114Authority Register

Cross-reference.

60.115Repeat Authority Errors

If several promises fail because of jurisdiction misunderstanding:

That indicates:

60.116Future Correction

Require jurisdiction review earlier in future platforms or business plans.

60.117Council Rejection

A Mayor may bring forward a proposal and lose the vote.

60.118Democracy

That is not automatically:

60.119Original Promise Matters

If promise was:

I will bring this to Council

then bringing it forward may be:

60.120If Promise Was:

The City will implement this

and Council rejects it:

The outcome commitment was:

60.121Record Both

Mayor action completed

Municipal outcome not approved

60.122No Council Blame Campaign

Official City report should state:

factually.

60.123Council Decision Record

Link to:

where appropriate.

60.124Public Consultation

A consultation may lead Council to:

60.125Listening Can Change Plan

That can be good government.

60.126Do Not Call It Completed Anyway

The original outcome still changed.

60.127"Superseded After Consultation"

May be appropriate.

60.128Rights Limit

Majority opposition alone cannot justify violating:

60.129Evidence and Law

Remain governing constraints.

60.130Responsible Change

The City should not become captive to:

we promised it, so we must do it regardless of evidence.

60.131Promise Is Accountability

Not:

60.132Other Government Block

Some commitments require another government's action.

60.133Evidence of Ask

Show that City actually:

60.134"Waiting on Province"

Is not credible if City:

60.135"Waiting on Canada"

Same.

60.136"Waiting on County"

Same.

60.137Ask Status

Cross-reference Section 57.

60.138External Block Evidence

Possible:

60.139No Response

Can be a real block.

Show:

60.140Escalation

Use proportionate escalation.

60.141Political Attack

Not substitute for:

60.142Intergovernmental Miss

Final report should distinguish:

60.143Harbour Example

If City seeks federal action on harbour:

Record:

Do not call federal inaction:

60.144Crossing

Same.

60.145Funding Miss

A project may depend on:

60.146Funding Assumption

Original business case should have identified:

funding.

60.147Speculative Funding

Should never be presented as:

60.148Grant Not Received

If project depended on it:

Reassess.

60.149City Funding Alternative

Do not automatically fill grant gap with:

Return to Council.

60.150Public Choice

Possible:

Continue with City funding

Reduce scope

Delay

Seek alternative funding

Stop

60.151Grant Application Quality

Review whether application failure resulted from:

60.152No Blame Without Evidence

Do not say:

Ottawa refused Owen Sound

when City simply:

60.153Matching Requirement

A grant may require City contribution.

Show.

60.154Operating Tail

Again.

60.155Lost Grant

If deadline missed through City error:

Say so.

60.156Grant Repayment

If required because project failed:

Say so.

60.157Procurement Miss

Procurement can delay or derail commitments.

60.158No Bid

Could indicate:

Review.

60.159One Bid

Requires careful value assessment.

60.160Bid Above Budget

Do not force award merely to protect promise.

60.161Retender

May be right.

60.162Scope Redesign

May be right.

60.163Cancel

May be right.

60.164Procurement Integrity Before Promise Optics

Never weaken procurement fairness simply to:

60.165Sole Source

Do not misuse because:

60.166Artificial Contract Splitting

Never.

60.167Procurement Delay Cause

If internal procurement began too late:

Say so.

60.168Procurement Readiness

Future lesson may be:

60.169Contractor Miss

A contractor can fail:

60.170Contract Remedies

Use appropriate:

process.

60.171Public Reporting

Report project impact without prejudicing:

60.172Contractor Failure Is Not Automatically City Blamelessness

Ask:

60.173Contractor Bankruptcy

Could be largely external.

60.174Contingency Planning

Still review.

60.175Deficiency

Persistent defects may prevent true completion.

60.176Warranty Failure

Track.

60.177Staff Capacity Miss

The City may promise more work than staff can realistically deliver.

60.178Workload Is Real

Do not blame employees for:

60.179Capacity Test

Before major commitments:

Ask:

Who does the work?

What stops?

Is expertise available?

Is temporary support needed?

60.180No Infinite Staff Capacity

Every new priority consumes:

60.181Council Priority Overload

If Council approves 100 urgent priorities:

Everything cannot be:

60.182Priority Ranking

Needed.

60.183Deferred Work

Show what was displaced.

60.184Hidden Opportunity Cost

Do not pretend new projects have no effect on existing workload.

60.185New Position

May sometimes be justified.

60.186Contractor

May sometimes be better.

60.187Stop Work

May sometimes be better.

60.188Capacity Failure

If management knew work was impossible but continued promising:

That is governance failure.

60.189Burnout Is Not Delivery Strategy

Do not complete political promises by:

60.190Overtime

Track when material.

60.191Staff Turnover

Could affect delivery.

60.192Succession

Could affect delivery.

60.193Key-Person Dependency

Identify.

60.194Technology Miss

Digital projects frequently fail through:

60.195Software Purchased

Does not mean:

60.196Implementation Failure

If system cannot perform promised function:

Report.

60.197Adoption Failure

If staff or residents do not use it:

Investigate why.

60.198Training

May be inadequate.

60.199User Experience

May be poor.

60.200Integration

May fail.

60.201Data Migration

May fail.

60.202Vendor Support

May fail.

60.203Privacy Gate

May appropriately stop launch.

60.204Accessibility Gate

Same.

60.205Cybersecurity Gate

Same.

60.206Responsible Delay

Better to delay unsafe system than:

60.207Technology Sunk Cost

Do not keep bad software merely because:

60.208Vendor Exit

Use.

60.209map.ca or RealMap

Any conflict-sensitive system should be stopped or delayed if:

standards are not satisfied.

60.210Personal Political Cost Is Irrelevant

Do not launch a Mayor-associated project simply to avoid embarrassment.

60.211Data Miss

Sometimes a commitment cannot be measured because baseline:

60.212Measurement Failure

That itself may be a failure.

60.213Baseline Required

If promise said:

reduce response time

and City never measured initial response time:

Outcome cannot be verified.

60.214Mark:

Outcome Unverifiable

where necessary.

60.215Unverifiable Is Not Completed

Do not assume success.

60.216Data Quality

Poor data can make target reporting unreliable.

60.217Improve Measurement

But preserve uncertainty.

60.218No Retroactive Cherry-Picking

Do not choose a favourable historical comparison after the fact.

60.219Outcome Miss

A commitment can be operationally completed but miss its outcome.

60.220Example

City launches a new service designed to:

The service launches.

Repeated contacts do not decline.

60.221Status

Could be:

Implementation Completed, Outcome Missed.

60.222Important Distinction

The City did what it said operationally.

The theory did not work.

60.223Learn From It

Outcome failure can be more useful than:

60.224Pilot Design

Pilots should make outcome failure safe enough to learn from.

60.225Pilot Miss

A pilot that shows:

can still be successfully completed as a pilot.

60.226Expansion Promise

If City promised permanent expansion regardless of pilot evidence:

That was poor commitment design.

60.227Decision Gate

Better.

60.228Housing Outcome Miss

Approvals may rise while:

Do not claim supply outcome.

60.229Business Outcome Miss

Program registrations may rise while:

60.230Downtown Outcome Miss

Events may grow while:

do not improve.

60.231Safety Outcome Miss

New program may launch while:

60.232Recreation Outcome Miss

Facility investment may occur while:

60.233Youth Outcome Miss

Youth meetings may increase while:

do not.

60.234Accessibility Outcome Miss

Policy may improve while:

60.235Privacy Outcome Miss

Policy may be adopted while:

60.236Environment Outcome Miss

Trees may be planted while:

60.237Partnership Outcome Miss

MOU may be signed while:

60.238Satisfaction Outcome Miss

Survey process may improve while:

60.239Financial Outcome Miss

Budget may be balanced while:

60.240Tax Outcome Miss

Rate may be lower while:

rise.

60.241Service Outcome Miss

Tickets may close faster while:

60.242Infrastructure Outcome Miss

Capital spending may rise while:

remain weak.

60.243Measure What Was Intended

Do not substitute an easier metric when the real outcome disappoints.

60.244Scope Miss

A project may deliver only part of original scope.

60.245Partial Completion

Report:

60.246No Percentage Theatre

Do not say:

92% complete

if the missing 8% is the feature that makes the project useful.

60.247Critical Missing Component

Highlight.

60.248Optional Missing Component

Different.

60.249Scope Priority

Not all scope is equal.

60.250Minimum Viable Completion

If originally defined:

May be legitimate.

60.251Retrofitted Definition

Do not invent minimum scope after problems arise merely to claim:

60.252Quality Miss

A project can finish physically but fail:

60.253Defects

Track.

60.254Rework

Track where material.

60.255Rework Cost

Show.

60.256Warranty Correction

Show.

60.257Safety Deficiency

High priority.

60.258Accessibility Deficiency

High priority.

60.259Quality Acceptance

Use professionals.

60.260Public Appearance

A project looking finished does not mean:

A project may fail legal review.

Should reduce this.

60.263Rights Concern

If legal review finds significant:

risk:

Stop or redesign.

60.264Responsible Stop

Better than:

Report material legal costs.

60.266Privilege

Do not disclose privileged advice improperly.

60.267Public Reason

Provide enough to explain:

without waiving privilege unnecessarily.

60.268Conflict Miss

A project may be delayed or stopped because:

60.269That Is Not an Excuse to Bypass Conflict Rules

Never.

60.270Founder-Associated Project

Requires independent process.

60.271Conflict Discovered Late

Ask why it was not identified earlier.

60.272Procurement Firewall

Must remain.

60.273Public Trust

Better to miss a project than:

60.274Environmental Miss

Unexpected contamination may block:

60.275Due Diligence

Review whether reasonable investigation occurred.

60.276Unknown Conditions Can Be Genuine

Do not pretend every underground issue was predictable.

60.277Contamination Liability

Show.

60.278Flood Risk

If evidence shows site inappropriate:

Change plan.

60.279Tree Failure

If tree cohort performs poorly:

Report:

60.280Building Energy Miss

If retrofit underperforms forecast:

Report.

60.281No Forecast Rewrite

Do not lower original expectation after result arrives without showing both.

60.282Partnership Miss

A partner may:

60.283Partner Dependency Risk

Should have been identified.

60.284Partner Failure Is Not Automatic City Failure

But resident impact remains.

60.285Backup Plan

Review.

60.286Partnership Exit

Use Section 57.

60.287SON Relationship

A relationship commitment may remain unresolved without being:

60.288Respectful Unresolved Status

Use accurate language.

60.289Do Not Grade SON Relationship Politically

Do not classify disagreement as:

60.290Mutual Commitment

Only score agreed commitments appropriately.

60.291Confidentiality

Protect appropriate relationship discussions.

60.292County Miss

City-County issues may remain unresolved.

60.293Shared Responsibility

Show each government's role.

60.294Cost Shift

Do not hide unresolved issues by moving cost.

60.295Ontario Miss

A provincial ask may be:

60.296Federal Miss

Same.

60.297City Advocacy Evaluation

Was the ask:

60.298No Political Blame Metric

The Scorecard should not rank governments by:

60.299Community Partner Miss

A nonprofit may not deliver.

60.300Capacity Review

Ask whether City should have assessed:

more carefully.

60.301Grant Recovery

If partner grant unused or misused:

Apply agreement.

60.302No Public Shaming Without Due Process

Report institutional facts.

60.303Volunteer Project Miss

A volunteer project may stall.

60.304Volunteer Capacity

Do not treat volunteers as:

unless agreement says so.

60.305Critical Service

Do not depend solely on volunteer delivery without contingency.

60.306Demand Miss

A program may attract little use.

60.307Low Demand

Can justify:

60.308Do Not Manufacture Users

No.

60.309Marketing

May be part of problem.

60.310But Marketing Is Not Always Solution

Maybe residents simply:

60.311Low Participation

Ask:

Awareness?

Price?

Access?

Schedule?

Poor design?

No demand?

60.312Do Not Protect Program From Evidence

If no demand:

Stop.

60.313Equity

Low participation by one group may reflect:

Investigate appropriately.

60.314No Vulnerability Profiling

Use privacy-safe methods.

60.315Cost Miss

Original project may become much more expensive.

60.316Cost Threshold

Before launch:

Major projects should define when cost increase triggers:

60.317Automatic Continuation

No.

60.318Escalation Trigger

Possible:

threshold.

Use project scale.

60.319No Universal 10% Rule

Different projects require different tolerance.

60.320Contingency

Spending contingency is not automatically:

60.321Contingency Exhausted

Worth reporting.

60.322Change Order

May be legitimate.

60.323Change Order Pattern

Repeated changes can indicate:

60.324Change Order Transparency

Show material changes.

60.325Estimate Maturity

An early conceptual estimate should not be compared directly with final cost without noting:

60.326Bad Promise

Do not promise exact cost before sufficient design certainty.

60.327Cost Range

May be better early.

60.328Political Pressure

Do not force unrealistically low early estimates.

60.329Affordability Decision

If project no longer passes complete-cost test:

Stop or redesign.

60.330"Too Much Already Invested"

Not enough.

60.331Time Miss

Some commitments simply take longer.

60.332Delay Cost

A delay may create:

60.333Delay Benefit

A delay may also allow:

60.334Delay Evaluation

Show both.

60.335Schedule Compression

Trying to recover lost time can increase:

60.336Election Deadline

Never compress unsafe work merely to finish before voting day.

60.337Seasonal Work

Weather windows matter.

60.338Winter Construction

May be inappropriate for some work.

60.339Contractor Availability

Can matter.

60.340Utility Coordination

Can matter.

60.341Permits

Can matter.

60.342Archaeology

Can matter.

60.343SON Engagement

Can matter.

Do not bypass engagement to recover schedule.

60.344Public Consultation

Same.

60.345Rights and Due Process Before Schedule

Always.

60.346Communication Miss

Sometimes the project is delayed but the larger failure is:

60.347Communication Commitment

Track separately where material.

60.348Advance Notice

Could have prevented frustration.

60.349Wrong Information

Can worsen delay.

60.350Correction

Use Section 55.

60.351No Silence

If timeline slips materially:

Update.

60.352Promise of Update

If City promises monthly update:

Measure it.

60.353Update Without Substance

Do not publish:

work continues

for six months.

Say what is:

60.354Resident Experience

Section 58 can reveal whether:

made miss worse.

60.355Service Recovery

A miss should have recovery response.

60.356Recovery Options

Complete

Redesign

Replace

Transfer

Pause

Stop

Handoff

60.357No Automatic "Complete"

Sometimes the right recovery is:

60.358Decision Owner

Identify.

60.359Decision Deadline

Avoid indefinite limbo.

60.360Limbo Is a Status Problem

A commitment should not remain:

Under Review

for years.

60.361Review Expiry

Major reviews should have:

60.362"Deferred"

Needs:

60.363"Blocked"

Needs:

60.364"Waiting"

Needs:

60.365"Ongoing"

Needs:

60.366"In Progress"

Needs:

60.367No Zombie Commitments

If no active work and no planned decision:

Use:

Not Proceeding

or another accurate status.

60.368Handoff

A missed commitment continuing beyond the term requires:

60.369Handoff Fields

Original commitment

Current status

Work completed

Work remaining

Money spent

Remaining cost

Contracts

Partner commitments

Key risks

Next required decision

60.370Handoff Is Not Recommendation to Continue Automatically

The next Council decides.

60.371Neutral Handoff

Provide facts.

60.372Outgoing Political Recommendation

Can be stated separately.

60.373Contractual Obligation

Clearly distinguish:

60.374Grant Obligation

Same.

60.375Regulatory Obligation

Same.

60.376Financial Exposure

Same.

60.377Handoff Priority

Some incomplete items are urgent.

60.378Safety

Flag.

Flag.

60.380Contract Deadline

Flag.

60.381Grant Deadline

Flag.

60.382Routine Policy

Lower urgency.

60.383No Political Booby Trap

Do not intentionally leave:

commitments for successor.

60.384Records Complete

Provide.

60.385Passwords and Systems

Institutional.

60.386Vendor Contacts

Institutional.

60.387Partner Contacts

Institutional.

60.388Council History

Included.

60.389Decision History

Included.

60.390Why It Missed

Included.

60.391Lesson Register

Every significant miss should produce a short lesson.

60.392Lessons Categories

Possible:

Plan Better

Scope Better

Estimate Better

Engage Earlier

Check Authority

Fund Earlier

Procure Earlier

Staff Properly

Pilot First

Stop Earlier

Measure Better

Communicate Better

60.393Lesson Owner

Someone should apply it.

60.394Lesson Without Process Change

Weak.

60.395Example

Lesson:

Check jurisdiction earlier.

Process change:

Every future major initiative receives an Authority Map before budget submission.

60.396Another Example

Lesson:

Bids arrived over budget.

Process change:

Major capital procurement requires estimate update before tender.

60.397Another

Lesson:

Residents were surprised by construction.

Process change:

Neighbour notification standard added before mobilization.

60.398Another

Lesson:

Program had no demand.

Process change:

Future optional service pilots require demand test before permanent staffing.

60.399Another

Lesson:

Vendor locked the City in.

Process change:

Export and exit tests added before technology renewal.

60.400Institutional Learning

This is why misses must remain visible.

60.401No Repeat Failure Without Explanation

If same failure happens again:

Show why lesson was not applied.

60.402Repeat Cause Metric

Track recurring causes.

60.403Example

If four projects fail because of:

that is organizational pattern.

60.404Root Cause Dashboard

Could show:

60.405Do Not Rank Departments by Miss Count Alone

Some departments manage:

projects.

60.406Risk-Adjusted Context

Use narrative and scale.

60.407Major Miss

Define in advance.

Possible criteria:

60.408Major Misses Separate

Publish prominently.

60.409Minor Miss

Still track.

60.410No Burial

Do not bury a:

among:

60.411Miss Count

Can be reported.

60.412But Count Alone Misleads

Use:

60.413Miss Rate

If used:

Miss Rate = Finite Commitments Due but Not Delivered by the Agreed Deadline ÷ Finite Commitments Due

60.414Do Not Use Miss Rate Alone

A City could improve it by:

60.415Ambition

Some ambitious commitments will fail.

60.416Recklessness

Ambition does not justify:

60.417Better Standard

Ask:

Were commitments ambitious but grounded, and were misses managed honestly?

60.418Promise Quality

Cross-reference Section 59.

60.419Overpromising

Repeated uncosted promises are:

60.420Underpromising

A government should not game Scorecard by promising only:

60.421Public Value

Commitments should be:

60.422At-Risk Table

CommitmentOriginal Due DateRiskCauseRecovery ActionNext Decision

60.423Missed Commitment Table

CommitmentOriginal PromiseOriginal DueFinal StatusPrimary CauseCost to DateHandoff

60.424Responsible Stop Table

CommitmentReason StoppedCost to DateCost Avoided / Remaining ExposureDecision Evidence

Avoid presenting estimated avoided cost as:

60.425External Block Table

CommitmentExternal Authority / PartnerCity Action CompletedBlockNext Step

60.426Council Rejection Table

CommitmentProposal PresentedCouncil DecisionDateResult

60.427Financial Exposure Table

CommitmentSpentContractedRecoverableRemaining LiabilityFunding Source

60.428Root Cause Table

CauseMajor MissesExamplesProcess Change

60.429Handoff Table

CommitmentRemaining WorkRemaining CostUrgencyNext Decision

60.430Lessons Table

MissLessonProcess ChangeOwnerImplemented?

60.431Outcome Miss Table

Completed InitiativeIntended OutcomeActual OutcomeStatusNext Decision

60.432Traffic Lights

Green

Not generally used for missed commitments.

Could indicate:

Amber

Commitment at risk, delayed or partially delivered with active recovery.

Red

Commitment missed, materially failed or outcome significantly below commitment.

Grey

Cause, evidence or outcome not yet sufficiently known.

60.433Status Words Matter More

Do not use colour to soften:

60.434Red Is Not Moral Condemnation

It means:

60.435Grey Is Temporary

A major miss should not remain Grey indefinitely.

60.436Cause Review Deadline

Set.

60.437Responsible Stop Label

May deserve a distinct symbol rather than pretending it is:

60.438Honest Complexity

A commitment can be:

Missed, but stopping prevented larger loss.

Say exactly that.

60.439Anti-Gaming Rule One

Do not delete missed commitments from the register.

60.440Anti-Gaming Rule Two

Do not change original promise wording after the miss.

60.441Anti-Gaming Rule Three

Do not move the original deadline after it has passed and call the commitment on time.

60.442Anti-Gaming Rule Four

Do not change a four-year commitment into:

long-term vision

after it becomes clear it will not be completed.

60.443Anti-Gaming Rule Five

Do not relabel:

Missed

as:

Ongoing

without active work and a real future decision.

60.444Anti-Gaming Rule Six

Do not use:

Under Review

indefinitely.

60.445Anti-Gaming Rule Seven

Do not say:

Waiting on another government

if the City has not completed its own required submission.

60.446Anti-Gaming Rule Eight

Do not blame Council if the proposal was never brought forward.

60.447Anti-Gaming Rule Nine

Do not blame staff for workload created by unrealistic political commitments.

60.448Anti-Gaming Rule Ten

Do not blame a contractor without reviewing City procurement and contract administration.

60.449Anti-Gaming Rule Eleven

Do not call cost escalation unforeseeable when the original estimate had little design behind it.

60.450Anti-Gaming Rule Twelve

Do not hide scope reduction while claiming the project was nearly completed.

60.451Anti-Gaming Rule Thirteen

Do not count partial delivery as complete because the missing part is difficult.

60.452Anti-Gaming Rule Fourteen

Do not substitute an easier outcome metric after the intended outcome fails.

60.453Anti-Gaming Rule Fifteen

Do not call program usage success when the original target was:

60.454Anti-Gaming Rule Sixteen

Do not call funding secured:

60.455Anti-Gaming Rule Seventeen

Do not call money spent:

60.456Anti-Gaming Rule Eighteen

Do not call a responsible stop a completion.

60.457Anti-Gaming Rule Nineteen

Do not call every stopped project a failure.

60.458Anti-Gaming Rule Twenty

Do not hide failed pilots.

60.459Anti-Gaming Rule Twenty-One

Do not keep a failed pilot running simply to avoid admitting failure.

60.460Anti-Gaming Rule Twenty-Two

Do not create a new pilot name and pretend the old failed initiative disappeared.

60.461Anti-Gaming Rule Twenty-Three

Do not remove sunk costs from public reporting because the project was cancelled.

60.462Anti-Gaming Rule Twenty-Four

Do not count avoided future spending as a verified saving automatically.

60.463Anti-Gaming Rule Twenty-Five

Do not use estimated opportunity cost as a precise dollar loss without evidence.

60.464Anti-Gaming Rule Twenty-Six

Do not assign every miss to:

external factors.

60.465Anti-Gaming Rule Twenty-Seven

Do not assign every miss to:

previous Council.

Inherited problems should be identified separately.

60.466Anti-Gaming Rule Twenty-Eight

Do not assign every miss to:

staff.

60.467Anti-Gaming Rule Twenty-Nine

Do not hide misses because litigation or negotiation limits some detail.

Publish what can lawfully be said.

60.468Anti-Gaming Rule Thirty

Do not classify a project as confidential simply because:

60.469Anti-Gaming Rule Thirty-One

Do not hide late projects until after the election.

60.470Anti-Gaming Rule Thirty-Two

Do not accelerate unsafe work to avoid a Red status before election day.

60.471Anti-Gaming Rule Thirty-Three

Do not sign incomplete acceptance documents for political timing.

60.472Anti-Gaming Rule Thirty-Four

Do not pressure staff or professionals to change status.

60.473Anti-Gaming Rule Thirty-Five

Do not create dozens of trivial completed tasks to numerically drown major misses.

60.474Anti-Gaming Rule Thirty-Six

Do not combine multiple missed promises into one category to reduce miss count.

60.475Anti-Gaming Rule Thirty-Seven

Do not invent new commitments after successful work to improve the apparent completion ratio.

60.476Anti-Gaming Rule Thirty-Eight

Do not remove politically inconvenient outcomes from the final audit.

60.477Anti-Gaming Rule Thirty-Nine

Do not let a campaign write the official explanation of a miss.

60.478Anti-Gaming Rule Forty

Do not let City administration write political excuses either.

Use factual institutional language.

60.479Election-Year Integrity

Year Four is where the Missed Scorecard matters most.

60.480Fixed Reporting Date

Publish final pre-election audit according to:

60.481Same Definitions

Use the same:

definitions used earlier.

60.482No Election Rebranding

Never.

60.483Official Report

Neutral.

60.484Candidate Response

Candidates can argue:

a miss was justified.

That belongs to:

60.485City Facts

Remain:

60.486No Selective Release

Do not release:

weeks before:

Publish together.

60.487No Friday-Night Dump

Major accountability reports should be released:

60.488Media Availability

Staff may explain:

60.489Political Accountability

Elected officials may explain:

60.490Staff Should Not Defend Campaign Promise

Not their role.

60.491Final-Year New Commitments

Do not add new commitments merely so they can be:

60.492Necessary New Work

Can still arise.

Track separately.

60.493Four-Year Cut-Off

Only promises genuinely part of the four-year program belong in:

60.494Ongoing City Work

Continue regardless.

60.495First-Year Baseline

Year One should identify:

60.496Year One Risk Review

Identify early:

60.497Correct Early

Better to revise in:

than pretend for:

60.498Year Two

Publish:

already occurring.

60.499No Mid-Term Victory Only

The annual report should contain:

60.500Year Three

Identify commitments unlikely to finish by term end.

60.501Year Three Decision

Choose:

60.502Do Not Carry False Hope

If completion is impossible:

Say so.

60.503Year Four

Finish what is responsibly finishable.

60.504Do Not Finish What Should Be Stopped

Key.

60.505Year Four Handoff

Prepare remaining:

60.506Four-Year Core Measures

Strong measures include:

60.507Completed on Time

Distinct.

60.508Completed Late

Distinct.

60.509Missed and Continuing

Distinct.

60.510Missed and Stopped

Distinct.

60.511Missed and Superseded

Distinct.

60.512Missed, External Block

Distinct.

60.513Missed, Democratic Rejection

Distinct.

60.514Outcome Miss

Distinct.

60.515Unverifiable Outcome

Distinct.

60.516No One Headline Percentage

The full picture matters.

60.517Four-Year Missed Commitments Audit

At term end publish:

Commitments missed

Completed late

Major commitments missed

Responsible stops

Council rejections

External-government blocks

Partner failures

Funding failures

Procurement failures

Contractor failures

Capacity failures

Technology failures

Outcome misses

Scope reductions

Quality failures

Cost overruns linked to incomplete work

Sunk costs

Remaining contractual exposure

Grant repayments

Resident impacts

Temporary mitigations

Root causes

Repeated causes

Lessons implemented

Lessons not yet implemented

Handoffs to the next Council

60.518Name the Biggest Miss

Use evidence.

60.519Name the Most Expensive Miss

60.520Name the Largest Sunk Cost

60.521Name the Largest Remaining Financial Exposure

60.522Name the Most Delayed Commitment

60.523Name the Most Important Outcome Miss

60.524Name a Commitment That Was Correctly Stopped

60.525Name a Commitment the City Should Have Stopped Earlier

If applicable.

60.526Name a Commitment Council Rejected

60.527Name a Commitment Blocked by Ontario

Where accurate.

60.528Name a Commitment Blocked by Canada

Where accurate.

60.529Name a Commitment Blocked by Grey County or another required partner

Where accurate.

60.530Name a Commitment That Failed Because the City Misunderstood Its Authority

60.531Name a Commitment That Failed Because Its Scope Was Poorly Defined

60.532Name a Commitment That Failed Because the Original Estimate Was Weak

60.533Name a Procurement Failure

60.534Name a Contractor Failure

60.535Name a Capacity Failure

60.536Name a Technology Failure

60.537Name an Initiative That Was Operationally Delivered but Missed Its Intended Outcome

60.538Name a Pilot That Proved the Original Idea Should Not Continue

60.539Name a Major Lesson the City Actually Implemented

60.540Name a Lesson the City Failed to Implement

60.541Name the Largest Missed Commitment Being Handed to the Next Council

60.542Name the Most Urgent Handoff Decision

60.543Promise Test

Ask:

Was this actually promised?

60.544Deadline Test

Ask:

Was it actually due?

60.545Delivery Test

Ask:

Was the promised deliverable actually completed?

60.546Authority Test

Ask:

Did the City control the result?

60.547Early Warning Test

Ask:

When did we first know it might fail?

60.548Disclosure Test

Ask:

When did residents find out?

60.549Cause Test

Ask:

Why was it missed?

60.550Responsibility Test

Ask:

Which cause was inside City control?

60.551Cost Test

Ask:

How much public money was spent before the miss?

60.552Exposure Test

Ask:

What financial obligation remains?

60.553Resident Test

Ask:

What practical consequence did residents experience?

60.554Recovery Test

Ask:

Is there still a responsible path to completion?

60.555Stop Test

Ask:

Would continuing now create more public value than stopping?

60.556Sunk-Cost Test

Ask:

Are we continuing because the project is still good, or because we are embarrassed by what has already been spent?

60.557Rights Test

Ask:

Would completing the promise create a rights, privacy, accessibility or fairness problem?

60.558Procurement Test

Ask:

Would completing the promise require weakening fair procurement?

If yes:

Do not.

60.559Safety Test

Ask:

Would schedule recovery compromise safety or technical quality?

If yes:

Do not.

60.560Staff Test

Ask:

Are we demanding unsustainable workload merely to protect political optics?

60.561Partner Test

Ask:

Did the partner actually fail, or did the City fail to fulfil its own responsibilities first?

60.562Government Test

Ask:

Did the other government actually reject or block the request, or are we simply using it as an excuse?

60.563Outcome Test

Ask:

Did the initiative produce the result used to justify it?

60.564Measurement Test

Ask:

Can that outcome actually be verified?

60.565Lesson Test

Ask:

What changed in City practice because this went wrong?

60.566Repeat-Failure Test

Ask:

Have we made this same mistake before?

60.567Handoff Test

Ask:

Does the next Council receive enough information to make a decision immediately?

60.568Political Test

Ask:

Would we describe this miss the same way if another party, Mayor or Council had caused it?

The answer should be:

Yes.

60.569Election Test

Ask:

Would this commitment still be marked Missed if voting day were tomorrow?

60.570Institution Test

Ask:

Could a completely new Council understand what happened without hearing the outgoing administration's political explanation?

It should.

60.571What Success Looks Like

A successful Missed Scorecard does not mean:

Success means:

60.572What Failure Looks Like

Failure includes:

60.573The Missed Commitments Scorecard Commitment

Owen Sound should commit to:

Publish what the City missed, not only what it completed.

Treat Missed as a factual status rather than automatic moral condemnation.

Distinguish City execution failures, responsible stops, democratic rejection, external blocks, changed evidence and shared responsibility.

Allow cause to remain under review temporarily when evidence is incomplete rather than inventing certainty.

Use the same underlying Commitment Register for completed and missed commitments.

Preserve the original promise, scope, target date, cost assumption and authority.

Record when a commitment actually became overdue or formally stopped.

Classify later delivery as Completed Late rather than rewriting history as On Time.

Never erase an original missed deadline when a revised deadline is approved.

Require transparent authorization and explanation for deadline changes.

Do not move deadlines at the last minute merely to avoid a negative Scorecard status.

Use At Risk as an early-warning status before commitments fail.

Do not punish staff for identifying risk early.

Do not label inactive commitments On Track merely because their deadlines have not arrived.

Track the date major risks were first identified and when residents were informed.

Do not allow major failures to remain hidden internally for years.

Escalate at-risk major commitments through the appropriate administrative and governance channels.

Use recovery plans with clear causes, corrective actions, costs and decisions.

Do not spend unlimited public money merely because a promise was made.

Apply the continuing-value test to every troubled commitment.

Recognize sunk cost without allowing sunk cost to dictate future decisions.

Publish money already spent on significant failed or stopped commitments.

Show recoverable funds, contractual obligations, termination costs and remaining exposure.

Do not invent precise staff-cost figures where the methodology does not support them.

Show grant repayment or clawback risks.

Do not continue an unsound project solely to preserve outside funding.

Compare the remaining public cost of completion against the public value still expected.

Include operating, maintenance and replacement obligations in recovery decisions.

Describe practical resident impacts of significant misses.

Do not fabricate private economic losses for political effect.

Show temporary mitigation separately from permanent completion.

Perform root-cause analysis on material misses.

Distinguish causes from excuses.

Use consistent cause categories so repeated organizational patterns can be identified.

Do not hide behind vague phrases such as market conditions or unforeseen circumstances when the actual cause can be described.

Acknowledge inadequate due diligence where it occurred.

Acknowledge weak estimating where it occurred.

Acknowledge unclear scope where it occurred.

Acknowledge jurisdiction errors where they occurred.

Acknowledge inadequate capacity where it occurred.

Acknowledge procurement and contract-administration failures where they occurred.

Distinguish external events from City-created problems.

Look for system causes rather than simply identifying the individual closest to the mistake.

Handle individual misconduct through proper professional, HR or legal systems rather than through public scorecard shaming.

Hold leadership accountable for organizational systems.

Publish when a commitment failed because the City misunderstood its legal authority.

Show what the City could lawfully do instead.

Use repeated jurisdiction errors as a signal to improve future Authority Maps.

Record Council rejection honestly.

Distinguish a Mayor completing a promise to bring something forward from the City actually implementing the proposal.

Do not turn official City reporting into blame toward councillors who voted differently.

Allow public consultation and evidence to change an original proposal.

Do not call a changed proposal the original promise completed.

Never continue an unwise commitment merely because changing course may be politically embarrassing.

For commitments dependent on another government, show the City's actual request, follow-up and response.

Do not claim the City is waiting on Ontario, Canada, Grey County or another partner if the City has not completed its own required work.

Use precise evidence when classifying an external block.

Distinguish City advocacy from the final decision of another government.

Label outside funding as secured, applied for or speculative from the beginning.

Do not present speculative grants as guaranteed financing.

Return to Council when outside funding fails rather than automatically transferring the gap to property taxpayers.

Explain whether grant failure resulted from eligibility, timing, proposal weakness or external competition.

Do not accuse another government of refusing support when the City was never eligible.

Report lost grants caused by City error.

Report repayment obligations where project failure triggers them.

Treat procurement integrity as more important than political schedule.

Do not weaken competitive processes merely to finish a promise before an election.

Review no-bid, one-bid and over-budget procurement results for underlying scope and market issues.

Retender, redesign, reduce scope or stop where public value requires it.

Never misuse sole-source procurement for political timing.

Review City procurement and contract administration before assigning all blame to a contractor.

Protect legitimate legal positions when contractor disputes are active while still reporting project status.

Treat staff capacity as a real constraint.

Do not make employees the scapegoat for more political priorities than the organization can realistically deliver.

Require capacity planning for significant new initiatives.

Show what existing work will be delayed when major new work is added.

Do not rely on chronic overtime and staff burnout as a promise-delivery strategy.

Identify key-person dependencies and succession risks.

Treat software purchase as the beginning of implementation, not proof of success.

Report digital projects that fail through integration, migration, privacy, accessibility, cybersecurity or user adoption.

Allow privacy, security and accessibility gates to delay or stop politically important technology projects.

Do not keep failed software merely because licensing money has already been spent.

Apply the strictest independence and conflict standards to technology associated with the Mayor or other elected officials.

Never launch a conflict-sensitive system simply to protect its founder from political embarrassment.

Recognize missing baseline data as a possible implementation failure.

Do not claim measurable improvement where the City failed to establish the original measurement.

Use Outcome Unverifiable where evidence cannot support a result.

Never select a favourable historical baseline after results are known.

Distinguish implementation completion from outcome achievement.

Allow the honest status: Implementation Completed, Outcome Missed.

Use pilots to test theories without forcing permanent continuation.

Treat a pilot that disproves the idea as useful evidence.

Do not promise permanent expansion before pilot evidence exists.

Apply the same outcome honesty to housing, business, downtown, safety, recreation, youth, accessibility, privacy, environment, partnerships, satisfaction, finance, tax, services and infrastructure.

Never replace a failed outcome with an easier activity metric.

Show exact delivered and undelivered scope on partially completed work.

Do not use vague percentages to hide the importance of missing components.

Do not invent a lower minimum completion threshold after delivery trouble begins.

Track quality failures, rework, defects and warranty problems where material.

Do not call a project technically complete merely because it looks finished.

Allow legal and rights concerns to stop original commitments.

Do not compromise Charter, privacy, accessibility, conflict or procurement obligations simply to preserve a promise.

Provide a sufficient public explanation of legal stops without unnecessarily waiving privilege.

Do not bypass conflict rules to prevent a project from appearing missed.

Review whether late-discovered conflicts should have been identified earlier.

Treat integrity as more important than completion percentage.

Use environmental due diligence to distinguish genuine unknown conditions from inadequate planning.

Show contamination and other inherited liabilities honestly.

Report environmental outcome misses such as poor tree survival or underperforming energy retrofits against their original expectations.

Do not lower forecasts retrospectively without showing the original forecast.

Distinguish partner failures from City failures while still reporting the resident impact.

Do not politically grade government-to-government disagreement with Saugeen Ojibway Nation as a partnership failure.

Score only mutually agreed commitments appropriately.

Distinguish City and Grey County responsibility on shared misses.

Report provincial and federal asks that were declined or unanswered without partisan scorekeeping.

Evaluate whether the City's advocacy was precise, timely and evidence-based.

Review community-partner capacity before relying on organizations for significant public delivery.

Do not publicly shame partner organizations without fair process.

Do not make critical services dependent on fragile volunteer capacity without contingency.

Treat low demand as real evidence.

Investigate whether low use reflects awareness, access, price, design or genuine lack of interest.

Do not manufacture participation merely to preserve a program.

Stop weak programs where evidence supports it.

Use privacy-safe methods when investigating participation barriers.

Set reconsideration triggers for major cost escalation.

Do not use one arbitrary percentage for every type of project.

Distinguish contingency use from true cost overrun.

Track material change orders and repeated patterns.

Explain estimate maturity when comparing early concepts with final cost.

Do not force unrealistically precise early estimates for political announcements.

Stop or redesign projects that no longer pass the Complete Cost test.

Measure both the cost and the possible benefit of delay.

Do not compress schedules in ways that create unsafe or low-quality work.

Do not let an election deadline override seasonal, technical, legal, Indigenous engagement or public-consultation requirements.

Treat communication failure as a separate accountability issue when residents were unnecessarily left uninformed.

Do not publish meaningless updates saying only that work continues.

Tell residents what is blocked and what happens next.

Give troubled commitments a clear recovery choice: complete, redesign, replace, transfer, pause, stop or hand off.

Do not allow Under Review, Deferred, Blocked, Waiting, Ongoing or In Progress to become permanent hiding places.

Require each of those statuses to have a reason and next decision.

Eliminate zombie commitments with no active work or realistic next step.

Give every material term-end miss a complete handoff package.

Show work completed, work remaining, cost, contracts, legal issues, partner obligations, risks and next decision.

Do not imply that the next Council is politically required to continue unfinished work unless legal commitments genuinely bind the City.

Separate legal obligations from outgoing policy recommendations.

Flag safety, legal, contractual and grant deadlines in the handoff.

Do not leave political booby traps for the next administration.

Transfer complete records, credentials, vendor contacts, partner history and decision history institutionally.

Require a practical lesson from significant misses, delays and stops.

Turn lessons into changes to real City processes.

Do not publish lessons that nobody owns or implements.

Track repeated root causes across multiple projects.

Treat repeated scope, jurisdiction, procurement or capacity problems as organizational issues.

Do not rank departments solely by number of missed commitments without accounting for project scale and complexity.

Define major misses in advance and report them prominently.

Do not bury major failures among dozens of minor administrative misses.

Publish miss counts only with significance and cause context.

Do not use a low miss rate as proof of strong government if the City simply avoided meaningful commitments.

Do not use ambition as an excuse for reckless promises.

Aim for ambitious but grounded commitments and honest management when some do not work.

Publish At-Risk, Missed, Responsible Stop, External Block, Council Rejection, Financial Exposure, Root Cause, Handoff, Lesson and Outcome Miss tables.

Use Green, Amber, Red and Grey only as supporting indicators rather than substitutes for plain status language.

Never delete missed commitments.

Never rewrite original wording after failure.

Never change an expired deadline to make a miss disappear.

Never convert a four-year promise into an undefined long-term vision after it becomes inconvenient.

Never use Ongoing or Under Review indefinitely to conceal inactivity.

Never blame another government when the City's own required work remains incomplete.

Never blame Council for an initiative the Mayor never actually presented.

Never blame staff for impossible workload created by political overcommitment.

Never blame contractors without reviewing City procurement and contract management.

Never describe a speculative early estimate as if it should have been a reliable final cost.

Never hide material scope reduction.

Never substitute activity measures for failed outcomes.

Never describe funding approval, spending or program launch as the public result itself.

Never call a responsible stop a completed promise.

Never call every stopped initiative a failure.

Never hide failed pilots or keep them running only to avoid embarrassment.

Never rename a failed initiative simply to make the history disappear.

Never hide sunk costs or repayment obligations.

Never call estimated avoided future spending a verified saving automatically.

Never turn uncertain opportunity costs into precise political loss claims.

Never attribute every miss to external circumstances.

Never attribute every miss to a previous Council.

Never attribute every miss to staff.

Never use confidentiality as a blanket shield for politically inconvenient project status.

Never delay reporting until after an election.

Never accelerate unsafe work, sign premature acceptance or pressure professionals for election-year completion.

Never flood the Scorecard with tiny wins to bury major misses.

Never combine several distinct missed commitments merely to reduce the miss count.

Never allow the campaign to write the City's official explanation of failure.

Use factual institutional language in official reporting.

Publish the final pre-election Scorecard on a predetermined schedule.

Use the same definitions throughout the full four-year term.

Publish completed and missed commitments together.

Release major accountability reports accessibly and normally rather than burying them.

Keep staff responsible for explaining technical facts and elected officials responsible for political decisions.

Do not create trivial Year Four commitments merely to generate quick completions.

Use Year One to identify commitment risks, authority mistakes, cost gaps and capacity limits early.

Correct weak promises early rather than protecting them for four years.

Publish real misses and responsible stops during Years One and Two, not just victories.

Use Year Three to identify which commitments are unlikely to finish and make honest recover, stop or handoff decisions.

Use Year Four to finish what should responsibly be finished, not everything at any cost.

Publish a Four-Year Missed Commitments Audit alongside the Completed Scorecard.

Separate Completed On Time, Completed Late, Missed and Continuing, Missed and Stopped, External Block, Democratic Rejection, Outcome Miss and Unverifiable Outcome.

Name the biggest miss.

Name the most expensive miss.

Name the largest sunk cost.

Name the largest remaining financial exposure.

Name the most delayed commitment.

Name the most important outcome miss.

Name a commitment the City responsibly stopped.

Name one it should have stopped sooner if the evidence supports that conclusion.

Name major Council rejections and external-government blocks accurately.

Name commitments that failed because the City misunderstood authority, scope, cost, procurement, capacity or technology.

Name an initiative that was operationally completed but failed to produce its intended outcome.

Name a pilot that proved an idea should not continue.

Name lessons that actually changed City practice.

Name lessons the institution failed to implement.

Name the largest incomplete commitment and most urgent decision being handed to the next Council.

Judge the final term not by whether every promise succeeded, but by whether the City told the truth about the promises that did not.

A strong Missed Scorecard should allow a resident to ask:

What did you promise?

What did you miss?

When did you know?

When did you tell us?

Why did it happen?

Was it your responsibility?

Was it Council's decision?

Was another government actually blocking it?

How much did we spend?

What do we still owe?

Was stopping the right decision?

What changed because you learned from it?

Is the same mistake happening again?

What does the next Council inherit?

Government should never fear that page.

A City capable of publishing:

Here are the things we got wrong

is demonstrating something more valuable than perfection.

It is demonstrating:

No four-year plan survives four years exactly as written.

Conditions change.

Evidence changes.

Governments change.

Costs change.

The integrity test is whether the record changes too.

Do not erase the miss. Name it. Explain it. Show the cost. Separate failure from responsible restraint. Learn from the cause. Fix the process. Stop what should stop. Hand off what remains. Never change the definition of success merely because the truth became inconvenient.

← Chapter 59: Completed: The Public Commitments Completion ScorecardChapter 61: The Initiative Format: The Standard for Every City Proposal →