---
title: "Create a resource plan from the schedule"
url: "https://help.altus.pro/fr/article/create-a-resource-plan-from-the-schedule"
language: "fr"
last_updated: "2026-06-16T01:50:52.559Z"
---

# Create a resource plan from the schedule

[Embedded content](https://player.vimeo.com/video/1024226135)

The Resource Plan in Altus allows project managers to define **resource demand** by specifying:

-   Required resources (Generic or Named)
-   Effort across time periods (hours or FTE)

or fulfilment through the **Resource Demand** process. Once fulfilled, the committed allocations are reflected back into the Resource Plan.

* * *

## Where This Is Performed

-   **Project → Resource Plan**

* * *

## Important: Purpose of the Resource Plan

The Resource Plan serves as the **single source of truth for resource demand**, enabling:

-   Structured resource requests across time
-   Alignment between project delivery and capacity
-   Integration with Resource Demand and availability management

* * *

## Option: Create Plan from Schedule

The **Create Plan from Schedule** feature allows you to generate a resource plan based on task assignments.

### To create a resource plan from a schedule:

1.  Ensure your project schedule includes:
    -   Start Date
    -   End / Finish Date
    -   Effort
    -   Duration
    -   At least one task assignment with an Altus resource
2.  Navigate to **Project → Resource Plan**
3.  Select **Data → Create Plan from Schedule**

This will:

-   Import resource assignments from Tasks
-   Create Resource Plan entries aligned to the schedule
-   Populate effort at a detailed (day-level) granularity

* * *

## Important: When to Use “Create Plan from Schedule”

> **Important:**  
> This feature is intended as a **one-off starting point during the planning phase**, not an ongoing synchronisation mechanism.

-   Each time it is run, it attempts to create new Resource Plan data
-   It should be used to initialise the plan, then maintained manually afterward

* * *

## Behaviour When Creating from Schedule

-   If no task assignments exist → no data is created
-   If draft or proposed data exists → you will be prompted to overwrite
-   If committed data exists → you must delete it before re-running

* * *

## Adding and Managing Resource Requests

You can create or update resource demand directly in the Resource Plan.

Project managers typically:

-   Add **generic roles** (e.g. Business Analyst)
-   Add **named resources** where known
-   Define **approval ownership** (e.g. pool owner or team manager)

* * *

## Entering Proposed Effort

-   Enter effort across time using:
    -   Hours, or
    -   FTE

> **Important:**
> 
> -   Only **named resources** display availability (based on calendars)
> -   Generic roles do not have availability constraints

As effort is entered:

-   Values are shown in the **Proposed column**
-   Hovering over values reveals additional details and status

* * *

## Saving vs Submitting Resource Requests

There is a key distinction in how data is processed:

**Save**

-   Stores the data
-   Keeps status as **Draft**
-   Does NOT notify resource managers

**Submit and Save**

-   Changes status to **Submitted**
-   Sends request to the appropriate manager
-   Triggers fulfilment in the Resource Demand view

> **Important:**  
> Resource requests must be **submitted** (not just saved) to be visible for fulfilment.

* * *

## Understanding Request Statuses

Each time period within a resource plan can have a status:

-   **Draft** – saved but not submitted
-   **Submitted** – sent for fulfilment
-   **Approved** – fulfilled as requested
-   **Set by approver** – fulfilled with a different resource

### Status Behaviour

-   Editing a submitted request changes it back to **Draft**
-   Submitting again re-sends it for fulfilment
-   Status is visible when hovering over values

* * *

## Viewing Committed Allocations

Once resource managers fulfil the request:

-   Values appear in the **Committed column**
-   You may see:
    -   Original requested resource fulfilled
    -   Substitute resources assigned
    -   Split allocations across multiple resources

> **Important:**
> 
> -   “Approved” indicates the requested resource was assigned
> -   “Set by approver” indicates an alternative resource was allocated

* * *

## Using Comments

Comments provide a way to communicate with resource managers.

-   Add context to requests
-   Indicate priority or constraints
-   Respond to fulfilment decisions

> **Important:**  
> Comments are not a chat system — they are a **record of decisions and communication**.

* * *

## Updating the Resource Plan

After fulfilment:

You can:

-   Increase or decrease demand
-   Add new resource requests
-   Adjust time-based allocations

Any changes:

-   Reset affected values to **Draft**
-   Require re-submission

> **Tip:**  
> Treat the Resource Plan as a **living document** that evolves with the project.

* * *

## How This Connects to Resource Demand

The workflow operates as follows:

1.  Project Manager creates resource requests (Resource Plan)
2.  Requests are submitted for fulfilment
3.  Resource Manager fulfils demand (Resource Demand / Heatmap)
4.  Allocations appear back in the Resource Plan as committed work

* * *

## Tips

-   Use **Create Plan from Schedule** only as an initial setup tool
-   Always use **Submit and Save** to trigger fulfilment
-   Review committed allocations regularly
-   Use comments to guide fulfilment decisions
-   Monitor changes as updates will require re-submission
-   Be mindful of named resource availability when requesting effort