> ## 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 #2
- URL: https://www.d365architect.com/understanding-the-resource-fulfilment-process-2/
- Published: 2026-10-15T19:42:05.000Z
- Updated: 2026-10-19T01:12:25.000Z
- Author: Jerome Asselin

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

In the first article, we explored the fundamentals of resource fulfilment, including Resource Requirements, Schedule Board configuration, and booking statuses.

In this second article, we focus on Fulfilment Preferences, Resource Requests and direct booking scenarios.

**#1 Configure Fulfilment Preferences Before You Start**

**Resource matching quality is heavily influenced by Fulfilment Preferences.**

Before carrying out resource fulfilment activities, review the **Fulfilment Preferences** configuration in the Universal Resource Scheduling application.

**Navigation**

**Universal Resource Scheduling App → Settings → Fulfilment Preferences**

**Key Parameters**

| Parameter            | Purpose                                                                                                              |
| -------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Interval             | Defines the duration between available time slots evaluated by the scheduling engine.                                |
| Intervals Begin      | Defines the start time from which scheduling options are generated based on resource availability and working hours. |
| Results Per Interval | Limits the number of resource suggestions returned for each scheduling interval.                                     |

These settings influence the scheduling recommendations generated by Universal Resource Scheduling and therefore affect both resource matching and visibility on the Schedule Board.

They should be reviewed early during implementation and validated with business stakeholders as part of the scheduling strategy.

Fulfilment Preferences should not be treated as purely technical configuration. They affect the scheduling experience presented to Resource Managers and Project Managers and should therefore reflect the organization's agreed resource management practices.

**#2 Understand the Resource Request Process**

**Resource Requests facilitate collaboration between Project Managers and Resource Managers.**

When operating in **Centralized Resource Allocation Mode**, the standard approach is to generate a Resource Request from a Resource Requirement.

**Create a High-Quality Resource Requirement**

The fulfilment process typically starts with a generic resource assigned to project work.

Before creating a Resource Request, ensure that the associated Resource Requirement contains meaningful information.

At a minimum, review the following fields:

- Duration
- Preferred Resources
- Skills and Characteristics
- Roles
- Resourcing Unit
- Description

The more relevant information the Resource Requirement contains, the more effective the resource matching process will be.

**Resource Manager Workflow**

After a Resource Request has been created:

1. Open the Resource Request.
2. Select **Find Resources**.
3. Review matching resources on the Schedule Board.
4. Either:
  - Create a **Proposed** booking.
  - Create a **Soft** or **Hard** booking directly.

When proposing a resource, the Resource Manager must select **Mark for Review** to indicate that the Resource Request is ready for review by the Project Manager.

If changes are required, the Resource Manager can use **Rescind Review** to reopen the Resource Request and adjust the proposed resources or bookings.

**Project Manager Workflow**

The Project Manager reviews proposed resources from the associated Resource Requirement rather than from the Resource Request itself.

The Project Manager can:

- Accept a proposed resource.
- Reject a proposed resource.
- Accept one proposal and reject others when multiple resources have been proposed.

After acceptance:

- The booking is confirmed.
- The named resource is added to the project team.
- Task assignments are updated according to standard Project Operations fulfilment logic.

**Resource Request Status Considerations**

One aspect of the Resource Request lifecycle that frequently surprises implementation teams is the way its status behaves after a proposal has been accepted.

After acceptance:

- The Resource Request status returns to **In Progress**.
- The Resource Request is not automatically completed.
- The Resource Manager must manually set the Resource Request to **Completed**.

Resource Request status should therefore be actively monitored and incorporated into resource management governance.

Although the Resource Request participates in the fulfilment workflow, the **Resource Requirement remains the primary record for understanding fulfilment progress**, because it provides visibility into both Resource Requests and the resulting booking records.

**Practical Governance: Identify Resource Requests Ready for Completion**

One of the most common operational challenges in Project Operations is the accumulation of Resource Requests that remain in an **In Progress** status long after the associated staffing activity has been completed.

This situation can occur after:

- A proposed resource has been accepted.
- The associated Resource Requirement has been fulfilled.
- Bookings have been created.
- Remaining Duration has reached zero.

As a result, Resource Managers can gradually accumulate a backlog of Resource Requests that no longer require action but still appear as active staffing demand.

**Create a Ready for Completion Work Queue**

A practical solution is to create a dedicated **Resource Request view** that identifies Resource Requests that are likely ready to be updated to **Completed**.

**Suggested View Columns**

- Resource Request Name
- Status
- Resource Requirement
- Project
- Requested Role
- Owner
- Created On
- Modified On

**Recommended Business Filter Logic**

Resource Request Status = In Progress AND Associated Resource Requirement Remaining Duration = 0

This filter highlights Resource Requests for which:

- The fulfilment workflow is still technically open.
- The associated demand appears to have been fulfilled.
- Additional staffing work may no longer be required.

A Remaining Duration of zero is often a strong indication that fulfilment activities are complete. However, it should be treated as an **operational heuristic rather than a system-enforced completion rule**.

Before updating a Resource Request to **Completed**, the Resource Manager should confirm that no outstanding review, staffing activity, proposal decision, or booking adjustment remains.

**#3 Fulfil a Resource Requirement Directly**

**Not every fulfilment scenario requires a Resource Request.**

Before discussing direct fulfilment, it is important to understand the **Resource Allocation Mode** configured in the Project Operations parameters.

**Resource Allocation Modes**

Project Operations supports two resource management approaches.

| Mode        | Description                                                                                             |
| ----------- | ------------------------------------------------------------------------------------------------------- |
| Centralized | Resource fulfilment is primarily managed by Resource Managers using Resource Requests.                  |
| Hybrid      | Project Managers and Resource Managers can both participate in fulfilment and create bookings directly. |

