Control Resource Leveling Priority in Microsoft Project 2010
Question details
The user wants to understand and control the order in which Microsoft Project 2010 levels tasks competing for the same resource.

- Product
- Microsoft Project 2010
- Device & OS
- not provided
- Scenario
- Multiple tasks share an overallocated resource and have identical default priority values.
- Observed behavior
- Project may choose an unexpected leveling order because several valid schedules are possible and factors such as slack, task relationships, and constraints influence the result.
Identify the tasks competing for the resource and review their dependencies, constraints, and slack. Check the current leveling order in Resource > Leveling Options before changing task priorities.
Set Task Priorities and Use Priority-Based Leveling
Use this method to tell Project which tasks should generally be protected from leveling delays.
Project can select among several valid schedules when tasks compete for a resource. Higher priority values generally make tasks less likely to be delayed; the default priority is 500.
In the Gantt Chart view, double-click a task that competes for the overallocated resource to open Task Information.
On the General tab, set Priority to a meaningful value from 0 to 1000. For example, leave a normal task at 500 and give a more important task 600, then click OK.
Go to Resource > Leveling Options and select Priority, Standard under Leveling order. Click OK.
On the Resource tab, select Level All, then review the affected task dates and resource allocations in the Gantt Chart.

Compare the ID-Only Leveling Order
Use ID-only leveling when you want Project to follow task ID order rather than prioritize tasks by planning importance.
Track Project Tasks in WPS Spreadsheets
WPS Office is a free, lightweight alternative for maintaining task lists and sharing project reports. Its familiar interface and Microsoft Office format compatibility make it easy to move existing documents and spreadsheets. It does not replace Microsoft Project's resource-leveling engine.

Frequently Asked Questions
Why does Project level tasks with the same priority in a different order than I expected?
Identical priorities do not guarantee a particular order. Depending on the leveling settings, Project can consider factors such as task relationships, slack, dates, and constraints when selecting a valid schedule.
What is the default task priority in Project 2010?
The default is 500. Double-click a task in the Gantt Chart and check Priority on the General tab of Task Information.
How do I stop Project from leveling a particular task?
Open the task's Task Information dialog, select the General tab, and set Priority to 1000. Project will not level that task.
Should I use ID Only or Priority, Standard for leveling?
Choose Priority, Standard in Resource > Leveling Options when task importance should guide the result. Choose ID Only when you want leveling to follow task ID order instead.




