The preventive maintenance app schedule that gets followed.
A preventive maintenance app has one job: turn a fixed interval, calendar time or a meter reading, into a task somebody actually does, and log proof that they did it. Not a reminder that gets snoozed, a PM task with a checklist, an assignee, and a closed record once it's done. That's the same test that decides whether the wider category of field service apps earns its keep in the field instead of just looking good in a demo.
This page is about the plumbing underneath any preventive maintenance app: how PM schedules actually differ from predictive and reactive maintenance, the fields a schedule needs to hold up, and what a CMMS is really tracking underneath it.
See preventive vs. predictive vs. reactiveThe short version
A schedule, seven fields, and proof it happened.
A preventive maintenance app needs an asset ID, an interval (time-based or usage-based), a checklist for that asset, an assignee, a next-due date it calculates itself, a timestamped completion log, and the parts used. Preventive maintenance means scheduling by time or usage; predictive means scheduling by the asset's measured condition instead; reactive means waiting for it to break. The rest of this page covers the real difference between those three, with the benchmark numbers a federal energy program actually publishes.
The three approaches
Preventive, predictive, or reactive — what's actually different.
The three terms get used loosely, but they schedule work on three genuinely different triggers. The U.S. Department of Energy's Federal Energy Management Program (FEMP) lays out the distinction and publishes benchmark ranges for how much of a maintenance program each approach should occupy:
| Approach | Triggered by | Scheduling basis | Typical industry share | Best-in-class target |
|---|---|---|---|---|
| Reactive | Equipment has already failed | None — run it until it breaks | 40–60% | 20–30% |
| Preventive | A fixed calendar date or usage meter | Time- or machine-run-based schedule | 30–50% | 25–35% |
| Predictive | The asset's measured condition | Sensor data — vibration, oil analysis, thermography | 10–15% | 30–40% |
Trigger, scheduling basis, and benchmark ranges from PNNL's O&M Best Practices guide for FEMP. "Typical industry share" is where most facilities actually land today; "best-in-class target" is where FEMP recommends they aim instead.
The same guide puts real numbers on why the shift matters. A preventive maintenance app's entire job is making the middle column, the scheduled kind, easy enough to actually run at that target share instead of drifting back toward reactive by default:
12–18%
Saved by a well-run preventive program over a purely reactive one.
8–12%
Saved on top of that by predictive maintenance, once the condition data exists to support it.
40–60% → <10%
Reactive maintenance's typical share of a program, versus FEMP's best-in-class target.
Try it
Reactive, preventive, or predictive — which fits this asset?
Pick one piece of equipment and answer what applies. This is a starting point, not a policy, the right call depends on your budget and your risk tolerance.
Suggested approach
Answer the questions above to see a suggested approach.
The schedule's fields
What a PM schedule needs to capture.
Strip away the vendor branding and every preventive maintenance app is scheduling the same seven things. Miss one and the schedule either stops generating tasks on its own or stops being provable after the fact:
Try it
Does your PM tracking capture this?
Check off what your current preventive maintenance schedule already records, on a wall calendar, a spreadsheet, or whatever app you use now.
0 of 7 · Start here — none of this is tracked consistently yet.
At its core, a preventive maintenance app is also a checklist app for teams: the schedule only proves anything if the checklist attached to each PM task actually gets filled in, item by item, by whoever did the work. A due date with no checklist behind it is just a reminder.
Try it
What's your PM compliance rate?
The single number that says whether a preventive maintenance program is actually preventing anything: PM tasks completed on time, divided by PM tasks scheduled.
PM tasks scheduled this month
Completed on time
Compliance rate
70%
Slipping. Tasks are piling up faster than they're getting closed.
Most of that checklist gets completed away from a desk, in a mechanical room, on a rooftop unit, or at a site with no signal at all, which means the app needs to capture it offline and sync later rather than assume a connection. That is a data and sync design decision worth making early, not a checkbox to add once the schedule is built — see offline app functionality before you scope the rest of it.
Where PM fits inside a CMMS
What a CMMS actually tracks.
A CMMS, or computerized maintenance management system, is the broader database a preventive maintenance schedule usually lives inside. IBM's explainer on CMMS software describes it as centering on a database that organizes asset and maintenance information into a handful of modules:
| CMMS module | What it stores | Where PM fits in |
|---|---|---|
| Asset registry | Serial numbers, warranties, install date, location | The record every PM schedule is tied to |
| Work order management | Work order numbers, assignments, status, PM schedules | Where the generated PM task actually lives |
| Resource & labor management | Technician certifications, hours worked | Who is allowed to sign off the PM task |
| Inventory & vendor management | Spare parts on hand, vendor and reorder info | The parts a PM checklist consumes |
| Reporting & audit trails | KPI dashboards, maintenance history | Proof the schedule was actually followed |
Module breakdown from IBM's CMMS vs. EAM explainer.
A dedicated preventive maintenance app doesn't need to be a full CMMS. It needs the asset registry and the work order module, since that's where PM schedules live, and it can skip or simplify labor management, vendor management, and the heavier reporting a full CMMS carries for larger asset portfolios.
CMMS vs. EAM: does a PM app need to go that far?
CMMS sits inside a bigger category, enterprise asset management (EAM), once an asset portfolio is large enough to need one. The same IBM explainer draws a clean line between the two:
| Scope | CMMS | EAM |
|---|---|---|
| Asset lifecycle covered | After installation — maintenance, scheduling, and costs | The entire lifecycle, from acquisition to decommissioning |
| Site coverage | Single-site or limited multi-site | Multi-site, across worksites and geographies |
| Financial data | Maintenance costs only | Full lifecycle cost — purchasing, repair, servicing — for total cost of ownership |
| Typical fit | One facility or a small asset portfolio | Distributed, asset-heavy operations |
Most teams building their own preventive maintenance app only need the CMMS side of this table. EAM-level scope, multi-site support and full lifecycle cost tracking, only starts to matter once you're managing assets across several locations with real acquisition-to-disposal budgeting behind them.
Terminology
PM task, work order, or inspection?
What separates these isn't the form, it's what triggers the record and who's allowed to close it. Get this wrong in your data model and reports like "all open PM tasks" start including things that were never PM tasks to begin with.
| Term | What triggers it | What it adds beyond the base fields | Who closes it |
|---|---|---|---|
| PM task | The maintenance calendar or a meter reading, not a complaint | A checklist tied to the asset's PM schedule | Whoever performs the scheduled check |
| Work order | A reported problem, or an approved request | Assignment, parts and labor, a full status history | The technician, then a reviewer who signs off |
| Inspection | A required check, like a pre-trip or safety walkthrough | A pass or fail per item, sometimes a compliance record | An inspector or a certified technician |
If a PM task turns up a problem beyond what the checklist expects, a bearing that's further gone than a routine lubrication would fix, it usually needs to spin off into a proper work order app record rather than staying logged as a completed PM check. And if what you're actually running is a required pass/fail walkthrough before equipment goes into service, that's closer to a heavy equipment inspection app than a PM schedule.
Picking an approach
A maintenance management app, without the drift.
Every option below can technically hold a PM schedule. Only a couple of them keep generating the next task on their own without someone remembering to. Toggle a requirement to see which ones actually meet it:
| Approach | Auto-generates the next task | Works offline in the field | Custom checklist per asset | Who maintains it |
|---|---|---|---|---|
| Wall calendar / paper checklist | No | yes, by default | yes, whatever you write | you, by hand |
| Generic reminder or calendar app | one-off, no checklist | depends | No | you |
| Spreadsheet | No | No | yes | you, and it drifts |
| Off-the-shelf CMMS | Yes | Yes | locked to their schema | the vendor |
| Custom-built PM app | Yes | Yes | whatever your assets need | you |
5 of 5 approaches match — toggle a requirement to narrow the list.
Free vs. paid
Is there a free preventive maintenance app?
For one technician tracking a handful of assets, sure. Most CMMS and maintenance management app vendors offer a free tier, but they cap it by number of assets, users, or PM schedules, and the parts most useful once you actually rely on it, custom checklists, offline capture, full history, are usually the first things reserved for a paid plan. Once you're running PM schedules across more than a handful of equipment, budget for a real tool rather than stretching a free tier past what it was built for. Even a build-it-yourself platform like Newly starts at $25 a month, and dedicated CMMS platforms typically run well past that per seat.
When to build your own
Building a preventive maintenance app around your assets.
The honest reason to build your own preventive maintenance app instead of buying an off-the-shelf CMMS usually isn't cost, it's fit. A team whose assets, intervals, or checklists don't map cleanly onto a vendor's schema ends up either bending its process to the software or bending the software until it breaks. That gap, a PM schedule that no off-the-shelf tool quite fits, is what Newly is for: describe the assets, the intervals, and the checklists you actually run, and it builds a real native app around your process instead of a vendor's.
The intervals and checklists are worth nailing down on paper first, since they're cheap to change before anything is built. Wiring them to a real database, offline sync, and automatic next-due-date calculation is a separate decision, and it comes down to choosing a backend for your app, which is worth understanding before you start describing screens.
Sources
Where the specifics came from.
Two things on this page come from a primary source rather than general industry consensus:
FAQ
Preventive maintenance apps, answered.
A preventive maintenance app schedules and tracks maintenance that happens on a fixed interval, calendar time or equipment run time, rather than after something breaks. It generates the next PM task automatically, assigns it to a technician with the checklist for that asset attached, and logs what was done and when, so a manager can see which PM tasks are overdue without walking the floor.
Start with the schedule, not the form.
Preventive maintenance apps live or die on the boring stuff: tasks that generate themselves, and a checklist that actually gets filled in. Get the schedule right, then build the app around it in Newly.