Resource Leveling vs. Smoothing: Guide & Examples [2026]
A. Togay Koralturk, Best-Selling PMP Author
Last updated on August 30, 2026
9 min read
Two project managers face the same over-booked engineer, and one quietly slips the deadline while the other holds it — the difference is which resource optimization technique they reached for. Resource leveling and resource smoothing both fix an over-allocated resource, but only one is allowed to move your finish date, and choosing wrong either blows the deadline or overloads your team. This guide explains resource leveling in full — what it is, how it works, how it differs from resource smoothing, its effect on the critical path, and how both are tested on the PMP and CAPM exams.
What is resource leveling?
Resource leveling is a resource optimization technique that adjusts the start and finish dates of activities so the work fits the resources you actually have available. It is what you use when a resource is over-allocated — assigned to more work than it can do at once — or when a resource is limited or shared. Leveling resolves the conflict by delaying activities until the resource is free.
Its defining trait is that it puts the resource limit ahead of the schedule. Because it will not assign a resource beyond its capacity, leveling can push activities later than the schedule originally planned — which means it can extend the project's finish date and change the critical path. That is the price of honoring a hard resource constraint, and it is exactly what separates leveling from its gentler counterpart, resource smoothing.
When to use resource leveling
Use resource leveling when honoring a resource constraint matters more than the original finish date. The trigger is almost always one of a few situations where demand for a resource exceeds its supply and something has to give.
Common cases where leveling is the right call:
- Over-allocation: a person or piece of equipment is booked on two or more activities at the same time and physically cannot do both.
- A limited or scarce resource: only so much of a specialized skill, tool, or material exists, and the schedule has to bend to that ceiling.
- A shared resource: a resource is split across projects, so your project can only use it during certain windows.
- A required maximum: a policy or safety limit caps how much a resource can be used in a period (for example, no overtime).
In all of these, the resource availability is the fixed point and the schedule is what flexes. If instead the finish date is the fixed point, you want resource smoothing.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
How resource leveling works
Resource leveling follows a straightforward loop: find where a resource is over-allocated, then reschedule activities to bring demand within capacity. In practice:
- Build the resource-loaded schedule. Lay out activities against a calendar and total each resource's demand per period.
- Find the over-allocations. Identify where a resource's demand exceeds its available capacity — the peaks that cannot actually happen.
- Delay activities to fit capacity. Push the conflicting activities later until each resource's demand stays within its limit, starting with activities that have float where possible.
- Recheck the critical path. Because leveling moves dates, it can create a new longest path. Recalculate the critical path and the finish date after leveling — the schedule you started with is not the one you end with.
A before-and-after example makes the trade visible. One engineer is booked on two parallel two-week activities, A and B, in the same two weeks — and B has no float:
| Schedule | Weeks 1–2 | Weeks 3–4 | Finish |
|---|---|---|---|
| Before leveling | A and B (engineer double-booked) | — | End of week 2, on paper only |
| After leveling | A | B | End of week 4 |
The original schedule finished in two weeks only as a fiction: it assumed one person doing two jobs at once. Leveling delays B until the engineer is free, and the finish date moves out two weeks — the honest price of the resource limit. The same move tells the two techniques apart: had B held two weeks of float, shifting it would have been resource smoothing, with the finish date untouched. The difference is never the move itself; it is whether float covers it.
Modern scheduling tools can level automatically, but the logic is always this same loop: demand is brought under the capacity ceiling.
Resource leveling vs. resource smoothing
Resource leveling and resource smoothing are the two resource optimization techniques, and the PMP loves the distinction between them. Both smooth out resource demand, but they obey different masters: leveling protects the resource limit and may move the finish date; smoothing protects the finish date and works only within available float. Here is the comparison:
| Resource leveling | Resource smoothing | |
|---|---|---|
| Protects | The resource limit (capacity) | The project finish date |
| Uses | Any delay needed, even beyond float | Only free and total float |
| Finish date | Can be extended | Unchanged |
| Critical path | Can change | Unchanged |
| Resolves over-allocation? | Yes, fully | Only within available float — may not be enough |
The mechanism is the real difference. Smoothing only ever moves activities inside their float, so by definition it never touches the critical path or the end date — but if an over-allocation is bigger than the available float, smoothing alone cannot fully fix it. Leveling has no such limit: it will delay whatever it must, which always resolves the over-allocation but can cost you time. A common real-world approach is to smooth first, and only level if smoothing cannot bring demand under the ceiling.
Resource optimization and the critical path
The critical path is where the two techniques visibly part ways. Smoothing, since it only consumes float and critical-path activities have none, simply reschedules non-critical work into the gaps. Leveling, when it delays an activity beyond its float, can make that activity's chain the new longest path through the project — redefining which activities are critical. This is why a leveled schedule must always be re-analyzed: the critical path before leveling tells you little about the critical path after. In fact, leveling a resource-constrained project is what gives rise to the critical chain, a resource-constrained version of the critical path.
Advantages and limitations
Resource leveling earns its place, but it is not free:
- Advantage — realistic schedules: leveling produces a plan the team can actually execute, because no resource is asked to be in two places at once. It replaces an impossible schedule with an achievable one.
- Advantage — prevents burnout and quality loss: by keeping demand within capacity, it avoids the overload that leads to mistakes, rework, and exhausted people.
- Limitation — it can delay the project: honoring resource limits can push the finish date, which may be unacceptable when the deadline is fixed.
- Limitation — it can raise cost and complexity: a longer schedule can cost more, and leveling can create a more fragile plan where small slips cascade. Smoothing avoids these costs but only works when there is enough float to absorb the peaks.
Resource leveling on the PMP® and CAPM® Exams
On the PMP exam, resource optimization is tested as a choice between leveling and smoothing driven by the project's binding constraint. The single fact the exam hinges on: resource leveling can change the critical path and extend the finish date, while resource smoothing works only within float and cannot. A scenario will hand you an over-allocated resource plus a constraint — a fixed deadline, a hard resource limit — and expect you to pick the technique that respects it.
The CAPM tests the same distinction a little more directly, often by asking which technique may delay the project or which stays within float, but the CAPM is scenario-based like the PMP, so expect to apply the difference rather than just define it. Both exams treat leveling and smoothing as the two resource optimization techniques and expect you to connect smoothing to float. Our PMP Complete Study Guide works these choices through with scenarios so the right technique is obvious the moment you spot the binding constraint.
PMP Practice Question: Resource Leveling vs. Smoothing
A senior specialist is assigned to two parallel activities scheduled in the same week, and cannot do both — an over-allocation. The project's finish date is fixed by contract and cannot move. One of the two activities has enough total float to be delayed a week without affecting the finish date, and the specialist is the only person qualified to do this work.
What should the project manager do?
a) Level the resources by delaying one activity until the specialist is available, accepting that the project's finish date will move later.
b) Smooth the resources by rescheduling the activity that has float, moving it within its available float so the specialist is no longer over-allocated and the finish date is unchanged.
c) Reassign one of the two activities to another team member to remove the over-allocation immediately.
d) Take no scheduling action and have the specialist work overtime that week to cover both activities.
Correct answer: B.
Rationale: Every option is a plausible response to an over-allocation, so the choice turns on the constraints buried in the stem: the finish date is fixed by contract, and one activity has enough float to absorb the shift. That is the textbook case for resource smoothing — move the floating activity within its float and the conflict disappears with the finish date and critical path untouched. Leveling would also resolve the clash, but leveling is permitted to push the finish date, which the contract forbids, and that is precisely the distinction being tested; reassigning the work fails on a detail you must catch, since the stem says the specialist is the only person qualified; and overtime ignores the scheduling tools entirely, buying fatigue and quality risk when a clean float-based fix exists. To drill this kind of constraint-matching question under exam conditions, work through our PMP practice exams or, at the entry level, our CAPM practice exams.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
Frequently asked questions
What is resource leveling?
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so the work fits the resources actually available, resolving over-allocation or honoring a limited resource. Because it puts the resource limit ahead of the schedule, resource leveling can extend the project's finish date and change the critical path.
What is the difference between resource leveling and resource smoothing?
Resource leveling adjusts dates to respect resource limits and can extend the finish date and change the critical path. Resource smoothing adjusts activities only within their free and total float, so it removes resource peaks without delaying the finish date or changing the critical path — but it cannot always fully resolve an over-allocation. Leveling protects the resource limit; smoothing protects the deadline.
Does resource leveling change the critical path?
Yes, it can. Because resource leveling is allowed to delay activities beyond their available float to respect resource limits, it can make a different chain of activities the longest path and push out the finish date. A leveled schedule should always have its critical path and completion date recalculated afterward.
When should you use resource leveling?
Use resource leveling when honoring a resource constraint matters more than the original finish date — for example, when a resource is over-allocated, scarce, or shared across projects, or when a hard limit such as no overtime applies. If instead the finish date must hold and there is float available, use resource smoothing.
What are the two resource optimization techniques?
The two resource optimization techniques are resource leveling and resource smoothing. Leveling adjusts the schedule to fit resource limits and may delay the project; smoothing adjusts activities within their float to avoid resource peaks without delaying the project. They are often used together, smoothing first and leveling only if needed.
Is resource leveling on the PMP exam?
Yes. Resource optimization is a core PMP scheduling topic. The exam tests it through situational questions that give you an over-allocated resource and a constraint, then ask whether to level or smooth — rewarding you for knowing leveling can extend the finish date and change the critical path while smoothing works only within float.
Is resource smoothing on the CAPM exam?
Yes. The CAPM covers both resource optimization techniques, usually a bit more directly than the PMP — often asking which technique may delay the project or which stays within float. Because the CAPM is scenario-based, expect to apply the leveling-versus-smoothing distinction in a short situation, not just recall the definitions.
Fast-Tracking vs. Crashing: Schedule Compression [2026]
Fast-tracking vs crashing, the two schedule compression techniques: what each is, how they differ, when to use which, and how both are tested on the PMP exam.
Bottom-Up Estimating: Definition, Steps & Example [2026]
Bottom-up estimating sums every work package for the most accurate cost or duration. How it works, a worked example, bottom-up vs top-down, and its limits.
Monte Carlo Simulation in Project Management [2026]
Monte Carlo simulation in project management: how it works, reading the S-curve and P50/P80 values, when to use it, and how it is tested on the PMP exam.
