Weekly Maintenance Scheduling: Loading Crew Hours Without Overbooking
A weekly schedule is where the PM plan meets real crew hours. Here is how to load the week by priority and capacity so the plan is one your team can finish.

The Friday plan that was full by Tuesday
The planner printed the week on Friday afternoon. Eleven PMs, a pile of backlog, a conveyor repair, and a pump rebuild someone had promised the production supervisor. Every technician had a full column of jobs. It looked organized.
By Tuesday noon it was wrecked. A compressor tripped and took two people for most of a shift. One technician was out sick. The pump rebuild ran long. Wednesday's jobs slid to Thursday, Thursday's slid to the following week, and the lowest-priority PMs quietly became overdue again. Nobody did anything wrong. The plan asked for more hours than the crew had.
That is the core problem with weekly maintenance scheduling. The schedule is only as honest as the hours behind it. This article walks through how to count the hours your crew really has, load the week by priority and trade, leave room for breakdowns, and spot an overloaded day before Monday starts.
Weekly maintenance scheduling starts with planned jobs
People use the words interchangeably, and that causes trouble.
Planning decides what the job is. Which tasks, which parts, which tools, how many labor hours, what permits or lockout steps. It happens once per job, ahead of time, and the result is a job package.
Scheduling decides when the job happens and who does it. It takes planned jobs and places them into specific days and technician slots, against the hours actually available.
You can't schedule well without planning. If a job has no hours estimate, you can't load it into a week. You can only hope. This is the heart of maintenance planning vs scheduling: planning produces the estimate, scheduling spends the capacity. For the upstream half, see how to build a preventive maintenance schedule, which covers turning assets and intervals into a due-date calendar. Weekly scheduling starts where that calendar ends.
It also helps to see where a job sits in its life. A job is open, then in progress, then completed, then verified. The weekly schedule is the step that moves jobs from open to in progress on purpose, instead of by whoever shouted loudest. Our piece on the work-order lifecycle lays out those stages.
Count crew capacity before you count jobs
Most overbooked weeks start with the wrong first step. The planner looks at the job list and starts assigning. Start with the hours instead.
Gross hours are headcount times shift length. They are not capacity. Several things come out before a single job is placed:
- Vacation, sick time, training, and any technician pulled to another area.
- Meetings, safety talks, and shift handovers.
- Walking to the job, fetching parts, waiting on permits, and clean-up.
- Time already committed to non-negotiable routine work.
The walking-and-waiting item deserves honesty. Published figures put the average technician at only about 25%–35% of their shift on actual hands-on wrench time (Cryotos, citing Plant Engineering/Reliable Plant, 2025). Good planning and scheduling can lift that from a typical ~30% to somewhere around 45% (Reliability Academy, 2025). Those are broad industry figures, not a target for your crew. Your own number comes from your own plant.
The practical lesson is simpler than the statistics. When you estimate a job at four hours of work, that is four hours of hands-on time. Your plannable capacity has to account for the rest of the day, or the schedule will promise more than it can deliver.
A worked capacity illustration
Here is a round-number illustration. It is not a benchmark. Swap in your own figures.
- Crew: 4 technicians, 5 days, 8-hour shifts. Gross hours: 4 × 5 × 8 = 160.
- Assume each technician has 6 productive hours per shift after meetings, walking, and waiting. Productive hours: 4 × 5 × 6 = 120.
- One technician is on vacation for 2 days. Subtract 2 × 6 = 12. Available hours: 108.
- Reserve a block for breakdowns and urgent requests. Say 22 hours. Plannable hours: 86.
Eighty-six hours is the number to load against, not 160. A planner who loads 140 hours into this week has built the Tuesday collapse in advance.
How do you pick your own productive-hours figure and breakdown reserve? Look back. Pull the last six to eight weeks of completed work orders and compare hours logged on planned work against hours logged on unplanned work. The reserve is whatever your plant really spends on interruptions, not a number from an article. Start there and adjust as the weeks go by.
Load the week in priority order
Once you know plannable hours, fill them in a fixed order. The order matters because the hours run out, and whatever you place last is what gets bumped.
- Safety-critical and regulatory work first. Anything with a required inspection or a defect that has to be fixed before equipment runs again. Guards, lockout hardware, forklift pre-use findings, pressure relief checks. These do not slide.
- Due and overdue PMs on critical assets. Rank by consequence of failure, not by who complained. If you haven't ranked your equipment, asset criticality ranking shows the consequence-times-likelihood method. A PM on the line that stops the plant outranks a PM on a spare transfer pump.
- Remaining due PMs. Everything else that has reached its due date this week.
- Backlog and corrective work. Pull from the oldest, highest-priority items first.
- Improvement and project work. Valuable, and the first thing to flex when the week goes sideways.
Notice what sits at the bottom. If the week gets squeezed, you want the squeeze to hit the work with the most room to move, not the PMs that prevent the next breakdown. Many missed PMs trace back to this exact ordering problem; why PM tasks get missed goes through the usual causes.
Load by trade, not just by total
A total of 86 plannable hours means nothing if 60 of the jobs need an electrician and you have one electrician. Capacity is per trade.
Split the plannable hours by skill: mechanical, electrical, instrumentation, lubrication, HVAC, whatever your plant uses. Then total the job hours by the same trades. Compare them trade by trade. A schedule can balance in total and still be badly overbooked for one person.
Two more constraints to check as you place each job:
- Equipment access. Many PMs need the machine stopped. Place them in the production windows that operations has agreed to, not wherever hours happen to be free.
- Parts and permits. A job with no part on the shelf is not schedulable yet. Leave it in the backlog until the part is in. Scheduling a job you can't start is how a technician ends up standing around with a full column of work.
Leave slack, and say what it is for
Back in the illustration, the 22-hour reserve is deliberate. A schedule loaded to 100% of plannable hours is a schedule that is already late.
Reserve slack for two things:
- Breakdowns and urgent requests. They will arrive. A week with no reserve means every breakdown pushes planned work out.
- Estimate error. Hours estimates are approximations. Some jobs run long. A little unassigned time absorbs it.
Then be honest about what happens when the reserve goes unused. If the week is quiet, the slack does not vanish. Pull work forward from next week's due list, starting with the highest-ranked items. That is a much better outcome than the reverse, where a bad week eats work you never had room for.
If you are working through a real overdue pile, slack is also what lets you chip away at it. A backlog that ages week after week usually means the reserve is too small or the week is overloaded. An aging view of the backlog, with open tasks sorted into age buckets against today's date, makes that visible. The Maintenance Backlog & Overdue Aging Tracker is one way to see how many weeks of work are sitting in the queue.
Check each day and each person before you publish
A week can fit in total and still fail on Wednesday. Before you release the schedule, run three checks.
Per technician. Add up the assigned hours for each person. Compare each to that person's available hours, not the crew average. One technician at 130% and another at 60% is a common pattern, and it usually means the easy assignments went to whoever the planner talks to most.
Per day. Look at each day as a column. Planners tend to front-load Monday and leave Friday empty, then Monday's work spills over. Spread the load, and keep the heaviest jobs away from the days when operations is likely to need the crew most.
Per job sequence. Check dependencies. If job B can't start until job A finishes, they cannot sit on the same technician's afternoon unless the hours truly fit.
Flag any person or day that exceeds capacity, then fix it by moving the lowest-priority job down the order. Don't squeeze estimates to make the numbers fit. That only moves the failure to Thursday.
A spreadsheet handles this well. The Weekly Work Plan & Technician Assignment Planner takes tasks and crew hours in and gives you an assigned week out, flagging where you've overloaded a technician or a day. It is a template you fill in with your own jobs, hours, and people, not a work-order system, and it does not generate or dispatch anything for you. If you already keep a PM calendar in Excel, it is a natural next sheet.
Close the loop at the end of the week
A schedule you never check against reality never improves. At the end of each week, spend ten minutes on three questions:
- How many of the jobs you scheduled were completed? List what slipped and why.
- How many hours did breakdowns and urgent work actually take? Update your reserve if it was off.
- Which estimates were wrong? Fix the job's hours so next time the plan is better.
After a month, these notes tell you more about your plant than any published average. You will see which jobs routinely run long, which trade is the constraint, and whether your reserve is too small. Feed the findings back into the next week's capacity count.
The goal isn't a perfect schedule. It is a schedule your crew can mostly finish, with the rest moved by choice rather than by default. Count real hours, load by priority and trade, keep slack, and check every person and day. That is weekly maintenance scheduling that survives contact with the plant floor.
Ready to go beyond the guide?
Get more guides like this in your inbox
Related guides
PM Program FundamentalsMaintenance Spare Parts Inventory: Setting Reorder Points from Your PM Schedule
Most stockouts are visible weeks ahead in the PM schedule. Here is how to tie parts to PM tasks and set reorder points from the work you have already planned.
PM Program FundamentalsHow to Structure a PM Schedule Template for Multiple Asset Types
A PM schedule template that works for one asset type often breaks when you add a second. Here's how to structure columns and intervals so it scales.
PM Program FundamentalsPM Scheduling Methods: Calendar-Based, Usage-Based, and Condition-Based Triggers
Not every asset should run on the same clock. Here's how to pick calendar-based, usage-based, or condition-based triggers for each piece of equipment.