Corrective maintenance — the complete operations guide
Corrective maintenance is every repair performed after a failure is detected. Managed well, it minimises downtime, controls costs, and feeds the preventive intelligence that stops the next failure from happening at all.
Used by manufacturing, healthcare, facilities, and fleet operations teams · No credit card required
What is corrective maintenance?
Corrective maintenance (CM) is maintenance performed on a physical asset after a failure, fault, or performance degradation has been detected — with the goal of restoring the asset to its required operational state. It is defined not by what is done, but by when: corrective maintenance is always a response to a detected condition, never a scheduled prevention.
Every corrective maintenance event begins with a failure signal — an operator reports unusual noise, a monitoring system raises an alert, a PM inspection finds a degraded component, or a machine simply stops working. That signal triggers a work order, a technician dispatch, a repair, and a record. How quickly and systematically an organisation moves through these steps determines the real cost of the failure.
Corrective maintenance cannot be eliminated — even the most mature PM programme cannot prevent every failure. But it can be structured. Organisations that treat CM as a random, ad hoc activity pay emergency labour premiums, suffer extended downtime from disorganised response, and miss the root cause data that would prevent recurrence. Organisations that manage CM through a formal work order system — with priority tiers, SLA deadlines, technician assignment, cost logging, and root cause analysis — convert uncontrolled failure events into operational intelligence.
What structured CM management solves
- Failures handled informally — no record of what failed, why, or what was done
- Extended downtime from disorganised emergency response
- Emergency repair costs 3–5× higher than equivalent planned service
- Recurring failures on the same asset because root cause was never addressed
- No visibility into which assets are consuming disproportionate CM spend
- SLA breaches on critical facilities or service contracts
- Repair-vs-replace decisions made without lifecycle cost data
Glossary
- Corrective Maintenance (CM)
- Maintenance performed after fault detection to restore an asset to operational state. Reactive by definition.
- MTTR
- Mean Time to Repair — average elapsed time from fault detection to full asset restoration. The primary speed metric for CM.
- First-Time Fix Rate
- Percentage of CM events resolved in a single technician visit without return visits. Target: ≥ 85%.
- Emergency Work Order
- Highest-priority CM work order requiring immediate response — typically for safety hazards or production-stopping failures.
- Root Cause Analysis (RCA)
- Post-repair investigation into why the failure occurred, driving PM adjustments or process changes to prevent recurrence.
- PM:CM Ratio
- Ratio of preventive to corrective work orders. Higher ratios indicate a more proactive maintenance culture.
- Deferred CM
- Non-urgent corrective repair that is documented and scheduled for a future maintenance window rather than immediate response.
Four types of corrective maintenance
Not all corrective maintenance is the same. Classifying CM by urgency, intent, and operational impact determines how the work order is prioritised, resourced, and managed.
Immediate Corrective Maintenance
Emergency response requiredThe most urgent CM category — triggered by failures that create immediate safety risk, production stoppage, or critical service outage. The work order is created and dispatched within minutes of detection. A technician is on-site within the SLA window (typically 1–2 hours). Operations do not resume until the asset is restored. Examples: electrical fault creating safety hazard, production line stoppage, critical infrastructure failure. In UniAsset, Incident Mode activates an escalation cascade to ensure emergency CMs are never silently delayed.
Examples
- Electrical fault with safety hazard — immediate isolation required
- Production line motor seizure — line stopped, output lost
- Emergency generator failure — building life safety at risk
- Critical medical device out of service during active clinical hours
Best for: Safety-critical failures and production-stopping breakdowns
Deferred Corrective Maintenance
Non-urgent, scheduled for a future windowDeferred CM covers failures where the asset is degraded or partially functional but operations can continue safely in the short term. The fault is logged as a work order, prioritised appropriately, and scheduled for the next available maintenance window — avoiding the cost of emergency response while ensuring the fault is formally tracked and not forgotten. Proper deferred CM management prevents the 'informal repair queue' — where faults are known but undocumented, leading to loss of information, cost accountability, and regulatory exposure.
Examples
- Fluorescent light failure in office — documented, deferred to weekend maintenance
- Minor oil leak on secondary pump — scheduled for next planned shutdown
- Door lock mechanism worn — functional but sluggish, repair deferred 48 hours
- Non-critical conveyor belt tracking issue — documented, deferred to shift end
Best for: Non-critical faults where immediate response is not operationally required
Run-to-Failure (Intentional CM)
Deliberate policy — no PM, replace on failureRun-to-failure (RTF) is a deliberate maintenance strategy applied to assets where the cost of PM exceeds the cost of failure and replacement. It is not neglect — it is a conscious economic decision. RTF is appropriate for low-cost, easily replaceable assets with no secondary failure consequences: light bulbs, fuses, non-critical consumables, certain batteries, and redundant components. RTF strategy should be explicitly recorded in the asset record so that when failure occurs, there is no ambiguity about whether a PM programme was intended. Applying RTF to critical assets is a high-risk error that is commonly made in under-resourced operations.
Examples
- Office fluorescent bulbs — replace on failure, no scheduled replacement
- Low-cost fuses in non-critical electrical circuits
- Redundant pump in a dual-pump system — secondary pump run to failure
- Consumable cutting tools in low-criticality machining operations
Best for: Low-cost, easily replaceable assets with no operational consequence on failure
Planned Corrective Maintenance
Fault identified, repair scheduled before failurePlanned corrective maintenance occurs when monitoring or inspection identifies a deteriorating component that has not yet failed — giving operations a defined window to schedule the repair before it becomes an emergency. This is the intended output of a mature PM programme: PM finds early-stage faults, a CM work order is raised and scheduled, the repair occurs during a planned maintenance window, and the asset never actually fails in service. Planned CM blurs the boundary between corrective and preventive maintenance — it is reactive in origin (a fault was found) but proactive in execution (it is scheduled before operational impact).
Examples
- PM inspection finds bearing wear — CM scheduled for weekend before failure
- Vibration monitoring detects early imbalance — alignment corrective scheduled
- Oil analysis finds elevated metal particles — pump overhaul booked in advance
- Visual inspection finds cracked belt — replacement scheduled for next shift break
Best for: Faults detected early enough to plan the repair before operational impact
How corrective maintenance works — the full incident-to-closure lifecycle
Every corrective maintenance event follows a lifecycle — from the moment a fault is detected to the moment the work order closes and root cause is documented. How an organisation manages each stage determines the true cost and recurrence risk of every failure.
Fault Detection & Reporting
The CM lifecycle begins the moment a fault is detected. Detection sources include operator reports ('the pump is making a grinding noise'), automated alerts from monitoring systems, inspection findings from PM visits, or a complete operational stoppage. Detection speed is the first determinant of MTTR — every minute between failure occurrence and fault reporting extends downtime. Structured reporting matters: a vague fault description ('machine not working') forces the technician to spend diagnosis time that a precise description ('no output pressure — pump motor running but shaft not turning') would have saved. In UniAsset, faults can be reported by any user with access — not just maintenance staff — ensuring rapid capture.
Outputs
Work Order Creation & Classification
A corrective work order is created — either manually by the maintenance manager or automatically from a fault report. The work order records the asset, fault type, fault description, and detected time. At creation, the fault is classified: fault category (mechanical, electrical, structural, software, user-caused), failure type (complete failure, partial degradation, intermittent fault), and location. Classification drives downstream analysis — without consistent fault classification, it is impossible to identify patterns like 'all electrical faults on this asset category' or 'all failures attributed to user error'. Classification is the data investment that makes CM intelligence possible.
Outputs
Priority Assignment & SLA Activation
The work order is assigned a priority level based on the operational and safety impact of the failure: Emergency (immediate safety risk or critical operations stoppage), High (significant operational impact, recovery urgent), Medium (operational impact moderate, scheduled response acceptable), Low (minor or cosmetic fault, deferred response appropriate). Priority selection activates the corresponding SLA — defining maximum permitted response time and resolution time. The SLA clock starts at work order creation. If Incident Mode is activated (Emergency priority), an escalation cascade notifies the Engineering Head and Operations Director immediately, bypassing normal notification routing.
Outputs
Technician Assignment & Dispatch
The work order is assigned to the appropriate technician based on skill set (electrical, mechanical, hydraulic), current workload, shift schedule, and proximity to the asset. The technician receives an in-app notification with the asset details, fault description, location, priority, and SLA deadline. For emergency priorities, the notification carries an alert indicator that cannot be dismissed without acknowledgement. Before dispatching, the technician reviews the asset's maintenance history — previous CM events on the same asset provide diagnostic context and may immediately suggest the likely cause based on known recurring fault patterns.
Outputs
Diagnosis & Parts Identification
The technician arrives on-site and diagnoses the fault. The diagnosis phase is where MTTR is most directly influenced: a technician with access to the asset's full maintenance history, schematics, and previous repair records diagnoses faster than one working from memory alone. The technician documents the confirmed diagnosis on the work order before beginning any repair — preventing the most common first-time fix failure scenario, where a repair is executed based on an assumed diagnosis that turns out to be incomplete. If parts are required that are not immediately available, an on-hold status is set with a parts-awaited reason code, and procurement is initiated. The SLA clock continues running — parts availability is a key MTTR driver.
Outputs
Repair Execution & Documentation
The technician executes the repair, following any applicable procedure or checklist. All actions are documented on the work order: labour time logged by the hour, materials consumed listed with quantities and part numbers, photographs taken of the failed component (before), the repair in progress, and the restored asset (after). After photographs are particularly important for disputed failures — they provide evidence of what was done and the state of the asset on restoration. Any additional findings noted during the repair — wear on adjacent components, signs of secondary damage, other deterioration that was not the cause of this CM event — are captured as follow-up observations.
Outputs
Functional Verification & Manager Sign-off
The repair is not complete until the asset has been tested and confirmed to be operating within specification. The technician runs the asset through a functional verification: confirm the fault symptom has resolved, verify operating parameters are within acceptable range, check for any abnormal noise, vibration, temperature, or pressure, and confirm the asset is ready to return to service. The technician submits the completed work order for manager approval. The manager reviews the repair documentation, assesses quality, validates cost entries, and approves closure. Incomplete documentation — missing materials, no functional test, no photos — should result in the work order being returned for completion before approval.
Outputs
Root Cause Analysis & History Update
Work order closure triggers the critical last step: root cause analysis. The RCA is documented directly on the CM work order — recording not just what failed, but why it failed and what action has been taken or should be taken to prevent recurrence. RCA outputs drive three downstream actions: PM rule modification (add a new PM interval, tighten an existing one, or update a checklist to detect this failure mechanism); operating procedure change (update the user procedure that may have contributed to the failure); or a design or specification change request. The closed work order creates a permanent CM record on the asset and adds its cost to the asset's accumulated maintenance total and TCO breakdown.
Outputs
How corrective maintenance operates across industries
The urgency, cost, and consequence of corrective maintenance varies dramatically by industry. Here is how CM is managed in four operational environments.
Operational outcomes
- Fault detected at 5% reject rate — line continued running during repair rather than full stoppage
- MTTR: 1 hour 42 minutes — asset history enabled immediate diagnosis
- RCA drove PM checklist update — spring fatigue mechanism now detected proactively
Operational outcomes
- Emergency CM response: patient transferred to backup unit in 4 minutes, equipment restored in 22 minutes total
- Full medical device traceability: parts replaced recorded with lot numbers on the CM work order
- RCA completed and reported to Medical Device Safety Officer within the same work order record
Operational outcomes
- Life-safety fault auto-escalated to Emergency — resolved in 47 minutes from detection
- SLA compliance 97.3% across 12 buildings — above contract minimum of 95%
- SLA breach pattern identified — AHU parts stocking policy review actionable from data
Operational outcomes
- Repeat failure pattern identified: 3 cooling system CMs in 6 months on same vehicle
- RCA drove PM checklist update: hose inspection added — prevents recurrence fleet-wide
- CM history + PM history cross-analysis only possible because both are in a single system
Key components of a corrective maintenance system
A structured CM system is built from interconnected components. Each element plays a specific role in converting an unplanned failure event into a documented, costed, analysed, and resolved operational record.
Corrective Work Order
The primary operational record of every CM event. Created on fault detection, it records the asset, fault description, priority, SLA deadline, assigned technician, repair actions, parts consumed, labour time, costs, and root cause. It is the instrument through which a failure is tracked from detection to closure — and the data source for every CM KPI and analysis.
Lifecycle: Open → Assigned → In Progress → On Hold → Awaiting Approval → Closed
Priority Matrix & SLA Framework
The classification system that determines how urgently each CM event is handled. Priorities (Emergency, High, Medium, Low) map to SLA response and resolution windows. The priority matrix should be defined based on asset criticality, operational impact, and safety consequence — not left to individual discretion. Consistent priority assignment is what makes SLA compliance data meaningful.
Drives: SLA deadlines, escalation triggers, resource allocation
Incident Mode / Emergency Escalation
Activated for Emergency-priority CM events, Incident Mode bypasses normal notification routing and fires simultaneous alerts to multiple stakeholders — Engineering Head, Operations Director, or any configured recipient. It ensures critical failures are never silently delayed due to a missed notification, and creates a clear chain of escalation evidence in the audit log.
Triggers: simultaneous multi-recipient alerts, mandatory acknowledgement
Fault Classification System
A standardised taxonomy for categorising CM faults by type (mechanical, electrical, structural, software, operator-caused), failure mode (complete failure, partial degradation, intermittent), and causal category (wear, fatigue, overload, incorrect operation, design deficiency). Consistent classification is the prerequisite for any CM pattern analysis — without it, the CM history is a list of events rather than an analysable dataset.
Enables: failure pattern analysis, recurring fault detection, RCA trends
Root Cause Analysis Record
The RCA is documented on the closed CM work order — recording the confirmed root cause, the contributing factors, and the corrective actions taken (or recommended) to prevent recurrence. RCA quality is the primary determinant of whether a CM event produces lasting operational improvement or simply gets repeated. A closed CM work order with no RCA is a missed learning opportunity.
Outputs: PM rule modifications, procedure changes, specification updates
CM Cost Log & TCO Integration
Every CM work order carries a cost log — labour hours at configured rates, materials with part numbers and quantities, and external contractor fees. On closure, the total CM cost is added to the asset's accumulated maintenance spend and TCO breakdown. The split between PM and CM costs per asset is visible in the TCO — revealing which assets are consuming disproportionate reactive maintenance spend.
Feeds: asset TCO, PM vs CM cost ratio, repair-vs-replace analysis
Breakdown & Failure History
The complete chronological record of every CM event on each asset. The failure history reveals failure frequency (is this asset failing more often?), failure patterns (is it always the same component?), and failure seasonality (does it fail more in summer?). This history is the primary data source for MTBF calculation, repeat failure detection, and the repair-vs-replace decision when a major CM event occurs.
Feeds: MTBF calculation, repeat failure detection, repair-vs-replace decisions
Immutable CM Audit Trail
Every action on a CM work order — creation, status changes, technician notes, cost entries, approval decisions, closure — is recorded in an immutable timestamped audit log. The CM audit trail is the definitive record of the organisation's response to a failure event. It cannot be modified or deleted. Regulatory auditors, insurers, and legal proceedings may all require access to CM audit records — the immutable trail provides defensible evidence.
Records: every status change, action, cost entry, and approval decision
How corrective maintenance connects to adjacent systems
Corrective maintenance does not operate in isolation. Its data feeds and is fed by every other operational system — assets, work orders, SLA, PM, and compliance.
Corrective maintenance system relationships
How CM connects to the broader operational knowledge graph
Primary system connections
Every CM event is executed and tracked through a work order — the primary operational record of the failure, repair, cost, and resolution.
Corrective Maintenance is managed through Work Orders
Failures originate from assets. Every CM work order is linked to a specific asset, adding to its failure history, cost record, and lifecycle data.
Corrective Maintenance is caused by and recorded on Assets
SLA frameworks define the maximum response and resolution time for each CM priority. SLA compliance is the governance metric for CM operations.
Corrective Maintenance is governed by Maintenance SLA
CM findings drive PM programme updates — new intervals, checklist additions. PM performance determines CM frequency — better PM means less CM.
Corrective Maintenance drives improvements in and is reduced by Preventive Maintenance
Secondary system connections
Corrective maintenance automation and system intelligence
Modern CM management is not manual coordination. These automation behaviours ensure that every failure event is captured, escalated, assigned, and tracked without relying on human memory.
Incident Mode emergency cascade
Emergency-priority CM events activate Incident Mode — firing simultaneous notifications to the Engineering Head, Operations Director, and any configured escalation recipients. Unlike normal notifications (which are easily missed), Incident Mode alerts require acknowledgement and create a visible escalation chain in the audit log.
SLA deadline auto-calculation
When a CM work order is created and a priority is assigned, the SLA response and resolution deadlines are calculated automatically based on the configured SLA framework. The deadline is visible on the work order and in the technician's queue — removing the need for manual deadline tracking and ensuring no SLA commitment is forgotten.
SLA breach escalation
When a CM work order approaches its SLA deadline without resolution, an escalation notification fires automatically to the assigned technician's manager. The escalation creates a timestamped record in the audit log — documenting both the SLA status and the escalation response, which is critical for contract SLA reporting.
CM cost auto-accumulation to TCO
Every CM work order closure automatically adds labour, materials, and contractor costs to the asset's accumulated maintenance total. CM costs are tracked separately from PM costs in the TCO breakdown — enabling the PM vs CM cost ratio analysis that validates preventive investment and drives repair-vs-replace decisions.
Linked CM from PM findings
When a technician records an abnormal finding during a PM inspection, a linked corrective work order can be raised directly from the PM work order. The parent-child relationship is preserved — showing that the CM originated from a PM finding rather than an operational failure. This is the data that validates the PM programme's fault-detection effectiveness.
Repeat failure pattern detection
The system tracks CM events per asset and can surface repeat failure patterns — the same fault type occurring multiple times within a defined period. Repeat failures are a leading indicator that RCA was either not performed or not acted upon. Detection allows maintenance managers to intervene before a chronic failure pattern becomes a major cost or reliability problem.
Maintenance record auto-creation
Closing a CM work order automatically creates a permanent maintenance record on the asset — capturing fault, repair, technician, parts, cost, and RCA findings. The CM history grows continuously and automatically. Every closed work order is an entry in the permanent, searchable asset service timeline.
MTTR and KPI auto-calculation
MTTR, first-time fix rate, emergency CM ratio, and PM:CM ratio are calculated automatically from work order data. Reporting requires no manual data assembly — the dashboard displays current KPI values in real time, enabling managers to monitor programme performance without dedicating time to spreadsheet maintenance.
Immutable CM audit trail
Every action on every CM work order — creation, assignment, status changes, notes, cost entries, approval decisions — is recorded in an immutable, timestamped audit event log. The trail cannot be modified. Regulatory, insurance, and legal proceedings can always access the complete, unaltered record of every corrective maintenance event.
Corrective maintenance best practices
The difference between a CM programme that controls failures and one that is controlled by failures is operational discipline — in how faults are classified, documented, escalated, and analysed.
Response discipline
Capture every fault as a work order — no informal repair queues
Every fault, regardless of perceived urgency or simplicity, must be logged as a work order. Faults handled informally — fixed without a record — disappear from the CM history, leaving gaps in the asset's failure record, cost accounting, and compliance evidence. The operations team that handles things 'quickly without logging them' is building a hidden liability.
Classify priority consistently — do not over-escalate or under-escalate
Priority assignment determines how quickly a technician is dispatched and which SLA deadline applies. Consistent classification requires a clear priority matrix with defined criteria — not individual judgement on each case. Operations that over-escalate (every fault becomes Emergency) destroy SLA credibility; those that under-escalate miss genuine emergencies.
Set lead time expectations at work order creation
When a CM work order is created, the assigned technician's expected response time should be communicated — not assumed. Operations teams that expect instant response on Medium-priority faults and maintenance teams that interpret Medium as 'when I have time' are the source of most CM SLA conflicts.
Documentation discipline
Document the diagnosis before executing the repair
The most common cause of first-time fix failure is a repair executed on an assumed diagnosis that turns out to be wrong. Requiring technicians to document their confirmed diagnosis on the work order before beginning repair creates a discipline that improves first-time fix rate and provides a record that distinguishes diagnostic failure from repair failure.
Log all materials consumed — not just labour time
CM cost data is only as complete as its inputs. Technicians who log labour but not materials produce systematically understated CM costs — making TCO analysis unreliable, budget forecasting inaccurate, and repair-vs-replace decisions poorly informed.
Take before and after photographs on every significant CM event
Photographs of the failed component and the restored asset create visual evidence that is invaluable for three purposes: quality assurance (was the repair done properly?), dispute resolution (what state was the asset in when we arrived?), and training (what does a failed seal bearing actually look like?).
Root cause analysis
RCA is required on every non-trivial CM event — not optional
Operations teams that treat RCA as optional produce CM histories that record what broke but not why. Without systematic RCA, the same failures recur because the underlying causes are never addressed. RCA does not need to be a lengthy report — a concise documented answer to 'why did this fail and what have we changed?' is sufficient for most CM events.
Act on RCA findings within the same work order closure process
An RCA finding that recommends a PM interval change must generate a PM rule modification before the work order is closed — not be filed as a note to be actioned later. RCA findings that are documented but not acted upon are a false sense of improvement — the data exists but the failure recurs.
Track repeat failures and treat them as programme failures
A repeat failure on the same asset within 90 days is evidence that the RCA was either not performed, not acted upon, or insufficient. Repeat failure rate should be tracked as a KPI — not to blame technicians, but to identify systemic gaps in the maintenance programme's ability to prevent recurrence.
Cost control
Monitor PM:CM ratio monthly — it is the most important leading indicator
The PM:CM ratio is the single metric that most directly reveals whether the maintenance programme is moving toward control or remaining reactive. A ratio below 1:2 (one PM for every two CMs) indicates the organisation is still predominantly reactive. Improving the ratio requires PM programme expansion and compliance improvement — both require manager attention.
Review CM cost by asset category to identify cost outliers
Assets with CM costs significantly above their category average are candidates for PM interval tightening, operating procedure review, or replacement evaluation. Monthly CM cost analysis by asset type surfaces these outliers in a way that anecdotal experience cannot — the highest-cost asset is not always the one that gets the most management attention.
Include deferred CM in the maintenance budget forecast
Deferred CM work orders — faults documented and scheduled for future maintenance windows — represent committed future maintenance spend. Including the deferred CM backlog in budget forecasting produces more accurate maintenance cost predictions than counting only closed CM costs.
Corrective maintenance metrics and KPIs
CM performance measurement quantifies responsiveness, quality, cost efficiency, and programme maturity. These KPIs provide the operational intelligence that guides corrective maintenance improvement.
Mean Time to Repair (MTTR)
Hours / MinutesAverage elapsed time from fault detection to full asset restoration. The primary speed metric for CM. Target varies by asset criticality: Emergency assets < 2 hours; High criticality < 8 hours; Medium < 24 hours.
Target: < 4 hours for critical assets
First-Time Fix Rate
PercentagePercentage of CM events resolved in a single technician visit without return visits or repeat work orders for the same fault. Low first-time fix rate indicates diagnosis quality issues — technicians are executing repairs without confirmed diagnoses.
Target: ≥ 85%
Emergency CM Ratio
PercentagePercentage of all CM work orders classified as Emergency priority. High emergency ratio (above 20%) indicates insufficient PM coverage — too many failures are reaching critical state before they are detected and addressed.
Target: < 10% of total CM volume
Repeat Failure Rate
PercentagePercentage of CM events on assets that experienced the same fault classification within 90 days. High repeat failure rate (above 15%) signals that RCA is not being performed or not being acted upon — failures recur because root causes are not addressed.
Target: < 10% within 90-day window
CM Cost per Asset
Currency / PeriodAnnual corrective maintenance spend per asset, segmented by category and facility. Compared against PM cost per asset to validate the economic argument for preventive investment. Assets with very high CM:PM ratios are candidates for PM programme expansion.
Benchmark: compare within asset category
SLA Compliance Rate
PercentagePercentage of CM work orders resolved within their SLA deadline. Critical for service contract management — SLA compliance is often a contractual obligation with financial penalties for breach. Track by priority tier to identify where SLA pressure is highest.
Target: ≥ 95% overall
PM:CM Ratio
RatioNumber of preventive work orders vs corrective work orders in a period. The primary indicator of maintenance programme maturity. Below 1:2 indicates reactive operations; above 2:1 indicates proactive maintenance culture.
Target: ≥ 1:1 (parity) → ≥ 2:1 (mature)
Work Order Backlog
CountTotal volume of open CM work orders at any given time. A growing backlog indicates that CM volume is outpacing maintenance resource capacity. Backlog by priority tier reveals whether the team is prioritising correctly — emergency and high priority backlog is more serious than low priority accumulation.
Target: zero Emergency backlog at all times
Mean Time Between Failures (MTBF)
Days / HoursAverage operational time between corrective maintenance events per asset or category. Improving MTBF validates PM programme effectiveness — a well-run PM programme should reduce failure frequency over time. Declining MTBF despite PM compliance indicates an interval or checklist deficiency.
Target: year-on-year improvement
Reactive firefighting vs structured CM vs PM-protected operations
Three levels of corrective maintenance maturity — defined by how failures are detected, managed, documented, and analysed.
| Dimension | Reactive Firefighting | Structured CM | PM-Protected Operations |
|---|---|---|---|
| Fault capture | Verbal, WhatsApp, ad hoc | Every fault logged as a work order | Faults often caught by PM before failure |
| Priority system | Loudest voice determines urgency | Defined priority matrix, consistent SLAs | Most CM is Medium/Low — few emergencies |
| Technician dispatch | Whoever is available | Skill-based assignment with SLA deadline | Planned CM can be resource-optimised |
| Cost tracking | No cost record — maintenance is just 'overhead' | Full cost log per work order, TCO accumulation | CM cost declining as PM prevents failures |
| Root cause analysis | None — fix and move on | RCA required on all significant CM events | RCA drives continuous PM improvement |
| Repeat failures | Common — same assets fail repeatedly | Detected and escalated via repeat failure tracking | Rare — PM catches deterioration patterns early |
| SLA compliance | No SLA — response time is unpredictable | SLA tracked per work order, breaches escalated | High compliance — most CM is planned corrective |
| PM:CM ratio | < 1:5 — almost entirely reactive | Improving toward 1:1 | > 2:1 — mostly preventive, minimal emergency CM |
Frequently asked questions
Detailed answers to the questions maintenance managers, operations directors, and facilities teams ask most frequently about corrective maintenance.
What is corrective maintenance?
Corrective maintenance (CM) is maintenance performed on an asset after a failure, fault, or performance degradation has been detected — with the goal of restoring the asset to its required operational state. Unlike preventive maintenance, which is proactive and schedule-driven, corrective maintenance is reactive: it is triggered by a failure event rather than a calendar interval. Corrective maintenance encompasses everything from emergency breakdown response to deferred non-critical repairs that are scheduled for a future maintenance window. The defining characteristic of corrective maintenance is that it is unplanned — the failure determines when the maintenance occurs, not a predetermined schedule.
What is the difference between corrective and preventive maintenance?
The fundamental difference is timing. Preventive maintenance (PM) is performed before failure occurs — on a schedule, at defined intervals, to prevent deterioration from reaching failure state. Corrective maintenance (CM) is performed after failure has occurred — in response to a detected fault or breakdown. The operational consequences are significant: PM work is predictable, budgeted, and can be scheduled to minimise operational disruption. CM work is unplanned, often urgent, and typically more expensive — studies consistently show that emergency corrective repairs cost 3–5 times more than equivalent planned PM service due to emergency labour rates, expedited parts procurement, and indirect costs of unplanned operational downtime. The goal of a PM programme is to reduce CM frequency, not eliminate it — even mature maintenance operations retain a corrective maintenance workload for failures that PM cannot predict or prevent.
What are the main types of corrective maintenance?
Corrective maintenance is typically classified into four types. Immediate corrective maintenance addresses failures that require same-session response — safety hazards, production-stopping breakdowns, or service failures directly impacting operations. The work order is created and dispatched within minutes of fault detection. Deferred corrective maintenance addresses failures that are real but non-urgent — the asset is degraded or partially functional but the repair can be scheduled for a future maintenance window without significant operational impact. Run-to-failure maintenance is an intentional CM strategy: for assets where the cost of PM exceeds the cost of replacement, the deliberate policy is to operate until failure and then replace rather than service. Planned corrective maintenance occurs when inspection or monitoring identifies a deteriorating component that has not yet failed — the repair is scheduled before actual failure occurs, blurring the boundary between corrective and preventive maintenance.
How is corrective maintenance managed through a work order system?
In a maintenance management system like UniAsset, corrective maintenance is managed through the work order lifecycle. When a fault is reported — by a user, technician, automated alert, or PM finding — a corrective work order is created, recording the asset, fault description, reported time, and reporter. The work order is assigned a priority level (Emergency, High, Medium, Low) which determines the SLA deadline for response and resolution. A technician is assigned and receives an in-app notification. The technician diagnoses the fault, procures parts if needed, executes the repair, and logs labour time, materials consumed, and findings. The manager reviews and approves the completed work order, which closes the record and adds the CM cost to the asset's total cost of ownership. Every action — assignment, status change, note, cost entry — is recorded in an immutable audit log.
What is MTTR and how do you improve it?
MTTR (Mean Time to Repair) is the average elapsed time from fault detection to asset restoration. It is calculated as: total corrective maintenance downtime ÷ number of corrective maintenance events. MTTR improvement is the primary operational goal of corrective maintenance management. The key levers are: (1) Detection speed — faster fault reporting reduces time to work order creation; (2) Response speed — efficient technician dispatch and parts availability reduce time-to-start; (3) Diagnosis efficiency — clear fault documentation and maintenance history reduce time spent diagnosing; (4) Parts availability — pre-stocked critical spare parts eliminate procurement delays; (5) Technician skill — technicians with asset-specific experience execute repairs faster; (6) Documentation quality — checklists and repair procedures reduce re-work and variation. A CMMS improves MTTR by making asset history, schematics, and previous repair records instantly accessible to the attending technician.
What is root cause analysis in corrective maintenance?
Root cause analysis (RCA) in corrective maintenance is the process of investigating why a failure occurred — not just what failed — so that the underlying cause can be addressed and recurrence prevented. RCA goes beyond the symptomatic fix (replacing the failed component) to identify the mechanism that caused the failure: inadequate lubrication, incorrect operating parameters, installation error, design deficiency, or missed PM interval. Common RCA methods include the 5-Why technique (iteratively asking 'why?' until the root cause is reached), fishbone/Ishikawa diagrams (categorising potential causes), and fault tree analysis (systematic decomposition of failure pathways). RCA findings should be documented on the corrective work order and drive one of three corrective actions: PM programme modification (add or tighten a PM interval), operating procedure change, or asset design or specification change.
What is the repair-versus-replace decision in corrective maintenance?
The repair-versus-replace decision arises when an asset suffers a corrective failure that is significant enough to question whether repair is economically justified. The decision framework considers: (1) Repair cost relative to asset replacement cost — if the repair cost exceeds 50–70% of replacement cost, replacement is typically more economical; (2) Asset age relative to useful life — an asset approaching end-of-useful-life with a major failure is a strong replacement candidate; (3) Failure frequency trend — assets with an accelerating CM frequency are consuming increasing maintenance resources and may cost more to maintain than to replace; (4) Parts availability — if parts are obsolete or unavailable, replacement is often the only practical option; (5) Technology obsolescence — newer replacement assets may offer significantly improved reliability or energy efficiency that changes the economic calculation. A CMMS provides the data needed for this decision: accumulated repair costs, failure frequency, and age — all visible on the asset record.
What is the PM:CM ratio and what does it indicate?
The PM:CM ratio is the number of preventive maintenance work orders completed relative to corrective maintenance work orders in the same period. A ratio of 1:1 means equal volumes of planned and corrective maintenance. A ratio of 1:3 (one PM for every three CMs) indicates predominantly reactive operations — the maintenance programme is dominated by breakdown response rather than planned prevention. World-class maintenance operations target a PM:CM ratio of 2:1 or higher — twice as many planned PM events as reactive corrective repairs. Improving the PM:CM ratio requires two simultaneous actions: increasing PM programme coverage (more assets with configured PM rules) and executing PM with high compliance (completing PM on time so assets do not deteriorate to failure between service events). The PM:CM ratio is a leading indicator of maintenance programme maturity — it reveals how much of the maintenance operation is in control vs reacting.
What are corrective maintenance KPIs?
The key corrective maintenance KPIs are: MTTR (Mean Time to Repair — elapsed time from fault detection to restoration; target varies by criticality, typically < 4 hours for critical assets); First-Time Fix Rate (percentage of CM events resolved in a single visit without rework — target ≥ 85%); Emergency CM Ratio (percentage of CM events classified as emergency/immediate priority — high ratio indicates insufficient PM coverage); Repeat Failure Rate (percentage of CM events on assets that had the same failure within 90 days — indicates RCA quality); CM Cost per Asset (annual corrective spend per asset, compared against PM spend for ROI analysis); Work Order Backlog (volume of open CM work orders — growing backlog indicates under-resourced maintenance); and PM:CM Ratio (relative volume of preventive vs corrective work — the primary indicator of maintenance programme maturity).
How does corrective maintenance interact with SLA management?
In a structured maintenance operation, corrective maintenance work orders are governed by SLA (Service Level Agreements) that define maximum permitted response and resolution times based on the fault priority. A typical SLA structure: Emergency priority — acknowledgement within 15 minutes, technician on-site within 1 hour; High priority — response within 2 hours, resolution within 8 hours; Medium priority — response within 24 hours, resolution within 3 business days; Low priority — resolution within 5–10 business days. SLA compliance is tracked per work order and reported as a metric. When a CM work order approaches its SLA deadline without resolution, the system triggers an escalation notification to the manager or Operations Director. SLA frameworks for corrective maintenance are often specified in facility management contracts or client service agreements — making SLA compliance a commercial obligation, not just an operational target.
What are the most common causes of high corrective maintenance frequency?
High CM frequency typically results from one or more of these root causes: (1) Absent or inadequate PM programme — the most common cause; assets deteriorate to failure because no scheduled maintenance intervenes before the failure threshold; (2) Low PM compliance — PM rules exist but work orders are consistently completed late, allowing deterioration to progress between service visits; (3) Incorrect PM intervals — PM intervals are too long for actual operating conditions; (4) Inadequate PM checklists — PM visits miss the deterioration mechanism because the checklist doesn't check the right parameters; (5) Operating outside design parameters — assets operated beyond rated capacity, in harsher environments than specified, or without specified consumables; (6) Poor installation or commissioning — early-life failures from incorrect installation rather than natural wear. Addressing high CM frequency requires identifying which of these root causes applies to the highest-CM-frequency assets and implementing targeted interventions.
How do corrective maintenance records contribute to asset lifecycle decisions?
Every corrective maintenance event creates a permanent record in the asset's maintenance history — recording the failure date, fault description, repair action, technician, parts consumed, and total cost. Across multiple CM events, this history reveals the asset's failure pattern: frequency of breakdowns, which components fail repeatedly, and the total cumulative CM cost. This data drives three critical lifecycle decisions. First, interval optimisation: if an asset is experiencing CM events between PM visits, the PM interval needs tightening to intercept the deterioration earlier. Second, repair-versus-replace: when cumulative CM costs approach replacement cost, or when failure frequency is accelerating, the asset lifecycle data justifies replacement. Third, fleet specification: when multiple assets of the same model show identical CM patterns, the findings inform procurement specification for replacement models or changes to operating procedure.
Get started
Manage corrective maintenance in UniAsset — free.
Log faults, dispatch technicians, track SLA compliance, document root cause, and build a complete CM history — in one system of record.
Used by manufacturing, healthcare, facilities, and fleet operations teams. No credit card required.