The schedule keeps breaking

Why weekly maintenance schedules fall apart

Find the first failed handoff behind missed work. Separate parts, access, scope, capacity, and break-in problems before changing the schedule.

Plant Floor · Practical maintenance management

The missed job is the result. Find what happened before it.

The schedule looked reasonable when it was published. By the middle of the week, several jobs have moved, the supervisor is assigning work from memory, and the review is turning into a discussion about effort. Before asking the crew to try harder, pick a missed commitment and reconstruct how it reached that point.

Was the job ready when it entered the schedule? Did operations agree to the access window? Was the right craft available? Did a new request change the priority? Those are different problems with different owners. Treating them all as “poor compliance” produces a number without a useful response.

Keep a record of the original commitment.

Use the schedule version your site actually committed to, alongside the work-order history. Keep subsequent changes visible. If every moved job quietly receives a new scheduled date, the final report can describe the revised plan while hiding the disruption people experienced.

Agree what counts as completion and which baseline you are comparing against. Keep started, partially completed, cancelled, and completed work distinct. Compare like with like before discussing trends. This guide does not set a capacity reserve, freeze window, or compliance target; use your approved local rules consistently.

For each miss, record the planned job, the original commitment, what actually happened, the earliest constraint you can verify, and the evidence. A timestamped note, material allocation, or access confirmation is more useful than a reason selected from memory a week later.

Check five handoffs before changing the schedule.

Materials: were the required items allocated and available for this job, or simply requested? An inventory balance alone does not prove availability at the work location.
Operations access: who agreed to release the asset, for which window, and who received that agreement on the executing shift? A date in the CMMS is not evidence that the asset owner agreed.
Scope and estimate: did the plan describe the actual job, required crafts, and access needs? Record scope discovered during execution separately from time lost waiting.
Crew and coordination: were absences, craft coverage, shared tools, and contractor dependencies known? Separate hours on a roster from the people who could perform this job in its window.
New work: what request changed the plan, who made the decision, and which commitment moved? Review it under the site’s escalation process without inventing a new emergency definition during the meeting.

More than one constraint can affect a job. Record the first verified barrier and any contributing conditions rather than forcing the story into a single convenient category. If the evidence is missing, mark it unknown and assign someone to recover it.

A fictional week with three different misses

Original fictional scenario. These jobs and outcomes illustrate the review method. They are not a customer case or a book excerpt.

Job A was planned for Monday, but its parts were requested rather than allocated. The crew learned about the shortage at the start of the shift. Job B had the materials and crew, but operations had not confirmed the proposed equipment window. Job C started with access and resources available, then revealed work outside the documented scope.

The same instruction, “hold the schedule,” will not resolve all three. For A, the planner and storeroom need a visible confirmation before scheduling. For B, the scheduler and operations contact need a specific agreement passed to the executing shift. For C, the planner needs execution feedback to review the scope and estimate.

Suppose the team also hears that Job A was interrupted later by another request. That later interruption does not erase the initial material problem. Keep both events in the record. Fixing only the last visible disruption could leave the original failure untouched.

End the review with a checkable change.

Select a recurring constraint you can substantiate and name the next handoff to improve. “Improve planning” is too broad. “The planner records the material allocation reference before this job type enters the schedule” gives the team something it can observe.

Name the person responsible and the next review date.
Specify what evidence will show that the handoff happened.
Check the next comparable jobs, including any that still miss.
Review the cause of the miss alongside completion results. A better percentage alone does not prove the change worked.

Keep unresolved work visible and follow the site’s authorization and safety processes. A scheduling review cannot authorize a repair, override a permit, or decide technical operating limits.

Bring the right artifact to the next meeting.

Start with the Planning System Audit if readiness fails before the schedule is built. Use the Job Plan Template and worked guide to make the missing preparation visible. The Schedule Compliance system map connects the result to upstream systems.

Record the diagnosis in the Schedule Compliance Root-Cause Worksheet. Use its categories as prompts, with your site’s approved capacity rules; a reserve assumption in a worksheet should not silently become plant policy.

The Schedule Builder separates available crew hours, a named reserve, committed work and optional ready jobs. It illustrates the book’s rolling 48-hour freeze while retaining the original weekly baseline. Confirm craft coverage and the reserve basis locally; it remains a teaching model, not authorization to execute or change work. If repeated failures keep generating new work, continue with the repeat-failure guide.

Source notes

This original guide draws on the work-management themes in Fix the System, Chapters 6, 7, and 19. For a primary industry reference, EPRI’s Maintenance Planning and Scheduling report discusses job-package requirements, coordination, and weekly review in sections 5-1, 5-2, 5-9, and 5-16. Published in December 2000 for fossil power plants, it supplies process context, not a universal target for every plant.