Maintenance Planning and Scheduling: The Ultimate Guide

Maintenance planning and scheduling is the process of fully preparing each maintenance job before anyone is assigned to it, confirming it is ready, and then committing it to a specific week, crew and equipment window. The two functions run in a fixed sequence, and keeping that order is what makes the schedule hold.

Maintenance planning defines the work before a crew is assigned. The planner sets the scope and job steps, estimates the labor hours, and confirms the parts, tools, permits, isolations and access the job needs. Once all of these are confirmed, the job is marked as ready to schedule.

Maintenance scheduling is the work of assigning ready jobs to a specific week, technicians and equipment window, based on the labor hours available and the operating plan.

It also helps to be clear about what the process is not:

• It is not the due date on an ERP work order. A date shows when someone wants the job done, but it says nothing about whether the job can actually run on that day.
• It is not a list of tasks. A list with no labor estimate and no readiness check behind it tells the crew what to do, but not whether they will be able to do it.

Planning decides what the job is, how it will be done and what it needs. Scheduling decides who will do it, when, and in which equipment window. While planning removes delays during a job, such as a technician stopping to find a missing part, scheduling removes delays between jobs, such as a crew finishing early with nothing ready to start next.

The table below compares the two, using the feedwater pump bearing job as an example.

The handoff between the two functions is where most plants get into trouble. Scheduling should only draw from work that planning has marked as ready, which makes the ready backlog the scheduler's only legitimate source of work. When a scheduler pulls in a job that is still waiting on a part or a permit, the job stops, and the rest of the week has to be rearranged.

Keeping to this rule also reduces downtime, because equipment comes out of service only when the crew can finish the job.

Why Combining the Planner and Scheduler Roles Breaks Both

When one person owns both planning and scheduling, today's urgent work almost always wins over next week's preparation. A planner who is pulled into chasing parts for a running breakdown stops building packages, and two weeks later the scheduler has very little ready work to load. The problem sits in the role design, so the answer is to set clear ownership:

• Keep the planner on future work: The planner prepares next week's jobs, not today's breakdowns.
• Separate weekly scheduling from daily supervision: The scheduler builds the weekly schedule from the planner's ready backlog, and the crew supervisor owns the daily schedule.
• Protect planning time in small teams: If one person holds both roles, block fixed planning days.

The maintenance planning and scheduling process steps often vary in number based on whether intake and prioritization are considered separate, readiness is considered as a step, or whether closeout is part of the process. However plants should note that a list of steps is not enough if work can move forward before the previous step is finished. Each step needs a clear owner and a check that must be met before the job moves on. This guide uses seven steps because each one ends in a decision someone signs off on, with an exit condition that must be true before the work moves on.

The steps described below follow the bearing job on feedwater pump B, which has an installed spare pump A.

Step 1: Capture and Screen the Work Request

Every request should be logged in one place, whether it comes from operator rounds, inspections, preventive maintenance triggers, condition alerts or production. Each request should be screened for the following before any planning time is spent on it:

• Check for duplicates: An open inspection request for the same pump B bearing is merged with the new one.
• Confirm the scope is clear and the correct asset or functional location is named.
• Stop bypassed requests: Informal requests leave no record, so the schedule loses hours nobody can see.

Exit condition: Request validated, asset identified and duplicates checked

Step 2: Prioritize by Asset Criticality and Risk

Priority should always be set before planning starts. Most plants use a priority matrix that weighs equipment criticality against the safety, environmental, production and cost impact of a failure. RIME (Ranking Index for Maintenance Expenditures), which multiplies a criticality score by a work type score, is one example; use the method your site has approved.

Exit condition: Priority code and required-by date set.

Step 3: Plan the Job and Build the Work Package

The planner turns the request into a work package a qualified technician can follow without stopping to ask questions. A complete package contains:

• Scope and step-by-step job instructions
• A labor estimate by craft
• A parts list, with stock checked and parts reserved
• Special tools, lifting gear and access equipment such as scaffolding
• Safety requirements, including permits and isolation points
• Drawings, manuals and the equipment's own past work orders
• Notes from the last time the same job was done

For repeat jobs, the planner starts from the saved job plan and the hours actually recorded last time. For example, the last bearing change on pump B sets the estimate at two mechanics for six hours.

Exit condition: Work package complete, estimate set and parts reserved.

Step 4: Confirm the Job Is Ready to Schedule

Once parts, permits, isolations, access, tools and the equipment release are confirmed, the job is marked as ready. It then joins the ready backlog, which is the pool of fully planned jobs the scheduler can choose from. For example, the bearings for pump B arrive Monday, the electrical and valve isolations are listed, and operations agree the pump can be released midweek, so the job is marked as ready.

Exit condition: Job marked ready and counted in the ready backlog.

Step 5: Build and Lock the Weekly Schedule

The scheduler selects ready jobs by priority and due date and matches them to next week's labor hours by trade. Operations agree to the equipment windows in a weekly scheduling meeting, usually midweek, and the schedule is published and locked a few days before the week starts so the storeroom can stage parts. After that, only emergencies can change it. For example, the pump B bearing job is grouped with an alignment check and a lubrication task on the same pump in one Wednesday window, so one isolation covers three jobs.

