Supervisor

Understand

Who this role is and what they own.

Reports to

Maintenance Manager / Engineering Manager

Key relationships

Operations Supervisor — daily priorities, permits, downdays, handbacks
Planner — backlog readiness and pack quality feedback
Scheduler — schedule commitment and break-in discipline

Top accountabilities

Chair the daily work-request review; approve priorities, route MOC / shutdown
Commit to and defend the weekly schedule; approve break-ins by name
Run pre-job briefs from the actual pack; own the safety envelope

Deep dive · phase-by-phase detail

P1Identify Work

Open ↓

The Supervisor is the daily intake gate for the maintenance backlog. Nothing enters the planning queue that they haven't screened for priority, evidence and legitimacy. Every vague or duplicate work request they let through costs the Planner a day and pollutes the reliability data downstream. The test of 'done well' here is that the backlog only ever contains real, actionable, well-described work.

What this role does

Chair the 15-minute daily work-request review with Operations and Planning at a fixed time — never skip, never reschedule
Assign a priority using the site risk matrix, not tone of voice or seniority of the requester
Route legitimate management-of-change, capital or shutdown scope out of the routine backlog on sight
Return vague, duplicate or safety-incomplete requests to the originator with a one-line coaching reason
Confirm the equipment tag matches the actual asset — bad tags corrupt failure data for years
Escalate any P1 to the Maintenance Manager the moment it lands, not at the next stand-up

Good looks like

Every overnight request has a decision (accept / return / route) by 09:00, every day
Priority distribution stays inside site targets — P1+P2 combined below ~20% of new work
Originators get feedback on rejected requests, so intake quality improves quarter over quarter
The Planner rarely sees a request that shouldn't have made it past intake

Bad looks like

'Just plan it' — everything accepted to keep the peace, backlog balloons with junk
Verbal side-channel requests bypassing the CMMS because 'it's faster'
P1 used to jump the queue; within a quarter the priority number stops meaning anything

P2Plan Work

Open ↓

The Supervisor is not the Planner, but they are planning's most important customer. If they accept sub-standard packs to keep the crew moving, pack quality collapses within a month and the site regresses to reactive work. The Supervisor's role here is to hold the standard — return bad packs, feed real constructability gaps back, and shield the Planner from being pulled into today's fire.

What this role does

Return sub-standard packs to Planning rather than let the crew improvise on the job
Feed constructability, access and bill-of-material gaps back into the Standard Job Plan library the same day
Shield the Planner from reactive break-in work so they can stay four weeks out on the horizon
Walk one high-risk pack per week with the Planner before it goes to Ready-to-Schedule
Coach crews to raise formal pack feedback in the CMMS, not verbally in the crib room
Insist on a real safety pack — job safety analysis, isolations, permits, hold points — before signing anything off

Good looks like

Crews open the pack and can start work — no chasing drawings, parts or permits mid-job
Repeat jobs get measurably better each cycle because feedback actually reaches the Planner
Pack rework rate (packs returned before start) sits below 5% and is trending down

Bad looks like

Supervisor becomes the informal Planner at 06:00 every morning — real planning stops
'We'll figure it out on site' — precision maintenance is impossible from there
Pack feedback lives in the Supervisor's head and never reaches the Standard Job Plan library

P3Schedule Work

Open ↓

This is where the Supervisor makes or breaks weekly performance. They own the commitment to the signed schedule and are the last defence against reactive drift. If break-ins are approved verbally and off the record, the schedule becomes fiction, compliance KPIs become theatre, and the crew loses trust in the plan.

What this role does

Confirm crew availability, leave and training cover before signing the schedule — not after
Attend the weekly scheduling meeting personally; sign the committed schedule with your name against it
Approve every break-in in writing with a category and a named approver — no verbal reshuffles
Review schedule compliance and the schedule-breaker Pareto with the Scheduler each week
Push back on Operations when planned work is bumped without a documented reason
Hold the crew to the sequence in the schedule unless you personally re-sequence it

Good looks like

Weekly schedule compliance trends above 85% with honest, unedited measurement
Break-ins have a named approver and a category — visible in the KPI pack, not hidden
The scheduling meeting takes 45 minutes because the Supervisor came prepared

Bad looks like

Verbal 'just swap it in' calls — the schedule becomes fiction inside two weeks
Break-ins relabelled as planned work so the compliance number looks good
The Supervisor lets the crew self-direct — cherry-picking replaces the schedule

P4Execute & Record

Open ↓

