Using Individuals Name in Resource Pool

The Planner's Dilemma

Should we add specific names and surnames into the resource pool, or stick to generic roles? Understanding the criteria for this decision is vital for long-term schedule stability.

The "Name" Trap in Engineering

During the Engineering phase, a list of specific individuals is often readily available. Planners are frequently tempted to add them one by one. Project Managers often prefer this approach, alleging it makes it easier to manage performance through schedule activities.

While it feels precise, adding individuals instead of roles can make resource leveling nearly impossible as the project scales.

The Middle Ground: Numbered Roles

Some planners find a middle ground by adding resources with numbering, for example, Civil Engineer 1, Civil Engineer 2, or Crew 1. This approach indicates the number of available resources without tying the schedule to a specific person who might leave or be reassigned.

Why Accuracy Matters

On certain instances, resources could be added with the individual person’s name whilst on others that should not be the case.! If the planner develops the resource pool incorrectly and adds the name instead of the role or vice versa, then it could create many problems for resource loading, resource management, resource Leveling, etc.