Owen Sound: A Four-Year City Business Plan

Home › The Public Scorecard › Chapter 51

The Public Scorecard

Chapter 51Safety: The Public Safety Scorecard

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

Public safety is too important to reduce to:

A safe city is one where:

The central principle is:

Safety should be measured by harm, risk, response, prevention and capacity, not by how much enforcement activity government produces.

More:

can sometimes mean stronger enforcement.

They can also mean:

Less enforcement activity can sometimes mean:

It can also mean:

That is why the Safety Scorecard must use several measures together.

The goal is not:

make the statistics look safe.

The goal is:

make Owen Sound safer and publish enough information for residents to judge whether that is actually happening.

51.1Purpose

The Safety Scorecard should answer:

Are serious incidents increasing or decreasing?

Are repeat calls consuming more or less emergency capacity?

Are urgent calls receiving appropriate response?

Are police resources being used on problems best suited to police?

Are other qualified responders available where appropriate?

Are fires being prevented as well as responded to?

Are traffic collisions and serious injuries changing?

Are dangerous locations being identified and corrected?

Are residents comfortable using public spaces?

Where does perceived safety differ from actual incident data?

Is responder capacity adequate?

Are prevention programs reducing repeat demand?

Are surveillance tools proportionate?

Are privacy and civil rights being protected?

Those are the meaningful questions.

51.2Safety Is Shared

Community safety is not produced by one department.

It may involve:

The Scorecard should show those roles without blurring authority.

51.3Do Not Turn Shared Responsibility Into Nobody's Responsibility

Every initiative still needs:

51.4Police Are Not the Entire Safety System

Policing remains essential.

But many safety risks are also influenced by:

51.5Police Should Not Become the Default Answer to Every Social Problem

Where another qualified response is:

the City and its partners should explore it.

51.6Other Responders Must Not Become Discount Police

The reverse is equally important.

A community worker or health professional should not be sent into:

situations simply because they cost less.

Responder safety matters.

51.7Right Responder Principle

The operating question is:

Who is best qualified to respond to this type of call safely?

Possible answers may include:

51.8Jurisdiction Still Applies

Not every responder is controlled by Owen Sound.

Where Grey County, a health body or another institution carries responsibility:

Report the partnership accurately.

51.9No Municipal Paramedic Fiction

If paramedics are operated outside the City's direct authority:

Do not publish paramedic performance as though Owen Sound Council controls it.

The City may report:

where relevant.

51.10Safety Scorecard Headline Measures

A first-page Safety Scorecard could include:

  1. Serious incident trend.
  2. Calls for service trend.
  3. Highest-priority response performance where publishable.
  4. Repeat-call demand.
  5. Repeat-location demand.
  6. Police proactive capacity.
  7. Right Responder diversions.
  8. Right Responder safety incidents.
  9. Fire incidents.
  10. Fire prevention activity.
  11. Repeat fire-risk locations where appropriate in aggregate.
  12. Traffic collisions.
  13. Serious traffic injuries and fatalities.
  14. High-risk road locations.
  15. Safety-related infrastructure corrections.
  16. Downtown actual safety.
  17. Downtown perceived safety.
  18. Public-space safety perception.
  19. By-law demand where relevant.
  20. Emergency-preparedness indicators.
  21. Major responder staffing or capacity pressures.
  22. Surveillance systems.
  23. Privacy incidents related to safety tools.
  24. Verified Safety Dividend, if any.
  25. Unresolved public-safety risks.

That is enough for the headline.

51.11Actual Safety and Perceived Safety

The Scorecard should always separate:

Actual Safety Indicators

Professionally recorded incidents and risks.

Perceived Safety

How residents experience the community.

Both matter.

Neither substitutes for the other.

51.12Perception Can Be Wrong

Residents may feel less safe while recorded serious incidents decline.

51.13Recorded Data Can Also Be Incomplete

Some harmful behaviour:

That is why experience matters too.

51.14Do Not Manipulate One With the Other

Do not say:

Residents feel unsafe, therefore crime is rising.

Do not say:

Recorded crime fell, therefore anyone who feels unsafe is wrong.

Use both.

51.15Safety Is Not Fear Management

The City's role is not to frighten residents into:

Communicate risk proportionately.

51.16Safety Is Not Image Management

The City should not suppress legitimate safety information to protect:

51.17Incident Categories

Public reporting should use professionally meaningful categories.

Do not create political categories designed for headlines.

51.18Serious Harm First

Particular attention should be given to incidents involving:

Raw count of minor incidents should not outweigh serious harm.

51.19Frequency and Severity

A good safety picture asks:

How often?

and

How serious?

51.20One Severe Event

A rare but catastrophic event can matter more than many minor calls.

Use context.

51.21Multi-Year Trend

Safety should generally be evaluated across multiple years.

A single month can be highly volatile.

51.22Monthly Data Still Useful

Monthly or quarterly monitoring helps operations.

Public interpretation should emphasize:

51.23Seasonal Effects

Some incidents vary by:

Use comparable periods.

51.24Population Change

Where comparing long periods:

Consider whether population changed materially.

51.25Rate Versus Count

For some measures, show:

Do not use a rate where the population denominator is unreliable.

51.26No Metric Shopping

Do not use:

Publish a stable method.

51.27Calls for Service

Calls for service can help show demand.

They are not identical to:

51.28One Incident Can Create Several Calls

Where data systems permit:

Distinguish:

51.29Call Volume Can Rise Because Reporting Improved

Do not automatically interpret more calls as:

51.30Call Volume Can Fall Because People Stop Reporting

Do not automatically interpret fewer calls as:

Cross-check with other information.

51.31Call Priority

Where public reporting is operationally appropriate:

Separate:

demand.

51.32Response Time

Response time should be used only where the metric is professionally appropriate.

51.33Priority Matters

Do not publish one average response time mixing:

That number would be misleading.

51.34Median and Tail

For appropriate priority calls:

Consider:

51.35Average Alone Can Hide Extremes

Same principle as other services.

51.36Response Time Is Not Entire Public Safety

A responder arriving quickly after harm occurs is not the same as:

Measure prevention too.

51.37Dispatch Time

Where relevant:

Distinguish:

components.

Do not blame field responders for delay elsewhere in the chain.

51.38Geography

Response performance can vary by:

Use professional interpretation.

51.39No Political Response-Time Promise

Do not promise:

Every call answered in six minutes.

Real emergency systems require priority and operational judgement.

