What Preventive Maintenance Really Looks Like, According to 686 of Your Peers

Ask a maintenance leader where their operation sits on the maturity ladder, and most will answer without much hesitation. 

Reactive, preventive, predictive: the language is everywhere, in conference keynotes, vendor decks, and job postings. A more interesting question is what that answer is based on. 

In broad strokes, reactive means fixing equipment after it breaks, preventive means servicing it on a schedule before it fails, and predictive means using asset history and condition data to step in before a failure shows up.

Definitions like that leave a lot of room, so a team’s self-placement usually comes down to gut feel. We wanted to know what happens when you measure behavior instead. 

For our most recent State of Maintenance Report, we surveyed 686 maintenance and operations professionals across the United States, split almost evenly between the people who plan the work and the people who perform it. Every respondent placed their own operation on the ladder. Separately, we asked three questions about how the work actually runs and scored the answers from 0 to 9. The label and score came from the same person, but they often didn’t match. 

How to measure maintenance maturity in three questions 

Your maintenance maturity score comes from behavior alone; industry, company size, and budget aren’t inputs. This means you can run the same audit on your own operation in just a few minutes by answering these questions: 

1. How are maintenance hours actually spent? Not how the schedule says they should be spent. If most wrench time goes to unplanned repairs, the operation runs reactive no matter what the plan looks like.
   
   • 0 points: Almost all reactive. Nearly every hour goes to whatever broke.
   • 1 point: Mostly reactive. Some PMs are on the calendar, but breakdowns take most of the week.
   • 2 points: About an even split between planned and unplanned work.
   • 3 points: Mostly preventive. Scheduled work fills most hours, and breakdowns are the exception.
   • 4 points: Substantially predictive. A real share of the work is triggered by asset history or condition data, not just the calendar.
2. How does work get tracked and recorded? Paper and memory sit at one end; a consistently used digital system at the other. This is where asset history either builds up or disappears.
   
   • 0 points: Paper, whiteboards, or memory.
   • 1 point: Spreadsheets or shared documents.
   • 2 points: A digital system that only part of the team uses consistently.
   • 3 points: A digital system the whole team uses consistently.
3. How many core maintenance metrics can you estimate with confidence? Count yours: PM compliance rate, unplanned downtime hours per month, annual downtime cost, mean time to repair (MTTR), mean time between failures (MTBF), and hands-on time per shift. Teams that can confidently estimate five or six of them make different decisions than teams that can estimate one or two, and they make them earlier.
   
   • 0 points: One or none
   • 1 point: Two to four
   • 2 points: Five or six

Add up your points to find your rung:

Where 686 of your peers landed

Look at those two distributions side by side, and the pattern is hard to miss: a Preventive plateau. The ends shrink and the middle swells. Teams at the bottom grade themselves too harshly, and teams at the top a little too generously.

Roughly two-thirds of the teams calling themselves reactive have built more structure than they give themselves credit for: a schedule that (mostly) survives the week, work logged in a system, a few metrics they can trust. In the field, “reactive” as a self-label often means “we had a rough month” and not  “we have no system.” 

The middle rung, meanwhile, holds two of every three teams we surveyed. If your operation scores preventive, you’re standing in the most crowded spot in the industry, and you’re further along than the firefighting weeks make it feel. 

What a preventive maintenance operation doesn't have is the infrastructure for the next climb: asset history deep enough to reveal failure patterns, and condition data consistent enough to act on before anything visibly breaks. That's the real difference between the middle rung and the top one. Getting to preventive asks a team to change its habits; getting to predictive asks those habits to have been in place long enough to leave a pattern behind.

Run the audit, then pick one habit 

The most useful thing about a behavioral definition is that it tells you exactly where to push. The teams at the top of the ladder weren't the biggest or the best funded. More than a third of predictive teams are small and midsize businesses, and nearly one in five maintains a single location. What they share is a short list of ordinary habits:

• Capture the work as it happens. A closeout note written at the asset beats any documentation initiative scheduled for next quarter. 
• Measure enough to know what’s true. Pick two or three metrics you can’t estimate today and start tracking them. 
• Turn the numbers into decisions. Without a defined process for acting on the data, a record system is just a reporting obligation.
• Choose tools your techs will actually use. Adoption is the return on the purchase, not a phase of the rollout. 

The audit only works if you answer it honestly, and honesty cuts both ways. Plenty of teams that call themselves reactive have more structure than they give themselves credit for, and some that call themselves predictive aren’t there yet. 

Share the result with your leadership before you propose anything new. A score you can both see is a better starting point than anyone’s gut feel.

From there, look at where you lost points and pick the one habit that fixes it. The full State of Maintenance Report has the complete benchmark, including downtime costs, technician time, CMMS adoption, and where AI actually fits, so you can put your own numbers next to your peers’. 

The audit takes five minutes. What you do after it is what moves you up a rung.