Skip to content
August 2026 · 9 min read

Planner, scheduler, long term planner: three different jobs

The titles get used interchangeably and the roles are not the same. What a planner owns, what a scheduler owns, where the long term view sits, and how the job changes between a routine week and a shutdown.

ConsultingPlanning & SchedulingWork Management
Process plant vessels and pipework lit up against a deep blue dusk sky

Key takeaways

  • A planner answers what the job is and what it needs. A scheduler answers when it runs and who does it. Merging the roles usually sacrifices the planning, because only one of them has a deadline.
  • Planning is constrained by job readiness, scheduling by capacity and access. They fail in different ways, so they need different measures.
  • A long term planner deals in workload, windows and commitments rather than job packs: the twelve month load, the next shutdown scope, and anything with a lead time longer than the weekly cycle.
  • Shutdown and turnaround planning is a different discipline again: milestone driven, critical path sequenced, and reforecast shift by shift while the window is open.
  • The vocabulary changes by industry, shut, turnaround, outage, possession, changeover, but the underlying roles do not.

Planning and scheduling are commonly carried by the same job title, the same person and, on a bad week, the same afternoon. Work is scoped between phone calls, the coming week is built in a spreadsheet from whatever the CMMS holds, and the long term view lives in a shutdown workbook that gets opened eight weeks out.

That merge is not a discipline problem. Planning and scheduling answer different questions, run on different horizons and fail in different ways, so combining them tends to sacrifice the one without a deadline. Planners, schedulers and the supervisors relying on them require clear boundaries between the roles, and measures that show which of them is failing.

What a planner does

A planner turns identified work into executable work. That means scoping the job from the notification or defect, deciding the method, estimating trade hours and crew mix, identifying and reserving parts, working out isolation, permits and access, and attaching the drawings, procedures and specialist resources the job needs.

The output is a job pack a competent crew could pick up and execute without hunting for anything. The planner works ahead of the schedule window, on jobs nobody has scheduled yet, which is exactly why the role is destroyed by being pulled into today. The honest measure of a planner is not how many jobs they touched, it is how many arrived at the schedule genuinely ready.

  • Scope and method, written so the job runs the same way whoever picks it up.
  • Trade hours and crew mix estimated well enough to schedule against, then corrected from actuals.
  • Parts identified, reserved and kitted, with lead times understood before the job is promised.
  • Isolation, permits, access and any lifting or confined space requirements sorted in advance.
  • Drawings, procedures, torque figures and specialist tools attached rather than assumed.

The planner exists to remove every reason a job could fail before anyone is asked to start it.

What a scheduler does

A scheduler decides what actually happens next week. That starts with an honest view of capacity: hours available by trade after leave, training, standing commitments and callout cover, not the headcount on the org chart. Ready work is then sequenced against that capacity and against the access operations can genuinely give.

On fly-in, fly-out work that view also has to follow swings, rostered days off and fatigue limits, so capacity is best read from the roster rather than rebuilt in a spreadsheet each week. Rostering and workforce management software such as Humanz, which we partner with, keeps rosters, leave and credentials in one place the scheduler can draw from.

The schedule is published, frozen and defended, and break-in work goes through one approval path so urgency becomes a visible decision rather than a habit. A scheduler with nothing ready to schedule does not have a scheduling problem, and no amount of calendar discipline will fix it.

  • Forecast capacity by trade honestly, including the hours already spoken for.
  • Sequence ready work so shared constraints, cranes, isolations, permits and operations windows, do not collide.
  • Negotiate access with operations rather than assuming it: a schedule the plant has not agreed to is a draft.
  • Freeze and publish the week, then hold it through a single approval path for break-in.
  • Report compliance against a definition that does not move between weeks.

Scheduling unready work does not produce a plan. It produces a list of hopes with dates on it.

The split in one table

Sites argue about where the boundary sits. It is worth arguing about once, then writing down, including the cases that fall between the two: parts chasing, permit lodgement, contractor bookings and who owns the job when it fails on the day.

AspectPlannerScheduler
Question answeredWhat is the job, and what does it need?When does it run, and who does it?
Unit of workThe jobThe week, then the day
Main constraintReadiness: parts, permits, access, methodCapacity: labour hours, equipment, production windows
Primary outputA job pack with hours, parts and methodA frozen, resourced schedule
Works mostly withReliability, engineering, supervisors and the storeOperations, supervisors and contractors
Fails asJobs reach the schedule not readyReady work waits while the week is rebuilt by phone
Measured byJob readiness and estimate accuracySchedule compliance and break-in

