What a Maintenance Planner Actually Needs From a CMMS (or a Planning-First Alternative)

The planner who opens a CMMS on Monday morning and can't find the schedule

It's Monday, 6:40 a.m. The planner pulls up the CMMS before the shift meeting, looking for the week's PM schedule — what's due, what's overdue, which technician is covering which asset. Instead the screen opens on a request queue: fourteen new tickets from the floor, sorted by submission time, not by criticality or due date. There's a button to create a work order. There's no button that says "show me this week's plan." The planner ends up exporting data to a spreadsheet anyway, because that's the only place the actual schedule lives.

This isn't a training problem. It's a design problem. Most CMMS platforms were built to capture and route work requests — a technician-facing, request-in/ticket-out tool. The planner's job is upstream of all that: deciding what should be done, when, by whom, with what parts on hand, before a single work order is ever opened. When the software only models the technician's half of the job, the planner ends up doing the planning half in a side spreadsheet no matter what the CMMS costs.

By the end of this piece you'll be able to name the specific capabilities a planning-first system needs — and tell, in about ten minutes with any CMMS demo, whether it was actually built for your job.

The planner's job is not the technician's job

A maintenance technician's job is execution: get the work order, go to the asset, do the task, log the result. A maintenance planner's job is everything that has to happen before that work order exists — rank assets by criticality, set PM intervals, sequence the week so techs aren't crossing the plant floor four times a day, check parts are on hand, and keep a backlog from quietly growing into next month's fire drill.

These are different cognitive jobs, and they want different screens. A technician wants "what's my next task." A planner wants "what's the state of the whole program" — a week view, a backlog aging view, a compliance trend, a criticality-ranked asset list. Software built around the ticket is good at the first question and weak at the second. That's the core distinction behind the planning-first vs. work-order-first framing we use across this site: a system is planning-first if the schedule is the primary object, and work-order-first if the ticket is.

If you're evaluating any platform — CMMS or otherwise — against this role, it helps to work from a structured list rather than a sales demo's default tour. Our CMMS buying checklist walks through the questions worth asking in that first call, most of which have nothing to do with price.

What a planning-first CMMS for maintenance planners actually does

A genuine planning-first CMMS for maintenance planners — or a disciplined spreadsheet system doing the same job — needs to do five things well, independent of whatever ticket-handling it also offers:

1. Hold a criticality ranking, not just an asset list. Every asset gets scored on consequence of failure and likelihood of failure, and that score drives PM interval and response priority — not the order assets happen to appear in a list.
2. Store PM tasks by interval, not by date. A pump's lubrication task is defined once, tied to a trigger (time, meter reading, or condition), and the system should generate the next occurrence automatically rather than requiring the planner to re-enter it.
3. Show a forward schedule, not just a backward history. The planner's question is "what's coming in the next one to four weeks," and the view should be built around that horizon, not a chronological list of closed tickets.
4. Track backlog aging. Work that's been open 0–7 days is a different problem than work open 60+ days. A planning tool should bucket backlog by age so it's visible before it becomes the thing an auditor finds.
5. Produce a compliance number on demand. Not buried in a report nobody runs — visible, current, and defensible if a manager or auditor asks for it this afternoon.

None of these require artificial intelligence or a live dashboard. They require the schedule to be the primary object the software is organized around. A technician-facing CMMS can bolt pieces of this on, but it shows in the workflow — extra clicks to get from "open ticket" to "see the week," extra exports to get a backlog-by-age view the software wasn't built to produce natively.

PM compliance: the number a planner has to be able to produce on demand

PM compliance percentage is the single number that answers "is this program actually running." The calculation is simple: completed PMs ÷ scheduled PMs × 100, measured over a rolling window (commonly 30 days). If 48 PMs were scheduled this month and 41 were completed within the compliance window, that's 41 ÷ 48 × 100 = 85.4%.

The window matters as much as the ratio. A widely used convention — sometimes called the "10% rule" — only counts a PM as compliant if it's completed within 10% of its scheduled interval; a monthly PM completed on day 34 of a 30-day interval falls outside that window and counts against the score even though it got done (MaintainX Learning Center, 2025). Maintenance experts treat 90% as the world-class standard for PM compliance, with industry averages commonly running 75%–80% — and a program below 80% is generally considered not functioning effectively (SMRP Best Practices, via eWorkOrders, 2025; MaintainX Learning Center, 2025).

A planner needs to be able to pull this number without building a pivot table from scratch every time someone asks. That's a planning-tool requirement as much as a reporting requirement — the schedule has to be structured cleanly enough, with real scheduled and completed dates per asset, that the ratio falls out of the data rather than having to be reconstructed.

