How to Level Resources in a Schedule
Resolve overloaded people, equipment and facilities without making arbitrary date changes. This guide shows how to identify capacity conflicts, choose the right adjustment and produce a schedule that can realistically be executed.
What resource leveling means
Resource leveling is the process of changing scheduled timing or work assignments so that demand does not exceed the resources realistically available. The resource may be a person, role, machine, vehicle, room, workstation, specialist, supplier or other limited capability required to perform an activity.
A schedule can appear logically correct while still being impossible to execute. Two activities may have valid predecessors and planned dates, yet both may require the same person at the same time. If that person cannot perform both assignments, the plan assumes capacity that does not exist. Resource leveling exposes and resolves that assumption.
The objective is not to keep every resource busy every minute. The objective is to create a credible combination of timing, workload and availability. A fully occupied schedule with no room for coordination, quality checks or predictable variation may look efficient but fail in real operation.
The U.S. Government Accountability Office describes resource leveling as adjusting activity timing or work assignments to account for availability. Its Schedule Assessment Guide also warns that a schedule without justified resource assignments can imply unlimited availability and create false confidence. For everyday scheduling, the lesson is straightforward: dates are believable only when the required capacity exists when the work is planned.
Resource leveling versus resource smoothing
| Decision point | Resource leveling | Resource smoothing |
|---|---|---|
| Primary constraint | Resource availability is treated as a firm limit. | The required finish date or critical path is protected. |
| Allowed timing change | Activities and even the completion date may move. | Activities move only within available schedule flexibility. |
| Main purpose | Create an executable plan using realistically available capacity. | Reduce peaks and uneven workloads without moving the required finish. |
| Typical use | A specialist, facility or machine cannot meet simultaneous demand. | Work can be repositioned within float to create a steadier workload. |
| Possible result | The critical path or final date may change. | The final date should remain unchanged if flexibility is sufficient. |
The terms are sometimes used loosely in everyday conversation. For reliable decisions, state which constraint is fixed. If capacity cannot increase, you are generally leveling around a resource limit. If the finish date cannot move and activities are adjusted only within existing flexibility, you are smoothing the workload. A schedule may use both methods at different stages.
Information required before leveling
Defined activities
Each activity should represent understandable work with a reasonable duration. Leveling vague summary items gives little insight into when a resource is actually needed.
Reliable dependencies
Identify what must happen before, after or alongside each activity. Resource decisions made on broken logic can move work into an impossible sequence.
Resource requirements
Record the role, skill, equipment or facility required, the amount of effort needed and whether substitutes are acceptable.
Availability calendars
Include working hours, planned leave, shift patterns, maintenance, closures, contractual limits and other known availability restrictions.
Priority rules
Decide which work moves first when two activities compete. Relevant factors include dependencies, milestone sensitivity, flexibility and business need.
Decision authority
Clarify who may reassign people, authorize overtime, accept a later date, change scope or approve an external resource.
How to level resources step by step
Choose the schedule and leveling horizon
Define the part of the schedule being evaluated. A practical horizon might be the next two weeks for an operations team, one academic term for a class planner or the remaining duration of a project phase. Use a horizon long enough to reveal downstream effects but detailed enough for availability information to be dependable.
Record the schedule version and status date. If work has already started, preserve actual dates and remaining work. Resource leveling should not rewrite completed history merely to make the plan appear cleaner.
Create a realistic availability profile
Determine when each constrained resource can actually work. For a person, subtract leave, training, standing meetings, support duties and other committed work from nominal working hours. For equipment, account for maintenance, setup, inspection and shared use. For rooms or facilities, record opening periods and existing reservations.
Avoid equating an eight-hour workday with eight hours of schedulable task capacity unless that assumption is true for the role. Availability should reflect the time that can genuinely be committed to the scheduled work.
Assign demand to the activities
State which resource is required, how much effort is needed and over what period the work can occur. Distinguish duration from effort. A task may span three days but require only six hours of a specialist’s attention. Conversely, a one-day activity may require several people simultaneously.
Identify whether the assignment is fixed, replaceable or shareable. A named approver may be mandatory, while general data-entry work may be reassigned among qualified team members.
Compare demand with capacity period by period
Total the assigned effort for each relevant day, shift or week and compare it with available capacity. Mark every period where demand exceeds availability. Also look for abrupt peaks followed by unused capacity, because moving flexible work may create a steadier and more practical plan.
Check shared resources across all included work, not only within one project. A schedule may look feasible in isolation while competing with another plan for the same person or equipment.
Identify the real bottleneck
Do not automatically move the largest task. Determine which specific skill, person, machine or decision capacity creates the conflict. An activity assigned to five people may be delayed because only one certified reviewer is unavailable. Addressing general staffing would not solve that bottleneck.
Protect immovable work
Mark activities tied to real external dates, safety windows, examinations, booked facilities, contractual commitments or mandatory dependencies. Confirm that the date is genuinely fixed rather than merely preferred. Artificially fixing too many activities removes the flexibility needed to resolve overloads.
Rank movable work using transparent rules
Among competing activities, consider dependency effects, available float, milestone sensitivity, required skill, cost of interruption and consequence of delay. Apply the rules consistently. Moving work only for the person who argues most strongly creates an unstable schedule and weakens trust.
Test the least disruptive adjustment first
Start with changes that preserve scope, quality and important milestones. Options include moving flexible work, changing sequence where logic permits, reassigning to an equally qualified resource, splitting independent portions, using a different approved facility or adjusting the work pattern.
Do not assume overtime is the default solution. It may be unavailable, unsustainable or inappropriate for the work. If additional capacity is considered, verify approval, competence, onboarding time and cost before treating it as available.
Recalculate downstream timing
Every movement can affect successors, handoffs and milestones. Recalculate dates after each meaningful adjustment. An activity that originally had flexibility may become critical after it is delayed. A different sequence may also create a new resource conflict later in the schedule.
Validate the proposed assignments
Confirm the result with the people who perform or coordinate the work. Check skills, access, location, shift limits, required collaboration and practical handoff time. Automated scheduling can identify mathematical availability, but it may not understand every operational restriction.
Document the decision and publish the updated plan
Record what moved, why it moved, who approved the change and which milestone or completion date was affected. Communicate the approved schedule rather than allowing different participants to work from conflicting versions.
Monitor actual workload and re-level when needed
Availability and remaining effort change during execution. Compare planned assignments with actual progress. Re-level when a key resource becomes unavailable, work takes materially longer than expected, priorities change or newly approved activities enter the same planning horizon.
Resource Load Analyzer
Add activities assigned to one resource. The analyzer totals demand, compares it with available capacity and indicates whether work must be moved, reassigned or supported with approved additional capacity.
| Suggested review order | Activity | Hours | Priority | Flexibility |
|---|
Resource-leveling options and tradeoffs
Delay a flexible activity
Move work to a period with available capacity. This is often the cleanest choice when the activity has flexibility and its successor dates remain acceptable.
Recheck all downstream dependencies. A task can consume its flexibility and become time-sensitive after being moved.
Reassign the work
Transfer the activity to another qualified resource with capacity. Confirm competence, access, accountability and handoff effort before assuming the reassignment saves time.
Split independent portions
Divide work only where portions can be completed separately without excessive coordination or quality risk. Splitting tightly integrated work may create more overhead than it removes.
Change valid sequencing
If two activities are not truly dependent, revise the sequence so another resource can progress while the bottleneck is occupied. Never delete a real dependency merely to improve the appearance of dates.
Add approved capacity
Additional staff, equipment, shifts or external support can help when the work is divisible and approved. Include procurement, onboarding and supervision time in the decision.
Change scope or deadline
When capacity is fixed and all required work cannot fit, leadership may need to reduce scope, phase delivery or approve a later date. Leveling makes this tradeoff visible rather than hiding it.
Worked resource-leveling examples
Shared designer across two launches
A designer has 30 available production hours next week. Launch A requires 22 hours and Launch B requires 18, creating ten hours of excess demand. Launch A assets are needed before a fixed media booking. Launch B has three days of flexibility and contains six hours of resize work that another qualified designer can perform.
A practical leveled plan protects Launch A, reassigns the six independent resize hours and moves four flexible Launch B hours into the following period. The schedule records the new handoff and approval time rather than treating reassignment as instant.
One laboratory for several classes
Three classes request the same laboratory during a two-hour period. Room capacity—not teacher availability—is the bottleneck. One activity requires equipment permanently installed in the laboratory; another can use portable equipment in a standard classroom; the third can occur the next morning.
Leveling protects the equipment-dependent class, moves the portable activity to a suitable classroom and reschedules the flexible class. The plan also checks teacher, student and equipment availability at the new times.
Restaurant onboarding during a busy week
A manager is assigned to regular shifts, two new-hire orientations and an inventory review. Demand exceeds the manager’s available administrative hours. Orientation must occur before employees begin work, while inventory review can move within the week.
The schedule protects orientation, assigns an approved supervisor to part of the standardized training and moves inventory review to a lower-demand period. Required manager-only topics remain with the manager.
Maintenance equipment bottleneck
Several activities require one lifting device. The original schedule places them in parallel, even though the device can support only one job at a time. The team sequences jobs by dependency and setup efficiency, reserves the device for each window and moves preparatory work earlier.
This avoids pretending the equipment exists in multiple places and reduces repeated setup without changing the technical order of work.
Common resource-leveling mistakes
Assuming nominal hours equal capacity
A person’s paid hours may include meetings, administration and support. Use genuinely schedulable capacity, not the maximum theoretical total.
Ignoring other schedules
A resource may appear free in one plan while already committed elsewhere. Consolidate demand across the relevant portfolio or operational calendar.
Moving work without recalculation
Every movement can alter successors, flexibility and milestones. Recompute downstream dates after each material adjustment.
Using priority alone
High priority does not eliminate dependencies, specialist requirements or fixed access windows. Use priority as one factor in a transparent rule set.
Overusing overtime
Overtime is additional capacity only when it is approved, appropriate, sustainable and supported by the people involved. It should not conceal a recurring structural shortage.
Trusting automatic leveling blindly
Software follows its configured rules. Review every important movement for practical feasibility, valid logic and unintended milestone effects.
How to judge whether the leveled schedule is better
A leveled schedule should be executable, not merely visually smoother. Compare resource demand with actual availability in every relevant period. Confirm that no resource is assigned more simultaneous work than it can perform. Then inspect milestone dates, critical dependencies, handoffs and newly created peaks.
Useful measures
- Number and size of remaining overallocations
- Peak demand compared with available capacity
- Milestone movement caused by leveling
- Amount of work reassigned or deferred
- Number of unapproved capacity assumptions
- Difference between planned and actual resource use
Quality questions
- Can every resource accept the proposed assignment?
- Are skill, location and access requirements satisfied?
- Are mandatory dependencies still intact?
- Have handoff and setup times been included?
- Do stakeholders understand changed dates?
- Is there a clear point for the next workload review?
Track actual workload after publishing the schedule. If the same resource is repeatedly overloaded, the problem may not be a one-time sequencing conflict. It may indicate insufficient capacity, unrealistic effort estimates, too much concurrent work or a dependency on one specialist. Escalate the structural decision instead of repeatedly moving the same activities.
Resource-leveling checklist
- The leveling horizon and schedule version are defined.
- Completed work and actual dates remain unchanged.
- Activities have reliable durations and dependencies.
- Required people, skills, facilities and equipment are identified.
- Availability reflects real commitments and restrictions.
- Demand is checked across all relevant schedules.
- Fixed work is separated from merely preferred timing.
- Movable work is ranked using documented rules.
- The least disruptive feasible adjustment is tested first.
- Reassignments account for skills and handoff effort.
- Downstream dates are recalculated after changes.
- New resource conflicts are checked.
- Milestone and completion effects are documented.
- Proposed assignments are validated with responsible people.
- The approved plan has one controlled published version.
- A future capacity-review point is scheduled.
Use the Weekly Schedule Builder to translate approved assignments into a dated weekly plan. Teams managing multiple employees can use the Employee Schedule Maker. Additional planning methods are available in the ScheduleFlowLab Guides.
Resource leveling FAQs
Can resource leveling change the project completion date?
Yes. When resource availability is a firm limit, resolving an overallocation may delay activities and move the final completion date. If work can be repositioned entirely within available flexibility, the completion date may remain unchanged.
Which activity should be delayed first?
There is no universal rule. Consider valid dependencies, milestone sensitivity, available flexibility, required skills, cost of delay and organizational priority. Document the rule so similar conflicts receive consistent treatment.
Should low-priority work always move?
No. Low-priority work may be a mandatory predecessor for important work or may have a fixed external window. Priority is only one factor; schedule logic and real constraints must also be respected.
Can one person be assigned to multiple tasks on the same day?
Yes, if the combined effort fits within real availability and the timing is practical. Simultaneous assignments, excessive context switching or travel requirements can make a mathematically possible plan unworkable.
Does adding more people always shorten an activity?
No. Some work cannot be divided efficiently, and additional participants may require onboarding, coordination or review. Confirm that the activity is divisible and that added resources possess the required capability.
When should resources be re-leveled?
Re-level when availability changes, remaining effort changes materially, new work is approved, priorities shift or progress creates a new bottleneck. The review frequency should match the speed and volatility of the schedule.
Can resource leveling be performed manually?
Yes. A small schedule can be leveled using a table or calendar that compares demand with capacity. Larger, interconnected schedules may benefit from scheduling software, but important movements still require human validation.
What if no adjustment can meet both capacity and deadline?
Present the tradeoff clearly. Decision-makers may need to add approved capacity, reduce or phase scope, change the deadline or accept a documented risk. Do not publish an impossible schedule simply because none of the choices is convenient.