> ## Content Index
> Fetch the complete content index at: https://www.d365architect.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Understanding the resource fulfilment process #3
- URL: https://www.d365architect.com/understanding-the-resource-fulfilment-process-3/
- Published: 2026-10-23T07:00:00.000Z
- Updated: 2026-10-23T07:00:00.000Z
- Author: Jerome Asselin

**Resource Requests, Fulfilment Preferences, and Multi-Resource Fulfilment**

In the first and second article, we explored the fundamentals of resource fulfilment, including Resource Requirements, the Schedule Board configuration, and booking statuses, got deeper in Fulfilment Preferences, Resource Requests and direct booking scenarios.

Let's now dive in the behaviour of Dynamics 365 Project Operations when fulfilling demand with one or multiple named resources, understanding how these elements interact is essential for building a predictable, scalable, and well-governed resource management process.

**#4 Understand Single-Resource and Multiple-Resource Fulfilment**

**Project Operations behaves differently depending on whether a generic Resource Requirement is fulfilled by one or multiple named resources.**

This distinction is often misunderstood and can have significant implications for task assignments, capacity planning, and project governance.

**Scenario A: One Named Resource**

The simplest fulfilment scenario occurs when a generic Resource Requirement is fulfilled by a single named resource.

**Example**

A project contains:

| Resource           | Role                  |
| ------------------ | --------------------- |
| Generic Consultant | Functional Consultant |

The generic resource is assigned to several tasks.

The Resource Requirement is fulfilled by:

| Resource   |
| ---------- |
| John Smith |

**Result**

When fulfilment occurs through the standard Project Operations process:

- The named resource is added to the project team.
- The generic resource is replaced by the named resource.
- Existing task assignments are transferred.
- Project planning can continue immediately using the named resource.

This is the most straightforward fulfilment scenario and requires minimal effort from the Project Manager.

**Why It Works**

Because only one resource is involved, Project Operations can safely assume:

The resource fulfilling the requirement is the same resource that should perform the work.

No assignment ambiguity exists.

**Scenario B: Multiple Named Resources**

The behaviour changes significantly when multiple named resources fulfil the same generic Resource Requirement.

**Example**

A generic Resource Requirement contains:

| Requirement        | Demand    |
| ------------------ | --------- |
| Generic Consultant | 120 hours |

The requirement is fulfilled by:

| Resource   | Booked Capacity |
| ---------- | --------------- |
| Resource A | 60 hours        |
| Resource B | 60 hours        |

**What Project Operations Does**

After fulfilment:

✅ Resource A is added to the project team.

✅ Resource B is added to the project team.

✅ Booking records are created.

✅ Resource demand may be considered fulfilled.

❌ The generic resource remains assigned to project tasks.

❌ Task assignments are not redistributed automatically.

This behaviour is intentional.

**Why Doesn't Project Operations Redistribute the Work?**

Project Operations cannot reliably infer the Project Manager's intent.

The system does not know:

- Which tasks should belong to which resource.
- Whether work should be distributed evenly.
- Whether one resource owns specific deliverables.
- Whether resources specialize in different parts of the project.
- Whether assignment timing should differ from booking timing.

For example:

| Task          | Effort |
| ------------- | ------ |
| Workshops     | 40h    |
| Design        | 40h    |
| Configuration | 40h    |

A Project Manager may decide to split the work as illustrated below:

| Resource   | Responsibility       |
| ---------- | -------------------- |
| Resource A | Workshops and Design |
| Resource B | Configuration        |

Another Project Manager may split all work evenly.

Because the application cannot infer these decisions, it intentionally leaves assignment ownership under Project Manager control.

**Key Principle:** When multiple resources fulfil a single generic Resource Requirement, Project Operations books the resources but does not automatically determine how the work should be allocated among them.

**Staffing vs Assignment Planning**

One of the most important concepts in Project Operations is understanding that:

**Fulfilment**

 Answers "Who has been booked?"

**Assignment Planning**

 Answers "Who will perform the work?"

Those questions often have the same answer in Scenario A, they are frequently different in Scenario B.

A Resource Requirement can therefore be fully fulfilled while assignment planning remains incomplete.

**Governance Implications**

Project Managers should not consider work complete simply because:

- Remaining Duration equals zero.
- Bookings exist.
- Named resources appear on the project team.

Before staffing is operationally complete, the organization should verify:

- Assignments exist.
- Assignment timing is correct.
- Booking timing is correct.
- Capacity supports the planned work.
- Resource Reconciliation has been reviewed.

The next section explains how to perform that validation.

**#5 Use the Resource Reconciliation Tab**

**Resource Reconciliation is one of the most valuable and underused capabilities in Project Operations.**

Project Operations intentionally treats Bookings and Task assignments as related but independent concepts.

A resource can have:

- Assignments without bookings.
- Bookings without assignments.

This flexibility supports real-world project planning but can create inconsistencies if not actively managed.

**Why Resource Reconciliation Matters**

Over time, bookings and assignments naturally drift apart.

Typical causes include:

- Project schedule changes.
- Delayed tasks.
- Additional assignments.
- Extended bookings.
- Resource availability changes.
- Multiple-resource fulfilment scenarios.

Without regular reconciliation:

- Capacity forecasts become unreliable.
- Utilization reports become misleading.
- Staffing decisions become more difficult.
- Resource managers lose visibility into true demand.

**What the Resource Reconciliation Tab Displays**

The Resource Reconciliation tab provides a time-phased view of:

- Project bookings
- Task assignments
- Variances between the two

The information can be viewed by Month, Week or Day

The tab displays information for every named resource on the project team.

**Information Displayed**

