Automated resource leveling in Microsoft Project can be used to reduce overallocations. The default behavior of the leveling engine is to adjust start and/or finish dates, in order to balance the demand for a resource. The default behavior can be adjusted through the Leveling Options Dialog Box, but we can also fine tune which tasks and which resources get leveled with simple changes.
In the following illustration, Task 1 is 20% complete and Task 2 is 25% complete. Both Steve and Wendy are overallocated:
If we click the Level All button on the Resource tab, Project will level the tasks as shown in the following illustration:
What if Task 1 was more important to get done first, and we didn’t want it leveled? Simply change the Priority field to 1000 and it will not level Task 1. Once we do that and click Level All, Project will split Task 2 as shown in the following illustration:
Alternatively, suppose we want to allow all tasks to be leveled, but we don’t want Wendy leveled? We could certainly select specific resources to level, but this may not be practical if there are a large number of resources on our project. In this situation, on the Resource Sheet view, insert the Can Level field. By default, this field is set to Yes; once we change it to No for Wendy and click Level All, Project will split Steve’s assignment but leave Wendy as being overallocated. The following illustration shows the Gantt Chart view:
The following illustration shows the Task Usage view:
Applies To: All Current Versions of Microsoft Project