High-level project resource requests should be created early in the project lifecycle to define:

• The resources required (Generic or Named)
• The level of effort required across time
• The expected demand to support project delivery

This enables enterprise resource management to:

• Monitor demand vs capacity
• Make informed staffing decisions
• Ensure resources are available for approved projects

The Resource Plan provides a time‑phased view of proposed and committed effort, allowing you to track how requested demand evolves into approved and fulfilled allocations.

For more details on the Resource Plan and its capabilities, refer to:
Altus Resource Plan documentation

Where This Is Performed

• Project → Resource Plan

Important: Purpose of the Resource Plan

The Resource Plan is used to:

• Capture project demand
• Communicate requirements to resource managers
• Facilitate allocation and fulfilment

It acts as the starting point for:

• Resource Demand
• Capacity planning
• Availability and workload balancing

Adding Resources to the Plan

1. Navigate to the Resource Plan tab within the project
2. Use the Add a Resource search box
3. Select:
4.  
   • A generic role (e.g. Business Analyst), or
   • A named resource (if known)

Tip:
You can add the same role or resource multiple times if needed, for example to represent different demand segments or time allocations.

Setting the Data Entry Mode

Depending on your organisation’s configuration, select the appropriate mode:

• Hours
• FTE (Full-Time Equivalent)
• Capacity %

This determines how effort is entered across time.

Entering Proposed Effort

• Enter values in the Proposed (P) column for each time period

This represents the resource demand being requested.

The Resource Plan grid displays effort across time (e.g. monthly periods), allowing you to build a time‑phased demand profile for each resource or role.

Important:

• Named resources show availability (based on calendars)
• Generic roles do not have availability

Be mindful not to over-request named resources beyond their available capacity.

Using Comments

You can add comments at the end of each resource row to:

• Provide context for the request
• Indicate priority or constraints
• Guide the resource manager during fulfilment

Important:
Comments are not real-time chat — they act as a record of communication visible to both project and resource managers.

Saving vs Submitting Requests

There is a key distinction in how requests are processed:

• Save
•  
  • Stores the data
  • Keeps status as Draft
  • Does NOT notify resource managers
• Submit and Save
•  
  • Changes status to Submitted
  • Sends a notification task and email to the relevant fulfiller
  • Makes the request visible in Resource Demand

Important:
Resource requests must be submitted (not just saved) to be processed.

Understanding Request Statuses

Each period within the Resource Plan has a status:

• Draft – saved but not submitted
• Submitted – awaiting fulfilment
• Approved – fulfilled as requested
• Set by approver – fulfilled using a different resource

Status Behaviour

• Editing a submitted request changes it back to Draft
• Re-submission is required after changes
• Status is visible when hovering over values

Viewing Committed Allocations

Once resource managers fulfil the request:

• Values appear in the Committed column
• The Resource Plan displays both:
•  
  • Proposed (requested) effort
  • Committed (approved) effort

This allows you to clearly compare:

• What was requested
• What has been approved and allocated

Important:
The Resource Plan is a time‑phased view, meaning each period shows both proposed and committed values.

Tip:
Differences between Proposed and Committed values indicate where:

• Demand has been partially fulfilled
• Resources have been substituted
• Capacity constraints have influenced allocation

Updating the Resource Plan

The Resource Plan is a living document.

You can:

• Adjust proposed hours
• Add or remove resources
• Update allocations over time

Important:
Any changes:

• Reset affected values to Draft
• Require Submit and Save again

How This Connects to Resource Demand

The workflow is:

1. Project Manager defines demand in Resource Plan
2. Requests are submitted
3. Resource Manager fulfils demand (Resource Demand / Heatmap)
4. Committed allocations appear back in the Resource Plan

Tips

• Create resource demand early in the project lifecycle
• Use generic roles first when specific resources are not yet confirmed
• Always use Submit and Save to trigger fulfilment
• Review committed allocations regularly
• Use comments to guide fulfilment decisions
• Align updates with project schedule and delivery needs