---
sourceDocument: Zurich Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-business-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Demand tasks

# Demand tasks {#ariaid-title1}

* Release version: Zurich
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Demand tasks

Demand tasks are specialized units of work designed to organize and track early-stage planning activities within a demand record in ServiceNow.
They help structure initial efforts before a demand is converted into a work entity such as a product, feature, or enhancement.
Unlike project tasks, which focus on execution and project completion, demand tasks emphasize preparation and planning during the demand phase.
Show full answer Show less  

## Key Features

* **Planning Focus:** Demand tasks are intended for activities such as gathering requirements, conducting design reviews, assessing feasibility, completing business case analyses, and performing security or compliance assessments.
* **Resource Management:** Resources can be assigned to demand tasks using standard assignment fields, and they can log time spent via time cards. This enables tracking of actual effort and cost during the planning phase.
* **Cost and Effort Tracking:** Actual cost for demand tasks is calculated based on resource hourly rates defined in the rate model or system defaults. Costs and effort from all demand tasks roll up to the parent demand record.
* **Separation from Execution Work:** Demand tasks are not suitable for execution activities. After demand approval and conversion into a work entity (e.g., project or feature), execution work is managed through project tasks instead.

## Important Considerations

* Resource assignments and tracked time on demand tasks do not transfer to the resulting work entity created from the demand; reassignment is required.
* Demand tasks do not support planned, actual, or original dates---only a due date is available, which does not influence demand workflows.
* Features commonly available in project tasks such as nested tasks, task constraints (e.g., Start ASAP), and execution methodologies (Agile, Waterfall, Hybrid) are not supported in demand tasks.

## Practical Impact for ServiceNow Customers

Using demand tasks enables ServiceNow customers to effectively manage and document the critical planning phase of demands, ensuring clarity and structure before formal project execution begins. This separation allows for more accurate cost and effort tracking during planning without impacting project timelines or workflows. Understanding the limitations compared to project tasks helps customers use demand tasks appropriately for preparation activities, improving overall demand lifecycle management.  
Demand tasks are units of work within a demand. Use them to plan and organize initial activities before converting the demand into a work entity such as a product, feature, or enhancement.

## Demand task overview {#demand-tasks-ppw__section_purpose_scope}

Demand tasks organize and track early-stage planning activities within the demand record. Use them before converting a demand into a work entity such as a feature, product, or enhancement. Unlike project tasks, which track
execution and drive project completion dates, demand tasks focus on planning and preparation. This difference shapes what demand tasks can do and how you use them.

Examples of demand tasks include:

* Gathering and documenting requirements from stakeholders
* Conducting design or architecture reviews
* Validating technical feasibility or dependencies
* Completing business case analysis or ROI assessment
* Conducting security, compliance, or impact assessments
* Assigning resources for discovery or planning phases

{#demand-tasks-ppw__ul_s45_2t2_rjc}

Demand tasks aren't appropriate for execution work. After the demand is approved and converted into a work entity such as a project or feature, execution work moves into project tasks.

## Assigning resources and tracking effort {#demand-tasks-ppw__section_fqd_t3b_f3c}

You can assign resources to demand tasks using the standard assignment fields. Resources assigned to demand tasks can submit time spent on them using a time card, enabling you to track actual effort and cost during the planning
phase.

Resource assignments on demand tasks aren't transferred to the work entity created from that demand. If you later convert the demand into a project or work item, you must reassign resources in the new work entity. Similarly, the
time and cost tracked on demand tasks remain within the demand record and don't transfer to the resulting work entity.

The actual cost for the demand task effort is derived from the hourly resource rate defined in the rate model, default labor rate, or default system property. The actual cost and effort for all demand tasks roll up to the
associated demand. For more information, see [Actual cost and effort calculations for demands](https://www.servicenow.com/docs/3T3EF3un7AZycZqX8KF1ug "Actual cost and effort represent the realized cost and time spent on demands and demand tasks. Values are calculated from approved time cards and hourly rates.").

## Differences from project tasks {#demand-tasks-ppw__section_x23_f3b_f3c}

Because demand tasks are used for early-stage planning and not execution tracking so they don't support some features that project tasks do:

* Planned dates, actual dates, and original dates aren't supported in demand tasks.
* The due date indicates when the task is targeted for completion and doesn't affect the demand workflow. Project tasks affect project completion dates when planned dates and actual dates are changed.
* Nested demand tasks aren't supported.
* Task constraints such as Start ASAP and Start on a specific date aren't supported.
* Execution types such as Agile, Waterfall, or Hybrid aren't supported.
{#demand-tasks-ppw__ul_mns_m3b_f3c}