A 90-day playbook for moving from reactive to preventive maintenance

This 90-day playbook will help you start to move from reactive firefighting to proactive maintenance management. You’ll learn how to master the foundational work that makes any maintenance strategy effective and sustainable, like clean data capture, clear accountability, and consistent review habits.

Read on to get a week-by-week framework for improving your maintenance maturity, the KPIs to track at each stage, and building a repeatable system that keeps progress on track.

Why most maintenance teams stay stuck in reactive work

Most teams assume the gap between reactive and proactive maintenance is a software problem, but the real barriers are processes, systems, and culture change.

"It's definitely not your techs," explains Isabel Jardine, Global Manager of Solutions Consulting at MaintainX. Technicians will try their best to do what you ask. But they need clear expectations and processes designed around how they actually work, not how leadership imagines they work.

Adopting overcomplicated systems and processes

Teams often over-index on complex systems without considering ease of use. The Toyota Kaizen philosophy offers a better approach: understand and improve the process first, before thinking about tools.

When workflows become overly complicated, they create friction for frontline workers. Ensure you’re creating processes that take into account the way technicians work and think, which is often, “What’s the easiest and quickest way to give you the information you need,” says Isabel. The easier it is to capture data, the better your insights will be.

Ignoring the technician experience

Processes designed without the technician's perspective rarely succeed. If your system requires too many steps or feels disconnected from actual work, adoption suffers. Technicians will engage with tools that genuinely help them and disengage from tools that don't. View every workflow from the lens of what technicians need to accomplish their work.

Lacking top-down accountability

Leadership engagement directly impacts success. As Isabel notes, "As soon as you stop looking at someone's data, they stop updating it." When leaders actively participate in reviews and ask questions about the data, accountability flows downward. Without visible commitment from the top, initiatives stall.

How to assess your maintenance maturity

A successful (and realistic) maintenance strategy will always rely on some combination of reactive and preventive maintenance strategies, all the way from run to fail to predictive maintenance. It’s not about going from 0 to 100, but rather achieving the right balance for your facility and assets. Understanding what that balance looks like and what you need to do to achieve it is how you build your roadmap to maintenance maturity.

Volume-based metrics can be misleading

Here’s a story from a real maintenance team. They were hitting a 70% preventive maintenance percentage by work order volume. Considering top-performing teams achieve around 80%, this looked solid. However, when they examined actual wrench time, those 30% reactive work orders took more than half of their total labor hours. This comparison revealed a completely different picture. This team was still primarily reactive despite the favorable ratio.

Use wrench time to reveal reality

Labor time allocation is the metric that reveals your actual maturity state. Track time spent on reactive versus planned work. If most wrench time goes to firefighting, you're still primarily reactive regardless of PM counts. Time doesn't lie the way volume metrics can.

The 90-day reactive-to-preventive framework

This framework focuses on building sustainable habits and celebrating incremental progress.

Phase 1 (days 1–14): Get really good at managing work

Standardizing the way you plan and schedule work is the foundation for everything else. Without clean work order data, all the other action you take and the data you collect is compromised.

"If you're not getting that part of the process humming, everything else you can just forget about it," Isabel explains. Define the system from request to work order to completion. Ensure each person knows what data they're responsible for, and start small to gather feedback.

1. Define your work order flow

Map the path from initial maintenance request through to creation, approval, execution, and completion. Identify who handles each stage and clarify handoff points where data can be lost or where errors happen.

2. Clarify roles and data responsibilities

Assign ownership for specific data fields at each stage. Audit work order summaries to verify completeness and accuracy. Look through work order summaries to see if the information gives you what you need, then validate with technicians.

3. Start small and gather stakeholder feedback

Begin in one area or with one team to test the process before scaling. Get feedback from each stakeholder on what worked and what didn't.

"The more your frontline team sees you lean in to improve things, the more they are going to buy into it and start to understand why it matters to them" says Isabel. Show end users the value of any changes you make. For example, any questions that are commonly brought up may be accessible in seconds from a new digital procedure.