51.40Police Workload

Workload should be measured more carefully than:

51.41Demand Per Officer

A crude demand-per-officer ratio may be useful internally.

It should not become the sole public metric.

Different calls require different effort.

51.42Officer Count Is Not Safety Outcome

More police can be necessary.

Fewer police can sometimes be justified.

The correct staffing level depends on:

51.43No Predetermined Police Cut

The Safety Dividend framework must never begin with:

We will cut X officers.

It begins with:

What demand changed, and what capacity is actually required?

51.44No Predetermined Police Increase Either

Likewise:

More officers always means safer

should not replace workload analysis.

51.45Staffing Business Case

Major staffing changes should consider:

51.46Operational Independence

Within the applicable policing governance framework:

Elected officials should not direct individual:

51.47Council's Role

Council may deal with lawful matters such as:

through the proper governance process.

51.48Mayor's Role

The Mayor should never say:

Arrest this person.

or:

Ignore that person.

That is not municipal leadership.

51.49Political Neutrality

Police service must not become an instrument for:

51.50Proactive Capacity

A police service consumed entirely by reactive calls may have little time for:

51.51Proactive Time

Where the service uses a professional measure:

Track available proactive capacity.

51.52Proactive Does Not Mean Quotas

Do not translate free officer time into:

51.53Prevention Work

Potential examples:

Measure actual outcomes where possible.

51.54Enforcement Count

Tickets, charges and arrests may be reported.

But they should be labelled:

activity measures.

Not automatically:

success measures.

51.55More Charges Can Mean More Crime

Or:

Interpret carefully.

51.56Fewer Charges Can Mean Less Crime

Or:

Again:

Context.

51.57Clearance Measures

If professional police reporting includes case-clearance measures:

Use them with appropriate definitions.

Do not imply every unsolved case represents poor policing.

51.58Victim-Centred Metrics

Where appropriate and privacy-safe:

Consider whether victims received:

51.59Victim Privacy

Never expose:

through scorecard reporting.

51.60Repeat Demand

One of the most important Safety Scorecard measures is:

How much demand comes from repeated calls involving the same underlying problem?

51.61Repeat Location

Track locations generating repeated calls where appropriate.

51.62Repeat Person

Be much more careful.

Do not build public:

Operational systems may need lawful case information.

Public Scorecard should be aggregate.

51.63Repeat Cause

Possible recurring causes may involve:

Use root-cause analysis.

51.64Root Cause Does Not Excuse Harm

Understanding why something happens does not mean:

It means the City seeks a more durable response.

51.65Repeat-Call Share

Possible measure:

Repeat-Call Share = Eligible Calls Linked to Recurring Locations or Defined Repeat Events ÷ Eligible Calls

Use a professionally appropriate method.

51.66Privacy First

Do not distort privacy rules simply because repeat-demand analysis sounds useful.

51.67Right Responder

The Right Responder model should begin as a carefully bounded pilot.

51.68Pilot Problem Definition

Before launch:

Identify specific call types where:

51.69Do Not Begin With Budget Savings

First question:

Can another qualified response safely improve the outcome?

Savings come later if they occur.

51.70Eligible Call Types

Define professionally.

Do not let a politician write a casual list.

51.71Exclusion

Potentially violent or high-risk calls may remain:

depending on professional protocols.

51.72Responder Qualification

Alternative responders require:

51.73Responder Safety

Track any safety incidents involving alternative responders.

51.74Police Backup

Protocols should define when police support is:

51.75Diversion

A Right Responder diversion occurs when an eligible call that would otherwise have consumed police response is safely handled through another approved response pathway.

51.76Do Not Count Every Referral as Diversion

A police officer attending first and then calling a service may still consume significant police time.

Measure accurately.

51.77Police Time Released

Where measurable:

Estimate actual officer time released.

51.78Time Released Is Not Cash Saving Automatically

Released capacity may be used for:

That is a:

capacity dividend

before it is a financial dividend.

51.79Capacity Dividend

This distinction should be central.

Capacity Dividend

Police or responder time becomes available for higher-priority work.

Financial Dividend

Actual recurring expenditure is reduced.

Do not confuse them.

51.80Right Responder Outcome

Possible measures:

51.81No Vulnerable-Person Score

Do not rate individual people based on:

51.82Follow-Up

Where partner systems allow and privacy rules permit:

Measure whether the person was connected to the intended service.

51.83Referral Does Not Equal Service Received

A phone number handed over is not:

51.84No Forced Follow-Up Surveillance

Do not create intrusive tracking merely to prove the program works.

Use aggregate partner data where possible.

51.85Repeat Call After Diversion

If the same type of demand immediately repeats:

Review whether the alternative response is working.

51.86Repeat Does Not Automatically Mean Failure

Complex needs may require multiple contacts.

Use professional interpretation.

51.87Pilot Stop Condition

The pilot should stop or be redesigned if:

51.88Scale Condition

Scale only after:

are demonstrated.

51.89Fire Safety

Fire protection should be measured through both:

51.90Fire Incidents

Track significant fire incidents.

51.91Fire Severity

Where professional reporting allows:

Separate:

outcomes.

51.92Fire Loss

Property-loss estimates may be useful.

Treat them as estimates.

51.93Life Safety

Fatalities and serious injuries are more important than:

51.94Fire Response

Use applicable professional service measures.

51.95Response Standard

Where a formal standard exists:

Measure it accurately.

Do not invent a campaign response target.

51.96Fire Staffing

Staffing decisions should follow:

analysis.

51.97Fire Station Location

Do not use the Scorecard to predetermine:

decisions without professional modelling.

51.98Fire Prevention

Track prevention activity such as:

where appropriate.

51.99Inspection Count Is Activity

Do not assume:

automatically means:

Track outcomes too.

51.100Risk-Based Prevention

Resources may be focused on:

where professional practice supports it.

51.101Inspection Completion

Track applicable required inspections.

51.102Overdue Inspection

A stronger metric may be:

required fire-prevention inspections overdue.

51.103Fire Code Compliance

Track recurring significant compliance issues at aggregate level.

51.104Private Information

Do not publicly shame individual homeowners.

Public commercial enforcement information should still follow lawful disclosure rules.

51.105Fire Education

Measure:

lightly.

Do not count a brochure as:

51.106Smoke and CO Alarm Programs

Where programs exist:

Track actual installations or verified assistance.

51.107No False Prevention Claim

Do not say:

These alarms prevented 20 fires

