Fulfilling a Single Generic Resource Requirement with Multiple Named Resources Purpose

Share

When a generic Resource Requirement is fulfilled by multiple named resources, Project Operations intentionally leaves the generic resource assigned to the project tasks.

In contrast to the single-resource fulfilment scenario described in Section #4, task assignments are not automatically redistributed when multiple named resources are booked against the same generic Resource Requirement.

Project Operations cannot reliably determine:

  • How the work should be divided.
  • Which tasks should be assigned to which resource.
  • Whether effort should be split equally or according to availability.
  • How assignment dates should align with booking dates.
  • Whether skills, role specialization, task ownership, or client continuity should influence the allocation.

The Project Manager must therefore translate the staffing decision into named-resource task assignments.

Important distinction: Fulfilling a Resource Requirement is not the same as completing resource assignment planning. A Resource Requirement may be fully booked while the assignments required for project delivery remain unresolved.

 

Example Scenario

Assume a project contains the following generic resource:

Resource

Role

Generic Project Consultant

Consultant

The generic resource is assigned to the following project tasks:

Task

Effort

Design Workshops

40 hours

Solution Design

40 hours

Configuration

40 hours

Total

120 hours

The generic Resource Requirement is subsequently fulfilled by two named resources:

Named Resource

Booked Capacity

Resource A

60 hours

Resource B

60 hours

Total

120 hours

After the bookings are created:

✅ Both named resources are booked to the project.

✅ Both named resources are added to the project team.

✅ The generic resource remains assigned to the project tasks.

❌ Task assignments are not automatically distributed among the named resources.

This is the expected system behaviour.

 

Recommended Fulfilment and Assignment Process

Step 1: Create the Named-Resource Bookings

Fulfil the Resource Requirement using the appropriate staffing process:

  • Resource Request process
  • Schedule Board
  • Direct booking (when supported by the configured Resource Allocation Mode)

Continue until the intended named resources and booked capacity have been secured.

Verify that:

  • The intended named resources appear on the project team.
  • The required booking records have been created.
  • The booking dates cover the periods during which the work is expected to occur.
  • The Resource Requirement's Remaining Duration reflects the current fulfilment position.

A Remaining Duration of zero indicates that the demand represented by the Resource Requirement appears to have been fulfilled through bookings. It does not confirm that task assignments have been distributed or aligned.

 

Step 2: Retain the Generic Resource Temporarily

Do not remove the generic resource or its assignments immediately after creating the named-resource bookings.

The generic resource still represents the planned work that must be distributed. Removing it before creating the named-resource assignments can make it more difficult to confirm:

  • Which tasks require reassignment
  • How much effort remains to be allocated
  • Whether the complete scope of planned work has been transferred
  • Whether the named-resource assignments collectively replace the generic-resource assignments

Safeguard: Do not remove the generic resource or reduce its assignments until the named-resource assignments have been reviewed, created, and validated.

 

Step 3: Review the Existing Generic-Resource Assignments

Review every task currently assigned to the generic resource.

Task

Current Resource

Assigned Effort

Design Workshops

Generic Project Consultant

40 hours

Solution Design

Generic Project Consultant

40 hours

Configuration

Generic Project Consultant

40 hours

Determine:

  • Which named resource should perform the work.
  • Whether multiple resources should contribute.
  • How effort should be divided.
  • When the work should occur.
  • Whether named resources have compatible bookings and availability.
  • Whether role, skills, ownership, or continuity considerations influence the allocation.

 

Step 4: Select an Allocation Strategy

The Project Manager should select an allocation approach that reflects both the project delivery plan and available booked capacity.

Option A: Task-Based Allocation

Assign complete tasks to individual named resources.

Task

Named Resource

Effort

Design Workshops

Resource A

40 hours

Solution Design

Resource A

40 hours

Configuration

Resource B

40 hours

This approach works well when task ownership can be assigned clearly.

 

Option B: Shared Task Allocation

Assign multiple resources to the same task and split the effort.

Task

Named Resource

Effort

Design Workshops

Resource A

20 hours

Design Workshops

Resource B

20 hours

This approach is useful when collaboration or parallel work is required.

 

Option C: Capacity-Informed Allocation

Use booked capacity as one input when allocating work.

Named Resource

Booked Capacity

Illustrative Assigned Effort

Resource A

80 hours

80 hours

Resource B

40 hours

40 hours

Assignments should be consistent with both booked capacity and planned project delivery.

Work should not be divided solely according to bookings when:

  • Skills differ.
  • Task ownership matters.
  • Delivery sequencing is important.
  • Role specialization is required.
  • Client continuity must be preserved.

 

Step 5: Create the Named-Resource Assignments

Update the project schedule to assign work to the named resources.

For each task:

  1. Add the named resource.
  2. Assign the appropriate effort.
  3. Review assignment start and finish dates.
  4. Confirm that assignment dates are compatible with booking dates.
  5. Repeat until the planned work has been distributed.

Example:

Task

Named Resource

Assigned Effort

Design Workshops

Resource A

40 hours

Solution Design

Resource A

20 hours

Solution Design

Resource B

20 hours