Phase 2 (days 15–45): Build and fine-tune a preventive maintenance plan, one PM at a time

Now it’s time to shift your focus to creating a well-run preventive maintenance program using your work order data. This phase isn’t meant to get you all the way from purely reactive to your ultimate preventive maintenance goal. Rather, it’s intended to give you baselines and frameworks for implementing PMs and consistently improving them.

Hold weekly data review meetings

Meet as a maintenance team weekly (at least) to discuss your preventive maintenance program. Review data and get extra context. Ask about challenges and obstacles, then make a plan to eliminate them. Make this the start of a feedback loop that makes your processes stronger every week.

Conduct an asset criticality analysis

Different assets need different approaches. Before choosing between predictive, time-based PM, or condition-based PM, understand how important each asset is.

For example, you might find that you’re completing PMs on an asset as if it’s operating at peak production, when it is, in fact, not in such high demand. This means your team is using double the amount of time to inspect and do routine maintenance on the machine than is necessary. If you scale back your PMs or switch to condition-based maintenance triggered by machine runtime hours, you might be able to save tens of thousands of dollars while minimizing risk.

Log everything in one platform

By day 45, aim to have all work—reactive and planned—logged in the same system. Partial logging creates blind spots that hurt analysis. Having everything in one place makes future progress much easier. Combining data helps you make meaningful comparisons.

Phase 3 (days 45–90): Use your data to refine your processes

The final phase makes use of all the data you’ve collected in the previous couple of months to refine your PM program.

Start tracking downtime and downtime costs

Downtime tracking requires more nuance than simpler metrics, especially when not integrated directly into the systems you already use. Start it later in the journey, around the 45 to 90-day mark, once data habits are established.

Audit data quality with your team

Review work orders with the people who completed them. Validate with technicians that the information captured matches what actually happened. These conversations show where training is needed when data doesn't match reality. They also strengthen the message that leadership is paying attention.

Celebrate wins and communicate progress

Share what you've accomplished with the data. Recognition strengthens the value of good data habits and keeps people engaged. Show stakeholders how the data led to specific improvements. Celebrating wins keeps momentum going through the harder parts of transformation.

The KPIs that will tell you if you’re plan is working

While your plan to move from reactive to preventive may look more or less positive with the eye test, numbers rarely lie. Keeping track of a few select KPIs will allow you to spot risk early and adjust your plan, or to reassure yourself and your team that you’re headed in the right direction.

Weeks 1–4: Created vs. completed work orders

This baseline metric reveals adoption gaps and missing data. If your team creates work orders but doesn't complete them, investigate why. Break this down by user to show who's engaging with the system. Expect some gaps initially. Aim for improvement, not perfection.

Weeks 5–8: Labor time and cost by asset

Labor time is critical for understanding where wrench time actually goes. Link labor to work orders and assets. This reveals which equipment costs the most to maintain. Trends will emerge that guide criticality and strategy decisions.

Weeks 9–13: Downtime and trend analysis

By this point, your team has established data habits. Compare month-over-month trends to check strategy effectiveness. If all other factors remain constant and you're doing more PMs while reactive work order time decreases, your preventive maintenance strategy is working.

How leadership support drives maturity gains

Leaders sometimes don't know the current process or how painful it is. Isabel shares an example: "The corporate-level executives in the room might have no idea it would take someone at least five to six hours to go through all the work orders, make sure the data's there, analyze the different spreadsheets, and generate a report they spend about five minutes discussing in a weekly meeting."

Understand the current state

Observe the reporting process end-to-end before making changes. Understand the data work required and question how much of that effort adds value.

Show accountability through visibility

Review dashboards and reports regularly. Ask questions about the data in team meetings. Your attention shows that this work matters. When leadership stops paying attention, people stop updating data.

Turn your 90-day plan into a repeatable playbook

The 90-day framework establishes habits, but real value comes from ongoing effort. Month-over-month comparison reveals whether your strategy is working. If you're doing more PMs and the amount of time spent on reactive work orders is reducing month over month, that's a sign your preventive maintenance strategy is working to get ahead of breakdowns before they happen.