Resource Levelling vs Smoothing: One Moves the Finish Date, One Never Does

TL;DR: Resource levelling shows up in 13 answer options in this bank and is keyed 3 times. Almost every wrong use is the same error: reaching for it to make a schedule shorter. Levelling fits work to the resources available, which usually makes the schedule longer. Smoothing is the version that protects the finish date, and it works only within float. One question tells you which the scenario wants: is the completion date allowed to move?

Both techniques even out uneven resource demand. That shared purpose is what makes them so easy to swap, and the exam builds questions specifically on the difference.

What actually separates levelling from smoothing?

Whether the finish date is permitted to move.

The bank states this as a rule in a record about an installation crew. The resource histogram peaks far above the number of people available in some weeks while the crew sits idle in others, and the activities concerned are not on the critical path and carry several days of float. The question asks which technique evens out the demand without moving the project's finish date. Keyed is resource smoothing, and the explanation gives the full distinction: smoothing and levelling are the two resource optimization techniques, and what separates them is whether the finish date is allowed to move. Smoothing adjusts activities only within their free and total float, so the critical path is untouched and the project completes on the same date. It then names the price, which is the part candidates skip: smoothing cannot always bring demand under the limit, because there is only so much float to work with.

The mirror record settles it from the other side. A part-time stonemason on the critical path forces the project manager to push the planned completion date back to fit the mason's limited availability. Keyed is resource levelling. Smoothing is offered as the distractor and loses in one clause: it works only within available float and does not change the critical path.

Why is levelling wrong so much more often than it is right?

Because candidates use it as a general-purpose schedule fix, and the bank writes it into distractors precisely where a compression technique belongs.

Four records make the same point with different surfaces. A project manager spends an extra $150,000 and finishes three weeks early: resource levelling is offered and loses to schedule compression, and the explanation says that levelling adjusts work to fit resource availability and normally lengthens the schedule rather than shortening it. A sponsor asks for faster delivery with no additional money: levelling is offered and loses to fast tracking. A client expands scope while keeping the date, requiring round-the-clock work: levelling is offered and loses to spreading work across time zones. A junior project manager asks how to forecast remaining duration by analysing the sequence with least scheduling flexibility: levelling is offered and loses to the critical path method, which the explanation dismisses in six words, noting that levelling smooths resource use over time.

The pattern is consistent enough to use as a heuristic. If the stem is about going faster, levelling is not the answer. It is the technique for a schedule that has to accommodate reality, not one that has to beat it.

Common trap: treating levelling as the answer whenever a resource is scarce. The bank offers it in exactly that shape and keys something else. A team member is unavailable, a specialist is stretched across projects, a crew is over-allocated, and levelling reads as the responsible response. But scarcity alone does not tell you what the scenario wants, because levelling costs you the finish date. The bank explains this rather than just marking the option wrong, and once you have seen the trade stated, the choice stops being a coin flip: check whether the stem has told you the date can move.

When does the bank key levelling?

Three times, and each is instructive.

The stonemason case is the pure definitional one: a constraint on the critical path, a date pushed back, and the technique named. The second is a matching-style item where levelling is simply the correct label for adjusting work to resource availability.

The third is the most useful for a scenario question. Planning a hospital wing refit, a project manager sees that the commissioning phase and the fit-out phase overlap, and both draw on the same small pool of mechanical and electrical engineers. The overlap is still months away. Keyed is developing a resource-levelling plan that addresses the anticipated bottleneck. The explanation gives the reasoning for the timing: the contention has been identified during planning, which is exactly when it can be resolved cheaply, by levelling the demand across the two phases so it stays within what the pool can supply.

Note what loses here, because all three distractors are things candidates do. Reallocating the engineers now simply moves the problem before the demand profile has been worked out. Compressing the overlapping phases intensifies the contention rather than relieving it. Telling the stakeholders about the potential issue does not resolve it. The keyed answer is the one that produces a plan, and the fact that the bottleneck is months away is not a reason to wait. It is the reason levelling is affordable here at all.

FAQ

What is the difference between resource levelling and resource smoothing? Levelling adjusts start and finish dates to respect a resource constraint, and it is allowed to move the project completion date and change the critical path. Smoothing adjusts activities only within their free and total float, so the critical path is untouched and the finish date holds. The trade-off is that smoothing cannot always bring demand under the limit.

Does resource levelling shorten the schedule? No, and this is the most common misreading. Levelling fits work to available resources and normally lengthens the schedule. If a question asks how to finish sooner, levelling is a distractor. Crashing and fast tracking are the schedule compression techniques.

When is resource levelling the keyed answer? When a resource constraint is real and the finish date is allowed to move, or when demand exceeds supply and there is not enough float to absorb it. The bank also keys developing a levelling plan when a resource bottleneck has been spotted during planning, months before it would bite.

Which technique do I use if the finish date cannot move? Smoothing, provided the over-allocated activities carry enough float. If they sit on the critical path or have no float, smoothing has nothing to work with, and the choice becomes levelling with a later finish or compression with added cost.

Try it yourself

PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.

Related reading: Crashing and Fast-Tracking: 4 Keyed, 22 Distractors, and One Question Settles It and Critical Path Method (CPM) & Float. Schedule and resource tasks are mapped on the Process domain study page.

Sources: PMI, 2026 PMP Examination Content Outline.

FAQ