Corrective maintenance is repair work carried out after a fault is found, restoring an asset to working condition.
Corrective maintenance is repair work carried out after a fault has been found, restoring an asset to working condition. The fault might surface as a breakdown mid-job, a defect spotted during an inspection, or a problem reported through a service ticket - what makes the work corrective is that the failure or defect already exists when the job is raised.
Immediate vs deferred corrective work
Corrective maintenance splits into two very different experiences. Immediate (emergency) corrective work follows a breakdown that stops something important: one of the trucks is off the road with a load booked, so the repair jumps every queue and costs whatever it costs. Deferred (planned) corrective work follows a fault that can wait: a cracked guard found at inspection, a sticking door, a slow hydraulic leak - the defect is logged, parts are ordered, and the repair is scheduled for a slot that does not stop work. The term “reactive maintenance” is often used loosely for the first kind; corrective covers both.
The gap between the two is mostly a reporting question. The earlier a fault is surfaced and logged, the more corrective work can be done on your schedule instead of the failure’s.
Corrective vs preventive maintenance
Preventive maintenance services working equipment on a schedule; corrective maintenance repairs equipment with a known fault. Neither is “the right one” - they are positions on a spectrum, and the sensible mix depends on the asset. Run-to-failure (corrective only, by choice) is rational for cheap, non-critical, or easily swapped items. Scheduled prevention earns its cost where failure is expensive, dangerous, or disruptive. Predictive maintenance sits between them, using condition data to time work just before failure. The expensive failure mode is not choosing corrective maintenance - it is defaulting to it for critical kit because nobody set up anything else.
The corrective workflow
A corrective job that goes well follows the same shape almost everywhere:
- Report - whoever finds the fault records what is wrong, on which asset, ideally with photos.
- Triage - someone decides severity: can the asset stay in service, should it be quarantined, who repairs it.
- Repair - the job becomes a work order, parts are sourced, the work is done in-house or sent out.
- Close-out - what was found, what was replaced, what it cost, and whether the asset returned to service.
The close-out is the step teams skip and later regret - it is the only part that pays off the next time the same asset misbehaves.
Why corrective records matter
A logged history of faults and repairs is what turns one-off annoyances into decisions. Repeat faults on the same asset make the repair-or-replace call legible; warranty claims need dated evidence of when the defect appeared; and downtime measures like MTTR and reliability measures like MTBF only exist if jobs are recorded against the asset. In AMPthilly, anyone can report an issue against an asset with photos and a category, the ticket moves through a repair queue, and the full ticket history stays on the asset record permanently.
Related terms
- Predictive Maintenance - condition data times the work just before failure
- Work Order - the scheduled unit of repair work a fault report becomes
- Service Ticket - the report that starts most corrective jobs
- MTTR - mean time to repair, the headline downtime measure for corrective work
- MTBF - mean time between failures, computed from logged corrective history