Execution is where safety and data quality are either enforced or eroded. The Supervisor sets the standard on the shop floor by physically being at the asset, verifying isolations, briefing from the actual pack and prompting real-time data capture. Bulk close-outs on Friday afternoons destroy the failure history that every downstream reliability decision depends on.

What this role does

Run a structured shift handover with the outgoing Supervisor — assets, permits, in-progress work, hazards
Pre-job brief every crew from the actual pack, at the asset — never from memory
Verify isolations on site and sign permits at the asset, never from the office
Walk the floor mid-shift and observe at least one job at a hold point
Prompt time confirmations, history text and failure codes before shift end — not week-end
Confirm permit close-out and formal handback to Operations before releasing the crew

Good looks like

Every job is briefed from the pack — the crew knows scope, hazards and hold points before starting
Time and history are entered on the day the work happens, from the catalogue not free-text
The Supervisor is at the asset for the risky lifts, isolations and start-ups, not at their desk

Bad looks like

Permits signed from the office; isolation verification skipped 'because we trust the crew'
Bulk close-out on Friday afternoon — history becomes fiction, failure data becomes unusable
Pre-job brief replaced by 'you know what to do' — safety envelope erodes silently

P5Close-out & Analysis

Open ↓

The Supervisor is the final quality gate on the record. If they let 'completed as per work order' close out without real history, reliability analysis downstream is corrupted forever — and no amount of Reliability Engineering effort can recover it. Formal close-out is not admin work; it is the last chance to protect the failure data the site depends on.

What this role does

Sample-check technically-complete work orders every day for history depth and failure-code accuracy
Coach individuals whose close-outs are consistently thin — name, example, one-on-one
Set work orders to Technically Complete only when the data meets the site standard
Prompt crews to raise follow-up work requests for discovered defects, not stack them onto the parent order
Formally close out work orders yourself — that is your quality gate, not the Planner's
Flag jobs where duration or materials diverged more than 20% from plan for the weekly variance review

Good looks like

History reads like a story a stranger could follow — symptom, cause, action, verification
Failure codes chosen match what was actually found, not the default first entry in the list
Close-out lag (technically complete → formally closed) is under a week, consistently

Bad looks like

'Completed as per work order' with no history — the single worst offender on any site
Codes defaulted to keep the queue clean; the catalogue becomes noise, not signal
Close-out authority delegated to the Planner — accountability and coaching loop both broken

P6Metrics & Continuous Improvement

Open ↓

The Supervisor is the operational sponsor of the reliability improvement loop. They read the KPI pack honestly, commit crew hours to investigations, and let the Reliability Engineer change the strategy — even when it means giving up a favourite routine. Without this sponsorship, bad actors keep failing and the CI register stays open forever.

What this role does

Walk the top three bad actors with the Reliability Engineer every week — physically, at the asset
Sponsor investigations by committing named crew hours and acting on the recommendations
Review Supervisor and crew performance against safety, compliance and close-out KPIs, not gut feel
Endorse PM and Standard Job Plan changes coming out of the CI register, and retire the ones being replaced
Use trend movement, not point values, when coaching — one bad week is not a trend
Represent the crew in monthly reliability reviews — bring floor context to the numbers

Good looks like

Findings from investigations turn into PM and Standard Job Plan changes that actually stick
Trends drive coaching conversations, not blame conversations
The crew sees the improvement loop close — same failure doesn't recur two quarters running

Bad looks like

KPIs presented, no actions closed — 'analysis theatre' becomes the culture
Every dip in a number becomes a personal performance issue instead of a system fix
The Supervisor protects the status quo and quietly blocks strategy changes at implementation

Good looks like

Every overnight request has a decision (accept / return / route) by 09:00, every day
Priority distribution stays inside site targets — P1+P2 combined below ~20% of new work
Originators get feedback on rejected requests, so intake quality improves quarter over quarter

Bad looks like

'Just plan it' — everything accepted to keep the peace, backlog balloons with junk
Verbal side-channel requests bypassing the CMMS because 'it's faster'
P1 used to jump the queue; within a quarter the priority number stops meaning anything

Learn

Courses, guides and reading to build the capability.

Academy modules

Structured pathway

Process guides

Phase deep-dives

Read & download

Free PDF guides

Competencies

Trade background plus supervisory trainingPermit-receiver certification and isolation competencyFluent in the CMMS work-order, permit and mobile workflowsCoaching and difficult-conversation skillsReading and acting on KPI trends, not point values