Maintenance planning and scheduling is the discipline that turns a maintenance strategy into work that actually gets done. Planning decides how each job should be executed; scheduling decides when. Together they are what separate a maintenance department that controls its week from one that is controlled by it. On most underperforming sites, the maintenance strategy is not the biggest problem. The path from strategy to executed work order is.
HolisticAM (Holistic Asset Management) is an Australian reliability engineering and asset management consultancy that designs and coaches work management on operating mine sites and plants. This guide covers the discipline end to end: what planning and scheduling each actually are, the work management cycle they sit inside, the roles that make them function, how to measure whether they are working, and the failure patterns we walk into most often.
Key takeaways: Planning and scheduling are different jobs. Planning is about the work itself: scope, parts, tools, steps and estimates, prepared before the job is due. Scheduling is about time and people: which ready jobs the crew executes next week, loaded against the hours actually available. Sites that merge the two, or let planners get dragged into today’s breakdowns, end up with neither.
In This Guide
- Planning and Scheduling Are Two Different Jobs
- The Work Management Cycle
- The Roles, and Why They Must Stay Separate
- What a Good Weekly Schedule Looks Like
- Measuring Whether It Is Working
- Where Planning and Scheduling Break Down
- How Planning Connects to Maintenance Strategy
- Getting Help with Planning and Scheduling
- Frequently Asked Questions
- Further Reading
Planning and scheduling are two different jobs
The fastest way to understand the discipline is to separate its two halves, because most sites blur them.
Maintenance planning answers “how”. For each incoming job, the planner defines the scope, the job steps, the parts and materials, the tools and equipment, the trades and estimated hours, and the permits and isolations. The output is a job plan (a work pack, on bigger jobs) that a tradesperson can execute without hunting for information. Planning happens in the future tense: planners work on jobs due weeks from now, not the breakdown happening today.
Maintenance scheduling answers “when and who”. The scheduler builds next week’s program from the backlog of planned, ready-to-execute work: jobs with parts on hand, resources matched to the trade hours actually available, and the plant access negotiated with operations. The output is a weekly schedule the crew is committed to, then a daily allocation run by the crew leader.
The reference doctrine for this split is Doc Palmer’s Maintenance Planning and Scheduling Handbook, and its core insight has held up for decades of practice. Planning multiplies the productive capacity of the crew you already have, but only if the planning function is protected from execution. A planner pulled into firefighting is a very expensive tradesperson’s assistant.
The work management cycle
Planning and scheduling sit inside a larger loop. The SMRP body of knowledge describes work management as the full cycle, and every stage feeds the next:
- Identify and validate. Work requests are screened so only genuine, non-duplicate work enters the system.
- Prioritise. A risk-based priority matrix, tied to asset criticality, decides what jumps the queue and what waits.
- Plan. The planner turns approved work into executable job plans: scope, steps, materials, estimates.
- Schedule. Ready work is loaded into the weekly schedule against forecast trade hours, agreed with operations.
- Execute. The crew works the schedule; the crew leader manages the day and the break-ins.
- Close out. What was done, what was found, and how the asset failed are recorded against the work order.
- Analyse and improve. Close-out data feeds failure analysis, plan corrections and the next round of strategy work.
The cycle is only as strong as its weakest stage. A site with excellent planners but no gatekeeping at work identification plans junk. A site with a disciplined schedule but no close-out standards learns nothing from the work it executes, and its failure history can never support the Weibull analysis or plan optimisation that should come next.
The roles, and why they must stay separate
| Planner | Scheduler | Crew leader / supervisor | |
|---|---|---|---|
| Tense | Future: jobs due in coming weeks | Next week: the committed program | Today: execution and break-ins |
| Owns | Job scope, parts, estimates, work packs | The weekly schedule and its trade-hour loading | Daily allocation, quality, in-field follow-up |
| Should never be | Chasing parts for today’s breakdown | Rewriting job scopes | Absorbing planning as a side duty |
On smaller sites one person may hold two of these hats, and that can work if the boundaries stay explicit: planning time is protected, and the schedule is still built from planned work rather than from memory. What does not work is the common drift where the planner becomes the crew’s parts chaser and administrative catch-all. The role exists to prepare future work; every hour spent on today’s emergency is an hour of next month’s productivity gone.
Palmer’s handbook argues that a properly protected planner can support twenty to thirty tradespeople. Whether or not a site hits that ratio, the direction of the argument is what matters: planning pays for itself through the productivity of the whole crew, which is exactly why it is the first casualty when it gets diluted. For the role itself in detail, including salary and career paths, see what a maintenance planner does.
What a good weekly schedule looks like
The weekly schedule is where planning either converts into output or quietly dies. The pattern that works:
- Built only from ready work. A job enters the schedule when it is planned, parts are on hand or staged, and access is achievable. Scheduling unplanned work is how schedules become wish lists.
- Loaded against real hours. The schedule is loaded to the trade hours the crew will actually have next week, after leave, training and known commitments. A schedule loaded to fantasy hours teaches everyone to ignore it.
- Agreed with operations. Plant access, isolations and production windows are locked in a weekly alignment meeting, not negotiated job by job on the day.
- Protected by break-in rules. Genuine emergencies displace scheduled work through an explicit decision with an agreed authority, not through whoever shouts loudest. Every break-in is recorded, because the break-in rate is one of the clearest signals of whether the site is running its plan or its plan is running behind its failures.
- Closed with a review. Schedule compliance is reviewed weekly: what was scheduled, what was done, and why the gaps happened. The point of the review is not the percentage; it is the reasons, which tell you which stage of the cycle to fix.
Measuring whether it is working
A small set of work-management measures, on consistent definitions (SMRP publishes the standard ones), tells the story:
- Schedule compliance: the share of scheduled work completed in the scheduled week. Its trend and its break-reasons matter more than any single number.
- Break-in rate: how much of the executed week was never on the schedule. The mirror of schedule compliance, and the honest measure of how reactive the site really is.
- Backlog in crew-weeks: total ready backlog divided by weekly crew capacity. Expressed this way it becomes a control number: enough backlog to build good schedules, not so much that priorities lose meaning.
- Planned versus reactive mix: the long-run indicator of whether planning and the underlying maintenance strategy are ahead of the failures or behind them.
- Wrench time: the fraction of a tradesperson’s day spent hands-on-tools rather than waiting, travelling or hunting for parts and information. Measured properly through work sampling, it is the baseline business case for planning investment, because almost everything that steals wrench time is something planning and scheduling exist to remove.
What we deliberately do not publish here is a table of universal benchmark targets. Definitions vary, site contexts vary, and a number imported from a conference slide has derailed more improvement programs than it has started. Baseline your own site on consistent definitions first; the direction of travel will be unambiguous. The formulas and traps behind the headline metrics are covered in our guide to maintenance and reliability KPIs.
Where planning and scheduling break down
The failure patterns repeat across industries:
- Planners absorbed into the day. The single most common defect. The org chart says planner; the diary says firefighter.
- The schedule as a wish list. Unplanned work scheduled, fantasy hours loaded, and by Wednesday the week is improvised.
- No gatekeeping at work entry. Duplicate, invalid and “while you’re there” work flooding the backlog until priorities are noise.
- Parts arriving after the job starts. Kitting and staging treated as optional; wrench time pays the bill.
- Close-out as a formality. One-line histories and no failure coding, which starves every downstream analysis. Getting failure data recorded against a usable standard such as ISO 14224 is what makes the history worth having.
- Planning quality nobody checks. Job plans that are really just titles; estimates never compared with actuals; no feedback loop from the trades who execute them. The fix is a working feedback habit, which is also why specific, executable work instructions matter more than volume of paperwork.
How planning connects to maintenance strategy
The strategy work that feeds the planner, FMECA, RCM and task optimisation, is what HolisticAM’s reliability engineering service delivers.
Planning and scheduling deliver whatever the strategy feeds them, which is why they cannot fix a broken strategy on their own. The failure modes and task decisions come from FMECA and RCM work upstream; a PM program that generates work without reducing failures needs a maintenance task optimisation review, not a better schedule for the wrong tasks. The dependable pattern: strategy decides what work exists, planning makes it executable, scheduling makes it happen, and close-out data flows back to improve all three. On one new iron-ore plant we built that chain from the start: 353 planned routine tasks across 23 asset lines, delivered CMMS-ready before first ore, so the crews ran a schedule from day one instead of discovering the backlog the hard way.
Getting help with planning and scheduling
HolisticAM designs and coaches maintenance planning and scheduling for heavy industry: work management process design, planning function establishment, weekly scheduling routines, and side-by-side coaching of planners, schedulers and supervisors on the live backlog. The starting point we recommend is evidence rather than a retainer: a fixed-scope work management audit that maps where your cycle leaks, then a sequenced fix. See our maintenance management services or talk to our team.
Frequently asked questions
What is the difference between maintenance planning and scheduling?
Planning defines how a job will be done: the scope, job steps, parts, tools, trades and time estimates, prepared in advance so the work is executable without delays. Scheduling defines when the job will be done and by whom, building a weekly program from planned, ready work loaded against the trade hours actually available. Planning is about the work; scheduling is about time and people.
What is a job plan in maintenance?
A job plan is the executable package a planner prepares for a maintenance task: the scope and job steps, required parts and materials, tools and equipment, trade requirements and estimated hours, plus permits, isolations and relevant drawings. On larger jobs it grows into a work pack. A good job plan lets a tradesperson start work without hunting for information, and it improves each cycle through feedback from the people who execute it.
How far ahead should maintenance work be planned and scheduled?
Planning works in a rolling horizon of several weeks to months ahead, so parts can be procured and access negotiated before jobs fall due; the horizon we typically design is a rolling twelve weeks. Scheduling commits one week at a time: a weekly schedule locked with operations, then daily allocation by the crew leader. The further ahead the planning horizon reaches, the less the week depends on luck.
Who should build the weekly maintenance schedule?
The scheduler (or scheduling function) builds the draft from planned, ready backlog, loaded against forecast trade hours. It is then agreed with operations and maintenance supervision in a weekly alignment meeting, and the crew leader runs daily allocation from it. What matters more than the job title is the sequence: the schedule is built from ready work, agreed jointly, and protected by explicit break-in rules.
Where should a site start improving planning and scheduling?
Start with a diagnostic, not a template. Audit the whole work management cycle: how work enters the system, backlog health, plan quality, schedule loading and compliance, break-in rate, and close-out quality. The audit shows which stage is leaking and in what order to fix it; sites that skip it usually fix the visible symptom while the real constraint sits two stages upstream.