without evidence.

51.108Repeat Fire Locations

Where professional analysis shows recurring incidents:

Review underlying conditions.

51.109Vacant Buildings

Vacant or deteriorating structures can create fire risk.

Coordinate:

51.110Vacancy Is Not Criminality

Do not equate:

with criminal residents.

Focus on property condition and risk.

51.111Emergency Access

Fire safety depends partly on:

Cross-reference Infrastructure.

51.112Downtown Street Changes

2nd Avenue or Civic Square design should preserve emergency access.

51.113Temporary Events

Event layouts should maintain required emergency access.

51.114Traffic Safety

Traffic safety should focus on:

Not merely:

51.115Collision Count

Track collisions where professionally available.

51.116Serious Injury

Give particular attention to:

51.117Vulnerable Road Users

Track safety involving:

where appropriate.

51.118No Blame From Mode Alone

Do not assume pedestrian or driver fault based solely on category.

Use investigation and engineering evidence.

51.119High-Risk Locations

Identify intersections or corridors with recurring:

51.120Public Map

A public safety map can show broad collision patterns.

Protect:

51.121Near Miss

Near-miss reporting can be useful.

But subjective reports need careful interpretation.

51.122Speed

Where speed data is collected:

Use actual measured speeds.

51.123Posted Speed Is Not Actual Speed

Track both where relevant.

51.124Enforcement

Ticket counts may supplement:

They do not replace it.

51.125Road Design

If repeated speeding occurs:

Ask whether:

contributes.

51.126Engineering Before Enforcement Alone

Some problems may need:

changes.

51.127Enforcement Still Matters

Dangerous behaviour may still require enforcement.

Both can be true.

51.128Traffic Safety Intervention

For each major intervention:

Define:

51.129Before-and-After Window

Use comparable periods.

51.130Regression to the Mean

One bad year can make a location appear improved naturally.

Use multi-year data where possible.

51.131No "Vision Zero" Branding Requirement

The City may adopt whatever formal traffic-safety framework Council chooses.

The Scorecard should focus on:

51.132Traffic Death Goal

No death is acceptable as a target outcome.

But a scorecard should still report reality honestly.

51.133Streetlight Safety

Cross-reference Infrastructure.

Lighting can support:

Do not claim direct crime reduction without evidence.

51.134Crosswalks

Measure:

where data supports it.

51.135Safe Routes

Family neighbourhood work should identify:

51.136School Jurisdiction

The City controls:

It does not control school operations.

Coordinate.

51.137Traffic Complaints

Use complaint data as:

Not proof.

51.138Speed Display Signs

If used:

Measure actual effect.

Do not count installations alone.

51.139Temporary Traffic Calming

Pilot before permanent where practical.

51.140Emergency Vehicle Impact

Review traffic-calming designs appropriately.

51.141Winter Impact

Likewise.

51.142Accessibility Impact

Likewise.

51.143By-Law Safety

By-law enforcement can affect:

51.144By-Law Count Is Not Safety Outcome

Number of tickets issued is an activity metric.

51.145Voluntary Compliance

Where appropriate:

A resolved issue without ticket may be success.

51.146Repeat Violation

Repeated non-compliance may require stronger response.

51.147Enforcement Consistency

Similar situations should receive similar treatment.

51.148No Political By-Law Enforcement

Supporters and critics receive the same standards.

51.149Anonymous Complaint

Anonymous reporting may be appropriate for some matters.

Do not allow it to become a tool for repeated harassment.

51.150Frivolous or Vexatious Use

Use a lawful, careful process for repeated abusive reporting.

Do not label ordinary criticism vexatious.

51.151Public Space

Safety in parks, trails, downtown and civic spaces should combine:

51.152More People Can Improve Comfort

But:

More people do not automatically mean:

Avoid simplistic claims.

51.153Empty Space

An empty park can feel unsafe.

It can also simply be:

Use context.

51.154Day and Evening

Perception surveys should distinguish:

51.155Stable Questions

Use the same core questions year to year.

51.156Safety Perception Question

Example:

How comfortable do you feel using this area during the day?

51.157Evening Question

How comfortable do you feel using this area after dark?

51.158Survey Sample

Publish:

51.159Survey Bias

People with strong positive or negative experiences may be more likely to respond.

Explain limitations.

51.160No Safety Poll as Referendum on Police

Perception surveys should not be:

Do you support the police?

Measure experience.

51.161Downtown Safety

Cross-reference Section 48.

51.162Do Not Double Count

The final city-wide scorecard should not treat one downtown incident as:

51.163Parks and Trails

Cross-reference recreation.

51.164Accessibility and Safety

A broken curb or poor snow clearing can be:

issue.

Coordinate metrics.

51.165Fire and Building Safety

Cross-reference Housing where:

require life-safety standards.

51.166Housing Instability and Safety

Housing instability can affect public safety demand.

Do not conclude:

That would be inappropriate.

51.167Behaviour, Not Housing Status

Respond to:

Not identity or housing status.

51.168Homelessness

Where Grey County leads housing and homelessness:

Coordinate safety responses rather than creating a duplicate City social-service system.

51.169Crisis Calls

Crisis-related police demand may deserve partnership with:

51.170Health Privacy

Do not publish mental-health or medical information in the Safety Scorecard.

51.171No "Mental Health Crime" Category

Avoid stigmatizing classification.

Measure:

professionally.

51.172Substance Use

Similarly:

Do not reduce people to labels.

Measure specific safety impacts.

51.173Overdose

Where another public health body maintains data:

Reference aggregate trends carefully.

Do not claim municipal control.

51.174Public Drug Use

Where behaviour creates public safety or public-space issues:

Respond according to:

51.175No Ideological Shortcuts

Neither:

enforcement solves everything

nor:

enforcement is never appropriate

is an operating standard.

Use the right response.

51.176Community Partners

Service clubs, faith organizations and nonprofits may contribute to:

51.177Partnership Safeguard

Public safety work should not depend on:

51.178Volunteers

Volunteers can help with:

within safe roles.

51.179Volunteers Are Not Police

Do not create:

roles.

51.180Safety Walks

Neighbourhood safety walks may identify:

issues.

51.181Report, Do Not Confront

Volunteer instruction should be:

observe, report, avoid confrontation.

51.182Youth Safety

Civic Corps participants may assist with:

under supervision.

51.183Youth Are Not Enforcement

No.

51.184Seniors Safety

Senior safety can include:

