What a Maintenance Planner Actually Does (And Why It Isn't "Doing Maintenance")

A technician spends twenty-five minutes hunting for a gasket. Not fixing anything — walking to the storeroom, finding the bin empty, checking a second location, calling the supervisor, deciding to substitute. The wrench never moves. Now multiply that by every job, across a crew, across a year. The hours add up to a full position's worth of lost work.

That waste is not a labor problem. Your technicians are not slow. It's a planning problem — and the person who solves it is a maintenance planner, a role most mid-market teams have never seen done well, which is exactly why they don't know what they're missing.

The one-line definition

A maintenance planner makes sure work is ready to execute before it reaches the floor: scoped, sequenced, kitted, and scheduled. The planner works ahead of the crew so the crew can work without interruption. When a tech picks up a planned job, every question is already answered and every part is already staged. The tech's entire shift goes to turning wrenches.

That's the whole idea. The planner trades their time, spent in advance, for the crew's time, multiplied across everyone who touches the work.

The six core jobs of a planner

The role has a handful of distinct responsibilities. Done together, they convert a stream of vague requests into a queue of execution-ready work.

Scoping work and writing job plans

The planner takes a request — "Pump 3 is making noise" — and turns it into a defined scope: what's actually being done, what "done" looks like, and a reusable job plan with step-by-step instructions. The first time a job is planned takes effort. Every time after, the plan is pulled off the shelf and refined.

Estimating labor, crafts, and duration

How many techs, which crafts, how long? The planner estimates so the schedule can be built honestly. Early estimates are imperfect; they get better as actuals come back. But even a rough estimate beats the alternative, which is a schedule built on hope.

Kitting parts and staging materials

The planner confirms parts are in stock, reserves them, and stages them — physically or in a kit — so the tech isn't walking to the storeroom mid-job. This single function recovers more wrench time than almost anything else.

Building and protecting the weekly schedule

The planner assembles next week's work into a realistic plan matched to available capacity, then protects it from the constant pull of "can you just look at this real quick." (Planning and scheduling are distinct jobs that often live in the same person — see planning vs. scheduling for why conflating them backfires.)

Grooming the backlog

The planner keeps the backlog healthy: prioritized, de-duplicated, free of dead work orders, and stocked with enough ready work to fill the coming weeks. A groomed backlog is the raw material of a good schedule.

Closing the loop

After the work is done, the planner captures actuals — how long it really took, what parts were really used, what the plan got wrong — and feeds that back into the job plan. Over time, the library of plans compounds in quality. This loop is what separates a planning program from a planning attempt.

What a planner is not

The fastest way to understand the role is by what it isn't.

A planner is not a supervisor. The supervisor runs today's crew and handles today's problems. A planner is not a technician — they don't turn wrenches, and putting your best tech in the chair to "plan in their spare time" gets you neither planning nor wrenching. A planner is not a parts clerk, though they work closely with stores. And a planner is not the CMMS administrator, though they live in the system daily.

The most common confusion is "planner equals scheduler." They overlap, but they answer different questions, and treating them as one job is a quiet, recurring source of chaos. That distinction gets its own full treatment here.

The "ahead of the work" principle

Here's the mental model that makes the role click. A planner works one to four weeks out. A supervisor works today. Those are different time horizons, and they pull a person in opposite directions.

When you ask one person to do both, today always wins. The radio is loud. The breakdown is now. The planning work — quiet, deferred, important — gets pushed to "when things calm down," which is never. The role collapses into expediting, and you're back to firefighting with extra paperwork.

Keeping the planner ahead of the work, structurally separated from today's fires, is the entire point. It's also why the function is so hard to bootstrap from inside a reactive shop without protecting it deliberately.

Why most mid-market teams don't have one

Good planners are scarce. The skill set — part craftsperson, part organizer, part data-handler — is uncommon, and people who've actually run a compliant weekly schedule command a premium. Fully loaded, a planner runs roughly $85k–$130k (the full cost math is its own article), and that's the first headcount cut when budgets tighten, because leadership can't see what it does.

And there's a chicken-and-egg trap: it's hard to evaluate a planner, or even justify the hire, if you've never had one and don't know what good looks like. So the gap persists, invisible, expensive, and self-perpetuating.

How much planner do you actually need?

The standard reliability benchmark is one planner per 15–20 technicians. That ratio is a useful starting point and a misleading stopping point, because it assumes a mature operation where the planner only plans. In a shop that's still mostly reactive, a single planner can't cover 18 techs on day one — too much of the work arriving is unplannable emergencies, and too little history exists to build job plans from. The ratio is where you're headed, not where you start.

Two things move the number. The first is your reactive ratio: the more of your work that arrives as unplanned breakdowns, the fewer techs one planner can support, because emergencies can't be planned ahead and they pull the planner into expediting. The second is the maturity of your job-plan library. A planner with a deep library of refined plans spends minutes attaching a proven plan to a work order; a planner building plans from scratch spends hours per job. So the same person covers far more techs in year two than in year one.

The practical read: if you have 12 technicians, you don't need 0.6 of a planner in a way you can hire. You need the planning function sized to your actual reactive load and plan-library maturity — which is precisely the case for buying the capacity in a right-sized increment rather than forcing it into a fixed full-time headcount.

How to tell the function is missing

You don't need a benchmark study to spot the gap. Watch for these:

Technicians regularly leave a job to chase parts that weren't staged.
There's no real weekly schedule — just a queue of work orders the crew pulls from reactively.
PMs slip routinely and nobody's quite sure what the on-time rate is.
The backlog is a black hole: work orders go in, some come out, no one's grooming it.
Your best people spend their day deciding what to do next instead of doing it.
"How long will that take?" is answered with a shrug.

If three or more of these are familiar, the planning function isn't underperforming — it's absent.

The takeaway

Planning is a distinct discipline. The deliverable isn't maintenance; it's execution-ready work — scoped, kitted, scheduled, and handed to a crew that can then do nothing but execute. Most mid-market teams are missing it not because they're badly run, but because they've never seen it run and can't justify a scarce, expensive hire to fill a gap they can't quite name.

The good news: you can buy the outcome without buying the headcount. Planning is a capacity, and capacity can be sized to what your operation actually needs.

What you're buying, concretely, is the six functions above run consistently by someone who stays ahead of the crew: job plans written and refined, work kitted, a weekly schedule built and protected, the backlog groomed, and the loop closed. Whether one person inside your walls does that, or the capacity is delivered as a service sized to your tech count and reactive load, the deliverable is identical — execution-ready work, every week, handed to a crew that can then do nothing but turn wrenches.

See what the planning function would look like for your site. Configure it →