---
sourceDocument: Australia Strategic Portfolio Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/it-business-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Requested Allocation form

# Requested Allocation form {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Use Requested Allocation form to create a request for resource plans in Planning or Rejected state.
{#requested-allocation-form__table_df1_q3r_54__entry__2}

| Field | Description |
|-|-|
| Start date | Start date for the requested allocation record. |
| End date | End date for the requested allocation record. |
| FTE | Number of units for the full-time equivalent selection for the requested allocation record. If a resource is requested as FTE, then the planned hours for each requested allocation record are calculated first. A total of all hours is then rolled up as planned hours on the resource plan. See [Resource plans](https://servicenow-prod.fluidtopics.net/0oxycyvtS_ftuGx503ZR9Q "Resource plans are the key element in resource management.") for an explanation of FTEs. Nota: Capacity isn't derived from FTE, but from schedules. Both FTE and schedules must be in synchronization with each other. |
| Resource plan | Resource plan number to which the requested allocation record is attached. This field automatically populates if the requested allocation record is accessed from a resource plan. |
| Planned hours | Number of hours to allocate to the requested allocation record. By default, the [Resource Plan form](https://servicenow-prod.fluidtopics.net/IvWsJKi880XSxHwzjI3gaA "Field descriptions for the resource plan form fields.") on the resource plan form are proportionally distributed among all the requested allocations based on the number of working days for each requested allocation record. However, it's possible to override the planned hours or the FTE. |
| Planned cost | Estimated cost of resource. `Planned cost = Planned hours * hourly rate` The hourly rate is derived from one of the following sources: * Resource rate from the resource plan, if the Rate override option is selected. * [Rate model](https://servicenow-prod.fluidtopics.net/piqljNJH29OY_qiYwDAfQg "Use a rate model to derive date-effective, criteria-driven hourly rates for calculating planned and actual resource costs for a project or demand."), if it's populated on the project or demand to which the resource plan is associated. * Labor rate card for user resource plans. * Role rate when resource is requested by [resource role](https://servicenow-prod.fluidtopics.net/l4PFE8Uir2GuJZt_V42dNg "Define project-specific roles for team members based on their skills and competencies."), if the role has a rate. * Group hourly rate if role doesn't have a rate or if the role is null. * System property com.snc.time_card.default_rate if all the other conditions fail. {#requested-allocation-form__ul_mnr_z1m_jx} Planned costs roll up to the Planned cost field on the resource plan. |
| Planned cost in project currency | Planned cost of a project task in project currency when the PPM Standard Multicurrency (com.snc.ppm_multicurrency) plugin is activated and the Project Currency view is enabled. |
| Planned cost in demand currency | Planned cost of a demand task in demand currency when the PPM Standard Multicurrency (com.snc.ppm_multicurrency) plugin is activated and Demand Currency view is enabled. |
[Tabela 1. Requested Allocation form]

{#requested-allocation-form__table_df1_q3r_54}