Not all safety belongs to police.

51.185Scam Awareness

Safe Information programming can support:

51.186Fraud Data

Police or other authorities may track reported fraud.

Do not assume every scam attempt is reported.

51.187Scam Prevention Outcome

Better measure:

51.188Phone Reuse

Reused phones or connectivity programs should not be marketed as:

without confirming actual emergency capability.

51.189Emergency Calling Claims

Verify before publishing.

51.190Emergency Preparedness

Community safety includes readiness for:

51.191Preparedness Scorecard

Cross-reference emergency resilience.

Possible measures:

51.192Exercise Count Is Not Readiness

A drill matters only if lessons are implemented.

51.193Exercise Finding

Track:

51.194Unresolved Emergency Findings

Show significant unresolved governance issues at a safe public level.

51.195Public Preparedness

Measure whether residents can find:

51.196No Fear Marketing

Preparedness should build:

Not panic.

51.197Public Alerting

Use official systems.

Do not make residents depend on:

51.198Offline Information

Maintain appropriate:

options.

51.199FM and Community Communication

Any local emergency broadcast concept must integrate with:

emergency communications.

Do not create a parallel unofficial alert system that confuses residents.

51.200Infrastructure Failure

Water, road, power or digital failures can become safety issues.

Cross-reference Section 47.

51.201Critical Road Closure

Track emergency access effects.

51.202Backup Route

Major corridors should have continuity planning where appropriate.

51.203Harbour Safety

Where City responsibility exists:

Track applicable municipal safety.

Do not assume federal port responsibilities.

51.204River Safety

Public access should include:

51.205Outdoor Recreation

Cross-reference Section 52.

51.206No Overwarning

Safety information should not make every outdoor activity appear dangerous.

Use proportionate risk.

51.207Safety Infrastructure

A dedicated measure should track small physical corrections that can reduce risk.

Examples:

51.208Safety Correction Register

For significant issues:

Risk

Responsible department

Action

Status

Completion

51.209Correction Time

Track serious hazards from:

51.210Temporary Mitigation

A temporary:

can be appropriate before permanent repair.

51.211Temporary Is Not Permanent Completion

Mark separately.

51.212Near-Term Capital

If full correction requires capital:

Show planned timing.

51.213Unfunded Safety Risk

High-risk unfunded infrastructure deserves visibility.

51.214Risk Triage

Not every complaint is equal.

Prioritize:

51.215Surveillance

Safety technology requires strong boundaries.

51.216Camera Inventory

Maintain an appropriate inventory of City-operated public-space surveillance systems.

51.217Inventory Fields

Possible:

Do not publish exploitable coverage detail.

51.218Purpose Limitation

A camera installed for:

should not quietly become a behavioural tracking system.

51.219Retention

Keep footage only as long as law and legitimate purpose require.

51.220Access

Control who can access footage.

51.221Audit

Material access should be auditable where technically appropriate.

51.222Facial Recognition

No facial recognition by default.

51.223Separate Decision Required

Any proposal for biometric identification would require:

It should not arrive through a software update.

51.224Behavioural Analytics

The same caution applies to:

51.225AI Safety Tool

If AI assists with:

require governance.

51.226AI Is Not Probable Cause

Do not treat an algorithmic flag as proof of wrongdoing.

51.227Human Review

High-impact decisions require authorized human judgement.

51.228Bias Testing

Where automated systems affect people:

Review:

51.229Vendor Secrecy

A vendor's proprietary claim should not prevent government from understanding:

51.230Exit

Safety systems need:

51.231No Surveillance Because Grant Available

A grant does not create the public-safety need.

51.232Privacy Incident

Track confirmed material privacy incidents involving safety systems at an appropriate public level.

51.233Security Incident

Likewise.

Do not expose technical vulnerabilities.

51.234Camera Effectiveness

If cameras are justified as crime-prevention or investigation tools:

Measure whether they actually contribute to the intended purpose where possible.

51.235Camera Count Is Not Success

More cameras is not a safety outcome.

51.236Removal Can Be Success

Removing a system that no longer has:

can improve:

51.237Public Space Without Surveillance

A public place should not require constant tracking to be considered safe.

51.238Data Sharing

Safety information shared across agencies should follow lawful agreements.

51.239Minimum Necessary

Share only what is required for:

51.240No Universal Safety Profile

Do not build a municipal resident risk score.

51.241No Social Credit

Absolutely not.

51.242No Political Risk Score

Likewise.

51.243Safety Dividend

The Safety Dividend is one of the easiest ideas to overstate.

It needs strict rules.

51.244First Principle

Safety improvement comes first.

51.245Second Principle

Capacity savings come before financial savings.

51.246Third Principle

Financial savings must be independently verified.

51.247No Predetermined Amount

The Safety Dividend may equal:

$0.

That is an acceptable outcome.

51.248Safety Dividend Preconditions

Before claiming a financial dividend:

  1. demand reduction is demonstrated;
  2. reduction is durable enough to rely on;
  3. service quality remains adequate;
  4. responder safety remains adequate;
  5. staffing or other recurring expenditure actually changes;
  6. Finance verifies the recurring saving.

51.249Police Time Released Is Not Dividend

If officers use released time for:

there may be:

No financial saving yet.

51.250Overtime Reduction

A verified reduction in recurring overtime could potentially become part of a financial dividend if:

analysis supports it.

51.251Vacancy Is Not Automatic Dividend

Leaving necessary positions unfilled is not:

51.252Attrition

If sustained demand reduction allows a position to disappear through natural attrition without harming service:

That may create a legitimate saving.

Verify.

51.253No Layoff Target

Do not manufacture the Dividend through layoffs simply to satisfy the campaign concept.

51.254Contract Saving

If alternative response reduces a recurring contracted cost:

Include only after full replacement costs.

51.255New Program Cost

Right Responder services may cost:

Subtract that before claiming savings.

51.256Net Safety Saving

A general concept:

Verified Safety Saving = Verified Recurring Cost Reduction - New Recurring Cost Required to Sustain the Safety Model

Finance determines the formal method.

51.257Transition Cost

Show separately.

51.258One-Time Saving

Keep separate from recurring.

51.259Avoided Cost

Keep separate again.

51.260Safety Dividend Allocation

If a verified financial dividend exists:

Allocate according to the adopted financial framework.

Do not create a private political fund.

51.261Capacity Dividend Reporting

Even with no financial dividend:

Publish capacity improvement.

Example:

