The pattern behind them all
Walk into most small and mid-sized Indian plants and the maintenance mistakes are remarkably consistent — not because the people are careless, but because the system is memory and paper. The fitter knows the machines, the store keeper knows the spares, the supervisor knows which line is trouble. It works until the person is on leave, the machine fails at 2 a.m., or an auditor asks for a record that only ever existed in someone's head.
That is the thread running through all nine mistakes below: each one is an information failure, not an effort failure. The work gets done; it just does not get captured in a way that lets anyone analyse it, prevent the next failure, or prove it happened. Which is why the fix, in almost every case, is the same — capture maintenance as linked records in a CMMS rather than in a diary. Read on for the specifics.
Mistake 1 — running maintenance on paper job cards
The most common mistake is also the most invisible: recording maintenance on paper job cards and in diaries. The work is written down, so it feels documented — but the data is unusable. You cannot total downtime by asset, spot a repeat failure, compute MTTR or MTBF, or hand an auditor anything but a stack of pages. The information exists and never joins up.
The fix: move the job card into software so each repair becomes a linked record — asset, problem, downtime, spares consumed, labour, cost, technician, status history. The same act of writing it down now produces reports, KPIs and audit evidence for free. This is the whole premise of a CMMS, and the deeper walk-through is in the maintenance work order process.
Mistake 2 — not capturing downtime
Closely related, and just as costly: breakdowns are noted ("compressor down, fixed") without a time down and a time restored. Without those two timestamps the plant is blind to its single biggest maintenance loss. You cannot see which machine loses the most hours, which cause repeats, or whether response is getting faster — so you firefight each breakdown as a fresh emergency and never attack the pattern. The dramatic one-off failure gets all the attention while the machine quietly losing two hours a week, often the bigger annual loss, goes unnoticed.
The fix: capture every failure as a breakdown ticket with a downtime clock, recorded at the machine when it happens. Those timestamps become the downtime-by-cause report and feed MTTR, MTBF and availability automatically. The full playbook is how to reduce machine downtime.
Mistake 3 — treating every asset the same
A plant that services every machine on the same calendar, or reacts to every failure with the same urgency, is wasting effort in two directions at once — over-maintaining cheap assets and under-protecting critical ones. Without an asset criticality ranking, maintenance attention follows whoever shouts loudest rather than where failure actually hurts most.
The fix: rank assets by criticality in the asset register — how badly does a failure of this machine hurt output, safety or quality — and let that ranking drive where preventive effort and spare stock go. Criticality is the lens that makes every other maintenance decision proportionate.
Mistake 4 — being purely reactive
Reactive-only maintenance — wait for it to break, then fix it — feels efficient because you never "waste" time on a machine that is still running. Counted properly, it is the most expensive way to run critical assets: unplanned downtime at the worst moment, premium emergency spares, overtime and secondary damage. The mistake is not reacting to failures; it is having no preventive layer on the machines that matter.
The fix: introduce targeted preventive maintenance — time- or usage-based schedules with checklists on the high-criticality assets, while rationally running cheap, quickly-replaced assets to failure. Drive it with PM-due alerts and measure PM compliance so it does not quietly slide. The economics are laid out in preventive vs breakdown maintenance.
Recognising your own plant in these?
A 30-minute demo of Fast Maintenance Software shows the asset register, breakdown capture with a downtime clock, PM schedules, spare reorder levels and calibration recall — on machines like yours.
Mistake 5 — spare-part stockouts
The single most common reason a two-hour repair becomes a two-day outage is a spare that was not on the shelf. The fault is diagnosed quickly; the machine then waits for a bearing, a seal or a control card to arrive. This is not a repair failure — it is a stock-discipline failure, and it is entirely preventable.
The fix: link each asset to its spare bill of materials and put a reorder level on every critical, long-lead or single-source spare, so the store is replenished before the failure. See Spare Parts & BoM and the deeper spare parts inventory management guide.
Mistake 6 — overstocking spares
The over-correction to stockouts is just as wasteful: buy two of everything, keep it all forever. That freezes working capital in slow-moving parts that sit for years and sometimes obsolesce before they are ever used — a particular drain for cash-conscious MSME plants. The mistake is treating all spares as equally worth holding.
The fix: right-size stock using consumption data. Hold genuine cover on critical and long-lead spares, but let the spare-consumption report expose the dead stock so it is not endlessly replenished. Reorder levels set by real usage, not by fear, keep the store lean without risking a critical stockout.
Mistake 7 — letting calibration lapse until audit
In any plant with measuring instruments — gauges, meters, test equipment — a quiet but serious mistake is having no recall system for calibration. The due date lives in a spreadsheet nobody checks, so instruments drift past due until an ISO 9001 or IATF 16949 auditor asks for the record. By then it is a nonconformity, and worse, every measurement taken with that gauge since it went out of calibration is suspect.
The fix: treat calibration as scheduled maintenance. A gauge register with a due follow-up raises a recall alert before the instrument expires, so calibration is current by routine — not rediscovered in a panic during audit week. This is exactly what the calibration and gauge management module does, surfaced next to the PM-due list.
Mistake 8 — ignoring AMC and warranty
A leak that never announces itself: paying out of pocket for a repair the manufacturer or an annual-maintenance contract would have covered — simply because nobody knew the asset was still in warranty or that its AMC visit was due. Across a fleet of machines with staggered purchase dates, this quietly recurs.
The fix: hold warranty and AMC dates on the asset record and let expiries raise an alert. You stop paying for covered repairs, and you stop paying for cover you are no longer using. On its own, this recovery can fund a good part of a CMMS.
Mistake 9 — keeping no maintenance history
The final mistake compounds all the others: no per-asset maintenance history. When every repair starts from a blank sheet, the technician re-diagnoses a fault the plant has seen five times, re-orders a spare it has fitted before, and repeats a fix that did not work last time. Institutional knowledge walks out the gate whenever an experienced fitter retires.
The fix: keep a complete maintenance history per asset — every PM and breakdown, spares, cost, downtime and photos — assembled automatically from the tickets. A technician who scans an asset's barcode/QR opens its full history at the machine, so diagnosis is faster and re-work rarer. The history is also the raw material for Dhruv AI to cluster recurring failure causes into named themes.
The single fix behind every fix
Notice how similar the fixes are. Nine different mistakes, one common cure: stop relying on memory and paper, and capture maintenance as linked records on one system. Once the asset, its spares, every preventive job and every breakdown are connected documents, the data to prevent all nine mistakes finally exists — and the reports, alerts and audit evidence come with it.
Fast Maintenance Software is that single system — built by Improsys in Pune on the shared Fast Suite platform, cloud or on-premise. It turns the asset register, spares, preventive and breakdown maintenance, calibration recall and history into linked records, with alerts over email, SMS and WhatsApp and reliability on the MTTR/MTBF dashboards — so the nine mistakes stop being how your plant runs.
Frequently asked questions
What are the most common maintenance management mistakes?
The nine that cost Indian plants the most: (1) running maintenance on paper job cards and diaries so nothing is analysable; (2) not capturing downtime, so you cannot see which asset or cause hurts most; (3) treating all assets equally instead of ranking them by criticality; (4) being purely reactive with no preventive schedule on critical machines; (5) spare-part stockouts that turn short repairs into long outages; (6) overstocking spares and freezing cash; (7) letting gauge and instrument calibration lapse until an audit finds it; (8) not tracking AMC and warranty, so you pay for covered repairs; and (9) having no maintenance history, so every diagnosis starts from scratch. Each is a management and information failure, and each is fixed by capturing maintenance as linked records in a CMMS rather than relying on memory and paper.
Why are paper job cards a problem in maintenance?
Paper job cards record that work happened but make the data unusable. You cannot total downtime by asset, spot a repeat failure, compute MTTR or MTBF, or prove a preventive programme to an auditor from a stack of diary pages. The information exists but never joins up, so decisions are made on impressions rather than facts. Moving job cards into a CMMS turns each repair into a linked record — asset, downtime, spares, cost, technician — so the same effort of writing it down now produces reports, KPIs and audit evidence for free.
How does not capturing downtime hurt a plant?
If downtime is not captured with a time-down and time-restored on each breakdown, the plant is blind to its single biggest maintenance loss. You cannot see which machine loses the most hours, which failure cause repeats, or whether response is getting faster, so you firefight every breakdown as a fresh emergency and never fix the pattern. The dramatic one-off failure gets attention while the machine that quietly loses two hours a week — often the bigger annual loss — goes unnoticed. Timestamped breakdown tickets are what turn downtime from an accepted nuisance into a measured number you can reduce.
Why do calibration lapses get found at audit time?
Because without a recall system, a gauge's due date lives in someone's memory or a spreadsheet nobody checks, so instruments quietly go past due until an ISO 9001 or IATF 16949 auditor asks for the calibration record. By then the lapse is a nonconformity, and worse, every measurement taken with that gauge since it went out of calibration is suspect. A CMMS treats calibration as scheduled maintenance — a gauge register with a due follow-up that raises a recall alert before the instrument expires — so calibration is current by routine, not rediscovered in a panic during audit week.
How do you fix reactive-only maintenance?
You fix it by introducing targeted preventive maintenance, not by trying to prevent everything. Start by ranking assets by criticality, then put time- or usage-based preventive schedules with checklists on the critical machines whose failure hurts most, while rationally running cheap, non-critical assets to failure. Drive the schedule with PM-due alerts so it does not slip, and measure PM compliance so you know it is actually happening. This shifts the ratio of planned to reactive work on the assets that matter, which is what lowers breakdown frequency and stabilises cost — without the waste of servicing everything on a calendar.