Resource Allocation and Leveling
Allocating resources
After the logic is set, assign people and equipment to activities. Resource histograms show demand over time; resource calendars show availability. Watch for over-allocation (one person booked above capacity) and contention (two activities needing the same scarce resource simultaneously).
Leveling versus smoothing
Resource leveling resolves over-allocation by shifting activities within their float; if float is insufficient, it may extend the project duration and move the critical path. Resource smoothing (time-limited) adjusts demand without extending the finish date, using float only. Know the distinction: leveling may change the end date; smoothing must not.
Other tools
Crashing adds resources to critical activities to shorten duration, at increased cost. Fast tracking overlaps activities that were sequential, raising rework risk. What-if analysis and Monte Carlo simulation test schedule risk. A resource-constrained schedule is built when availability, not logic, drives the sequence.
Traps in questions
- Calling smoothing "leveling" when the question says the end date must not move.
- Assuming leveling never changes duration; it can.
- Crashing a non-critical activity - it will not shorten the project.
- Fast tracking without acknowledging increased risk.
Rule of thumb
If the finish date is fixed, smooth. If over-allocation must be resolved and the date can move, level. Crash only critical activities, and only where cost per day saved is acceptable.
Worked example: A designer is booked 120% in week 4. Shifting one task by 3 days uses its 4-day float, so the finish is unchanged - that is smoothing. If the float were only 2 days, leveling would push the finish out by 1 day.