Configuration

Resource B

40 hours

At this stage, confirm that the total named-resource assignments represent the work previously assigned to the generic resource, unless the project plan has intentionally changed.

 

Step 6: Reduce or Remove the Generic-Resource Assignments

Only after the named-resource assignments have been created should the Project Manager reduce or remove the generic-resource assignments.

Use the following sequence:

  1. Confirm that every intended task has a named-resource assignment.
  2. Confirm that the required effort has been transferred.
  3. Confirm that assignment timing reflects the delivery plan.
  4. Reduce or remove the corresponding generic-resource assignments.
  5. Review the schedule for missing or duplicated effort.
  6. Confirm that no unintended generic-resource assignments remain.

This sequence helps prevent planned effort from being omitted during redistribution.

 

Step 7: Validate Through the Resource Reconciliation Tab

Open the Resource Reconciliation tab and compare bookings with assignments for each named resource.

Verify that:

  • Named-resource assignments reasonably align with booked capacity and planned project delivery.
  • Assignment dates align with booking dates.
  • Booking Shortages have been identified and addressed.
  • Excess Bookings are understood and are either intentional or have been reduced appropriately.
  • Generic-resource assignments have been reduced or removed as intended.
  • The project's total planned effort still reflects the approved delivery plan.

Matching total hours is not sufficient if bookings and assignments occur in different periods.

Example Timing Mismatch

Resource

Assignment Period

Booking Period

Result

Resource A

Week 2

Week 4

Timing mismatch

In this scenario, assignment and booking totals may match across the project, but the required capacity has not been reserved for the period in which the work is planned.

Review the daily timescale whenever higher-level totals may conceal timing differences.

 

When Should the Generic Resource Be Removed?

The generic resource can remain on the project team temporarily for planning purposes even after named resources have been booked.

Consider removing it only when:

  • All intended named resources have been booked.
  • The required task assignments have been created.
  • Generic-resource assignments have been reduced or removed appropriately.
  • The project schedule has been reviewed for missing or duplicated effort.
  • The Resource Reconciliation tab has been reviewed.
  • No future planning activity depends on the generic resource.

Some organizations deliberately retain generic resources until staffing and assignment planning have stabilized.

The appropriate timing should be defined by project and resource management governance practices.

 

Common Mistakes to Avoid

Removing the Generic Resource Too Early

Removing the generic resource before redistributing its assignments can make it difficult to confirm the original scope and effort that must be transferred.

Recommended approach: Create and validate named-resource assignments before reducing or removing generic-resource assignments.

 

Assuming Bookings Automatically Create Assignments

Booking multiple named resources does not automatically distribute assignments among them.

Recommended approach: Treat booking creation and assignment distribution as related but separate activities.

 

Allocating Work Without Considering Booking Dates

A resource may have enough total booked hours, but not during the period in which the work is scheduled.

Recommended approach: Validate both booking volume and booking timing through the Resource Reconciliation tab.

 

Allocating Work Solely According to Booking Percentages

Booked capacity is important, but it should not override:

  • Skills
  • Task ownership
  • Delivery sequencing
  • Role specialization
  • Client continuity

Recommended approach: Balance booked capacity with the project's delivery requirements.

 

Closing the Staffing Process Too Early

A Resource Requirement may appear fully fulfilled even though assignment planning remains incomplete.

Before considering staffing operationally complete, confirm that:

  • Required bookings exist.
  • Named-resource assignments have been created.
  • Generic-resource assignments have been addressed.
  • Assignment and booking dates have been reviewed.
  • Resource Reconciliation has been completed.
  • Any remaining variances are understood and documented.
  • For organizations using Resource Requests, Resource Requests have been reviewed and updated according to the governance approach described in Section #2 and Appendix A.

 

Practical Completion Checklist

  • The intended named resources have been booked.
  • The Resource Requirement's Remaining Duration reflects the current fulfilment position.
  • Booking dates support the planned work periods.
  • Generic-resource task assignments have been reviewed.
  • An allocation strategy has been agreed.
  • Named-resource assignments have been created.
  • Assigned effort has been validated against the project plan.
  • Assignment dates have been checked against booking dates.
  • Generic-resource assignments have been reduced or removed only after named-resource assignments were created.
  • The project schedule contains no unintended missing or duplicated effort.
  • Booking Shortages and Excess Bookings have been reviewed.
  • Remaining variances are understood and documented.
  • Resource Reconciliation has been reviewed at the appropriate timescale.
  • Resource Requests have been reviewed and updated according to the organization's fulfilment governance process.

 Recommended Governance Policy

When a generic Resource Requirement is fulfilled by multiple named resources, staffing can be considered operationally complete only after the required bookings have been created, task assignments have been distributed to the named resources, generic-resource assignments have been addressed, and the result has been validated through the Resource Reconciliation tab.

The staffing process aligns three related but distinct elements:

  1. Resource Requirements, which represent demand.
  2. Bookings, which reserve resource capacity.
  3. Task Assignments, which define the work resources are expected to perform.

Aligning all three ensures that the project schedule accurately reflects both the staffing decision and the intended delivery plan.