Planning prepares the job — scope, parts, tools, permits, procedure, labour estimate. It answers how, and it happens before the work is scheduled. Scheduling commits ready work to a date and a crew against available capacity. It answers when and who. They are different jobs and shouldn’t be done by the same person at the same time.
The metric they move is wrench time — the fraction of a technician’s paid hours spent actually doing maintenance. Reactive shops sit at ~25–35%; planned-and-scheduled shops reach 50–60%. That swing is equivalent to growing the crew by half or more.
Steer it with backlog (keep 4–6 weeks of ready work) and schedule compliance (did we do what we planned?). The CMMS is the system of record that makes it all visible.
1 · Two different jobs, often confused
The single most common mistake in maintenance management is treating “planning” and “scheduling” as one activity. They are distinct, and conflating them is why so many improvement efforts stall.
- The planner works ahead of the work. For each approved job they define the scope, identify and stage the parts, list the tools and special equipment, arrange permits and isolations, write or attach the procedure, and estimate the labour. The planner’s product is a ready-to-schedule work package — a job with every foreseeable obstacle already removed. The planner does not fight today’s fires.
- The scheduler works with the near future. From the pool of planned, ready jobs, they build a weekly (and daily) schedule that matches the available labour hours, crafts and equipment windows to the highest-priority ready work — then negotiates that schedule with operations.
The golden rule: planning is about content, scheduling is about time. A planner who keeps getting pulled into today’s breakdowns stops planning, the ready backlog dries up, and the schedule collapses back into reactive firefighting. Protecting the planner’s time is the whole game.
2 · The work-order lifecycle
Every job, from a leaking gland to a major overhaul, moves through the same lifecycle in the CMMS. Understanding it is understanding work management:
The loop matters as much as the steps: the failure codes and findings captured at close-out are the raw material for bad-actor analysis, RCA and life-data analysis. A work order that closes with “completed” and nothing else throws that data away. Good close-out is where work management feeds reliability.
3 · Wrench time: the number that pays for everything
Wrench time (or tool time) is the share of a paid maintenance hour spent actually performing maintenance at the job site — not travelling, not waiting for parts, not searching for a drawing, not getting a permit signed. It is the closest thing maintenance has to a productivity index, and it is shockingly low when work is unmanaged.
The reason planning and scheduling pay for themselves is pure arithmetic: if wrench time rises from 30% to 50%, each technician delivers two-thirds more productive work for the same wages. A 30-person crew starts doing the work of 50. The model shows where the hours go and how planning and parts availability claw them back:
Interactive — Where the maintenance hour goes
Live modelHow the paid hour is spent
Wrench time vs work planned
4 · Backlog — the reservoir that makes scheduling possible
You cannot schedule a full, efficient week if there is no ready work to draw from. Backlog is that reservoir, and it is healthy, not bad — provided it is the right size and visible. Two distinctions matter:
- Total backlog vs ready backlog — only planned work with parts and permits in hand can actually be scheduled. Ready backlog is the number that feeds the schedule.
- Backlog measured in weeks, not job count:
backlog weeks = ready backlog hours ÷ weekly crew capacity. The widely-used healthy range is about 4–6 weeks of crew-ready work.
Too little backlog (<2 weeks) and the scheduler is forced to use poorly-prepared or low-value jobs to fill the week. Too much (>8–10 weeks) and either you are under-resourced or work is being raised faster than it can be done — a signal in its own right.
5 · The weekly cycle & schedule compliance
Mature maintenance runs on a rhythm: a weekly schedule is built and frozen, executed, and then measured. The headline measure is schedule compliance — the percentage of the scheduled work that was actually completed as planned:
The enemy of compliance is break-in work — unplanned jobs forced into a frozen week. A little is unavoidable; a lot means the upstream problem (reliability, or weak planning) hasn’t been solved. Compliance and the wider KPI set are how you tell whether the system is improving or just busy.
This is the execution layer of everything else in the Academy. The RCM and FMECA studies decide what work is worth doing; the PM and PdM strategies decide when; planning and scheduling are how that work actually gets done efficiently — and the CMMS (the system Bluestream implements, increasingly tied into Microsoft Dynamics 365) is the backbone that carries the work orders, history and KPIs end to end.
Key takeaways
- Planning ≠ scheduling. Planning prepares the job (the “how”); scheduling commits ready work to time and people (the “when/who”). Protect the planner from firefighting.
- Wrench time is the prize. Moving from ~30% to ~50% is like growing the crew by two-thirds — for free.
- Keep 4–6 weeks of ready backlog so the scheduler always has good work to build a full week from.
- Measure schedule compliance (80–90%) and watch break-in work — it tells you if the system is under control.