X hours of police response capacity redirected to higher-priority work.

Only if measurement is credible.

51.262Do Not Monetize Every Hour

Officer time does not automatically convert into cash.

51.263Safety Dividend Table

MeasureBaselineCurrentVerified Effect

Possible:

51.264Safety Dividend Anti-Gaming Rule

Never use:

for positions that remain fully funded.

51.265Safety Dividend Anti-Gaming Rule Two

Never count a grant paying for Right Responder as:

if the grant expires.

51.266Safety Dividend Anti-Gaming Rule Three

Never count reduced enforcement activity as:

without evidence.

51.267Safety Dividend Anti-Gaming Rule Four

Never claim safety improvement solely because expenditures fell.

51.268Safety Dividend Anti-Gaming Rule Five

Never make a staffing cut first and use subsequent lower spending as proof the pilot worked.

51.269Community Safety Cost

The Scorecard should show major City public-safety expenditures.

Cross-reference Finance.

51.270Cost Is Not Outcome

A larger safety budget is not automatically:

A smaller one is not automatically:

51.271Cost per Call

Some services may calculate:

internally.

Use cautiously.

A homicide investigation and noise call are not equivalent.

51.272Severity Weighting

Do not invent a simplistic weighting formula merely to create one workload score.

Use professional workload methods.

51.273Overtime

Track major:

overtime where appropriate.

51.274Overtime Context

Possible causes:

51.275Repeated Overtime

Persistent high overtime may indicate:

issue.

51.276Low Overtime

Low overtime is not automatically success if shifts are:

51.277Vacancy

Track authorized and actual staffing at an appropriate level.

51.278Authorized Versus Filled

Distinguish.

51.279Leave

Do not publish sensitive employee medical information.

Use aggregate availability where needed.

51.280Recruitment

Public-safety recruitment difficulty may affect capacity.

Report accurately.

51.281Training

Mandatory training is part of readiness.

51.282Training Hours

Training-hour counts are activity measures.

More is not automatically better.

51.283Certification

Track required qualifications where appropriate.

51.284Equipment Readiness

Fire and police operational equipment must be serviceable.

High-level readiness can be reported.

51.285Critical Vehicle Downtime

Cross-reference fleet.

51.286Backup Capacity

Emergency services require redundancy.

Do not label unused emergency equipment:

without operational analysis.

51.287Facilities

Public-safety facilities should have:

plans.

51.288Communications

Emergency communications require resilience.

51.289Radio Reliability

Technical measures should remain professional.

Publicly report high-level availability or major failures where appropriate.

51.290Cybersecurity

A digital outage can impair:

Cross-reference Digital Sovereignty.

51.291Cyber Incident Reporting

Publicly disclose material effect when appropriate.

Do not expose vulnerabilities.

51.292Manual Continuity

Critical services should have fallback procedures.

51.293Power Failure

Backup plans.

51.294Telecom Failure

Backup plans.

51.295Facility Failure

Alternate operations.

51.296Emergency Exercise

Test coordination.

51.297Exercise Lessons

Track whether lessons were implemented.

51.298Major Event Safety

Large public events may require:

planning.

51.299Event Safety Cost

Where material:

Show City cost.

51.300Event Attendance Does Not Override Safety

Do not weaken emergency requirements to fit more people into an event.

51.301Event Security

Use proportionate measures.

51.302No Security Theatre

Do not add highly visible controls that create little actual risk reduction merely to:

51.303Threat Assessment

Use qualified professional judgement.

51.304Public Communications

During a major incident:

Provide:

51.305Do Not Speculate

Early incident information can be wrong.

Say:

not yet confirmed.

51.306Rumour Correction

Safe Information can help correct:

51.307Do Not Amplify Every Rumour

Correct what matters.

51.308Media

Public-safety information should be released through appropriate professional channels.

51.309Mayor as Spokesperson

During major incidents:

The Mayor may support public communication.

They should not:

51.310Political Credit During Emergencies

Avoid.

Emergency response is not campaign content.

51.311Emergency Photos

Do not publish images that expose:

for political promotion.

51.312Incident Review

After major events:

Review:

51.313Public After-Action Summary

Where appropriate:

Publish lessons at a safe level.

51.314No Blame Theatre

After-action review is for:

Individual misconduct, if any, belongs in proper processes.

51.315Safety Complaints

Residents should have routes to raise:

concerns through the correct process.

51.316Wrong Door

If a complaint belongs to another statutory body:

Help the resident reach it.

51.317No Mayor Complaint Court

The Mayor should not personally decide:

complaints.

51.318Safety Survey

A periodic community safety survey can ask:

How safe do you feel in your neighbourhood during the day?

After dark?

Downtown?

In parks and trails?

What physical issue most affects your sense of safety?

Do you know how to report a non-emergency concern?

51.319Avoid Leading Questions

Do not ask:

Are you concerned about rising crime?

That presupposes the answer.

51.320Stable Sample

Use consistent method over time.

51.321Phone and Paper

Offer non-digital participation where practical.

51.322No Political Segmentation

Do not divide results by:

51.323Geographic Results

Neighbourhood-level results can be useful.

Suppress or aggregate small samples.

51.324No "Unsafe Neighbourhood" Label

Avoid stigmatizing areas based on:

51.325Public-Safety Data Quality

Every measure needs:

51.326Police Data Owner

Police service through the appropriate governance framework.

51.327Fire Data Owner

Fire service.

51.328Traffic Infrastructure Data Owner

Appropriate City engineering or public works function.

51.329Right Responder Data Owner

The approved lead plus participating partners.

51.330Safety Perception Data Owner

City survey administration or independent research process.

51.331Finance Data Owner

Finance verifies the Safety Dividend.

51.332No Mayor-Certified Safety Statistics

The Mayor may discuss results.

They do not create the underlying data.

51.333Measurement Frequency

Possible:

Serious incident and demand trend

Quarterly and annually.

Fire

Quarterly or annually according to reporting practice.

Traffic

Quarterly or annual depending on data.

Right Responder

Quarterly during pilot.

Safety perception

Annual or stable periodic survey.

Safety Dividend

Annual after verification.

51.334Real-Time Dashboard Caution

Not every safety measure should be:

Real-time incident maps can create:

risks.

51.335Delay Can Protect Integrity

Publishing verified aggregate data later may be better than instant unverified data.

51.336Public Incident Map

If one exists:

Use appropriate delay and aggregation.

51.337Victim Protection