| Information        | Description                               |
| ------------------ | ----------------------------------------- |
| Bookings           | Reserved project capacity                 |
| Assignments        | Planned task work                         |
| Difference         | Variance between bookings and assignments |
| Totals             | Rolled-up values for the time period      |
| Task-Level Details | Individual assignment data                |

The objective is not necessarily to achieve perfect alignment every day.

However, significant variances should be understood and managed.

**Understanding the Difference Calculation**

For each named resource Bookings – Assignments = Difference

In a fully aligned plan, the difference is 0

However, temporary differences may be expected.

Examples include:

- Future planned work
- Recently created assignments
- Pending booking updates
- Transitional staffing activities

The goal is to understand the reason behind the variance.

**Using the Resource Reconciliation Tab in Practice**

**Think of the Resource Reconciliation tab as the project's resource balancing dashboard.**

The purpose of Resource Reconciliation is not merely to identify discrepancies. It is to ensure that:

- Project assignments reflect the staffing strategy.
- Booked capacity supports planned work.
- Resource utilization remains realistic.
- Capacity forecasts remain accurate.
- Staffing decisions are translated into executable project plans.

Review Resource Reconciliation at least:

- During initial staffing
- Before project reviews
- After major schedule changes
- After fulfilling Resource Requirements
- Before resource governance meetings
- Before releasing resources from a project

The following process can be used consistently across projects.

**Step 1: Review Overall Project Variances**

Open the **Resource Reconciliation tab** and review the overall project totals.

Focus on:

- Resources with significant shortages
- Resources with significant excess bookings
- Resources showing unusual fluctuations
- Newly staffed resources
- Recently reassigned resources

At this stage, the objective is to identify where further investigation is required.

**Step 2: Drill Into Individual Resources**

Expand the resource and review:

- Bookings
- Assignments
- Variance values
- Assignment timing
- Booking timing

Review the data at:

- Month level
- Week level
- Day level

Do not conclude that resources are aligned simply because monthly totals appear balanced.

A resource may show:

 40 hours booked and 40 hours assigned while still having significant timing mismatches.

**Step 3: Investigate Booking Shortages**

Booking shortages occur when Assignments > Bookings

**Example**

| Resource   | Assignments | Bookings |
| ---------- | ----------- | -------- |
| Resource A | 40h         | 24h      |

**Questions to Ask**

- Is the assignment still required?
- Is the assignment timing correct?
- Is the resource available?
- Were bookings reduced accidentally?
- Has demand increased since staffing occurred?

**Possible Responses**

- Extend bookings
- Move assignments
- Reassign work
- Revise the schedule
- Request additional resources

The goal is to ensure that planned work is supported by reserved capacity.

**Step 4: Investigate Excess Bookings**

Excess bookings occur when Bookings > Assignments

**Example**

| Resource   | Bookings | Assignments |
| ---------- | -------- | ----------- |
| Resource B | 40h      | 8h          |

**Questions to Ask**

- Is more work expected?
- Is capacity intentionally reserved?
- Is planning incomplete?
- Has project scope been reduced?

**Possible Responses**

- Create assignments
- Reduce bookings
- Release capacity
- Retain bookings intentionally

The objective is to ensure that reserved capacity has a valid business purpose.

**Step 5: Validate Timing Alignment**

One of the most overlooked reconciliation activities is validating dates rather than hours.

**Incorrect Alignment Example**

| Resource   | Assignment Period | Booking Period |
| ---------- | ----------------- | -------------- |
| Resource A | Week 2            | Week 4         |

In this situation:

✅ Total hours may match.

❌ The resource is unavailable when the work is scheduled.

This type of issue often remains hidden at the month level.

**Recommended Practice**

When investigating material discrepancies:

1. Move to the daily timescale.
2. Review booking dates.
3. Review assignment dates.
4. Confirm that assignments occur during booked periods.

Timing alignment is often more important than volume alignment.

**Step 6: Validate Multiple-Resource Fulfilment**

This review becomes critical after the scenario described in Section #4.

**Example**

Bookings:

| Resource   | Booking |
| ---------- | ------- |
| Resource A | 60h     |
| Resource B | 60h     |

Assignments:

| Resource           | Assigned Effort |
| ------------------ | --------------- |
| Generic Consultant | 120h            |

This situation indicates:

✅ Capacity exists.

✅ Named resources have been booked.

❌ Work has not yet been redistributed.

The Resource Reconciliation tab is often the quickest way to identify these situations.

**Recommended Review**

Confirm:

- Named resources have received assignments.
- Generic assignments are being reduced appropriately.
- Capacity and assignments align.
- Staffing decisions are reflected in the schedule.

**Correct Differences Deliberately**

**The goal of reconciliation is not to force every difference to zero immediately.**

Some discrepancies are expected and even intentional.

Examples include:

- Resources booked before detailed planning occurs
- Future assignments not yet created
- Temporary staffing transitions
- Planned reserves of capacity
- Short-term scheduling adjustments

The Project Manager should understand the variance before correcting it.

![](https://storage.ghost.io/c/01/04/01046de9-7e0b-4441-996a-1f9d5cf4f9d1/content/images/2026/10/image-3.png)

**Final Thoughts**

Resource fulfilment in Project Operations is far more than a scheduling exercise. It is a governance process that combines project planning, staffing, capacity management, and collaboration between Project Managers and Resource Managers.

Resource Requirements express demand.

Bookings reserve capacity.

Assignments define the work resources are expected to perform.

The Resource Reconciliation tab connects these three elements and provides the visibility required to ensure that staffing decisions are accurately reflected in project execution.

Organizations that establish disciplined fulfilment and reconciliation practices are far better positioned to:

- Improve resource visibility
- Enhance capacity planning
- Reduce staffing inconsistencies
- Increase forecast accuracy
- Deliver projects more predictably