Resource Leveling in MS Project: Fix Over-Allocation

A project manager opens a schedule on Monday morning and there they are. Little red people icons stacked down the left side of the Gantt chart, one after another, each shouting that someone is booked for more hours than a day actually contains. First instinct is to reach for the button labelled Level All and let Project sort it out. That instinct is where a lot of good schedules quietly die.

Here’s the thing nobody mentions in the rush. Levelling doesn’t magically add hours to anyone’s day. It moves work later in time so the same person isn’t doing two things at once, which means the finish date can slide, sometimes by a lot, and it can do this silently across dozens of tasks in a single click.

So before touching anything, it’s worth understanding what the feature does to the dates. Because the difference between a helpful cleanup and a wrecked plan is whether someone knew what was about to happen.

Why the Usual Advice Fails You

Most guides do the same thing. Point at the red person icon, say click Level All, end the article. What they skip is the part that matters, which is that levelling rewrites the schedule based on rules nobody set.

By default, Project is allowed to delay tasks as far as it needs to remove the conflict. On a plan with tight dependencies, that can shove a delivery date weeks out, and the change happens across so many tasks at once that spotting what moved becomes genuinely hard afterwards.

And there’s a second gap. Almost nobody explains how to reverse it. People run levelling, watch their timeline stretch, panic, and abandon the feature entirely because they assume the damage is permanent. It isn’t. But not knowing that is exactly what keeps teams manually dragging tasks around for hours when a constrained, reversible pass would have done it in seconds.

Point is, the button works fine. Running it blind is the problem.

What Resource Leveling in MS Project Actually Does Before You Run It

Levelling looks at every resource flagged as over allocated and asks one simple question: can this work be spread out so nobody is double-booked? To answer it, Project either delays a task, splits it into pieces, or reorders which task a person tackles first.

Total work never drops. A 40-hour task stays 40 hours. What changes is when those hours land on the calendar.

“Levelling doesn’t give anyone more hours in the day. It just stops them from spending the same hour twice, and the cost of that is time.”

Microsoft’s own documentation is blunt about this tradeoff, noting that levelling can delay the completion of individual tasks and even the project itself. Their guidance on how to distribute project work evenly across a team is worth reading before a first run, because it frames the feature as a redistribution tool rather than a fix.

So the safe mental model is this. You’re trading schedule length for a realistic workload. Sometimes that trade is fine. Sometimes it destroys a deadline promised to a client. The only way to know is to control how far Project is allowed to push.

The Safe First Move: Level Within Slack Only

Before running anything, save a baseline. Go to Project, then Set Baseline. This snapshots current dates so before and after can be compared, and honestly it’s the single most useful habit for anyone nervous about the outcome.

Now the actual safe pass. There’s a setting most people never touch that changes everything: levelling only within available slack. Slack is the wiggle room a task has before it starts affecting the finish date. Restrict levelling to slack only and Project is told it may reshuffle work, but it is not allowed to push the project end date. Tasks with float get moved. Tasks on the critical path stay put.

That is the safest way to level resources in Microsoft Project without giving the tool permission to move the deadline.

To set this up:

1. Go to the Resource tab and click Levelling Options.
2. Set levelling to Manual so it only runs when you say so, never automatically as you type.
3. Under “Resolving over-allocations”, tick the box for Level only within available slack.
4. Choose whether Project can split remaining work and adjust individual assignments, depending on how granular you want it.
5. Click Level All, or select specific tasks and use Level Selection.

The trade here is honest. Because Project can’t extend the finish date, it may not resolve every conflict. Some red icons might survive the pass. That’s not a failure, it’s the tool telling you those conflicts genuinely can’t be fixed without either more time or more people. Which is exactly the information you needed.

The Resource Levelling dialog box reference from Microsoft walks through each option in that panel for anyone who wants the full breakdown of what every checkbox controls.

Finding the Over-Allocation Before You Fix It

Fixing over allocated resources blindly is guesswork. You want to see the problem first, and the resource usage view is built for exactly that.

Switch to it under the View tab, choose Resource Usage. Every resource shows up listed with their assigned hours broken down day by day. Over-allocated cells appear in red, and now the shape of the problem is visible, whether someone is 20% over on a single day or slammed at 300% for a whole week.

Project managers searching for how to fix the red person icon in Project usually end up here, in Resource Usage, because it shows the overload instead of just the warning.

This matters because the fix depends on the pattern. A one-day spike often clears itself with a within-slack pass. A sustained overload across weeks means you’re short-staffed, and no amount of levelling will invent the missing hours. Reddit’s MS Project community threads on preventing resource over-allocation circle this same point repeatedly: the tool surfaces the truth, it doesn’t create capacity.

How to Undo Levelling When It Goes Wrong

This is the part almost no guide covers, and it’s the reason people are scared of the feature. Levelling is completely reversible.

If a pass pushes the dates somewhere unwelcome, go to the Resource tab and click Clear Levelling. Clear it for the entire project or just for selected tasks. Project removes the levelling delays it added and returns tasks toward their pre-level positions. Pair that with the baseline saved earlier and you can compare exactly what shifted, then decide whether to keep it, tweak it, or start over.

Because this safety net exists, experimenting becomes low-risk. Run a within-slack pass, look at the result, clear it if you hate it, adjust the options, run again. Nobody loses a plan doing that.

When Levelling Isn’t the Answer

Sometimes the honest fix isn’t rescheduling at all. If the resource usage view shows someone buried at 250% for a month straight, levelling will just smear that overload across a longer stretch of calendar, blowing the deadline to do it.

At that point the real options are adding a person, reducing scope, or accepting a later date. Guidance from practitioners on resource levelling best practices tends to land here too: the feature is a scheduling helper, not a staffing solution. Knowing which problem you actually have saves a lot of wasted clicking.

FAQ

Does levelling change the amount of work on a task?
No. It only changes when the work happens. Total effort stays identical, Project just moves those hours to a point where the assigned person isn’t double-booked.

Will resource leveling in ms project always push my finish date?
Only if you let it. Level within available slack and the finish date is protected, because Project can only reshuffle tasks that have float. The tradeoff is that some conflicts may remain unresolved.

How do I get rid of the red person icon in Project?
Fix the underlying over-allocation. Open the resource usage view to see where the overload sits, then level within slack or manually move a task. The icon clears once no resource exceeds capacity on any day.

Can I undo levelling if it makes things worse?
Yes. Resource tab, Clear Levelling, either for the whole project or selected tasks. It removes the delays levelling added. Pair it with a saved baseline and you can see precisely what changed.

Should I set levelling to automatic or manual?
Manual, almost always. Automatic levelling recalculates as you edit, which makes a live plan feel like it’s fighting you. Manual lets you level deliberately, review the result, and clear it if needed.

Wrapping Up

Resource leveling in MS Project is safe once you understand it moves work in time rather than adding capacity. Save a baseline, level within slack as the first pass to protect the finish date, use the resource usage view to see the real shape of the overload, and keep Clear Levelling as the undo button. Do that and the red icons stop being a threat and start being useful information about where the plan actually needs help.

Getting the tool right matters more when the software underneath is genuine and licensed properly, so it behaves predictably.