Suppress sensitive locations where necessary.

51.338Domestic Violence

Never publish location detail that could expose victims.

51.339Youth Incidents

Protect minors.

Protect medical privacy.

51.341Small Numbers

Suppress where re-identification is reasonably possible.

51.342Open Data Boundary

Safety Open Data should serve:

without exposing people.

51.343Data Retention

Safety systems should follow lawful retention.

51.344Cameras Are Not Infinite Archives

Retention must be purpose-based.

51.345Incident Records

Formal policing or fire records follow their applicable legal frameworks.

The municipal dashboard does not replace them.

51.346Safety Baseline

Year One should establish:

51.347Baseline Imperfection

If historical measures are not comparable:

Say so.

51.348No Reconstructed Crime Baseline From News Stories

Use professional records.

51.349Year One Safety Objective

Establish the baseline, complete risk reviews and begin limited prevention or Right Responder pilots where justified.

51.350Year Two Safety Objective

Expand only interventions showing:

51.351Year Three Safety Objective

Institutionalize successful prevention and responder models.

51.352Year Four Safety Objective

Publish the four-year safety record without election-year distortion.

51.353Four-Year Core Measures

Strong candidates:

51.354Do Not Predetermine a Crime Target

Crime and harm can be influenced by many factors.

A target such as:

crime down exactly 25%

may create bad incentives.

51.355Directional Goal

Better:

reduce preventable serious harm and repeat demand while maintaining emergency capacity and rights.

51.356Specific Operational Targets

Certain measures may have professional standards.

Use those.

51.357Safety Scorecard Table

A headline table could use:

MeasureBaselineCurrentStandard / DirectionTrendStatusOwner

Possible rows:

51.358Right Responder Table

MeasureBaselineCurrentTrend

Possible:

51.359Fire Table

MeasureBaselineCurrentStandardTrend

51.360Traffic Safety Table

MeasureBaselineCurrentChange

Possible:

51.361Perception Table

Area / QuestionBaselineCurrentResponse CountTrend

51.362Surveillance Table

System TypePurposeReview StatusRetention ReviewedContinue / Modify / Remove

Avoid exposing sensitive exact coverage.

51.363Safety Dividend Table

MeasureCurrentVerified Financial Effect

51.364Traffic Lights

Possible:

Green

Meeting adopted professional standard or improving as intended.

Amber

Material risk or declining performance requiring review.

Red

Significant safety or capacity concern.

Grey

Data insufficient or outside municipal control.

51.365Red Requires Context

A spike in a small category may create a Red status.

Explain:

51.366Green Requires Context

A low call count does not automatically mean:

51.367External Measures

Do not assign Red/Green municipal performance to:

as though Council controls it.

Use contextual status.

51.368Anti-Gaming Rule One

Do not measure safety success by arrests alone.

51.369Anti-Gaming Rule Two

Do not measure safety success by tickets alone.

51.370Anti-Gaming Rule Three

Do not measure safety success by calls for service alone.

51.371Anti-Gaming Rule Four

Do not use one month's crime data to define a multi-year trend.

51.372Anti-Gaming Rule Five

Do not switch between incident counts and population rates depending on which looks better.

51.373Anti-Gaming Rule Six

Do not combine urgent and non-urgent response time into one misleading average.

51.374Anti-Gaming Rule Seven

Do not reduce police activity and call the reduction:

without evidence.

51.375Anti-Gaming Rule Eight

Do not increase police activity and call the increase:

without evidence.

51.376Anti-Gaming Rule Nine

Do not classify police time released as financial saving while payroll remains unchanged.

51.377Anti-Gaming Rule Ten

Do not manufacture a Safety Dividend by leaving necessary positions vacant.

51.378Anti-Gaming Rule Eleven

Do not manufacture a Safety Dividend through layoffs before demand reduction is proven.

51.379Anti-Gaming Rule Twelve

Do not ignore the cost of the alternative-response program.

51.380Anti-Gaming Rule Thirteen

Do not classify a referral as successful connection automatically.

51.381Anti-Gaming Rule Fourteen

Do not call fewer visible vulnerable people:

if people were simply displaced.

51.382Anti-Gaming Rule Fifteen

Do not call camera installation a safety improvement merely because equipment was purchased.

51.383Anti-Gaming Rule Sixteen

Do not count training hours as safety outcomes.

51.384Anti-Gaming Rule Seventeen

Do not count fire inspections as fires prevented without evidence.

51.385Anti-Gaming Rule Eighteen

Do not count speed tickets as collision reduction.

51.386Anti-Gaming Rule Nineteen

Do not call resident fear:

51.387Anti-Gaming Rule Twenty

Do not call lower fear:

51.388Anti-Gaming Rule Twenty-One

Do not publish vulnerable-person maps for public accountability.

51.389Anti-Gaming Rule Twenty-Two

Do not use safety systems to create political intelligence.

51.390Anti-Gaming Rule Twenty-Three

Do not change safety survey questions immediately before an election to create a favourable result.

51.391Anti-Gaming Rule Twenty-Four

Do not delay unfavourable safety data until after election day.

51.392Anti-Gaming Rule Twenty-Five

Do not accelerate favourable data for campaign use.

51.393Election-Year Integrity

Year Four must preserve:

51.394No Crime Campaign From City Channels

Official municipal communication should not say:

Vote for continuity because crime fell.

Campaigns can debate the record separately.

51.395No Candidate Attack From City Channels

Likewise.

51.396Police Neutrality

Official policing communications should remain professionally neutral.

51.397Fire Neutrality

Same.

51.398Incident Timing

Do not time routine public release for political benefit.

51.399Major Incident During Election

Normal emergency communication continues.

Campaign implications are irrelevant.

51.400Final Four-Year Safety Audit

At term end publish:

Serious-harm trend

Calls for service

Priority response performance

Repeat demand

Proactive capacity

Right Responder result

Fire incidents

Fire prevention

Traffic safety

High-risk locations corrected

Public-space safety

Safety perception

Surveillance review

Privacy impact

Emergency readiness

Safety Dividend

Unresolved risks

51.401Name the Biggest Safety Improvement

Use evidence.

51.402Name the Biggest Safety Failure

Use evidence.

51.403Name the Biggest Repeat-Demand Problem

At aggregate level.

51.404Name the Most Successful Right Responder Outcome

If one exists.

51.405Name a Right Responder Idea That Did Not Work

If applicable.

51.406Name the Biggest Fire-Prevention Improvement