The selected mode influences:

- Who participates in fulfilment activities
- Whether Resource Requests are required
- How projects are initially staffed
- The behaviour of Resource Requirements created during project initiation

The chosen mode should be aligned with the organization's governance model and resource management maturity.

**Centralized Resource Allocation Mode**

In a **Centralized** model:

- Project Managers create Resource Requirements.
- Resource Managers own fulfilment activities.
- Resource Requests are commonly used.
- Proposed bookings are reviewed before final confirmation.
- Staffing decisions are controlled centrally.

This model is often selected by organizations that:

- Manage shared resource pools.
- Require formal approval processes.
- Have dedicated Resource Managers.
- Need visibility into enterprise-wide capacity planning.

The workflows described in Section #2 are typically associated with this operating model.

**Hybrid Resource Allocation Mode**

In a **Hybrid** model:

- Project Managers can staff projects directly.
- Resource Managers can still participate when needed.
- Resource Requirements exist but Resource Requests may not be required.
- Bookings can be created directly from projects.
- Staffing decisions can be made more quickly.

This model generally provides greater flexibility while retaining the ability to use Resource Managers where appropriate.

Organizations often select Hybrid Mode when:

- Resource Managers are not involved in every staffing decision.
- Project Managers are expected to manage portions of their own resource allocation.
- Faster fulfilment cycles are required.

**Hybrid Mode and Automatically Generated Resource Requirements**

One of the most surprising behaviours for implementation teams occurs when a new project is created in Hybrid Mode.

Project Operations automatically generates a **Resource Requirement** in the background.

This Resource Requirement is intentionally broad and does not contain predefined matching criteria such as:

- Roles
- Skills
- Preferred Resources

Its purpose is not to represent a specific staffing need.

Instead, it serves as the underlying mechanism that supports direct booking from the project.

**Why Does This Requirement Exist?**

When a Project Manager selects:

**Project Team → Book** then Project Operations requires a Resource Requirement to support the scheduling and matching process.

Rather than forcing the Project Manager to manually create one beforehand, the application generates a generic Resource Requirement automatically.

This behaviour often causes confusion because implementation teams find Resource Requirements on newly created projects even though nobody explicitly created them.

In reality, these records are a technical mechanism that supports direct fulfilment.

**Direct Fulfilment Workflow**

In Hybrid Mode, a Project Manager can book resources directly from either:

- The **Project Team** page
- A **Resource Requirement**

Although both actions ultimately create bookings, the underlying Resource Requirement remains the record used by the scheduling engine to support fulfilment.

A Project Manager can therefore fulfil a Resource Requirement without:

- Creating a Resource Request
- Involving a Resource Manager
- Using the proposal and review process

**Direct Booking Process**

A typical direct booking process is:

1. Open the project.
2. Navigate to the Project Team.
3. Select **Book**.
4. Open the Schedule Board.
5. Identify appropriate resources.
6. Create the booking.
7. Choose the desired booking status.

The booking can be:

- Hard Booked
- Soft Booked

The selected booking status determines capacity consumption and team membership behaviour, as discussed in Part 1 of this series.

**What Happens During Direct Fulfilment?**

When direct fulfilment is used:

**Resource Request**

- No Resource Request is created.
- No proposal workflow occurs.
- No review cycle is required.

**Resource Requirement**

- Remains the primary fulfilment record.
- Tracks fulfilment status.
- Tracks associated bookings.

**Booking**

- Is created immediately.
- Reflects the selected booking status.

This considerably simplifies the fulfilment process compared to the centralized model.

**Monitoring Fulfilment Progress**

When Resource Requests are not used, the primary indicator of fulfilment progress becomes the **Remaining Duration** field on the Resource Requirement.

**Remaining Duration**

The Remaining Duration field reflects the portion of the Resource Requirement that has not yet been fulfilled through associated bookings.

| Remaining Duration | Interpretation                                        |
| ------------------ | ----------------------------------------------------- |
| Greater than zero  | Resource demand remains open or partially fulfilled.  |
| Equal to zero      | Resource demand appears to have been fully fulfilled. |

Many organizations use Remaining Duration as the primary operational indicator of open staffing demand when using direct fulfilment.

**Remaining Duration as a Governance Indicator**

A Remaining Duration value of zero is often a strong indication that fulfilment activities are complete.

However, Remaining Duration should be viewed as a:

**Governance indicator, not a system-enforced completion rule.**

Before considering staffing complete, Project Managers should verify:

- Required bookings exist.
- Booking dates align with project needs.
- Resource assignments are correct.
- Resource Reconciliation has been reviewed where appropriate.
- No additional fulfilment activities remain.

This distinction becomes particularly important when multiple named resources fulfil a single Resource Requirement, which is the topic of the next section.

**Key Takeaways**

**Centralized Mode**

✅ Resource Requests drive fulfilment.

✅ Resource Managers play a primary role.

✅ Proposal and review workflows are commonly used.

**Hybrid Mode**

✅ Direct booking is available.

✅ Project Managers can fulfil Resource Requirements directly.

✅ Automatically generated Resource Requirements support project-level booking.

**Direct Fulfilment**

✅ Faster staffing process.

✅ Reduced administrative overhead.

✅ Requires governance around Remaining Duration and booking validation.

**Practitioner Recommendation:** Even when operating in Hybrid Mode, establish clear guidance regarding the use of automatically generated Resource Requirements, direct booking practices, and the review of Remaining Duration. Consistency in these areas significantly improves staffing visibility and reporting quality.