What Is Resource Leveling?
Resource leveling is the process of adjusting a project schedule to resolve resource overallocation — situations where more work is assigned to a resource than it can handle at one time. CPM assumes unlimited resources, but reality does not. When two tasks need the same electrician at the same time, one must wait.
The core trade-off: resource leveling may extend the project duration to respect resource limits. This is not a failure — it is a realistic schedule. An infeasible schedule that looks fast but requires people to be in two places at once is not a plan.
The Invisible Schedule Killer
Most project delays are not caused by individual tasks taking longer than estimated. They are caused by resource contention — Task B was ready to start but the only person who could do it was stuck on Task A. This contention is invisible in a CPM schedule because CPM does not model resources. Resource leveling makes the problem visible and solvable.
Leveling vs. Smoothing
| Technique | Objective | Constraint | Effect on Duration |
|---|---|---|---|
| Resource Leveling | Eliminate overallocation — no resource exceeds capacity | Resource limits are fixed; project end date may move | May extend project duration |
| Resource Smoothing | Reduce resource peaks while respecting the project end date | Project end date is fixed; only uses available float | No change to project duration |
When to Use Which
Use leveling when resources are the binding constraint and you can flex the timeline (internal projects, early planning). Use smoothing when the deadline is fixed and you need to work within it (contractual delivery dates, regulatory deadlines). Smoothing can only use available float — if there is not enough, you either level (and slip) or add resources.
How Resource Leveling Works
The Resource Histogram
A resource histogram shows demand for a specific resource over time:
Wk 1: ██ (2 needed, 2 available) ✅
Wk 2: ████ (4 needed, 2 available) ❌ Overallocated
Wk 3: ███ (3 needed, 2 available) ❌ Overallocated
Wk 4: █ (1 needed, 2 available) ✅
Wk 1: ██ | Wk 2: ██ | Wk 3: ██ | Wk 4: ██ | Wk 5: █ ✅
Priority Rules for Leveling
When two tasks compete for the same resource, which one goes first?
| Rule | Logic | When to Use |
|---|---|---|
| Minimum Float First | The task with the least float gets the resource | Default rule — protects tasks closest to becoming critical |
| Critical Path First | Critical-path tasks always win | Prevents project extension from resource contention on the critical path |
| Shortest Task First | Finish the quick task to free the resource sooner | Maximizes throughput and unblocks downstream tasks |
| Most Successors First | The task that unblocks the most downstream work goes first | Reduces total idle time in the network |
| Earliest Due Date | Task with the nearest deadline goes first | Customer-driven projects with hard delivery dates |
Resource Types in Manufacturing Projects
| Resource Type | Examples | Leveling Consideration |
|---|---|---|
| Skilled trades | Electricians, welders, millwrights, pipe fitters | Often the binding constraint. Cannot easily substitute. |
| Equipment | Cranes, forklifts, test equipment, welding machines | Fixed quantity. Schedule equipment use, not just people. |
| Engineering | Controls engineers, process engineers, validation specialists | Shared across multiple projects — multi-project leveling needed. |
| Contractors | External trades, consultants, system integrators | Can often flex quantity (at a cost premium). |
| Space / access | Work permits, confined space, cleanroom access | Physical constraints that limit how many tasks can run in parallel. |
Multi-Project Resource Leveling
In most manufacturing environments, resources are shared across multiple projects. This is where leveling gets complex — and where Critical Chain's drum resource concept and portfolio management become essential.
✅ Good Resource Management
- Level resources during planning, not after delays appear
- Use resource histograms to visualize demand vs. capacity
- Identify the drum resource (most constrained) and stagger projects accordingly
- Maintain resource calendars with vacations, training, and availability
- Level first using float; only extend the project if necessary
❌ Common Mistakes
- Scheduling without considering resources — infeasible "fantasy schedules"
- Overallocating key people across 3-4 projects and hoping they can "make it work"
- Leveling only within projects, ignoring cross-project contention
- Treating all resources as interchangeable (not all electricians have the same skills)
- Forgetting non-project work (maintenance, operations support) that consumes resource time
🎯 Key Takeaway
A schedule that ignores resource constraints is a fantasy. Resource leveling makes your schedule realistic by ensuring no one is expected to be in two places at once. Start with CPM for the logic, then level to respect reality. Use smoothing when the deadline is sacred, leveling when resources are the binding constraint. The real power comes from identifying your drum resource — the one person or piece of equipment that constrains everything — and scheduling the whole portfolio around that constraint.
Interactive Demo
Level resource demand across tasks. Shift work to keep resources below the capacity line.
Stop reading, start modeling
Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.