Exit condition: Schedule published and frozen, with operations sign-off recorded.

Step 6: Execute and Manage the Daily Schedule

The crew supervisor turns the weekly schedule into daily assignments. Urgent work that was not on the schedule, often called break-in work, can displace a scheduled job only if it meets the following criteria:

• Only work above a set priority, usually P1, can displace scheduled work.
• Every break-in is logged with a reason code.
• Technicians record time, findings and parts used as they work, ideally on a mobile device, instead of from memory at the end of the shift.

For example, when a cooling water leak breaks in on Tuesday, the supervisor logs the reason and moves a P3 job to the following week. Pump B stays on Wednesday.

Exit condition: Work executed, with break-ins logged against reason codes.

Step 7: Close Out the Work Order and Record What Happened

Closeout is where the next plan improves. A work order closed with only the word complete teaches the planner nothing, so closeout should capture:

• Actual hours against the estimate, and the parts actually used
• The as-found and as-left condition of the equipment
• Failure codes that record what failed and why
• Technician notes on anything the plan missed

In the future, the planner updates the job plan library from these notes. For example, the pump B job ran two hours over because of a seized coupling hub, so the planner added a hydraulic puller and two hours to the plan for next time.

Exit condition: Work order closed in the system of record, with actuals and feedback attached.

A job is ready when the requirements that could stop the work or make it unsafe are confirmed. Materials, permits, isolations, access, skills and equipment release all affect whether the crew can finish in the planned window. Use this checklist before any job goes on the schedule.

Parts and permits are the checks most often assumed rather than proven. When parts are picked and staged before the week starts, the storeroom has confirmed they physically exist, which a stock figure cannot do, and good kitting exposes wrong or missing items days early. An electronic permit to work lets the planner see permit status next to the work package instead of chasing it by phone.

Isolations are also a safety requirement. For work covered by the OSHA lockout/tagout standard, employers must have written energy control procedures setting out the steps for shutting down, isolating, blocking and securing equipment. Isolation points should therefore be confirmed during planning.

Many planning teams aim to keep two to four weeks of ready work, so the scheduler has options when a window opens or a job slips.

A planning horizon is how far ahead a decision looks. Annual planning sets major outage and budget commitments; multi-week planning prepares jobs with lead-time requirements; weekly scheduling commits ready jobs; and daily supervision manages progress and exceptions. Each horizon should feed the next.

In chemical, refining and oil and gas plants, some long-range inputs are set by regulation. The OSHA process safety management standard requires inspection and test frequencies on covered process equipment to follow manufacturers' recommendations and good engineering practice. Those dates go into the annual plan first, so an inspection due next year can decide which outage window gets booked today.

Shutdowns, Turnarounds and Outages

Shutdown, turnaround and outage work follows the same plan-then-schedule sequence, but every step happens earlier and at a much larger scale. Scope usually freezes months ahead, readiness has to cover contractor crews, scaffolding and hundreds of permits, and every job that is not ready when the unit comes down adds hours to the outage itself. In a refinery or chemical plant, where each outage day means lost production, an unready job on the critical path costs far more than the same job in a normal week.

• Routine work is usually planned two to four weeks ahead, while turnaround work needs a planning lead time measured in months.
• Late scope additions should go through formal approval, because each one competes for readiness effort that the existing scope still needs.
• Readiness reviews in the final weeks before shutdown should focus on long-lead parts, contractor mobilization and permit volume.

Maintenance scheduling turns the ready backlog into a committed week, and it only works when every job it places has already passed the readiness checks. Three questions decide whether a schedule holds up: where the work comes from, how many hours you schedule and how you handle urgent jobs.

Time-Based, Usage-Based and Condition-Based Schedules

Repairs found during these jobs and breakdowns compete for the same labor hours, and predictive alerts still need planning and a readiness check like any other job.

How Many Hours Should You Schedule Each Week?

Start with the hours your team will actually be on site, not the headcount. Subtract known absences from the total labor hours by trade, then hold back a reserve for urgent work based on your site's recent history. Fill what remains with ready jobs.

The 18% is an example, not an industry target, and the reserve matters in both directions. Schedule the full 352 hours and every urgent job pushes a planned job off the schedule, compliance falls, carried-over jobs pile into the next week and technicians stop trusting the plan. Make the reserve too large and the team finishes early with nothing ready to start. Check your actual share of urgent work each month and adjust the reserve.

Handling Urgent Work After the Schedule Is Locked

Break-in work is urgent work that was not on the schedule but has to be done during the week. It cannot be avoided, but it can be controlled:

1. Set a priority threshold, so only work at or above it, usually emergencies, can break into the frozen schedule.
2. When a break-in arrives, postpone a job that has not started instead of interrupting one already in progress.
3. Record every break-in with a reason code.
4. Review the reason codes in the weekly scheduling meeting. These reviews often show that some emergencies were routine jobs raised late, which points to an intake problem rather than an equipment problem.
5. Set next week's break-in allowance from the measured rate.

