---
title: Create demand form
description: Create a demand for your application or capability.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/application-portfolio-management/eaw-create-new-demand-form.html
release: australia
topic_type: reference
last_updated: "2026-03-12"
reading_time_minutes: 4
breadcrumb: [Enterprise Architecture Workspace reference, Enterprise Architecture Workspace, Enterprise Architecture]
---

# Create demand form

Create a demand for your application or capability.

<table id="table_b5z_33b_ybc"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Assumptions

</td><td>

Assumptions made for the demand. Assumptions help to define scope and risks, and fine-tune the estimates for time and cost.

</td></tr><tr><td>

Approved end date

</td><td>

The approved date for completing the demand.

</td></tr><tr><td>

Approved start date

</td><td>

The approved date for starting the demand.

</td></tr><tr><td>

Action

</td><td>

Course of action for the demand.

</td></tr><tr><td>

Barriers

</td><td>

Major barriers to the demand.

</td></tr><tr><td>

Business capabilities

</td><td>

One or more capabilities to associate the demand with.

</td></tr><tr><td>

Impacted business applications

</td><td>

Business applications that are impacted by the demand.

</td></tr><tr><td>

Capital budget

</td><td>

Total capital budget allocated to the demand across all fiscal years.

 The value is rolled up from the Capital expenditure \(Capex\) budget of the demand.

</td></tr><tr><td>

Category

</td><td>

Category of the demand. The available options are:

-   **Strategic**
-   **Operational**

</td></tr><tr><td>

Business unit

</td><td>

Business unit to which the demand submitter belongs.

</td></tr><tr><td>

Capital expense

</td><td>

Capital expenditure \(Capex\) for the demand.

</td></tr><tr><td>

Business case

</td><td>

Business arguments that support the demand.

</td></tr><tr><td>

Collaborators

</td><td>

Users who can edit or contribute to the demand. A demand requester can select any user as a collaborator.

</td></tr><tr><td>

Demand manager

</td><td>

Name of the demand manager.

</td></tr><tr><td>

Demand

</td><td>

The name of the demand.

</td></tr><tr><td>

Enablers

</td><td>

Key enablers of the demand.

</td></tr><tr><td>

Demand actual cost

</td><td>

Total cost incurred while working on a demand and demand tasks. **Note:** To populate this field, you must run the **Update Demand Actual Cost and Actual Effort** schedule job.

</td></tr><tr><td>

Demand actual effort

</td><td>

Time accrued or spent by a resource while working on a demand or a demand task. **Note:** To populate this field, you must run the **Update Demand Actual Cost and Actual Effort** schedule job.

</td></tr><tr><td>

Financial return

</td><td>

Result is calculated based on values in the **Total costs** and **Financial benefit** fields.

</td></tr><tr><td>

Risk level

</td><td>

The level of risk associated with the demand. The available options are: -   **Critical**
-   **High**
-   **Moderate**
-   **Low**
-   **Planning**

</td></tr><tr><td>

Financial benefit

</td><td>

Estimate of revenue if the demand is approved.

This value is rolled up from the benefit breakdown of the demand.

 You can also enter the value manually. Select a currency icon and enter a value.

</td></tr><tr><td>

ROI %

</td><td>

Assesses demand return on investment \(ROI\) compared to other demands.

</td></tr><tr><td>

Impacted business units

</td><td>

Business unit that is impacted by the demand.

</td></tr><tr><td>

Labor costs

</td><td>

Expenses associated with the manpower required to work on the demand.

</td></tr><tr><td>

In scope

</td><td>

Scope of the demand. It’s the set of boundaries that define the extent of a demand.

</td></tr><tr><td>

Operating budget

</td><td>

Total operational budget allocated to the demand across all fiscal years.

The value is rolled up from the Operational expenditure \(Opex\) budget of the demand.

</td></tr><tr><td>

Related records

</td><td>

Records associated with the demand.

</td></tr><tr><td>

Risk of not performing

</td><td>

Risks if the demand is not approved, for example, risk of loss of opportunity.

</td></tr><tr><td>

Due date

</td><td>

Requested completion date of the demand.

</td></tr><tr><td>

Risk of performing

</td><td>

Risks if the demand is approved and implemented.

</td></tr><tr><td>

Operating expense

</td><td>

Operational expenditure \(Opex\) for the demand.

</td></tr><tr><td>

Other costs

</td><td>

Other miscellaneous costs associated with the demand.

</td></tr><tr><td>

Out of scope

</td><td>

Activities or deliverables that aren’t in the scope of the demand. Anything which isn’t defined in the scope is out of scope.

</td></tr><tr><td>

Cost

</td><td>

Total cost associated with the demand.

</td></tr><tr><td>

Score

</td><td>

Demand score is calculated based on **Risk**, **Value**, and **Size** attributes in the base system. -   When the **Risk** and **Size** are high, the score of the demand is low.
-   When the **Value** is high, the score of the demand is high.

</td></tr><tr><td>

Risk

</td><td>

Risk value calculated from the demand assessment.

</td></tr><tr><td>

Strategic Alignment

</td><td>

A value to assess how closely the demand aligns with the strategic goals of the organization.

</td></tr><tr><td>

Value

</td><td>

Business value of the demand.

</td></tr><tr><td>

Type

</td><td>

Type of the demand. The available options are: -   Project
-   Change

 The **Category** field selection determines the options available in the **Type** field.

</td></tr><tr><td>

Size

</td><td>

Size of the demand.

</td></tr><tr><td>

T-shirt size

</td><td>

Categorizing the demand into different sizes, to give a quick understanding of the relative complexity of the demand and the effort required for its completion.

 The available sizes are:

-   **S- Small**
-   **M- Medium**
-   **L- Large**
-   **XL- Extra Large**
-   **XXL- Extra Extra Large**

</td></tr><tr><td>

Stage

</td><td>

The current state of progression of the demand.

</td></tr><tr><td>

Start date

</td><td>

Start date of the demand.

</td></tr><tr><td>

Submitted on

</td><td>

Date on which the demand was submitted for approval.

</td></tr><tr><td>

Total planned cost

</td><td>

Result is calculated based on values in the **Capital expense** and **Operating expense** fields.

</td></tr><tr><td>

Visited states

</td><td>

The different states through which the demand has passed through.

 For example, the demand has gone through the states of **Open** and **Closed**. The visited state number in this scenario will be 2.

</td></tr><tr><td>

Primary goal

</td><td>

The primary goal behind the creation of the demand

</td></tr><tr><td>

Digital integration

</td><td>

Digital integration associated with the demand.

</td></tr></tbody>
</table>**Parent Topic:**[Enterprise Architecture Workspace reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-portfolio-management/eaw-reference.md)

**Related topics**  


[Exploring demands](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-portfolio-management/eaw-demands.md)

[Add or edit a demand](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-portfolio-management/eaw-create-demand-ba.md)