Most city maintenance teams already know that planned work costs less than emergency repair, yet the day still gets eaten by service calls, breakdowns, and urgent fixes. Moving from reactive to preventive maintenance is less about willpower and more about asset data, scheduling, and priorities that survive a busy week. This roadmap compares both approaches across streets, water, wastewater, fleet, and facilities, then lays out a 90-day plan with KPIs. Along the way you will see where Oxmaint maintenance management software fits into the shift.
Reactive vs Preventive Maintenance: A City Roadmap
Cities that repair assets only after they fail pay for it in overtime, service gaps, and lost public trust. This guide shows how public works teams move to planned maintenance in 90 days.
Reactive lane
- Asset fails in service
- Resident or crew calls it in
- Emergency dispatch
- Repair with whatever parts exist
- Paperwork filled in later
Planned lane
- Scheduled inspection runs
- Small defect is found early
- Work order is planned
- Repair with parts staged
- History recorded at closeout
What reactive maintenance really costs a city
The repair invoice is only the visible part. Reactive work spreads its cost across budgets, schedules, and public confidence.
One failure, two timelines
An illustrative scenario, not a case study: a sewage lift station pump develops a worn bearing.
Run to failure
- Week 0: Vibration and heat rise, but nobody is looking.
- Week 3: The pump seizes on a weekend night and the wet well rises.
- Same night: Staff are called in, a bypass is arranged, and parts are sourced urgently.
- Next week: Repair, cleanup, and a regulatory conversation about the overflow risk.
Preventive and condition-aware
- Week 0: A scheduled round records unusual vibration and temperature.
- Week 1: A work order is raised and the bearing is reserved from stores.
- Week 2: The standby pump carries the load while the duty pump is repaired in daylight.
- Closeout: Readings and parts used are logged against the asset.
Why city teams stay reactive
Reactive habits are rarely a choice. They grow out of structural pressures, and a roadmap has to deal with each one.
- No reliable asset listYou cannot schedule care for assets you have not recorded. Spreadsheets and tribal knowledge leave gaps.
- Capital over maintenanceNew projects attract funding and ribbon cuttings, while upkeep of existing assets competes quietly for what remains.
- Paper and disconnected systemsWork orders on clipboards and separate tools for fleet, water, and facilities hide the true backlog.
- Staffing gaps and retirementsWhen experienced technicians leave, the unwritten schedule in their heads leaves with them.
- Urgent beats importantA burst main or a downed signal always outranks a lubrication route, so preventive work slides.
- PM that nobody trustsGeneric schedules with no link to condition or failure history get skipped because they feel like paperwork.
Reactive, preventive, and condition-based compared
Each strategy has a place. The question is which one fits each asset class and risk level.
| Factor | Reactive | Preventive | Condition-based |
|---|---|---|---|
| Trigger | Failure or complaint | Calendar, runtime, or usage interval | Measured condition or inspection finding |
| Planning | Little or none | Scheduled and resourced ahead of time | Planned once a threshold is crossed |
| Cost pattern | Spiky and hard to forecast | Steady and predictable | Targeted, with less unnecessary work |
| Service disruption | Often unplanned and public | Scheduled around demand | Usually scheduled before functional failure |
| Data needed | Basic request log | Asset list and task history | Readings, inspections, and failure history |
| Best suited to | Low-consequence, easily replaced items | Assets with age-related wear and regulated tasks | Critical or costly assets where condition can be measured |
| Main risk | Safety, outages, and compounding damage | Over-servicing if intervals are never reviewed | Needs reliable measurement and follow-through |
Ready to plan the work instead of chasing it?
See how a single system for assets, work orders, and schedules can turn urgent calls into planned jobs for your public works crews.
You need a mix, not a slogan
The goal is not zero reactive work. It is to make reactive work a deliberate choice rather than the default.
When run to failure is reasonable
- The asset is inexpensive and quick to replace.
- Failure creates no safety or regulatory consequence.
- A spare is in stock or the service has a redundant path.
- Inspection would cost more than the repair it avoids.
Decide which assets move to preventive first
Limited crews cannot do everything at once. Score each asset class by consequence of failure and likelihood of failure, then sequence the work.
Protect
High consequence, lower likelihood. Planned inspections, spares, and tested standby equipment.Fix first
High consequence, high likelihood. Preventive plans plus condition checks, starting now.Run and watch
Low consequence, low likelihood. Light-touch inspections, repair when needed.Streamline
Low consequence, high likelihood. Simple routine PM or planned replacement cycles.The overdue PM spiral
Many cities already have preventive schedules. The trouble is that skipped tasks feed the very emergencies that cause more skipping.
- PM task is skippedAn urgent call pulls the crew away.
- Wear goes unnoticedSmall defects grow without a record.
- Failure arrivesThe asset breaks at the worst time.
- Emergency work expandsCrews now have even less time.
- More PM is deferredThe backlog grows and the loop repeats.
Ways to break the loop
- Protect a fixed share of weekly labor hours for planned work.
- Track overdue PM by asset criticality, not as one flat number.
- Retire or rewrite tasks that crews consistently skip for good reason.
- Reschedule missed PM automatically so it stays visible.
A 90-day roadmap from reactive to preventive
Start narrow, prove the value, then expand. Trying to cover every asset in the first month is the quickest way to stall.
Build the foundation
- Pick two or three asset classes, such as lift stations, fleet, or key facilities.
- Load a basic asset register with location, type, and owner.
- Score criticality for each asset class.
- Move all new requests into one work order queue.
Schedule and standardize
- Draft PM tasks from manufacturer guidance and technician experience.
- Build inspection checklists for mobile use in the field.
- Stage common spare parts for the highest-risk assets.
- Agree what counts as on time, late, and emergency work.
Measure and expand
- Review PM compliance and the reactive-to-planned ratio.
- Adjust intervals using failure and inspection history.
- Share early results with supervisors and leadership.
- Choose the next asset classes to onboard.
Starter preventive tasks by city asset group
These are examples to adapt. Always follow manufacturer instructions and applicable regulatory requirements for your jurisdiction.
| Asset group | Example preventive or inspection tasks | Typical trigger |
|---|---|---|
| Streets and signage | Pavement condition surveys, sign retroreflectivity checks, crack sealing | Calendar and condition |
| Water distribution | Hydrant inspection and flushing, valve exercising, meter checks | Calendar |
| Wastewater lift stations | Pump rounds, vibration and temperature readings, wet well cleaning, standby tests | Runtime and condition |
| Fleet | Oil and filter service, brake inspection, tire checks, pre-trip defect reports | Mileage or engine hours |
| Facilities | HVAC filter changes, roof inspections, generator exercise, fire system checks | Calendar |
| Parks and playgrounds | Equipment safety inspections, surfacing checks, irrigation tests | Calendar and season |
| Stormwater | Inlet and catch basin cleaning, outfall inspection, pond maintenance | Calendar and storm events |
KPIs that show the shift is working
Track a short set of measures monthly and review them with the people who do the work.
PM compliance
PM completed on time ÷ PM scheduledPlanned-to-reactive ratio
Planned work hours ÷ reactive work hoursBacklog age
Average days open for non-emergency work ordersRepeat failure rate
Assets with repeat corrective work in a period ÷ assets with corrective workEmergency overtime share
Overtime hours on emergency jobs ÷ total overtime hoursMean time to repair
Total repair time ÷ number of repairsHow Oxmaint supports the transition
Oxmaint is maintenance management software for assets, work orders, and schedules. It does not replace judgment, but it keeps the plan visible.
Without a shared system
- Asset details live in spreadsheets and memory
- PM reminders depend on one supervisor
- Field findings are copied from paper days later
- Backlog is estimated, not measured
- Parts shortages surface during the repair
With Oxmaint
- Asset records hold history, location, and documents
- Preventive schedules generate work orders automatically
- Mobile inspections capture readings and photos on site
- Dashboards show compliance, backlog, and cost
- Inventory tracking supports staged spare parts
Making the case to council and finance
Leaders respond to clear numbers and a small first step, not a request to overhaul everything.
- Show current reactive spendingPull overtime, emergency parts, and rental costs for the last year.
- Name the risky assetsUse criticality scores to show where failure would hurt most.
- Propose a bounded pilotLimit scope to a few asset classes with defined KPIs.
- Report on a fixed rhythmShare compliance and backlog trends every month.
Reactive vs preventive maintenance FAQs
Is preventive maintenance always cheaper than reactive?
Not for every asset. Low-consequence, cheap items can run to failure, while critical assets usually justify planned care.
How long does it take a city to shift?
A pilot can show early results in 90 days. Full coverage usually takes longer. Book a demo to scope your first phase.
What is a good PM compliance target?
Set it by asset criticality and baseline first. Many teams aim higher for critical and regulated assets.
Do we need sensors for condition-based maintenance?
No. Structured inspections with recorded readings are a practical starting point before adding instrumentation.
Can a CMMS handle several departments?
Yes. Water, fleet, parks, and facilities can share one asset and work order system. Create an account to explore it.
What preventive maintenance looks like in each city department
The principle is the same everywhere, but the tasks differ. Start with the department where failures hurt residents most.
Common objections and honest answers
Every city hears the same reasons for staying reactive. Each has a practical response.
- We do not have timeReactive work is what consumes the time. Protecting a small block of planned hours each week, even a modest one, reduces the emergencies that eat the rest.
- We do not have the dataStart with what you know. A basic register of the most critical assets and a handful of inspection tasks is enough to begin, and data improves with every work order.
- Emergencies always come firstThey will. The aim is to have fewer of them. Define what counts as a true emergency so routine requests do not jump the queue.
- Crews will see it as extra paperworkMobile checklists and short forms keep entry quick. Show crews how the records protect them when a decision is questioned.
- It will not survive the next budget cutTie the program to measured results such as lower overtime and fewer repeat failures, so it is defended with evidence rather than opinion.
- Our assets are too old to botherOlder assets often need inspection most. Preventive work and condition checks help you decide what to renew and when.
Mistakes that stall the transition
Most failed efforts break down in the same few places.
- Launching across every department at once, so no crew gets enough support to change habits.
- Copying generic PM templates without checking them against local conditions and failure history.
- Scheduling work without protecting crew hours, so tasks pile up as overdue within a month.
- Measuring only activity, such as tasks created, rather than outcomes like repeat failures and emergency overtime.
- Skipping parts planning, which turns a planned job into a delayed one.
- Letting leadership see the program only when something goes wrong, instead of sharing a regular, simple report.
Turn your next emergency into a planned work order
Give crews, supervisors, and leadership one record of every asset, inspection, and repair. Start with a small pilot and build from there.
