Scheduler

Understand

Who this role is and what they own.

Reports to

Planning Leader

Key relationships

Planner — receives Ready-to-Schedule work
Operations Leader — downdays, access, production plan
Supervisor — crew availability, execution feedback

Top accountabilities

Filter the backlog; only fully ready work enters the candidate list
Draft the schedule to 80–85% load, sequenced by asset and location
Run the weekly scheduling meeting and secure named sign-off

Deep dive · phase-by-phase detail

P1Identify Work

Open ↓

The Scheduler is not in the intake gate, but every new P1 that lands is a potential schedule-breaker. Their job in this phase is to make break-ins visible and countable — not absorb them silently — so the whole site can see what is really disrupting the plan and act on the pattern, not the incident.

What this role does

Log every break-in with a cause category, named approver and hours cost — no exceptions
Feed the break-in Pareto back to the Supervisor and Operations Manager weekly with the top three named
Escalate any single break-in that consumes more than 10% of the week's crew hours the day it happens
Track break-in source — Operations, Reliability, Safety, Regulatory — so the pattern is visible, not just the total
Confirm any 'emergency' actually meets the site's break-in criteria; return manufactured emergencies to the Supervisor

Good looks like

Break-in rate is measured honestly against a locked definition and is trending down over the quarter
The top three break-in causes are named, owned and worked on — not just reported
Operations can see the cost of their own break-ins in the weekly pack

Bad looks like

Break-ins quietly slotted into the schedule and the compliance number stays 'green'
'Emergency' becomes the default label — the category loses all meaning
Break-in Pareto exists but nobody owns the top items — same three appear quarter after quarter

P2Plan Work

Open ↓

The Scheduler is the gatekeeper on the Ready-to-Schedule bar. If they let half-ready packs onto the candidate list to hit a coverage target, day-of failures spike and weekly compliance collapses. Their job is to reject half-ready work without apology and to hold Planning to a real definition of 'ready'.

What this role does

Verify materials, kitting, permits and labour before adding any pack to the candidate list
Push back on packs with 'sundries', missing drawings or unresolved isolations — return, don't schedule
Walk the candidate list with the Planner on Thursday afternoon and withdraw anything that has slipped
Reserve materials in the CMMS against the specific week's schedule, not the parent work order
Confirm operations downtime windows for any pack that needs an asset release before it goes onto the schedule

Good looks like

The candidate list only holds work that is genuinely executable next week
Day-of failures caused by pack readiness sit below 5% of scheduled hours
The Planner respects the bar because the Scheduler enforces it consistently

Bad looks like

Scheduling half-ready work to hit a coverage KPI — day-of failures spike and compliance collapses
Ready-to-Schedule status set on hope rather than the checklist
Scheduler quietly accepts packs the Planner knows are weak, because 'we have to fill the week'

P3Schedule Work

Open ↓

This is the Scheduler's home phase. They own the weekly schedule end-to-end — from the candidate list, through the scheduling meeting, to a signed, frozen commitment. The test of a good scheduler is not the compliance percentage; it is that the crew, the Supervisor and Operations all trust the schedule enough to work to it.

What this role does

Level-load to 80–85% of net capacity — leave, absentee factor, training and meetings deducted honestly
Sequence work by asset, location and permit to minimise travel, isolations and permit re-issues
Chair a decisions-only scheduling meeting; publish the agenda and the candidate list 24 hours in advance
Publish and freeze the schedule at the same time each week — same day, same hour, every week
Update the schedule daily for approved break-ins and displaced work — but do not re-baseline
Secure a named sign-off from the Supervisor and Operations before releasing the schedule

Good looks like

Weekly schedule compliance is above 85%, measured against the frozen version, not the live one
The scheduling meeting takes 45 minutes because homework was done beforehand
Crew loading is honest — 80–85% net capacity leaves room for the inevitable break-in without collapsing the week

Bad looks like

100% capacity loading — every break-in blows the entire week's plan
'Rolling' schedule that is edited all week — there is nothing stable to measure compliance against
Meetings that debate every job — 90 minutes long, no decisions, everyone leaves frustrated

