Skip to content
Project Management Basics

Resource Leveling: How to Fix an Overloaded Schedule, With an Example (2026)

What resource leveling is, how it differs from resource smoothing, an example for a four-person engineering team, and a weekly process for even workloads.

By Ryan Kramer, founder of Wisegrid. Last updated November 2026.

Resource leveling is a way of rescheduling work so nobody is booked for more hours than they have. When one person is overloaded in a given week, some of their tasks are moved to a later week or split across weeks. Leveling keeps the plan realistic, but it can push the project’s finish date out if the moved work has no room to slip.

Overloaded people are the most common reason a plan that looked fine on paper misses its dates. One senior engineer booked at 52 hours a week does not work 52 hours; something quietly slips. This guide explains resource leveling in plain words, how it differs from resource smoothing, a worked example for a four-person team, and a simple weekly process.

Key takeaways

– Leveling moves or splits tasks so each person’s weekly hours stay within what they have.

– Smoothing does the same, but only within slack. It never moves the finish date, so some overload may remain.

– Level by person and by week. A team total under capacity can still hide one overloaded person.

– Use available hours, not 40. Meetings, admin and time off come out first.

– If leveling pushes the end date, decide on purpose: accept the slip, add help, or cut scope.

What is resource leveling?

Resource leveling adjusts a schedule to match the people you actually have. It starts from a plan where tasks are scheduled as early as possible, finds the weeks where someone is booked over their available hours, and moves the extra work to weeks where they have room. Microsoft’s guide to Project describes it the same way: leveling works by delaying tasks or splitting them, and it can delay the project’s finish date.

The word “resource” usually means people, but it can be any limited thing: a survey crew, a crane, a testing lab. The method is the same.

Resource leveling vs resource smoothing

These two are often confused. The difference is what you protect: the people’s limits or the finish date.

Compared Resource leveling Resource smoothing
Fixed limit People’s available hours The finish date
Tasks can move Anywhere, even past the end Only within their slack
Finish date May move later Does not move
Overload left None Some may remain

Slack, also called float, is how long a task can slip without delaying the finish. Use smoothing when the date is fixed by a contract. Use leveling when the people limit is real and the date can move, or when you need to show a client why it must.

Resource leveling example

A four-person civil engineering team over four weeks. Each person has 36 available hours a week after meetings and admin. The first table is the plan as scheduled, with every task starting as early as possible. Bold cells are over 36 hours.

Person Week 1 Week 2 Week 3 Week 4
Priya, structural 52 44 20 16
Marco, civil 30 34 38 22
Dana, civil 18 22 30 36
Sam, drafting 40 46 24 12
Total 140 146 112 86

The team total looks fine. Capacity is 144 hours a week (4 × 36), and only week 2 is over it. But Priya is booked 16 hours over in week 1, and Sam is over in both early weeks. The total hides that. Total work is 484 hours against 576 available, so the work fits in four weeks if it can move.

After leveling, tasks with slack are moved later, and Dana starts two independent tasks earlier. Each person’s total hours stay the same; only the weeks change.

Person Week 1 Week 2 Week 3 Week 4
Priya, structural 36 36 30 30
Marco, civil 32 34 36 22
Dana, civil 30 30 26 20
Sam, drafting 36 36 32 18
Total 134 136 124 90

What this tells you: nobody is above 36 hours, and the total is still 484. The project still finishes in week 4 because Priya’s and Sam’s moved tasks had slack. If they had not, the honest answer would be a later finish, help from another team, or a smaller scope, and the client should hear that now. Our capacity planning guide covers how to work out available hours.

Watch: Capacity Planning in 2 Minutes (2 minutes)

Watch “Capacity Planning in 2 Minutes” on YouTube →

How to level resources, step by step

  1. Work out available hours per person per week. Start from a full week, then take out meetings, admin and time off. Count part-timers with full-time equivalents (FTE).
  2. Put every task on a timeline with its hours, its person and the tasks it depends on. An Excel Gantt chart is enough to start.
  3. Add up hours by person and week. Flag every cell over the available hours.
  4. Move tasks that have slack into weeks where that person has room. Start with the lowest-priority work.
  5. Split long tasks if part of the work can be done later.
  6. Reassign only when skills match. Moving work to someone else is reallocation, not leveling, but it is often the faster fix.
  7. Check the finish date. If it moved, decide what to do and tell the people who need to know.

Common resource leveling mistakes

  • Using 40 hours as capacity. Nobody has 40 project hours a week. Planning at 40 builds overload into the plan.
  • Leveling the team total only. One overloaded specialist can stall three other people.
  • Ignoring dependencies. Moving a task without moving what depends on it creates a plan that cannot happen.
  • Leveling once. Plans change weekly. Last month’s leveled plan is out of date.
  • Hiding the slip. If leveling pushes the date, it goes in the risk register and the client update, not in a drawer.

Resource leveling for engineering and architecture firms

Design firms run many small projects at once, and the same few senior people are needed on all of them. That makes leveling a firm-wide job, not a project job. Look at each person across every project, then level. A firm-wide view also shows when the real fix is hiring, which the utilization rate guide and the free utilization rate calculator help you judge.

Leveling also protects the fee. Overloaded senior staff either work unpaid overtime or push work to whoever is free, often at the wrong rate. Both show up later in budget vs actual.

From spreadsheet to a shared workload view

A workload grid in Excel works for one team. It gets hard when every project manager keeps their own copy, people appear on several projects, and nobody can see the total for one person across all of them.

In Wisegrid, each project’s tasks live in its own sheet, and a cross-sheet report adds up hours by person and week across every project. Overloaded cells show up the moment a project manager books more work. The resource planning template and the capacity planning template have this layout ready, and hours logged in the timesheet template show whether the plan held.

FAQ

Does resource leveling change the critical path?

It can. Leveling moves tasks to fit people’s hours, and if a moved task had no slack, the finish date moves and the critical path changes. Resource smoothing avoids that by moving tasks only within their slack, so the finish date stays fixed.

When should you use resource leveling?

Whenever someone is booked above their available hours, and especially before you promise a date. Use it during planning, then again each week as new work arrives. If the finish date is fixed by contract, start with smoothing and add help where overload remains.

What is the difference between resource leveling and resource allocation?

Resource allocation is deciding who does which task. Resource leveling is moving tasks in time so each person’s hours fit. In practice you do both: allocate first, level second, and reassign when leveling alone pushes the date too far.

Can you do resource leveling in Excel?

Yes. Put people in rows, weeks in columns and planned hours in the cells, then highlight anything above available hours. Move tasks by hand. It works well for one team and gets harder across many projects.

Sources


See every person’s week across every project

Plan people with the resource planning template, check capacity with the capacity planning template, and log real hours in the timesheet template.

Start free → · Capacity planning guide → · Resource planning template →


About the author Ryan Kramer is the founder of Wisegrid, a higher-capacity work management grid built around a 1,000,000-cell-per-sheet limit, date-triggered automations with run history, and cross-sheet reporting. He writes about the project management documents teams actually keep updated. More from Ryan →