Deferred maintenance is preventive, predictive or corrective work that was due but has been postponed, usually because of budget, labor, parts or pressure to keep a machine running. In a factory it builds up as a backlog of overdue jobs. Each one carries risk, because a defect you could have caught on inspection keeps moving toward a failure while it waits.
Most articles treat deferred maintenance as something that happens to an organization: the budget got cut, the team is short. In a plant it usually happens one job at a time. Production won't release the machine this week. The bearing is on backorder. A shutdown is three weeks away, so the job can wait until then.
Each of those is a decision someone made. The problem isn't that maintenance gets deferred. Every plant defers work. The problem is when nobody records who decided, why, and what's being done about the risk in the meantime.
What deferred maintenance is, and what it isn't
APPA, the professional body for facilities managers, defines deferred maintenance as "preventive, predictive, or corrective maintenance that assets and systems should have undergone but have not yet done so." The key word is should. The work was due, and it didn't happen.
APPA also separates it from deferred capital renewal: major renewal or replacement work that went unfunded in past budgets. The plant-floor version of that is a postponed overhaul or a machine running past the point where it should have been replaced. Both get called "deferred maintenance" in conversation, but they're decided in different meetings and fixed with different money, so it's worth tracking them separately.
Two more distinctions help:
- Deferred maintenance vs. backlog. Your backlog is every job that's been identified but not done, including work that isn't due yet. Deferred maintenance is the slice of that backlog that's overdue.
- Deferred maintenance vs. run-to-failure. Running a non-critical asset until it breaks is a maintenance strategy chosen in advance. Nothing was due, so nothing was deferred. A critical asset that's running to failure because its PMs keep slipping is a different story.
Defer, reschedule, cancel or run to failure?
These four get confused all the time, and the confusion is how deferred work goes missing. Here's how to tell them apart:
| Decision | What it means | When it's legitimate | What to record |
|---|---|---|---|
| Reschedule | Move the job within its tolerance window | The task still gets done inside its agreed window (say, a monthly PM done 3 days late within a ±5-day window) | Nothing special. It's still on time |
| Defer | Postpone the job past its due window | The risk of waiting is understood and lower than the cost of stopping now | Owner, reason, risk, new due date, interim control |
| Cancel | Remove the task for good | The task adds no value, or the asset is gone or changed | Who removed it and why, so the PM schedule stays honest |
| Run to failure | No preventive task by design | Non-critical asset, failure has no safety or production impact and causes no secondary damage | The strategy itself, set when the PM plan is built |
The row that causes trouble is the second one, especially when it's handled like the first. Pushing a due date out by three weeks without calling it a deferral makes the job look rescheduled. It isn't.
Deferred maintenance examples on the plant floor
Typical deferrals in a manufacturing plant, and what each one is actually risking:
| What gets deferred | Why it happens | The risk while it waits | A sensible interim control |
|---|---|---|---|
| Weekly lubrication route on a filler | Line is running a peak order | Bearing and chain wear speeds up, heat builds | Lubricate the critical points only, finish the route at the next stop |
| Conveyor bearing flagged on a vibration check | Waiting for the next changeover | Bearing failure takes out the shaft or the gearbox | Recheck vibration and temperature every shift, set a hard deadline |
| PM on a hydraulic press | Seal kit is on backorder | Leak gets worse, pressure drops, oil on the floor | Daily leak check, drip tray, expedite the part |
| Instrument calibration on a temperature controller | Technician pulled onto breakdowns | Product made out of spec without anyone knowing | Spot-check against a reference thermometer |
| Annual gearbox overhaul | Pushed into next year's budget | Wear spreads to gears and housing, overhaul becomes replacement | Oil analysis and a vibration baseline before the decision |
| Belt replacement on a packing line | Production won't release the machine | Belt snaps mid-shift, unplanned stop | Inspect belt condition daily, keep a spare at the line |
Notice that every row has a reason that sounds sensible. That's what makes deferred work hard to manage. Nobody's being careless. The trouble starts when the interim control column is blank.
Why deferred maintenance gets more expensive
Deferred work doesn't stay the same size while it waits. Two mechanisms make it grow.
The P-F interval. In reliability-centered maintenance, the P-F curve describes how most failures develop: there's a point (P) where a defect first becomes detectable, and a later point (F) where the asset actually fails. Inspections and PMs exist to catch the problem somewhere between P and F, when it's still a planned repair. Deferring an inspection past that window turns a planned repair into a breakdown. The defect was always going to need fixing. Deferral decides whether you fix it on your schedule or the machine's.
Collateral damage. Failures rarely stay contained. A dry bearing overheats and scores the shaft. A slipping belt glazes the pulley. A slow hydraulic leak lets in contamination that damages the pump. The original job was a bearing, a belt or a seal. The deferred job becomes a shaft, a pulley set or a pump, plus the downtime to fit them.
That's why deferred maintenance is usually described as a liability rather than a saving. The cost hasn't been avoided, only moved, and it tends to come back bigger and at a worse time.
How to defer safely: the five things to record
Sometimes deferring is the right call. Stopping a bottleneck machine in the middle of a customer order to change a belt that has weeks of life left would be the wrong decision. What turns a reasonable deferral into a hidden risk is the lack of a record.
Every deferral should capture five things:
- Owner. The named person who decided the job can wait. Not "production" or "the team".
- Reason. No parts, no access, no labor, waiting for a shutdown. The reason tells you what has to change before the job can happen.
- Risk. How critical the asset is and what happens if it fails before the work is done. Use your asset criticality ranking if you have one.
- New due date. A real date, not "next shutdown" or "when things calm down".
- Interim control. What you'll do to watch the risk until then: extra inspections, a condition check every shift, a run-hours limit, a spare staged at the machine.
A simple deferral record you can copy:
| Field | Example |
|---|---|
| Work order / PM | PM-0412, monthly bearing inspection, Conveyor C3 |
| Original due date | 28 Oct |
| Deferred by | Shift maintenance lead |
| Reason | Line not released, peak order through 6 Nov |
| Asset criticality | High (feeds the only case packer) |
| Risk if it fails | Line stop, possible gearbox damage |
| New due date | 7 Nov, during the planned changeover |
| Interim control | Vibration and temperature check every shift, spare bearing staged at the line |
| Escalate if | Vibration rises above the alarm level, or the new date slips |
If a deferral can't fill in the last two rows, it isn't really a deferral. It's a job that's been forgotten.
How deferral hides in your KPIs
This is the part that catches plants out. Two of the most common maintenance KPIs can look healthy while deferred work piles up.
PM compliance measures the share of preventive tasks completed within their due window. Schedule compliance measures the share of scheduled work done as scheduled. Both compare completed work against what was due. So if a deferred PM's due date simply gets moved out, it drops out of this month's denominator. It isn't late, as far as the KPI knows. Compliance stays at 95% while the real backlog grows.
The fix isn't a new metric. It's keeping deferrals visible:
- Track deferred work as its own number, separate from the open backlog.
- Count a PM against its original due date when you report compliance, or report deferred PMs alongside the compliance figure.
- Look at the age of deferred jobs, not just the count. Ten jobs deferred for a week is a busy month. Ten jobs deferred for a quarter is a program that's slipping.
The work order backlog section of our maintenance KPIs guide covers how to break backlog down by priority and age, which is where deferred work shows up first.
How to work down a deferred backlog
Once deferred work has built up, you won't clear it all at once. A practical order:
- List it and rank it. Pull every overdue job and sort by asset criticality and risk. A deferred lube route on a bottleneck filler outranks a deferred inspection on a spare compressor.
- Close the dead ones. Some deferred tasks no longer apply: the asset was replaced, or the task never added value. Cancel them properly, with a reason.
- Protect PM time going forward. If new PMs keep slipping, the backlog will refill as fast as you clear it. A maintenance planner who schedules PM time that production actually agrees to is the usual fix.
- Bundle into planned stops. Group deferred jobs by machine and line so they can all be done in one shutdown or changeover instead of asking for the machine five times.
- Fix the cause, not just the list. If most deferrals say "no parts", the problem is spares. If most say "no access", it's the production agreement. The reason field from your deferral records tells you which.
Where a CMMS helps
Deciding whether a job can wait is a judgment call. Software doesn't make it for you. What software can do is make sure the decision gets recorded, and that deferred work doesn't quietly fall off the list.
In MachDatum, overdue PM plans surface in the PM list as soon as they pass their due date, and due-date reminders go out before and after. Escalation rules can pull in the plant manager automatically when a job stays overdue past a set time. Work order workflows are configurable, so a "Deferred" state can require a reason and a new due date before anyone can move a job into it, and every state change is logged with who made it and when. Asset criticality sits on the asset record, so triage starts from the right list.
We're onboarding our first group of manufacturing teams now. If deferred work in your plant lives in someone's head or a spreadsheet, see how MachDatum CMMS handles work orders and PM schedules.