Horizons, and where the long term planner sits

The roles separate again by horizon. A supervisor is deciding today, a scheduler is deciding next week, a planner is getting jobs ready for weeks nobody has committed to yet, and somebody has to be looking at the next twelve months. That last view is the one most commonly missing.

HorizonUsually owned byWhat is being decided
TodaySupervisorAllocating people to a schedule that already exists, and handling what the shift found
Next weekSchedulerSequencing ready work against confirmed capacity and agreed access
Rolling four to thirteen weeksPlanner, with the schedulerGetting work ready in time: parts ordered, permits raised, access and contractors booked
Quarter to yearLong term plannerLevelling workload against the production plan, holding shutdown scope, long lead materials, contract labour and budget
Multi-yearAsset management and engineeringShutdown cycle strategy, major component change-outs, overhauls and replacement, feeding the capital plan

What the long term planner actually owns

A long term planner is not a planner with a longer list. The unit of work changes: they deal in workload, windows and commitments rather than job packs. The daily questions are whether the next twelve months of maintenance fits inside the production plan, which items have to be ordered now to exist later, whether shutdown scope is growing, and what happens to the following quarter if a major outage moves.

The role earns its keep on the constraints nobody can fix at short notice: a nine month lead time on a gearbox, a crane booking, a specialist contractor available in one window a year, a change-out that has to align with a rail closure, a wet season or a demand peak. It is also where maintenance and production stop negotiating week to week and agree a shape for the year.

  • A forward workload by trade and by month, so the year is levelled rather than lumpy.
  • Shutdown and outage windows agreed with production, and the scope held against each one.
  • Long lead materials, rebuild exchanges and major components ordered against the plan, not the crisis.
  • Contract labour and specialist services booked while the market still has capacity.
  • The maintenance plan reconciled with the capital plan, so replacement and overhaul decisions are not made twice.

Anything the weekly cycle cannot fix at short notice belongs to somebody's long term plan, whether or not the role exists on the org chart.

Shutdowns and turnarounds are a different job

A shutdown planner and a routine planner share a title and not much else. Shutdown work is built into a work breakdown and sequenced on a critical path through a fixed window, driven by a milestone schedule counting back from the start date: scope freeze, pack completion, materials on site, contractor mobilisation. Isolation and permit planning happens at a volume the routine week never sees, shifts run around the clock, and an allowance for discovery work is built in because opening equipment is how you learn what is inside it.

The stakes change the discipline. A weekly schedule that slips a day costs some tool time and a rescheduled job. A turnaround that slips a day costs a day of production plus a day of everyone mobilised for the window, which is why precision that would be over-engineering in a routine week is simply the standard here.

AspectRoutine and weekly workShutdown or turnaround
Planning horizonRolling weeks, continuousMonths to years, milestone driven
Scope controlBacklog grooming and priorityScope challenge, then a freeze date that gets defended
Sequencing logicFit ready work into available windowsCritical path through a fixed window, with float understood
Typical toolsCMMS scheduling, spreadsheets, weekly KPI reportingCritical path scheduling software, work packs, dedicated coordination tools
WorkforceSite crews, known capacitySite crews plus contractors mobilised for the window
RhythmWeekly cycle with daily adjustmentReforecast every shift while the window is open
Cost of slippingTool time and a rescheduled jobProduction for every hour of overrun, plus a standing workforce
Key measuresSchedule compliance, break-in, backlog healthMilestone adherence, scope growth, float consumed, cost against plan
  • A scope challenge that removes anything doable online: work that does not need the outage should not be consuming the window.
  • A freeze date with a named owner and a change process, because uncontrolled late scope is the most common cause of overrun.
  • Critical path logic, so everyone knows which jobs move the finish date and which have float to give.
  • Resource histograms by trade and by shift, checked against what the site can physically absorb: beds, buses, laydown, cranes and permits.
  • A deliberate allowance for discovery work, sized from history rather than optimism.
  • A close out that captures actual hours and durations, so the next cycle estimates from evidence instead of memory.

In a turnaround the schedule is not a plan for the work. It is the cost model for the outage.

The vocabulary changes by industry

The roles travel between industries better than the words do. What is called a shut in one operation is a turnaround, an outage, a possession or a changeover in the next, and turning up with the wrong vocabulary costs credibility faster than any technical gap.