Over time, this routine also raises your planned maintenance percentage, because fewer jobs reach the crew as unplanned work.

Most planning and scheduling programs struggle with the same small set of principles, and each one produces a clear symptom on the plant floor when it is ignored. The planning rows follow the principles in Doc Palmer's Maintenance Planning and Scheduling Handbook, and the last two are additions for industrial plants.

If your plant is mostly reactive, start with three: log every request in one place, keep planners on future work and schedule only ready jobs. Together they make the real workload visible, give planners time to prepare it and make the weekly schedule hold.

Even when the process is well designed, these problems come up again and again in plants that are trying to make it work.

Operations will not release the equipment: A schedule is credible only when production agrees to release the equipment. Resolve constraints in the weekly meeting and keep ready jobs available for unexpected windows.

Estimates are based on guesswork: Planners without a hands-on background often struggle most with job durations. Group past work orders by job type, average the recorded hours and walk the job with an experienced technician. Most overruns come from what nobody planned for, such as a seized bolt.

Job packages are too detailed for the work or too vague to guide it: Keep repeatable steps concise, with the drawings, hazards and asset-specific instructions needed in the field. Ask technicians whether the package answers their practical questions.

Accountability lands on the planner: The planner prepares work, the supervisor manages execution, operations confirms equipment availability, and stores and safety own their commitments. Clear ownership helps explain a missed job.

A planning and scheduling process can look busy and still fail to deliver. Metrics show whether the committed week happened, whether plans can be trusted and whether there is enough ready work ahead.

The most important is schedule compliance: how much of the work on the weekly schedule was completed as scheduled. It only stays high when jobs were ready, hours were realistic and urgent work was controlled.

These definitions follow SMRP Best Practices, Metrics and Guidelines, which also offers a version based on work order counts. Whichever you choose, apply it consistently.

Review the metrics together, because one number can mislead. If compliance rises while jobs keep finishing well under estimate, estimates may be set too high. If compliance looks healthy but the ready backlog is shrinking, next month's schedule will be hard to fill.

When work reaches the field before it is ready, the plant pays for it in four ways: idle labor, outside contractors, extra inventory and longer outages.

• Labor and overtime: Technicians waiting for parts, permits or instructions are still paid for. The unfinished work due to lack of readiness often moves to overtime which impacts wrench time negatively. Ricky Smith and R. Keith Mobley put wrench time at 25 to 35% in plants without a structured planning and scheduling program, against 55 to 65% at world-class sites.
• Contractor spend: When nobody can see how much internal capacity is free, work goes out to contractors by default, often at a higher hourly rate for the same job.
• Spare parts inventory: Shortages found on the day of work mean expedited freight and extra stock that ties up working capital.
• Lost production: On a bottleneck asset, every hour a repair waits for a part or an isolation is lost output.

The table below prices the labor cost alone, using example numbers. Replace the assumptions with your own figures.

The $637,500 is paid time that produced no work. The $937,500 is a separate scenario for replacing that capacity with contractors. Both are modeled examples, not measured results.

This is why planning and scheduling is one of the most direct ways to reduce maintenance costs: it recovers hours the plant is already paying for.

How Indorama Ventures Cut Contractor Headcount by 38%

At its Port Neches, Texas site, Indorama Ventures already ran SAP PM and IBM Maximo, but frontline execution was largely paper-based and the maintenance backlog had reached 24 weeks. The site deployed Innovapptive's Connected Worker Platform to connect notifications, permits, parts and technicians in real time.

Contractor headcount fell from 140 to 87, a 38% reduction, and overtime was cut in half. The backlog dropped 58% to 10 weeks, the site realized $19M in EBITDA savings in 2025, and the program identified a $50M cost reduction opportunity across the enterprise.

Every plant needs one official record of its maintenance work. For most asset-intensive plants, that is an ERP or EAM such as SAP PM, IBM Maximo or Oracle, holding the work order, costs, materials and equipment history. What it does not do on its own is tell the scheduler whether this week's jobs can actually run. Those answers sit with the storeroom, operations, safety and technicians, and usually travel by phone, email and spreadsheet.

This is why many plants add an execution layer on top of their ERP or EAM instead of replacing it. The work order stays in the system of record, while the execution layer checks readiness against live data, shows available crews and equipment windows, and sends field results back. AI makes that layer faster by drafting work packages, sizing durations from similar past jobs and flagging readiness gaps, while planners and schedulers keep the final decision.

A usable schedule depends on reliable job history, material status, readiness, available hours and field feedback. When those details are split across spreadsheets, messages and paper forms, context can be lost between the system of record and the crew.

Innovapptive’s Maintenance Planning and Scheduling Software connects these decisions around work orders in the ERP or EAM the plant already uses. That application remains the system of record; iMPS adds guided workflows to prepare work, check dependencies and coordinate execution. It is not a replacement CMMS or a condition-monitoring system; it helps teams prepare and execute work that enters the maintenance process.

This focus on connecting planning to frontline execution is part of why Frost & Sullivan named Innovapptive its 2026 Global Company of the Year for augmented connected worker, end-to-end platforms.