A facilities lead usually meets the maintenance-versus-preventive-maintenance decision after something has already gone wrong. A chiller fails overnight, a server room loses temperature control, and the first morning meeting becomes a scramble over occupants, vendors, parts, and budget. Or a polished lobby floor causes a slip after an inspection was skipped, turning a small housekeeping omission into a safety review, an incident report, and a backlog problem.
The choice isn't philosophical. It affects uptime, occupied space, liability exposure, technician workload, and the next quarter's maintenance plan. Preventive maintenance is often the right foundation, but fixed-interval work can waste labor on healthy, low-consequence assets. The practical answer is a mixed strategy, using reactive, preventive, condition-based, and predictive work according to the asset's actual risk.
The Moment a Reactive Call Becomes a Preventive Question
At 2 a.m., a chiller alarm wakes the on-call technician. By arrival, the server room temperature is rising, the emergency vendor is checking availability, and operations wants an outage estimate. The immediate job is restoration, not a debate about maintenance theory. The critical decision comes after the incident: should the next failure still be accepted as a surprise?
A smaller event can expose the same weakness. A skipped lobby inspection leaves moisture on a polished surface, and someone slips the following morning. Even with a limited repair bill, the facility faces injury, documentation, staff time, and questions about whether the hazard should have been identified earlier. OSHA guidance calls for floors to be kept clean and dry as far as feasible, with walking surfaces free of hazards such as spills and loose objects (OSHA walking-working-surface guidance).
The operational cost of waiting
Reactive maintenance starts after a failure, defect, or hazard has appeared. That choice fits a cheap, replaceable item with little consequence if it stops. It is a poor fit when failure interrupts occupied operations, creates a safety concern, damages connected systems, or demands specialist labor at short notice.
Preventive work puts the technician in control of the timing. Inspection, cleaning, lubrication, testing, adjustment, or replacement happens while the asset still operates. The facility selects the work window instead of letting an alarm, complaint, or incident select it.
Practical rule: If failure would cancel occupancy, break a safety control, damage another system, or require emergency labor, place the asset on a planned strategy.
Industry maintenance research commonly reports lower costs and downtime for preventive programs, including the effects of emergency labor, expedited parts, production loss, and collateral damage. UpKeep's summary of Department of Energy source material describes preventive maintenance as typically costing 3 to 5 times less than reactive maintenance, with 12% to 18% lower maintenance costs and 35% to 45% less downtime cited for preventive approaches (UpKeep's maintenance statistics reference).
Use those figures as a default in risk-sensitive operations, not as permission to schedule every asset at the same interval. Fixed-interval PM is the safest starting point for high-consequence equipment. For cheap, accessible, low-risk assets, reactive work may waste less. Where inspections reveal changing conditions, condition-based work can beat both a rigid calendar and run-to-failure. The next step is to define those terms precisely.
Defining Maintenance and Preventive Maintenance Clearly
“Maintenance” is the umbrella. It includes every activity used to preserve, restore, inspect, clean, test, or improve an asset. Reactive maintenance, also called corrective or run-to-failure maintenance, starts after a fault, alarm, complaint, or visible degradation appears. The workflow is simple: dispatch, diagnose, repair, test, and restore.
Preventive maintenance, or PM, is planned work performed at predetermined time or usage intervals while the asset is still functioning. A technician may inspect an air-handling unit, clean a coil, check a belt, test an emergency light, service a backflow preventer, or replace a filter before failure. The purpose is to reduce the probability or consequence of failure, not to make every asset receive the same treatment.
A useful primer on the wider subject is this facility maintenance overview. For teams working across products and equipment lifecycles, održavanje i popravak proizvoda also offers relevant context on maintenance and product repair.
PM is only one part of planned maintenance
Planned maintenance includes work prepared in advance, whether the trigger comes from a calendar, an inspection result, a condition reading, or a known corrective task. PM is the time-based or usage-based subset. That distinction matters because teams often label every planned ticket “preventive,” even when a technician acted on a vibration reading or thermal scan.
Condition-based maintenance, or CBM, uses a measured condition to decide whether work is needed. A technician might take a vibration reading, inspect a belt, use thermography on an electrical panel, or send an oil sample for analysis. The inspection may happen on a schedule, but the repair trigger comes from the asset's condition.
Predictive maintenance, or PdM, extends that idea with monitored indicators and, in suitable programs, continuous data analysis. Vibration, thermography, temperature, pressure, and oil analysis can reveal degradation without forcing a replacement at every calendar interval. Keep the work-order categories honest. If the trigger is a sensor threshold, record it as condition-based or predictive work, not fixed-interval PM.
Comparing Objectives, Workflows, and KPIs
Reactive maintenance optimizes short-term restoration. The technician responds to an alarm or complaint, finds the fault, and returns the asset to service. The approach can minimize immediate scheduling effort, but it leaves the facility exposed to whatever timing, parts availability, and collateral damage the failure creates.
Preventive maintenance optimizes failure avoidance, predictable access, lifecycle care, and compliance execution. The trigger is a calendar or usage threshold, so the planner can stage parts, permits, access equipment, occupant notices, and vendor support before the work begins.
| Dimension | Reactive (Corrective) Maintenance | Preventive Maintenance |
|---|---|---|
| Objective | Restore service after a fault | Reduce failure likelihood and plan care |
| Trigger | Alarm, complaint, defect, or failure | Time, usage, inspection interval, or policy |
| Planning horizon | Same day or immediate response | Scheduled window with prepared labor and parts |
| Typical technician time | Diagnosis and restoration can expand unpredictably | Defined task time, with exceptions for discovered defects |
| Primary KPI | MTBF and MTTR | PM compliance and planned maintenance percentage |
| Failure mode | Disruption arrives before the work is ready | Over-maintenance or missed degradation between intervals |
What the numbers actually tell you
MTBF, mean time between failures, helps show whether failures are occurring less often. MTTR, mean time to repair, shows how quickly the team restores service once a failure occurs. Those measures belong naturally to reactive work, although PM should influence MTBF and reduce the severity of events that drive MTTR.
For a PM program, track PM compliance rate and planned maintenance percentage. Compliance tells you whether scheduled tasks are completed when due. Planned maintenance percentage tells you how much of the maintenance workload was prepared rather than generated by emergencies. Facilities teams also watch downtime cost, warranty spend, backlog age, and emergency labor as shared outcomes.
Preventive maintenance KPI examples can help teams standardize those definitions before comparing buildings or vendors. A commonly used operating target is to have planned work exceed 85% of maintenance activity, while MTBF rises and downtime cost falls, as described in this preventive maintenance KPI guide. Don't treat that target as a trophy. If technicians complete 90% of low-value PM tickets while a critical chiller fails repeatedly, the dashboard is hiding the core issue.
Pros and Cons of Each Approach in Practice
Reactive maintenance earns its place on the schedule when the asset is cheap, redundant, easy to replace, or already near the end of its useful life. You avoid scheduling overhead and don't spend labor servicing equipment that may operate without trouble. A corridor light fixture often belongs here, provided the failure doesn't create a safety issue and replacement stock is available.
The downside is concentrated risk. Emergency work can bring premium parts, overtime, expedited freight, collateral damage, and rushed decisions. When technicians work around occupants or hazards without preparation, the safety exposure rises. OSHA guidance specifically emphasizes clear walkways, prompt spill cleanup, slip-resistant surfaces in high-risk areas, and control of moisture and grease (OSHA slip, trip, and fall prevention material).
Preventive maintenance gives the team a controlled work window, a stable parts pipeline, and a better chance to preserve warranties and catch defects before they interrupt operations. It also belongs in housekeeping. A rec center crew using gym equipment wipes after busy periods, for example, is performing planned care that protects equipment surfaces and supports hygiene rather than waiting for visible buildup or complaints. For a facility choosing supplies, commercial disinfecting wipes can fit a documented cleaning station with a dispenser and replenishment process.
Where PM goes wrong
Fixed-interval PM isn't automatically efficient. It becomes wasteful when technicians replace healthy parts without evidence of wear, repeat identical tasks that don't affect failure risk, or service assets whose failure has minimal consequence. It can also create “infant-mortality” waste when unnecessary intervention introduces a new defect.
Calendar work can miss emerging failure modes between inspections. A vibration or thermal reading may reveal a developing issue earlier than a routine visual check. Repeated, identical tasks can also wear down technician engagement, especially when planners never review whether the interval matches actual asset behavior.
The verdict is straightforward. Reactive maintenance is appropriate for selected low-consequence assets. PM is the safest default for predictable wear and compliance-sensitive tasks. Condition-based or predictive work earns its cost on assets where fixed intervals miss the failure pattern or where downtime consequences justify better visibility.
Cost, Downtime, and Risk Trade-offs
A rec center crew following a scheduled wipe-down protocol after busy periods shows the basic trade-off clearly. Planned labor and supplies cost something, but the schedule prevents a small issue from becoming an urgent service call. Reactive work can look cheaper because no labor or parts were arranged in advance. Add emergency labor, expedited shipping, lost output, tenant disruption, secondary damage, and supervisor time, and that comparison changes.
Use the whole event cost, not just the repair invoice. Fixed-interval PM is the safest default when wear is predictable, failure consequences are high, or compliance requires documented checks. It becomes wasteful when staff service healthy assets without evidence of deterioration, repeat tasks that do not reduce failure risk, or interrupt operations for low-consequence equipment. Condition-based monitoring is the better choice when readings can show degradation earlier than a calendar task. Run-to-fail remains sensible for selected assets that are inexpensive, accessible, and unlikely to create safety or service problems.
| Metric | Reactive Maintenance | Preventive Maintenance |
|---|---|---|
| Cost pattern | Irregular, with emergency premiums and collateral costs | Smaller planned draws for labor, parts, and access |
| Downtime timing | Unplanned, often during occupancy or production | Scheduled around operating constraints |
| Parts strategy | Ordered after diagnosis, sometimes expedited | Staged or forecast from the PM plan |
| Safety exposure | Higher when the fault creates an urgent work environment | Reduced through inspections and planned controls |
| Budget effect | Spikes that disrupt forecasts | More predictable monthly and quarterly allocation |
| Main risk | Failure, secondary damage, and service interruption | Over-maintenance or missed failures between intervals |
Translating the loss picture
Manufacturing asset-management research from the National Institute of Standards and Technology reported $119.1 billion in losses in 2016, including $18.1 billion from downtime and $100.2 billion from lost sales caused by delays and defects (NIST manufacturing asset management research). Those figures do not predict the return from a particular building's PM program. They establish why maintenance belongs in revenue protection and operational planning, not only in the repair budget.
For the next quarter, rank assets by the consequences of failure. Put scheduled work first for equipment that can stop occupancy, disrupt service delivery, cause water or electrical damage, or compromise a safety control. Estimate parts, contractor access, permits, cleaning, and temporary space protection before approving the schedule. The goal is not to eliminate every reactive ticket. It is to keep predictable failures from arriving as financial surprises.
Decision Criteria for Choosing the Right Approach
Use three filters for every significant asset: criticality, failure predictability, and consequence cost. Criticality covers safety, regulatory, financial, and operational impact. Predictability asks whether wear follows a recognizable pattern and whether the team can observe degradation. Consequence cost includes repair, collateral damage, downtime, liability, and the effect on occupants.
Apply the filters to real assets
A rooftop HVAC unit serving a server room scores high on criticality and consequence. It may require scheduled inspection and service, and the most important components may justify condition monitoring. Waiting for a failure isn't an acceptable operating policy when the unit supports a space that depends on stable environmental control.
A corridor light fixture is different. If the corridor has adequate lighting redundancy, replacement is quick, and failure doesn't create an unsafe route, run-to-fail is reasonable. Keep replacement units in stock and make the work order easy to create. Don't send a technician on a recurring PM route just to confirm that a low-consequence fixture still works.
A fleet of sump pumps in a parking garage sits in the middle. Their failure may not interrupt normal operations immediately, but water accumulation can damage property and create slip hazards. A lightweight PM program, including visual inspection, float testing, discharge checks, and debris removal, is more sensible than either full predictive instrumentation or pure run-to-failure.
Match intensity to asset reality
Use reactive work for low-criticality, low-consequence assets that are cheap and fast to replace. Use fixed-interval PM for predictable wear, required inspections, routine cleaning, and assets where a missed failure would create an avoidable operational problem. Use condition-based monitoring when sampled readings can improve decisions without the cost of continuous sensors. Use predictive monitoring when the asset is critical, failure patterns are difficult to predict, and the consequence cost supports the data infrastructure.
One facility can, and should, use all four approaches simultaneously. A single policy across the whole asset register is a sign that the team hasn't completed the criticality work.
Sample PM Schedule and Facility Operations Checklist
A workable schedule starts with asset risk, not a blank calendar. Put high-consequence HVAC, electrical, plumbing, life-safety, and water-management assets on planned routes. Keep housekeeping and hygiene work separate, with defined standards, products, contact times, and verification fields. A generic “clean facility” ticket hides missed steps and makes completion hard to audit.
A practical weekly cadence can stay simple. Monday covers inspections and hazard discovery. Midweek handles filter service, lubrication, and small planned corrections. Friday is for reviewing logs, closing incomplete work, and assigning discovered defects a priority code in the backlog. Adjust the cadence when asset history or operating conditions justify it. Fixed intervals are a safe default for predictable wear and required inspections, but they waste labor when failure patterns are weak and condition checks can guide the decision.
| Asset Class | Daily | Weekly | Monthly | Quarterly | Annual |
|---|---|---|---|---|---|
| HVAC | Check alarms and unusual noise | Inspect access areas and visible belts | Review filters and drain pans | Service filters, coils, and belts as specified | Test controls, alarms, and seasonal readiness |
| Plumbing | Check leaks, temperature complaints, and wet areas | Inspect valves, drains, and pump rooms | Review fixtures and shutoff access | Test backflow equipment where required | Review isolation plans and major components |
| Electrical | Walk panels for heat, odor, or damage | Check clearances and housekeeping | Review lighting defects and emergency signage | Test selected emergency lighting functions | Coordinate qualified inspection and testing |
| Housekeeping | Remove spills, obstructions, and waste | Inspect entrances, stairs, kitchens, and locker rooms | Review chemical stock and equipment condition | Audit cleaning standards and training records | Review contracts, products, and program performance |
| Life safety | Confirm access to emergency equipment | Inspect visible damage and signage | Review open deficiencies | Test scheduled systems under applicable procedures | Coordinate formal inspections and documentation |
The under-ten-minute walk-down
Crew leads can record one pass per zone directly in the CMMS:
- Visual cues: Check for spills, loose flooring, blocked exits, damaged guards, leaks, corrosion, and missing signage. Create a corrective work order when a condition exceeds the site standard.
- Sensory checks: Note unusual heat, odor, vibration, noise, or airflow. Escalate anything outside the normal baseline instead of relying on memory.
- Housekeeping controls: Keep floors dry where feasible, clear aisles and stairs, and maintain drainage or dry standing surfaces in wet-process areas. Moisture control and clear walking surfaces reduce avoidable slip and trip exposure, consistent with OSHA surface and moisture guidance.
- Hygiene controls: Clean hard surfaces before disinfecting. Disinfectants work only when the surface is cleaned first and remains wet for the label's full contact time. The CDC distinguishes cleaning, which removes dirt and germs, from disinfecting, which uses chemicals to kill germs on hard, nonporous surfaces (EPA and CDC disinfecting guidance).
- Action line: Record the asset, condition, immediate control, and follow-up owner. “Spill cleaned, warning sign placed, flooring repair ticket opened” is useful. “Checked area” is not.
For campus recreation centers, include locker rooms, restrooms, benches, drinking fountains, shared mats, and high-touch gym equipment on the same route. Product labels matter more than marketing language. Position dispensers at point of use to support execution, but staff still need training on cleaning first, wet contact time, and disposal. That single placement decision helps a schedule survive contact with a busy facility, while training and verification determine whether the task was done correctly.
Measuring Results and Rolling Out a Preventive Program
A reactive call becomes useful only when it changes the next maintenance decision. Track MTBF, MTTR, planned maintenance percentage, and work-order backlog age from the start. MTBF should improve as recurring failures decline. MTTR should fall when parts, access, instructions, and vendor support are ready. Planned maintenance percentage matters only when the completed work is meaningful, while backlog age exposes a schedule the team cannot realistically deliver.
Published research supports disciplined execution, but it does not guarantee results from an untested schedule. One peer-reviewed study reported 48.5% lower unplanned downtime and 63.2% fewer defects with preventive maintenance. Its comparison also found predictive-heavy operations had 18.5% less downtime and 87.3% fewer defects than preventive-heavy operations (peer-reviewed maintenance study). Use those findings to justify measurement and review, not to promise the same outcome in your facility.
Run a controlled pilot
Choose one critical system and establish a 60-day baseline for all four KPIs. Lock the relevant schedule, then require consistent records for failure modes, parts, labor, and deferrals. Expand to another asset class only after the pilot produces reliable records and technicians can complete the work within the assigned windows.
Keep the rollout practical:
- Overbuilt CMMS: Remove fields nobody uses and workflows that send technicians back to a desk.
- Impossible schedules: A PM plan that exceeds available labor creates deferrals and false compliance.
- Weak failure coding: A reactive ticket marked only “fixed” cannot show which PM task or condition check needs adjustment.
Review results at 30, 60, and 90 days. Compare avoided downtime, emergency labor, backlog health, warranty spend, and planned-work quality with the program's cost. Use this preventive maintenance program guide to support rollout planning, then reconcile it with your CMMS capabilities, manufacturer instructions, vendor support, and compliance requirements.
Cleaning and sanitizing belong in the same operating system as mechanical work. Train janitorial and student staff to follow defined frequencies for gym equipment, locker rooms, restrooms, and shared surfaces. Use scheduled disinfection protocols, select EPA-registered disinfectants according to surface compatibility and contact time, and verify that treated surfaces remain visibly wet for the required period. Place supplies at the point of use, but audit execution rather than assuming availability equals completion.
Start with the asset register this week. Mark each major asset by criticality, predictability, and consequence cost. Assign reactive, fixed-interval PM, condition-based, or predictive work accordingly. Build one realistic 90-day pilot around the highest-consequence system, add its walk-down checklist to the CMMS, and train everyone responsible for inspection, cleaning, and escalation before the first scheduled task.
Leave a Reply