P4Execute & Record

Open ↓

During execution the Scheduler is the site's early-warning system. Carry-overs, deferrals and disruptions are the signal, not the noise. If the Scheduler is not reconciling the day against the plan and asking why, next week's schedule will be built on last week's lies.

What this role does

Reconcile the day's schedule against actuals at end of day — capture reasons for slippage with a code
Confirm tomorrow's readiness with the Supervisor and Planner before end of shift
Update the live schedule with approved break-ins immediately, with the named approver captured
Flag any pack that carries over more than one day for a variance conversation with the Planner
Track and publish daily compliance against the frozen weekly schedule — not a private spreadsheet

Good looks like

Every deferral has a reason code — nothing silently vanishes off the plan
Tomorrow's crew mobilises knowing exactly what they are on, before they get to site
Carry-overs are the exception, and each has a documented cause

Bad looks like

Deferrals lost in the noise; end-of-week compliance is a guess, not a measurement
Break-ins added to the schedule after the fact so the KPI improves — the number becomes meaningless
Scheduler disengages from the live day and only surfaces on Friday

P5Close-out & Analysis

Open ↓

The Scheduler feeds actuals back into the capacity model so next week's schedule is a fraction more honest than this week's. If capacity assumptions never update, the schedule and reality drift apart quarter after quarter until nobody believes the plan.

What this role does

Compare planned versus actual duration per crew each week; adjust capacity assumptions with evidence
Feed variance findings to the Planner every Friday for estimate correction
Recalculate the absentee factor monthly from real leave, training and safety-stand-down data
Publish a monthly 'capacity model versus reality' one-pager to the Maintenance Manager
Retire capacity assumptions that have been wrong for more than two quarters — do not carry them forward silently

Good looks like

The capacity model tracks reality within a small, known margin — everyone trusts it
The Planner's estimates get better cycle over cycle because the Scheduler feeds real variance data back
Absentee factor is a real number, updated monthly, not a five-year-old assumption

Bad looks like

Capacity numbers copied forward for years — the schedule is fiction and everyone knows it
Variance data collected but never used to update the model
The Scheduler and Planner never talk after Wednesday — feedback loop is broken

P6Metrics & Continuous Improvement

Open ↓

The Scheduler owns the two KPIs that expose the health of the whole work management system — schedule compliance and break-in rate. They must publish these honestly, defend the definitions, and drive the systematic elimination of the top three schedule-breakers every quarter.

What this role does

Publish weekly schedule compliance and break-in rate against a locked definition — never edit historical numbers
Present the top three schedule-breaker causes with a named owner and a due date for each
Run a quarterly review of the break-in Pareto with Operations and Reliability — same top-three should not repeat
Track hours lost to schedule-breakers separately from hours lost to pack readiness — different fixes
Escalate any schedule-breaker cause that stays in the top three for more than two quarters

Good looks like

Break-in causes get systematically fixed — the same top-three doesn't repeat quarter after quarter
KPI definitions are stable and locked — trend lines are trustworthy for years, not months
The Maintenance Manager can point to specific fixes that reduced break-in rate this year

Bad looks like

KPI definitions quietly redefined to make the number look better
Top three schedule-breakers stay the same for a year and nobody owns the fix
Compliance number is 'green' but everyone on the floor knows it is engineered, not earned

Good looks like

Break-in rate is measured honestly against a locked definition and is trending down over the quarter
The top three break-in causes are named, owned and worked on — not just reported
Operations can see the cost of their own break-ins in the weekly pack

Bad looks like

Break-ins quietly slotted into the schedule and the compliance number stays 'green'
'Emergency' becomes the default label — the category loses all meaning
Break-in Pareto exists but nobody owns the top items — same three appear quarter after quarter

Learn

Courses, guides and reading to build the capability.

Academy modules

Structured pathway

Process guides

Phase deep-dives

Read & download

Free PDF guides

Competencies

Strong operational understanding of the plant and its constraintsFluent in the CMMS scheduling module and capacity modellingFacilitation — able to chair a decisions-only meeting in 45 minutesNumerate — comfortable with capacity, absentee factor and compliance maths