Use actual evidence.

51.407Name the Biggest Traffic-Safety Improvement

Show before and after.

51.408Name the Most Persistent High-Risk Location

At an appropriate public level.

51.409Name the Largest Unresolved Safety Infrastructure Risk

Put it into the handoff.

51.410Name the Safety Perception Gap

Where did:

differ most?

51.411Name the Surveillance Tool Removed or Reduced

If one no longer had sufficient justification.

That can be success.

51.412Name the Verified Safety Dividend

If it is:

$0

publish:

$0.

51.413Name the Capacity Dividend

If time was successfully redirected.

51.414Name the Biggest Emergency-Preparedness Lesson

Use the exercise record.

51.415Serious Harm Test

Ask:

Did preventable serious harm decline where the City and its partners had realistic influence?

51.416Response Test

Ask:

Did urgent calls receive appropriate professional response?

51.417Capacity Test

Ask:

Did responders retain enough capacity for their core duties?

51.418Right Responder Test

Ask:

Did the right professional reach more of the right calls safely?

51.419Repeat Demand Test

Ask:

Did recurring problems consume less emergency capacity because root causes were addressed?

51.420Police Test

Ask:

Did police remain focused on policing while preserving professional independence?

51.421Fire Test

Ask:

Did fire prevention and emergency readiness remain strong?

51.422Traffic Test

Ask:

Did serious road harm decline at locations where interventions were made?

51.423Public-Space Test

Ask:

Could residents use public spaces with greater confidence without turning those spaces into surveillance zones?

51.424Rights Test

Ask:

Did safety policy protect due process, privacy, equal treatment and freedom from unnecessary monitoring?

51.425Behaviour Test

Ask:

Did the City respond to harmful behaviour rather than treating poverty, homelessness, religion or political disagreement as threats?

51.426Financial Test

Ask:

Were claimed public-safety savings real, recurring and independently verified?

51.427Data Test

Ask:

Did public-safety reporting become more accurate without exposing victims or sensitive operational information?

51.428Election Test

Ask:

Would the same safety numbers have been published if they were politically inconvenient?

51.429Institution Test

Ask:

Would the public-safety system operate professionally if a completely different Mayor took office tomorrow?

It must.

51.430What Success Looks Like

Safety success does not mean:

Success means:

51.431What Failure Looks Like

Failure includes:

51.432The Safety Scorecard Commitment

Owen Sound should commit to:

Measure safety through harm, risk, response, prevention and capacity rather than enforcement volume alone.

Separate actual safety indicators from perceived safety.

Treat both as important without pretending they are the same thing.

Use multi-year trends for volatile safety data.

Do not cherry-pick individual months or offence categories.

Show counts and population-adjusted rates consistently where both are appropriate.

Distinguish calls for service from confirmed incidents.

Do not interpret more calls automatically as less safety.

Do not interpret fewer calls automatically as more safety.

Separate urgent and non-urgent response performance.

Do not publish one blended response-time number that hides priority differences.

Use response time as one safety measure rather than the entire measure.

Treat prevention as seriously as response.

Measure police workload rather than assuming staffing needs from population alone.

Never predetermine a police staffing cut to manufacture savings.

Never assume a staffing increase is automatically the answer without workload evidence.

Use priority demand, investigations, proactive capacity, overtime and vacancies in staffing analysis.

Respect professional policing governance and operational independence.

Never allow the Mayor or Council to direct individual investigations, arrests or enforcement decisions.

Keep policing politically neutral.

Measure proactive capacity without turning it into ticket quotas.

Treat arrests, charges and tickets as activity measures rather than automatic success measures.

Protect victims in public reporting.

Measure repeat demand and recurring locations where that improves problem solving.

Never create public lists of repeat vulnerable individuals.

Use root-cause analysis without excusing harmful behaviour.

Begin Right Responder programs with the question of safety and effectiveness rather than budget reduction.

Define eligible alternative-response calls professionally.

Do not send non-police responders into inappropriate dangerous situations merely to save money.

Require alternative responders to have appropriate training, supervision, protocols and insurance.

Measure responder safety.

Define when police backup is required.

Count diversions honestly rather than classifying every referral as a police call avoided.

Measure actual police capacity released where possible.

Separate capacity dividend from financial dividend.

Never call released officer time a cash saving while expenditure remains unchanged.

Track repeat demand after alternative response.

Do not create intrusive follow-up surveillance simply to prove a referral worked.

Stop or redesign alternative-response pilots that fail safety or effectiveness tests.

Scale only after evidence supports expansion.

Measure fire safety through both emergency response and prevention.

Track serious fire outcomes separately from routine incident counts.

Use applicable professional fire-response standards rather than political targets.

Base fire staffing and facility decisions on professional risk analysis.

Track required prevention inspections and overdue work where appropriate.

Do not claim inspections automatically equal fires prevented.

Coordinate vacant-building, property-standard and fire risks.

Preserve emergency access in downtown street and event design.

Measure traffic safety through collisions, serious injuries and fatalities rather than tickets alone.

Track pedestrian and cyclist serious harm where appropriate.

Use repeat collision locations to guide engineering analysis.

Protect victims when mapping traffic incidents.

Use measured speeds rather than complaints alone.

Recognize street design and enforcement as complementary tools.

Evaluate major traffic interventions using before-and-after evidence.

Use several years of data where possible so one unusual year does not create a false success story.

Do not require a particular traffic-safety brand or slogan in order to pursue measurable harm reduction.

Keep by-law ticket counts separate from public-safety outcomes.

Recognize voluntary compliance as a legitimate enforcement result where appropriate.

Enforce similar circumstances consistently regardless of politics.

Prevent anonymous reporting systems from becoming tools for harassment.

Keep public-space safety focused on behaviour, risk and physical conditions rather than status.

Never count removal of vulnerable people from view as a safety outcome.

Measure safety perception during both daytime and evening using stable questions.

Publish survey sample size and limitations.

Do not label neighbourhoods unsafe based on small or incomplete samples.

Coordinate housing and homelessness safety work with Grey County and appropriate community partners.

Do not build a duplicate City social-service bureaucracy solely to demonstrate activity.

Protect medical and mental-health privacy.

Do not create stigmatizing categories such as "mental health crime."

Respond to specific harmful behaviour rather than identity or housing status.

Use community organizations where they add real capacity while maintaining equal public service regardless of faith or politics.

Keep volunteers in safe observation, preparedness and support roles rather than enforcement roles.

