A project schedule can show every task finishing on time while assigning the same specialist to two full days of work on one date. The diagram is tidy; the capacity assumption is impossible. Resource levelling exposes that conflict.
In Microsoft Project’s levelling documentation, overallocations can be addressed by delaying or splitting tasks according to the chosen settings. Moving work can also move the project’s finish date. Restricting changes to available slack may leave some conflicts unresolved.
See the conflict before choosing a remedy
Take a fictional example. One designer is available for eight hours on Monday. Two independent tasks each require eight hours of that person’s work and both are scheduled for Monday. Drawing them in parallel does not create sixteen hours of capacity.
One task could move to Tuesday, an appropriately qualified second person could take it, or the scope and estimates could be revisited. Each option changes something meaningful. Simply suppressing an overallocation warning changes none of them.
Read the assumptions behind the new date
Before presenting a levelled schedule, check working calendars, assignment effort, dependencies and priorities. A mistaken holiday entry or an unrealistic allocation can move dates for the wrong reason. Software can apply rules consistently while using poor inputs.
Keep a copy of the original planning assumptions and explain why the revised schedule differs. The message to stakeholders should identify the constrained work and the decision required, rather than saying only that “the tool delayed us.”
- Which resource is limiting the sequence?
- Can the work genuinely be split?
- What additional capacity would be effective, and when?
- Which deadline or scope choice needs an explicit trade-off?
Use the result as a conversation
A later calculated finish is not automatically evidence of poor performance. It may reveal a conflict that existed before anyone started. Equally, a date unchanged by levelling is not proof that every staffing assumption is sound.
Review the changed assignments with the people doing the work. A credible plan connects dates to available capacity and makes exceptions visible. That gives a manager something concrete to negotiate before the workload turns into missed commitments.