Quick Answer

Resource leveling is a schedule optimization technique that adjusts activity start and finish dates so no person, crew, or piece of equipment is booked beyond its available capacity. To level a schedule, you find the overallocation, check float, delay or split the lowest-priority work, then recheck the critical path and agree on any new finish date.

Watch resource leveling on a real schedule

Our short explainer walks through resource leveling on a real example. Watch it first, then use the steps below on your own plan.

Resource Leveling in Project Management (With a Real Example), from the PMTraining YouTube channel.

What is resource leveling?

Resource leveling is one of two resource optimization techniques in project scheduling. You reach for it after you assign real people to the schedule and find someone booked for more hours than they have.

The network diagram can look perfect while the resource histogram (a bar chart of demand per period) tells a different story. One engineer at 160% in a single week is a schedule that will fail quietly, through overtime, rushed work, or missed handoffs.

Leveling fixes that by moving work until demand fits inside capacity. Because it will move activities that have no float, leveling can change the critical path and push out the finish date. Its lighter cousin, resource smoothing, only moves work within float, so the finish date holds.

Leveling belongs mainly to predictive and hybrid schedules. Agile teams handle the same problem through capacity-based iteration planning.

How to do resource leveling, step by step

Work through these five steps in order:

  1. Set real capacity. Assign named resources and update their calendars for holidays, part-time splits, and other projects.
  2. Find the overallocation. Run the resource histogram and mark every period where demand crosses the capacity line.
  3. Check float first. If the overloaded activities have float, smooth them and stop. The finish date holds.
  4. Delay or split the lowest-priority work. Push it until the resource frees up, or split a long activity around the peak.
  5. Recheck the critical path and finish date. If the date moved, decide with your sponsor whether to accept the slip or buy capacity through overtime, a contractor, or a second crew.
The five steps of resource leveling as a decision flow A flowchart of the five leveling steps. Step 1, set real capacity, leads to step 2, find the overallocation, which leads to step 3, a decision: does the overloaded work have float? If yes, smooth within float and the finish date holds. If no, step 4 delays or splits the lowest-priority work, and step 5 rechecks the critical path. A second decision asks whether the finish date moved. If no, rebaseline and communicate the new plan. If yes, agree on the date with your sponsor: accept the slip, or buy capacity with overtime, a contractor, or a second crew. Leveling starts with a float check and ends with a date decision. No Yes No Yes 1. Set real capacity Named resources and accurate calendars 2. Find the overallocation Demand above the capacity line 3. Does the overloaded work have float? 4. Delay or split Move the lowest- priority work first 5. Recheck the critical path Leveling can create a new one Smooth within float The finish date holds Did the finish date move? Rebaseline Same date, new resource plan Agree on the date with your sponsor Accept the slip, or buy capacity with overtime, a contractor, or a second crew. Why step 3 comes first Smoothing is the free exit. Check float before you move any work, so you only level the overload that truly has nowhere to slide.
PMTraining framework showing the five resource leveling steps as a decision flow. Steps match the walkthrough above.

How it works in practice

An ERP rollout. One data-conversion specialist is assigned to the finance and HR conversions in the same two-week window, and both activities sit on the critical path. Leveling sequences HR after finance, which pushes go-live out two weeks. The sponsor weighs that slip against a contract specialist's cost, hires one for HR, and keeps the original date.

A residential build. On a home construction project, one framing crew is scheduled to start two houses on the same Monday. The builder levels by framing the second house after the first is under roof. That house finishes eight working days later, and the builder resets its closing date with the buyer before the contract is signed, not after.

We often see newer project managers accept whatever dates the software produces and skip step five. That conversation is the step that protects you.

Where to learn more

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) is the primary home for resource leveling. The Eighth Edition, published in November 2025, underpins the PMP exam launched in July 2026. Its Schedule and Resources performance domains show how demand, capacity, and float interact.

The Standard for Portfolio Management helps when one resource pool serves many projects. Its capacity and capability management guidance is leveling at the portfolio scale.

Frequently Asked Questions

Can scheduling software level resources automatically?

Yes. Tools such as Microsoft Project include automatic leveling that delays or splits tasks based on priority and resource calendars. Treat the result as a draft. The software cannot know which delay your sponsor will accept, so review every move before you rebaseline.

What happens to the critical path after resource leveling?

It often changes. Once two activities wait on the same resource, that resource dependency becomes part of the longest path, so work that had float can turn critical. Recalculate the critical path after every leveling pass and watch the activities that just lost their float.

Conclusion and next steps

Resource leveling trades time for a schedule your people can actually deliver. Run the five steps, then make the date decision out loud with your sponsor.

Our live PMP certification classes work through schedule and resource trade-offs with an instructor, so you practice the judgment behind the steps.

About the Author

Christopher Scordo, PMP, ITIL, is Founder and Managing Director of PMTraining, a PMI Premier Authorized Training Partner that has trained more than 175,000 professionals over 19 years. More about the team.

Sources:

Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Eighth Edition

Project Management Institute, The Standard for Portfolio Management, Fourth Edition

PMTraining, Resource Leveling in Project Management (With a Real Example) (YouTube)