Resource Demand in Altus is driven by Project Resource Requests created in a project’s Resource Plan. These requests define:

• The resources required, either Generic or Named
• The effort required across time periods
• The approval path for fulfilling the demand

The Resource Demand view allows resource managers, team managers, line managers, or pool owners to review unfulfilled requests, validate availability, and commit suitable resources to project work. Once fulfilled, those committed allocations flow through to the project resource plan, availability heatmaps, and resource reporting.

For supporting product guidance, refer to Altus Resource Demand documentation.

Where This Is Performed

• Resources → Resource Demand

Important: Who Typically Performs This

This activity is typically managed by:

• Resource Managers
• Team Managers
• Line Managers
• Pool Owners

The view is normally filtered to show only the unfulfilled resource requests for resources that the current user is responsible for fulfilling.

Before You Fulfil Demand

Resource Demand is typically driven from the Project Resource Plan, where project managers:

• Add generic roles or named resources
• Enter effort across time using hours or FTE
• Assign a pool owner or team owner where required
• Add comments to guide fulfilment
• Submit requests using Submit and Save

Important:

• Save only stores the request
• Submit and Save formally sends the request for fulfilment and notifies the appropriate manager

Set the Planning Horizon

1. Navigate to Resources → Resource Demand
2. Use the toolbar to define:
3. • Time scale (e.g. Month, Week, Year)
   • Unit of measure (e.g. FTE)
   • Visible date range

Important:
The selected date range controls:

• The visible planning horizon
• Availability heatmap display
• Autofill and allocation behaviour

Review Resource Requests

Resource requests can be reviewed and grouped in different ways:

• Group by Resource to fulfil demand across multiple projects
• Switch to Monthly view for easier planning
• Switch to FTE view if effort was entered in FTE

This provides visibility into competing demand and allocation requirements.

Fulfil Demand for Named Resources

For named resources, availability must be considered before committing work.

To fulfil a named resource request:

1. Locate the named resource request
2. Hover over the proposed value to review details
3. Use one of the following methods:
4. • Click the proposed value to copy it into the committed column
   • Enter committed values manually
   • Use ellipsis (…) → Auto Fill to copy proposed values
4. Click Save to confirm the allocation

Tip:
Auto Fill (from the ellipsis menu on a specific request) copies the requested effort into the committed columns, allowing controlled fulfilment of individual requests.

⚠️ Avoid using the global Autofill button (typically located at the bottom right of the page), as this will automatically commit all pending resource requests without review, potentially bypassing capacity checks and human decision-making.

Partially Fulfil or Split Requests

You are not required to assign a single resource to fulfil a request.

You can:

• Partially allocate a resource
• Add additional resources to fulfil the remaining demand
• Replace a requested resource entirely
• Split allocation across multiple resources

Best Practice:
Always provide a comment when you deviate from the original request (e.g. splitting work or assigning a different resource).

Fulfil Demand for Generic Roles

Generic roles must be fulfilled by assigning named resources.

To fulfil a generic request:

1. Locate the generic role
2. Click ellipsis (…) → Add Fulfilment Resource
3. Search and select an appropriate resource
4. Review availability
5. Adjust committed values if required
6. Click Save

When assigned:

• The named resource appears indented under the project request
• Proposed values are often copied into committed values
• You may need to adjust allocations manually if changes are made

Use Comments to Communicate Decisions

Comments provide a structured way to communicate between project managers and resource managers.

• Comments are not real-time chat
• They form a record of decisions
• They are visible on both sides

Use comments to explain:

• Partial fulfilment
• Resource substitutions
• Allocation decisions
• Prioritisation

Understand Request Statuses

Different statuses indicate the state of a request:

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

Fully vs Partially Fulfilled Requests

• Fully fulfilled requests disappear from the default view
• Partially fulfilled requests remain visible
• Filters can be adjusted to show fulfilled requests

Availability and Heatmaps

Availability is a key factor in fulfilment decisions:

• Only named resources have availability (based on calendars)
• Generic roles do not have availability
• The heatmap shows:
• • Capacity
  • Committed work
  • Remaining availability

Important:
Avoid over-allocating resources by reviewing availability before committing work.

Tip:
Resource demand can also be fulfilled directly from the Availability Heatmap, which provides a resource-centric view of capacity versus committed work across projects. From here, you can adjust allocations and save changes to fulfil demand without using the Resource Demand view.

👉 Refer to:
https://docs.altus.pro/products/AltusPPM/AsBuilt/Resources/Availability-Heatmap.html

Delegation

You can adjust filters to act on behalf of another manager.

This allows you to:

• View requests outside your default scope
• Fulfil demand on behalf of other managers

How This Impacts Altus

Fulfilling resource demand updates:

• Project resource plans
• Committed work allocations
• Resource availability views
• Insights reporting

This ensures alignment between project demand and organisational capacity.

Tips

• Use monthly view for planning consistency
• Use FTE view for capacity-based planning
• Always validate availability before committing resources
• Use comments to explain fulfilment decisions
• Review demand regularly to prevent over-allocation
• Use the heatmap to rebalance workloads