Management
7 signs your maintenance is still reactive
Requests by text message, preventive work nobody owns, history in one technician's head: seven signs of reactive maintenance and the first step out of each.
Hardly any team describes itself as reactive. Even so, many spend the month chasing the next problem, with a preventive plan that exists on paper and metrics nobody can calculate.
The seven signs below will help you recognize that pattern. For each one, you'll find the symptom, why it's costly and the first step out. You don't have to fix everything at once; the goal is to know where to start.
Reactive is not the same as corrective
Every operation has corrective work. Equipment breaks, and some low-criticality assets are deliberately run to failure. That is a strategy.
Reactive maintenance is something else: it's when corrective work stops being a choice and becomes the default way of working, because records, planning or analysis are missing. The difference lies less in how many breakdowns you have and more in how much the team learns from each one.
The question that tells them apart: after a failure, can your team say why it happened and what was done to keep it from happening again? If the answer depends on who you ask, your maintenance is still reactive.
Signs at work intake
1. Requests arrive by text or phone and never become a record
The symptom: the operator messages the technician they know, who fixes it and moves on. There's no work order, or it gets opened later, when someone remembers.
Why it's costly: a failure fixed outside the system doesn't exist in the history. MTBF looks better than reality, the problem equipment looks healthy and nobody can prioritize based on data. Requests also get lost when the technician is off.
The first step: define a single intake channel and agree that work without a work order doesn't count. Make opening a request as easy as possible, for example with a QR code on the asset, so that logging it is faster than sending a message.
2. Preventive work has no owner, or is always overdue
The symptom: the preventive plan exists, but it's the first thing to be pushed back when something urgent comes up. Overdue work orders pile up, and at the end of the month someone closes a batch of them at once.
Why it's costly: preventive work that doesn't happen prevents no failures, and the team loses confidence in the plan. In regulated installations, such as HVAC systems covered by a documented maintenance plan, work you can't prove was done is also a compliance risk.
The first step: assign each preventive routine to a person, with a due date, and track the percentage of preventive work completed on time. If the plan is too big for the team, cut it down to what fits and deliver on it.
Signs in execution
3. The history lives in the senior technician's head
The symptom: "ask Carlos, he knows." The only way to find out what has already been done on an asset is to talk to whoever has worked there for years.
Why it's costly: diagnosis is slow for everyone who isn't that person, and the knowledge walks out the door with vacations, leaves and retirements. New technicians repeat attempts that have already proven useless.
The first step: start with the most critical assets. On every work order, record what was found and what fixed it. Within a few months, the history no longer depends on memory.
4. Work orders are closed with "replaced" and no cause
The symptom: the description field says "replaced bearing," "ok," "fixed." There's no failure mode and no cause, just the action.
Why it's costly: without a cause, the same failure comes back and is treated as if it were new. You replace the bearing every six weeks without noticing that the real problem is misalignment.
The first step: add two required fields with fixed lists when closing a work order: failure mode and probable cause. For failures that keep coming back, apply a simple analysis such as the 5 Whys.
5. Missing parts only show up at repair time
The symptom: the technician diagnoses the problem, goes to the storeroom and finds the part is out of stock. A rush purchase starts, and the equipment sits idle waiting.
Why it's costly: waiting for parts is often the biggest share of equipment downtime, bigger than the repair itself. That's what the breakdown in the 5 components of MTTR shows. Rush purchases also cost more and leave fewer supplier options.
The first step: list the parts used in corrective work over the past few months and set minimum stock for the ones that come up often or stop critical assets. Link parts to the work order, so consumption becomes data.
Signs in analysis
6. Metrics are calculated by hand at the end of the month
The symptom: someone spends days consolidating spreadsheets to put together the monthly report. By the time it reaches management, the next month is already half over.
Why it's costly: a late metric only explains the past. A bad trend on an asset is noticed weeks after it starts, and the planner's time goes into data entry instead of analysis.
The first step: pick a few metrics (MTBF, MTTR, on-time preventive work, backlog) and make sure they come straight from the work orders. If you're not yet confident in the math, see how to calculate MTBF and MTTR.
7. The spreadsheet records but doesn't analyze
The symptom: there's a spreadsheet with hundreds of rows of jobs. It answers "what was done on March 12," but not "which asset failed most this quarter, and why."
Why it's costly: the effort of recording is being made, but the payoff never arrives. Patterns such as repeat failures, assets that always overrun repair time or overloaded technicians stay invisible.
The first step: standardize the fields (asset, work order type, failure mode, timestamps) so the data can be grouped. Standardized data is what makes any analysis possible, manual or automated.
Where to start
If you recognized several signs, don't try to tackle all seven at once. The order that usually works:
- Records: every job becomes a work order, with timestamps and asset (signs 1 and 3).
- Cause: every corrective work order closes with failure mode and cause (sign 4).
- Plan: preventive work with an owner and tracked due dates (sign 2).
- Analysis: metrics and stock fed by the work orders themselves (signs 5, 6 and 7).
Broadly speaking, this path is the first step on the maintenance maturity curve. A CMMS like taskfield helps you sustain these steps: work orders are logged from the technician's app, even offline, failures are coded at closing, and AI flags repeat failures from the history.
Summary
- Reactive maintenance is when corrective work becomes the default because records, planning and analysis are missing.
- Work without a work order and work orders without a cause are the two signs that most distort the history.
- Preventive work without an owner doesn't happen; parts found missing at repair time stretch downtime.
- Metrics should come from work orders, not from spreadsheets consolidated at the end of the month.
- Start with records, then cause, plan and analysis.
Calculate it now. Run the numbers with your own data in the free calculators:
