Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Know it well enough for the exam? Questions on Resource Leveling are scenario-based, not definitional.
Practice it freeExplanation
Leveling is applied after the first CPM schedule exists, when a resource histogram or the scheduling tool shows that a constrained resource is over-allocated. It is also used when shared resources are only available at certain times (recorded in resource calendars) or when the organization wants a resource used at a steady level rather than in peaks.
The mechanics are simple: delay the activities competing for the resource, using float first and going beyond float when there is not enough. If the organization allows it, long activities can be split. Most scheduling tools can level automatically, but the project manager should review the result, because the tool's choice of which activity waits may not match business priorities.
Leveling is one of several responses to over-allocation, and the right one depends on which constraint is fixed. If the end date is fixed, smoothing within float or adding resources (at a cost) is the answer. If the resource is genuinely capped, leveling produces the only achievable plan. If the leveled finish date breaches the schedule baseline, that goes through change control rather than being absorbed silently.
Resource leveling in plain language
The critical path method builds a schedule as if every person and machine were available whenever the logic says work can start. Real projects have one database specialist, one crane, one test lab. When the schedule asks a resource to be in two places at once, it is over-allocated, and the dates on paper are not achievable.
Resource leveling fixes that by moving work until the demand on each constrained resource fits its availability. It accepts a later finish date if that is what it takes. That is the whole difference from resource smoothing, which may only move work within its float and never touches the end date.
You reach for leveling when a resource is genuinely capped: a single specialist, a shared piece of equipment, a contractual limit on crew size, or a person released only part time by a functional manager (recorded in the resource calendars). It is applied during Develop Schedule, after the CPM dates exist, and again whenever assignments change.
Worked example: one specialist, two overlapping tasks
A reporting project has four activities. Priya is the only database engineer and works on A, B and C. D is done by the wider team.
| Activity | Duration (days) | Predecessors | Resource |
|---|---|---|---|
| A — Data model | 2 | — | Priya |
| B — Build data warehouse | 4 | A | Priya |
| C — Build report queries | 3 | A | Priya |
| D — User acceptance test | 2 | B, C | Team |
Before leveling: the CPM schedule
CPM starts B and C together on day 3. The critical path is A → B → D (2 + 4 + 2 = 8 days). C finishes on day 5 but D can't start until day 7, so C has 1 day of total float.
| Activity | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| A — Data model | |||||||||||
| B — Data warehouse | |||||||||||
| C — Report queries | |||||||||||
| D — UAT (team) | |||||||||||
| Priya's load | 1 | 1 | 2 | 2 | 2 | 1 | · | · | · | · | · |
Priya's load is 2 on days 3, 4 and 5. Nobody can do 16 hours of focused work in an 8-hour day, so this schedule will slip; the question is whether you plan the slip or discover it.
Try smoothing first
Smoothing may shift C only within its 1 day of float. Moving C to days 4–6 still overlaps B on days 4, 5 and 6, so the over-allocation remains (just moved). Smoothing can't solve a 3-day conflict with 1 day of float.
After leveling
Leveling lets C wait until Priya finishes B. C now runs on days 7–9 and D on days 10–11.
| Activity | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| A — Data model | |||||||||||
| B — Data warehouse | |||||||||||
| C — Report queries | |||||||||||
| D — UAT (team) | |||||||||||
| Priya's load | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | · | · |
Three things changed, and each is a favourite exam point:
- The finish date moved from day 8 to day 11 (+3 days).
- C went from 1 day of float to zero. The critical path is now the resource-driven chain A → B → C → D, which did not exist in the logic-only network.
- Priya's peak demand dropped from 2 to 1, with no idle gaps for her between days 1 and 9.
Compare the options
| Option | Finish | Over-allocation | Trade-off |
|---|---|---|---|
| CPM schedule as is | Day 8 | 3 days at 2× | Unrealistic; the slip happens anyway |
| Resource smoothing | Day 8 | Still 3 days | Keeps the date but not enough float to fix it |
| Resource leveling | Day 11 | None | Achievable plan; 3 days later |
| Add a second DB engineer for C | Day 8 | None | Extra cost and onboarding risk |
| Run B first, then C, but overlap D with C | Earlier than 11 | None | Fast tracking; rework risk if UAT starts on partial reports |
In a real project you would bring the leveled date and the alternatives to the sponsor. If the extra three days breach the schedule baseline, that is a change request, not a quiet update.
Common exam traps
Choosing leveling when the scenario says the end date cannot move.
A fixed end date points to resource smoothing (or adding resources). Leveling is the answer when the resource limit is the hard constraint and the date is allowed to move.
"Resource leveling never changes the critical path."
It often does. Leveling can create a new critical path made of activities linked only because they share a resource, as C did above.
Confusing leveling with crashing.
Crashing adds resources to shorten the schedule (cost goes up). Leveling works within the resources you have (time goes up). They pull in opposite directions.
Thinking leveling always delays the project.
If the conflicting work has enough float, leveling may finish on the original date. It may extend the schedule; it does not have to.
Using the resource histogram as the answer.
A resource histogram shows the over-allocation (the "2" bars above). It is how you spot the problem, not how you fix it.
The PMBOK Guide 6th edition lists leveling and smoothing as the two resource optimization techniques of Develop Schedule. In agile settings the same problem is handled differently: the team plans to its capacity at iteration planning, limits work in progress, and keeps a sustainable pace, so over-allocation is prevented rather than leveled out afterwards.
Leveling vs smoothing at a glance
| Resource leveling | Resource smoothing | |
|---|---|---|
| Primary constraint | Resource availability | Project end date |
| Can the finish date move? | Yes | No |
| Can the critical path change? | Yes | No |
| Moves activities | Beyond their float if needed | Only within their float |
| Resolves every over-allocation? | Yes, by design | Not always |
| Typical trigger | One specialist, shared equipment, crew limits | Peaks and valleys you want evened out |
Practice and related pages
Free practice questions on this concept (full explanations, no signup):
- What resource leveling is used for
- All free CAPM schedule questions
- PMP: plan and manage budget and resources — balancing competing resource demands
Study next:
Spelling
Key Points
- •Resolves over-allocation by moving work; the resource limit takes priority over the date
- •May extend the finish date and create a new critical path
- •Uses float first, then goes beyond float when needed
- •Resource smoothing, by contrast, keeps the end date and moves work only within float
- •Spot the problem with a resource histogram; fix it with leveling or smoothing
Exam Tip
Read which constraint is fixed. If the resource is capped and the date may move, the answer is leveling. If the date is fixed, the answer is smoothing (or adding resources). Leveling can extend the schedule and change the critical path; smoothing cannot.
Frequently Asked Questions
Related Topics
Resource Smoothing
Resource smoothing is a resource optimization technique that adjusts activities within their available float so that resource requirements do not exceed predefined limits, without changing the project end date.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Float (Total Float and Free Float)
Total float is the amount of time an activity can be delayed from its early start without delaying the project finish date. Free float is the amount of time an activity can be delayed without delaying the early start of any successor activity.
Resource Calendars
Resource calendars identify the working days, shifts, start and end of normal business hours, weekends, and public holidays when each specific resource is available for project work.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Resource Smoothing
Resource smoothing is a resource optimization technique that adjusts activities within their available float so that resource requirements do not exceed predefined limits, without changing the project end date.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Part of
Schedule Management
Practice Resource Leveling
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.