Wrench time is the real lever, not headcount

Here's a number that should bother any plant manager thinking about adding headcount before fixing planning: the average maintenance technician spends only about 25%–35% of a shift on actual hands-on repair work — "wrench time." The rest goes to travel, waiting on parts, looking for information, and rework (Cryotos, citing Plant Engineering/Reliable Plant, 2025).

Effective maintenance planning and scheduling — sequencing jobs, staging parts in advance, batching work by location — can raise wrench time from that typical ~30% toward 45%–55% or higher, which functions like adding crew capacity without adding a single hire (Reliability Academy, 2025). This is the single strongest argument for treating planning as its own discipline rather than a side task a technician or supervisor squeezes in between work orders. It also explains why reactive programs stay expensive even with a full crew: the U.S. Department of Energy documents that reactive maintenance costs 3 to 5 times more than planned preventive maintenance once emergency labor, expedited parts, and production loss are counted, and a functioning PM program produces an estimated 12%–18% cost savings over a reactive one on average (U.S. DOE/FEMP, 2010; 2024 via eWorkOrders). At the average facility, more than 55% of maintenance resources are still spent reactively (U.S. DOE/FEMP, 2010) — which is largely a planning gap, not a staffing gap.

Why most CMMS platforms are built for the technician, not the planner

This isn't a conspiracy — it's a pricing structure. Limble, MaintainX, Fiix, and UpKeep all charge per user per month, which means the vendor's revenue grows every time the plant hires a technician. The natural product incentive under that model is to make the technician's mobile experience excellent — fast ticket creation, quick photo capture, simple checklist completion — because that's the seat generating the bill. The planner's screens (schedule view, backlog aging, criticality ranking) are real but secondary, and on several of these platforms they sit behind a higher tier.

Some structural specifics worth knowing before a demo call, each independent of pricing: Limble does not publish flat per-user rates and instead routes buyers to a calculator that varies with user count and billing cycle. MaintainX publishes tiered per-user pricing, and preventive maintenance itself is excluded from its free tier, with meter-based PM, parts inventory, purchase orders, and API access gated to a higher tier. On both platforms, "requester" accounts — people who only submit requests, not planners or technicians — are free, which quietly concentrates the real cost on exactly the planner and technician seats doing the scheduling work. Fiix, now owned by Rockwell Automation, is positioned around an IoT/AI integration path rather than a flat fee. UpKeep's lower tiers commonly omit checklist and meter-based trigger features that a planning-first workflow depends on.

None of this makes per-user software wrong for every plant — a facility already standardized on one of these platforms for work-order routing may reasonably keep it. But it explains why a planner evaluating a CMMS often finds the tool capable at the technician layer and thin at the planning layer: that's the seat the business model rewards building for. Our breakdown of flat-fee vs. per-user CMMS pricing and the broader CMMS pricing models explained piece both walk through how these structures play out as crew size grows — useful reading before any contract gets signed.

Evaluating any system — CMMS or spreadsheet — against the planner's job

Before paying for anything, it's worth testing a candidate system — CMMS, spreadsheet, or otherwise — against the planner's actual week rather than a vendor's feature list. Ask it to:

• Show the next 14 days of scheduled PMs, sorted by criticality, without an export.
• Produce a current PM compliance percentage with the calculation window stated.
• Bucket open work orders by age (0–7, 8–30, 31–60, 60+ days).
• Show which PM tasks are tied to which parts, and whether those parts are in stock.
• Let a planner re-sequence next week's plan around a single technician's schedule in under five minutes.

If the honest answer is "not without building something custom," that's a signal the tool was built around the ticket, not the plan — worth knowing before the first invoice, not after. Our guide to choosing a CMMS for a small manufacturing plant goes deeper on sizing a system to a specific headcount and asset count rather than a vendor's largest customer story.

For a plant not yet ready to commit to a per-user platform, a structured spreadsheet system — an asset register, a criticality matrix, a PM interval worksheet, a backlog tracker, and a compliance calculation built from real dates rather than a vendor's black box — covers every item on that list above today, at a flat one-time cost rather than a bill that climbs with every hire. The MaintenancePlanning Complete Kit bundles those templates for exactly that reason: planning-first, not request-first, and not metered by headcount.

If what you actually want eventually is a connected, planning-first system — one schedule, live compliance tracking, no spreadsheet reconciliation — that's the direction our own CMMS is headed, and you can join the waitlist to get access as it ships. Until then, the templates are built to do the planner's job on their own, with or without a CMMS behind them.