Tell volunteers to report rather than confront.

Never use Civic Corps youth as enforcement personnel.

Include scams, falls, winter access and emergency information in the broader concept of safety.

Verify emergency-calling capabilities before making claims about reused phones or connectivity programs.

Include emergency preparedness, communications resilience and exercises in the Safety Scorecard.

Measure whether exercise findings were corrected rather than simply counting exercises.

Maintain emergency information through more than social-media channels.

Do not build unofficial emergency alert systems that compete with professional emergency communication.

Cross-reference infrastructure failures that create public-safety risk.

Maintain appropriate river, harbour and outdoor safety information within actual municipal responsibility.

Track small physical safety corrections such as crossings, lighting and sidewalk hazards.

Distinguish temporary mitigation from permanent correction.

Show high-risk unfunded safety infrastructure needs.

Maintain an inventory of City-operated surveillance systems at an appropriate governance level.

Give every surveillance system a specific purpose and review date.

Use purpose-based retention rather than keeping footage indefinitely.

Control and audit access where appropriate.

Do not use facial recognition by default.

Require a separate high-threshold public and legal process before any biometric surveillance proposal.

Do not allow biometric capability to arrive quietly through software upgrades.

Treat automated behavioural scoring and persistent person tracking with the same caution.

Never treat an AI safety flag as proof of wrongdoing.

Require authorized human review for high-impact decisions.

Review high-impact AI systems for accuracy and false positives.

Do not allow vendor secrecy to prevent meaningful public accountability.

Maintain exit and portability for safety technology.

Never buy surveillance merely because outside funding is available.

Track privacy incidents involving safety technology at an appropriate level.

Measure camera effectiveness against the purpose used to justify it.

Never use camera count as a safety-performance measure.

Treat removal of unnecessary surveillance as a legitimate improvement.

Share safety information across organizations only for lawful and necessary purposes.

Never create a universal municipal resident risk score, social credit score or political risk score.

Treat safety improvement as the first condition of any Safety Dividend.

Treat capacity improvement as distinct from financial savings.

Allow the verified Safety Dividend to be zero.

Require durable demand reduction before claiming recurring savings.

Require service and responder safety to remain adequate.

Require Finance verification before any financial Safety Dividend is announced.

Do not count positions that remain funded as financial savings.

Do not count necessary vacancies as efficiency.

Do not create layoffs simply to manufacture a campaign promise.

Subtract the ongoing cost of alternative response before calculating net savings.

Separate recurring savings, one-time savings and avoided costs.

Do not treat temporary grant funding as permanent financial savings.

Publish capacity improvements even where no financial dividend exists.

Never monetize every released responder hour as if it were cash.

Track major public-safety costs without assuming higher or lower expenditure alone proves success.

Interpret overtime together with staffing, events and major incidents.

Distinguish authorized staffing from filled positions.

Protect individual employee health and leave information.

Keep public-safety equipment, facilities, communications and digital systems ready.

Maintain fallback procedures for power, telecom and digital failures.

Test emergency coordination and implement lessons.

Plan major event safety proportionately.

Do not weaken safety requirements to increase event capacity.

Avoid security theatre that looks strong without reducing meaningful risk.

Communicate confirmed facts during major incidents and say when information is still unknown.

Correct material rumours without amplifying every rumour.

Do not convert emergency response into campaign content.

Publish appropriate after-action lessons after major incidents.

Give residents clear complaint and oversight routes without creating a Mayor's personal complaint court.

Use safety surveys that measure resident experience rather than political support.

Maintain consistent survey wording over time.

Protect small geographic samples from stigmatizing disclosure.

Give every safety metric a professional data owner.

Do not allow the Mayor to certify or rewrite operational safety statistics.

Use real-time public safety data only where the privacy, accuracy and operational risks justify it.

Protect victims of domestic violence, youth and health-related incidents from identifiable reporting.

Use aggregate Open Data where accountability can be improved safely.

Maintain lawful data-retention limits.

Use Year One to establish the safety baseline and test limited improvements.

Use Year Two to scale only what proves safe and effective.

Use Year Three to institutionalize successful prevention and responder models.

Use Year Four to publish the full safety record using the same definitions used before the election year.

Never cherry-pick crime statistics for incumbent benefit.

Never delay bad safety data until after an election.

Never accelerate favourable safety data for campaign use.

Publish the full Four-Year Safety Audit.

Name the biggest safety improvement.

Name the biggest safety failure.

Name the largest repeat-demand problem.

Name the Right Responder result, including failed approaches.

Name the biggest fire-prevention improvement.

Name the biggest traffic-safety improvement.

Name the most serious unresolved safety infrastructure risk.

Name where recorded safety and perceived safety differed most.

Name surveillance tools that were removed or reduced because they were no longer justified.

Publish the Safety Dividend honestly, including zero.

Publish any capacity dividend separately.

Judge the final safety record by whether serious harm, preventable risk and repeat demand improved without weakening emergency capacity, professional independence or civil rights.

A strong Safety Scorecard should allow Owen Sound to have a more mature conversation.

Instead of:

Crime is out of control.

or:

Everything is fine.

Residents should be able to see:

Here is what happened.

Here is how serious it was.

Here is the multi-year trend.

Here is what keeps repeating.

Here is how quickly urgent calls were handled.

Here is how much emergency capacity exists.

Here is where another responder worked better.

Here is where another responder did not work.

Here are the fire risks.

Here are the dangerous road locations.

Here is what residents say they experience.

Here is what the professional incident data shows.

Here is the surveillance we use.

Here is why.

Here is what we removed.

Here is the actual financial saving.

If there was no financial saving, here is the capacity improvement instead.

Safety policy should be strong enough to protect people without needing to exaggerate danger.

It should be disciplined enough to use police for police work without pretending every problem is a police problem.

It should be compassionate enough to use qualified alternative responders where they genuinely work.

It should be cautious enough to stop those alternatives when they do not.

It should be technologically capable without turning residents into subjects of permanent monitoring.

And it should be financially honest enough to say:

The program made us safer, but it did not save money.

if that is what the evidence shows.

That is public-safety accountability.

Protect people. Reduce preventable harm. Preserve emergency capacity. Use the right responder. Fix repeat risks. Measure perception and reality separately. Protect civil rights. Count real savings only when they are real.

← Chapter 50: Business: The Public Business ScorecardChapter 52: Recreation: The Public Recreation Scorecard →