Maintenance planning and scheduling: the weekly cycle that keeps a plant running
Planning decides how a job will be done, scheduling decides when and by whom, and the weekly cycle with a freeze in it is what makes either measurable. What the plan, program and schedule each are, what makes work ready, the cycle step by step, one path for break-in work, the five measures, and the CMMS setup that holds it, with a free weekly schedule template.
Key takeaways
- Maintenance planning decides how a job will be done. Scheduling decides when, and by whom. Run by the same person in the same hour, both are done badly.
- The weekly cycle is the heart of it: capacity set, a draft built from ready work, agreed with operations, frozen on a fixed day, executed, then reviewed. The freeze is what makes the measures mean anything.
- Work is only scheduled when it is ready: scoped, with a job pack, parts on hand, permits known and access confirmed. A schedule built from unready work is a list of hopes.
- Break-in work is controlled by one approval path, not by banning it. The measure is how much of the executed week was added after the freeze, and why.
- The measures that tell the truth are schedule compliance, PM compliance, break-in share, backlog in crew weeks and the planned share of work. Defined once, reported weekly, read as a set.
Maintenance planning and scheduling is the process that turns a backlog of identified work into work that gets done as intended. Planning decides how a job will be done: its scope, steps, trades, durations, parts, permits and access. Scheduling decides when it will be done and by whom, by loading ready jobs into the hours available for the coming week, agreeing that with operations and freezing it.
Most sites have both in some form. What separates the ones that run calmly from the ones that run on the phone is the cycle: a fixed weekly rhythm with a freeze in it, a gate that only lets ready work through, one path for break-in work, and a handful of measures defined once and read together every Monday.
This guide covers what the plan, the program and the schedule each are, where work comes from and how the backlog is kept honest, what makes a job ready, the weekly cycle step by step, how break-in work is controlled, the measures, the CMMS setup that holds all of it, and the mistakes that bring it down. A weekly schedule template comes with it.
Free download
Weekly maintenance schedule template
A capacity tab by trade, a schedule tab laid out by day and work order, a break-in log, and schedule compliance and break-in share calculated from what you enter.
Planning and scheduling are two jobs
The titles are used interchangeably and the jobs are not the same. A planner works ahead of the schedule, in the field and in the CMMS, making jobs ready. A scheduler works in the week before execution, fitting ready jobs to the hours available and negotiating equipment access with operations. The supervisor works in the day, assigning people and dealing with what the day brings. Planner, scheduler and long term planner sets the three roles out in detail.
When one person does all three, the urgent always beats the important. The planner is pulled into today's breakdown, no jobs are made ready for next week, next week's schedule is built from unready work, half of it stalls, and the breakdowns continue. Protecting the planner from the day is the first structural decision, and it is a management decision rather than a planning one.
Plan, program, backlog, schedule
Four words carry most of the confusion, so they are worth separating before the cycle makes sense.
| Term | What it is | Who owns it | How often it changes |
|---|---|---|---|
| Maintenance strategy | Which failure modes are managed, and by what kind of task, decided by analysis or by template | Reliability engineering | When the analysis is revisited |
| Maintenance plan | The recurring tasks and intervals for an asset, held in the CMMS, that generate preventive work orders | Planner, from the strategy | When wear life or failure data says the interval is wrong |
| Maintenance program | All the maintenance plans across the site, and the preventive work they generate | Maintenance manager | Standing, reviewed by asset class |
| Backlog | Every identified work order not yet done, preventive and corrective, with its priority and readiness | Planner | Daily, as work is raised and closed |
| Weekly schedule | The specific work orders assigned to specific days and crews for the coming week | Scheduler, frozen by the superintendent | Rebuilt every week, frozen once |
| Daily schedule | Who does which job today, from the frozen week | Supervisor | Every day |
Where work comes from, and keeping the backlog honest
Work arrives from four places: the preventive program, which is predictable; condition monitoring and inspection findings, which arrive with some warning; notifications raised by operators and tradespeople, which arrive without any; and projects and improvements, which arrive on their own timetable. Every one of them lands in the backlog, and the backlog is only useful if it is kept honest.
Honest means every work order has a priority set by a rule rather than by who shouted, a readiness status that reflects whether it could be scheduled tomorrow, and an age. The backlog is measured in crew weeks, by trade and priority, so the number means something. A corrective backlog that keeps growing is a reliability problem, not a scheduling one, and the backlog is where it shows first.
- Set priority by consequence, from the same criticality scale the strategy uses, so urgent means the same thing on every work order.
- Review the backlog weekly: duplicates closed, stale notifications cancelled with a reason, readiness updated.
- Report the backlog in crew weeks by trade, and separately for the work that is ready.
- Treat a growing corrective backlog as a signal to look at the strategy, not as a reason to add overtime.
Ready to schedule
The gate between planning and scheduling is readiness. A work order is ready when it has a scoped job pack, parts received and kitted, permits and isolations identified, access and lifting confirmed, and any preparation by operations agreed. The scheduler draws only from ready work. A schedule built from unready work is a list of hopes, and the week spends itself waiting.
Readiness is a status on the work order, set by the planner and visible to the scheduler, and it is worth configuring the CMMS so a job cannot be scheduled without it. The share of the backlog that is ready, by trade, is one of the most useful numbers a planner reports, because it says whether next week's schedule can be filled without compromise.
Scheduling unready work does not get it done sooner. It gets it started, stalled and rescheduled.
The weekly cycle
The cycle below assumes a Monday to Sunday execution week. The days shift by site; the order and the freeze do not. Each step has an owner and an output, and the output of one is the input to the next.
Week before
Monday
Capacity set
Supervisors
Tuesday
Draft schedule built
Scheduler
Wednesday
Operations alignment
Scheduler and operations
Thursday
Schedule review meeting
Maintenance superintendent
Friday
Schedule frozen
Maintenance superintendent
Execution week
Daily
Daily schedule and break-in control
Supervisors
Daily
Progress and feedback
Tradespeople and supervisors
Week after
Monday
Compliance review
Planner and superintendent
↻ The review feeds the next draft
| When | Step | Owner | Output |
|---|---|---|---|
| Week before, Monday | Capacity set | Supervisors | Available hours by trade for the coming week, after leave, training and standing commitments |
| Week before, Tuesday | Draft schedule built | Scheduler | Ready-to-schedule work loaded to the capacity, in priority order, with the PM program first |
| Week before, Wednesday | Operations alignment | Scheduler and operations | Equipment access and production windows confirmed against the draft |
| Week before, Thursday | Schedule review meeting | Maintenance superintendent | Conflicts resolved, the schedule agreed by operations, maintenance and the planner |
| Week before, Friday | Schedule frozen | Maintenance superintendent | The frozen schedule issued. Anything added after this is break-in work |
| Execution week, Daily | Daily schedule and break-in control | Supervisors | Each day's work assigned by person, break-in requests through the one approval path |
| Execution week, Daily | Progress and feedback | Tradespeople and supervisors | Work orders closed with hours, findings and job plan feedback the same day |
| Week after, Monday | Compliance review | Planner and superintendent | Schedule compliance, break-in share and the reasons for every miss, fed into next week's draft |
What each step is for
Capacity comes first because everything else is loaded into it. Supervisors set the hours actually available next week, by trade, after leave, training, standing meetings and the hours that permits and travel will take. Loading a schedule to nameplate crew hours is the most common reason compliance sits at sixty per cent.
The draft is built from ready work in priority order, with the preventive program first, because PM compliance is the discipline that stops the corrective backlog growing. The scheduler levels the draft against capacity by trade and groups work by area and equipment, so one isolation and one access serve several jobs. Operations alignment is where the draft meets production: which equipment can be released, on which days, for how long.
The review meeting is short and decides. Conflicts are resolved, what operations cannot release is moved, and the schedule is agreed by the people who will have to live with it. Then it is frozen on a fixed day by a named person, and from that moment every change is a break-in that goes through the approval path and is counted. The freeze is what gives schedule compliance its meaning.
During the week the supervisor turns the frozen schedule into daily assignments and handles break-in requests. Tradespeople close work orders the same day with hours, findings and feedback on the job plan, which is how the next pack gets better. On Monday the planner and superintendent review compliance and the break-in share, with a reason against every miss, and those reasons shape the next draft.
Break-in work: one path, counted
Break-in work is not the enemy. Plant fails, and some of it has to be fixed today. The problem is break-in work that arrives by phone, displaces whatever was nearest, and is never counted. The fix is one approval path, usually the supervisor with the superintendent as escalation, that asks two questions of every request: can this wait for next week's schedule, and if not, which scheduled job does it displace?
Approved break-ins go onto the schedule, marked as added after the freeze. At the Monday review the break-in share and the reasons are read together, because the share has three different causes with three different fixes. A reliability cause means the strategy on that equipment needs work. A planning cause, where the job was known and not scheduled, means the backlog review is not catching it. A discipline cause, where it could have waited, means the approval path is not being used.
Ban break-in work and it goes underground. Count it and it becomes a measure you can act on.
The measures, read as a set
No single number describes a planning and scheduling process. Five, defined once and read together every week, do. The SMRP metrics give standard definitions, and the point of adopting them is that the numbers stop being argued about and start being used.
| Measure | What it is | What a bad number usually means |
|---|---|---|
| Schedule compliance | Scheduled hours done as scheduled, over all scheduled hours, against the frozen schedule | Unready work scheduled, capacity overstated, or break-in displacing the plan |
| PM compliance | Preventive work orders done within their due window, over all due | The program is being traded for corrective work, and the backlog will grow |
| Break-in share | Hours added after the freeze, over all hours worked | Reliability, planning or discipline, and the reasons say which |
| Backlog in crew weeks | Open work hours by trade over weekly capacity, with the ready share separately | Over four to six weeks: under-resourced or a reliability problem. Under two: work is not being identified |
| Planned share | Hours on work with a job pack, over all hours worked | The planner is being pulled into the day, or readiness is not being gated |
- The Schedule Compliance Calculator works out compliance and break-in share from a week's hours, the same way the template does.
- Tool time studies, done occasionally rather than weekly, show how much of a scheduled hour reaches the job. They explain why compliance can be high and output low.
- Report the measures on one page, weekly, with the trend. A quarter of honest trend is worth more than any target.
The preventive maintenance plan, and keeping it right
The preventive program is where the weekly cycle meets the maintenance strategy. Each maintenance plan in the CMMS carries a task, an interval and a basis for that interval: a wear rate, a failure history, a manufacturer recommendation, a statutory requirement or a template by criticality. The basis is what lets the interval be challenged later.
Intervals drift wrong in both directions. Tasks inherited from a vendor manual are often too frequent for the duty, and tasks set by calendar on equipment that wears by the tonne are wrong whenever throughput changes. The feedback loop that fixes this is small: findings and as-found condition recorded on every preventive work order, reviewed by asset class, and intervals adjusted with the reason logged. Sites call it PM optimisation, and it is where a planner's time pays back most.
The master data underneath the plans decides whether any of this works. A plan on the wrong functional location, a task list with no durations, or a bill of materials with no parts produces a work order that cannot be made ready, and the schedule inherits the gap.
The CMMS setup that holds the cycle
The process runs on whichever system the site has. SAP, Maximo, Pronto and the rest all support it, and the CMMS or EAM choice matters far less than the configuration. What the cycle needs from the system is specific.
- Work order statuses that match the gates: raised, approved, planned, ready, scheduled, in progress, complete, closed. The ready status is the one most systems are missing.
- A priority code set by a consequence rule, with the rule written down where people raise work.
- Resource capacity by trade and week, so the schedule can be levelled in the system rather than in a spreadsheet beside it.
- A way to mark work added after the freeze, so break-in share is a query and not a recollection.
- Job plans and task lists with durations and materials, so a preventive work order arrives planned.
- Closure fields for findings, as-found condition and feedback, short enough that tradespeople fill them in.
The CMMS does not create the cycle. It holds the one the site decided on, or it holds the absence of one.
Common mistakes
- One person planning, scheduling and supervising, so planning never happens.
- A schedule loaded to nameplate crew hours, so compliance is low before the week starts.
- Unready work scheduled to fill the week, then stalled on parts and permits.
- No freeze, or a freeze that moves, so compliance is meaningless and nobody trusts it.
- Break-in work by phone, uncounted, so the plan is displaced invisibly.
- Measures defined differently each week, and argued about instead of acted on.
- Preventive intervals inherited from a manual and never challenged against findings.
- Readiness and priority held in a planner's head, so the cycle stops when they are on leave.
Putting the cycle in place
Separate the roles
Planner, scheduler and supervisor defined, and the planner protected from the day.
Clean the backlog
Priority by rule, readiness on every work order, duplicates and stale work closed.
Configure the system
Statuses, capacity, the after-freeze flag and closure fields set up in the CMMS.
Run the cycle
Capacity, draft, alignment, review, freeze, execute, review, on fixed days.
Count break-in
One approval path, every addition marked, reasons read weekly.
Report and adjust
Five measures on one page with the trend, and intervals corrected from findings.
Separate the roles
Planner, scheduler and supervisor defined, and the planner protected from the day.
Clean the backlog
Priority by rule, readiness on every work order, duplicates and stale work closed.
Configure the system
Statuses, capacity, the after-freeze flag and closure fields set up in the CMMS.
Run the cycle
Capacity, draft, alignment, review, freeze, execute, review, on fixed days.
Count break-in
One approval path, every addition marked, reasons read weekly.
Report and adjust
Five measures on one page with the trend, and intervals corrected from findings.
Common questions
What is maintenance planning and scheduling?
Planning is the work of deciding how a maintenance job will be done: its scope, steps, trades, durations, parts, permits and access, recorded in a job pack. Scheduling is deciding when it will be done and by whom, by loading ready jobs into the available hours for a coming period, agreeing that with operations and freezing it. Together they are the process that turns a backlog of identified work into work that gets done as intended.
What is the difference between a maintenance plan, a maintenance program and a maintenance schedule?
The maintenance plan, held in the CMMS, is the set of recurring tasks and intervals that the maintenance strategy produced for an asset. The program is all of those plans across the site, which generate the preventive work orders. The schedule is the list of specific work orders, preventive and corrective, assigned to specific days and people for a coming week. Plans and programs are standing; the schedule is rebuilt every week.
What does a maintenance planner do?
A planner scopes work in the field, writes the job pack, identifies and orders the parts, specifies the permits, isolations and access, estimates the hours and keeps the job plan library current, so that when a job is scheduled the crew can start it. A planner works a week or more ahead and should not be pulled into today's breakdowns, which is the most common way the role fails.
What does ready to schedule mean?
That a work order has everything it needs to be done when the schedule says: a scoped job pack, parts received and kitted, permits and isolations identified, access and equipment confirmed, and any operations preparation agreed. A scheduler should only draw from ready work. Scheduling unready work is how a week starts with half its jobs waiting on something.
How is schedule compliance calculated?
Scheduled work completed in the week it was scheduled, divided by all work scheduled for that week, usually in hours. It is only meaningful when the schedule was frozen before the week began, because a schedule edited during the week to match what happened scores a hundred per cent every time. The Schedule Compliance Calculator on this site works it out alongside break-in share.
How should break-in work be handled?
Through one approval path that asks whether the job can wait for next week's schedule, and if it cannot, which scheduled job it displaces. Approved break-ins go onto the schedule and are counted as added after the freeze. The weekly review then looks at the break-in share and the reasons, because a high share is either a reliability problem, a planning problem or a discipline problem, and each has a different fix.
What is a good schedule compliance target?
Commonly quoted targets sit around 85 to 90 per cent for schedule compliance and 10 per cent or less for break-in work, and a plant that has just introduced a frozen schedule usually starts well below that. The trend matters more than the target. A site that reports honestly and improves each quarter is in better shape than one that hits a number by editing the schedule.
Key terms
Plain-language definitions from our glossary for the concepts this article leans on.
Standards and further reading
- Best practices, metrics and guidelines for maintenance and reliability (SMRP)
- Recommended practices for planning, scheduling and cost engineering (AACE International)
- Operations and maintenance best practices guide (US DOE Federal Energy Management Program)
- ISO 55001:2024 Asset management system requirements (ISO)
- ISO 14224:2016 Collection and exchange of reliability and maintenance data for equipment (ISO)
- The Asset Management Landscape, third edition (GFMAM)
- Asset Management Council, Australian asset management community (Asset Management Council)
Related case studies and tools
- Work management and scheduling uplift (case study)
- Schedule Compliance Calculator (tool)
Related reading
Working through something like this?
See how we approach these initiatives, or tell us what you are dealing with.