5.4 Resource Scheduling and Leveling
Key Takeaways
- A pure CPM schedule assumes unlimited resources; resource leveling reconciles the schedule with the finite crews, equipment, and cash actually available.
- Resource leveling shifts non-critical activities within their available float to smooth the resource histogram, ideally without extending the project duration.
- Resource-constrained (resource-limited) scheduling fixes the resource cap first and lets the completion date slip; time-limited leveling fixes the end date and smooths resources only within existing float.
- Leveling consumes float, so activities that were near-critical can become critical and the network can develop a new, resource-driven critical path.
- The goal of leveling is a stable, achievable resource profile that avoids costly peaks (overtime, extra rentals, hiring/firing) and idle valleys.
Resource Scheduling and Leveling
Why this topic matters for the PE Construction exam: A raw CPM schedule tells you when work can happen if resources are unlimited, but real projects have a fixed number of crews, a limited crane fleet, and a cash-flow ceiling. Project Planning and Scheduling carries a heavy weight (7–11 questions), and the exam expects you to recognize how resource leveling reshapes a schedule and how it interacts with float.
The Problem: Resource Peaks and Valleys
When you build a CPM network, every activity is scheduled at its Early Start (ES) by default. If several activities that use the same resource (say, a concrete finishing crew) can all start early, they pile up on the same days. Plotting the daily resource demand produces a resource histogram — and an unleveled histogram is usually spiky: sharp peaks on some days and deep valleys on others.
Peaks are expensive and often impossible: you cannot put 30 carpenters on a job that only has room or supervision for 12. Valleys are wasteful: you pay to mobilize a crew and then leave it idle. Resource leveling (also called resource smoothing when the deadline is fixed) reshapes that histogram to something the project can actually staff and fund.
Using Float to Level
The key mechanical insight the exam tests is that leveling is accomplished by shifting non-critical activities within their float. Every non-critical activity has Total Float (TF) — the days it can slip without delaying the project. By delaying a resource-hungry non-critical activity toward its Late Start (LS), you can move its resource demand off a peak day and onto a valley day.
Worked example
Suppose Activities B and C both need the same 8-person masonry crew, both are 3 days long, and both are scheduled to run on Days 4–6, demanding 16 masons on those days. Only 8 masons are available.
- Activity B is on the critical path (TF = 0). It cannot move.
- Activity C has TF = 4 days.
By delaying Activity C to start on Day 7 (using 3 of its 4 float days), the two activities run back-to-back instead of in parallel. Peak demand drops from 16 to 8 masons, the crew works continuously, and — because C stayed within its float — the project end date does not change.
Two Leveling Strategies
The exam distinguishes two philosophies, and the right answer depends on what is held constant:
| Strategy | What is fixed | What is allowed to change | Typical use |
|---|---|---|---|
| Time-limited (resource smoothing) | Project completion date | Resource peaks are reduced only by shifting activities within available float | Hard contractual deadline; you must finish on time |
| Resource-limited (resource-constrained) | Maximum available resource (crew size, crane count) | Project completion date may be extended | Fixed crew/equipment cap that cannot be exceeded |
In time-limited leveling, you never exceed the float, so the finish date is protected but the resource peak may not fully disappear. In resource-limited leveling, the resource cap is absolute; if smoothing within float is not enough, activities are pushed past their late dates and the project finishes later.
Leveling Consumes Float and Can Move the Critical Path
A critical, easily missed consequence: when you delay a non-critical activity to level resources, you consume its float. An activity that had 4 days of float might be left with zero. If the resource logic forces enough delay, a chain of formerly non-critical activities can become critical — producing a resource-driven (or “resource-critical”) path that is different from the original logic-driven critical path.
This is why leveling is done after the initial CPM pass, and why a leveled schedule must be re-analyzed: the near-critical activities you smoothed may now govern the completion date. Software performs leveling with heuristics (e.g., prioritize activities with the least float, shortest duration, or earliest late finish), because a mathematically optimal solution for large networks is computationally impractical.
Exam Traps
- Leveling within float does not change the project duration; leveling beyond float does. Watch which one the question describes.
- Critical activities have no float, so they cannot be shifted to level resources. If a peak is caused by critical work, only re-sequencing, adding resources, or crashing can help.
- Do not confuse resource leveling (smoothing how many resources are used per day) with time–cost trade-off / crashing (buying a shorter duration by adding resources). They are different tools covered in the next section.
A non-critical activity with 5 days of total float is delayed by 3 days to smooth a labor peak. Assuming no other logic changes, what happens to the overall project completion date?
A contractor has a firm, contractually fixed completion date but an unleveled crew histogram with sharp peaks. Which leveling approach is appropriate, and what is its main limitation?
Why must a CPM network be re-analyzed after resource-limited leveling forces several non-critical activities past their late dates?