IndustryWhat the window is calledWhat usually constrains it
MiningShut, shutdown, campaign maintenance, mill relineStockpile cover and circuit bypass, crusher and mill availability, roster cycles, mobilising to remote sites, wet season access
Oil and gasTurnaround, TAR, unit shutdownStatutory inspection and pressure equipment intervals, permit and isolation volume, simultaneous operations, offshore bed limits and weather windows
ManufacturingPlanned downtime, changeover, shutdown weekThe order book, line availability and OEE targets, changeover sequence, seasonal demand peaks
Power and utilitiesOutage, unit outage, planned interruptionNetwork switching and load, seasonal peaks, customer interruption limits, outage dates committed externally well in advance
RailPossession, track occupation, corridor closureAccess windows negotiated against the timetable and freight paths, worksite protection, regulator obligations
Facilities and propertyPlanned preventive maintenance, essential services servicingOccupancy and tenant access, statutory servicing dates, contracted response times
AgricultureOff season overhaul, pre season serviceSeasonal windows: sowing and harvest do not move, dealer and parts availability
  • In mining the binding constraint is often production cover rather than labour: whether the circuit can be bypassed or the stockpile can carry the plant through the window.
  • In oil and gas, inspection intervals on pressure equipment set turnaround timing, so planning starts years out and the date moves for very little.
  • In manufacturing the planner negotiates with the order book, and changeovers are scheduling events in their own right.
  • In utilities, outage dates carry external commitments, so a slipped window becomes a market and regulatory conversation rather than an internal one.
  • In rail the scarce resource is access to the corridor, so a possession is planned like a shutdown even when the work inside it is small.
  • In facilities, statutory servicing dates and building access dominate, and the evidence of completion matters as much as the completion.

Where the structure breaks down

  • The planner spends the day expediting today's breakdowns, so nothing is planned and everything is scheduled.
  • Scheduling from the backlog rather than the ready backlog, which fills the week with jobs that were never going to run.
  • No long term view at all: every shutdown is planned from a standing start and every long lead item becomes an express freight order.
  • The shutdown planner is borrowed from the weekly cycle for the three months before the window, so routine planning stops exactly when the site can least afford it.
  • One measure covering both roles, so a readiness failure and a protection failure look identical on the report.

Two roles need two measures. A single compliance number cannot tell you whether the work was not ready or the week was not protected.

What good looks like

  • The boundary is written down, including who owns parts chasing, permits and contractor bookings.
  • Planning time is protected from today, in the routine and in where the planner physically sits.
  • The ready backlog is counted in crew-weeks, so everyone can see whether there is enough ready work to fill a schedule.
  • A named long term view exists, even if it is one person for one day a fortnight, keeping the forward load and the next shutdown scope current.
  • Each role carries its own measures, reviewed together in the same weekly forum.

Separating the roles

  1. Define the boundary

    Write down what planning owns, what scheduling owns, and who handles the cases in between.

  2. Protect planning

    Planning works ahead of the schedule window, insulated from today's breakdowns.

  3. Gate the handoff

    Nothing reaches the schedule without a complete pack, materials kitted and access agreed.

  4. Set the horizons

    Weekly, a rolling wave, and a named long term view for workload, shutdown scope and long lead items.

  5. Measure per role

    Readiness for planning, compliance and break-in for scheduling, milestones and scope growth for shutdowns.

Common questions

What is the difference between a maintenance planner and a scheduler?

A planner defines the work: scope, method, trade hours, parts, permits and access, producing a job pack any competent crew could execute. A scheduler decides when that work runs, sequencing ready jobs against available labour, equipment and production windows. Planning answers what and how, scheduling answers when and who.

Can one person do both roles?

On a small site it often has to be one person, and that can work. The risk is that scheduling has a deadline and planning does not, so the calendar crowds out the job packs and the role drifts into expediting. Where one person carries both, protect planning time explicitly and measure job readiness separately from schedule compliance.

What does a long term planner do that a weekly planner does not?

They work in months and quarters rather than weeks: levelling maintenance workload against the production plan, holding scope for the next shutdown, forecasting long lead materials and contract labour, and keeping the maintenance plan consistent with the capital plan. The output is a forward workload and a set of commitments, not a job pack.

How is shutdown planning different from weekly planning?

Scope is fixed to a milestone date and then defended, work is sequenced on a critical path through a fixed window rather than fitted into a spare slot, much of the workforce is mobilised from outside the site, and the schedule is reforecast during execution, often every shift. The stakes differ too: an hour of overrun costs production plus the standing cost of everyone brought in for the window.

Key terms

Plain-language definitions from our glossary for the concepts this article leans on.

Standards and further reading

Related case studies and tools

Related reading

Working through something like this?

See how we approach these initiatives, or tell us what you are dealing with.