Corrective Maintenance
Reactive repair after a fault occurs, as distinct from planned or condition-based work.
A high corrective-maintenance ratio is rarely a maintenance-team performance problem. It is usually a maintenance-budget or PPM-schedule-design problem showing up downstream.
Why this service exists
Some corrective work is genuinely unavoidable — no PPM or condition-monitoring regime eliminates all faults — but a disproportionate reliance on corrective maintenance is one of the most reliable diagnostic signals in FM that something upstream (funding, schedule design, condition monitoring) is failing.
What the service covers
- Fault triage and prioritisation.
- Emergency and non-emergency reactive repair.
- Root-cause logging.
Assets and objects
- Cuts across all hard-service asset categories, same as PPM.
Who takes part
- Helpdesk/triage functionRequired
Mandatory as first point of contact.
- TechniciansRequired
Deliver the repair.
- FM operations managerSituational
Tracks backlog and root-cause trends.
What the service needs
- Fault reports (from occupants, from monitoring systems, from routine inspection).
- Asset criticality ratings for prioritisation.
How delivery runs
- 01Triage incoming faults by severity and asset criticality.
- 02Dispatch and execute repair against defined response-time tiers.
- 03Log root cause, not just the symptom fixed.
- 04Feed root-cause data back into PPM schedule review — this feedback loop is the step most often skipped, and its absence is why the same faults recur.
What is delivered
- Completed repairs.
- Fault logs with root-cause classification.
- Response-time performance data.
From output to outcome
Repaired faults with logged root cause.
Restored function after failure.
Explicitly framed as a lagging outcome, since a well-run FM organisation should be reducing reliance on this outcome over time via better PPM and condition-based strategy, not optimising corrective response time as an end in itself.
Where it gets tense
- The same fault recurring repeatedly without the root cause ever being addressed at the PPM-schedule level.
- Corrective maintenance ratio rising over time without anyone flagging it as a strategic signal rather than routine operational noise.
Strategic, tactical, operational
A rising corrective-maintenance ratio should trigger a PPM/budget review, not just more helpdesk capacity.
Response-time tiering by asset criticality, not a flat response time for every fault regardless of consequence.
Genuine root-cause logging takes more technician time than closing a work order with a one-line note — worth resourcing deliberately rather than treating as an optional nicety.
Performance indicators
- Response time by severity tier
Shows service level against risk.
- First-time-fix rate
Efficiency indicator.
- Corrective-vs-planned maintenance ratio
Diagnostic signal for upstream problems.
- Fault recurrence rate
Shows whether root causes are genuinely addressed.
Risks
- For statutory assets, unresolved corrective faults can move a facility out of compliance — the connection to Statutory/Compliance Maintenance should be explicit, not incidental.
Statutory context
Corrective maintenance itself is not statutorily mandated, but unresolved corrective defects on statutory assets can move the organisation directly out of legal compliance.
Sourcing options
- Single service
Embedded within the same contract structure as the underlying asset's PPM coverage.
- In-house
Often combined with in-house breakdown response.
Technology and data
- CMMS-based fault logging and dispatch.
- Increasingly integrated with BMS/IoT alerts that generate corrective work orders automatically from sensor thresholds.
Competencies required
- Fault diagnosis.
- Root-cause analysis discipline.
Common mistakes
- Closing a corrective work order on symptom resolution without root-cause investigation.
- Treating a rising corrective ratio as a workforce capacity problem rather than an upstream strategy problem.