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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# RIDAC Change Request form

# RIDAC Change Request form {#ariaid-title1}

Release version: Australia  
Updated August 4, 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 RIDAC Change Request form

The RIDAC Change Request form is designed to help ServiceNow customers document, track, and manage proposed changes related to demand or project planning items.
It enables effective monitoring of change request statuses and supports transparent communication throughout the change implementation process.
Show full answer Show less  

## Key Features

* **Number:** Auto-generated unique identifier for each change request.
* **State:** Tracks the current status with options like Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped.
* **Title:** Required concise summary that serves as the record title.
* **Description:** Detailed explanation including rationale, scope, expected benefits, and context of the change.
* **Business Justification:** Explains the rationale and problem/opportunity addressed by the change.
* **Priority:** Levels from Critical (1) to Planning (5) to assist with prioritization and scheduling.
* **Estimated Cost:** Financial estimate to implement the change, aiding budgeting and planning.
* **Impact:** Assesses potential effect with options High, Medium, or Low.
* **Approval:** Tracks approval status including Not Yet Requested, Requested, Approved, and Rejected.
* **Assigned to:** Designates the user or team responsible for implementation.
* **Due date:** Target date for completing the change.
* **Category:** Classifies the change as Resource, Scope, Schedule, or Cost for routing and reporting.
* **Parent Execution item:** Automatically links the change request to its related project or demand for integrated tracking.
* **Planning Item:** Auto-populated association to the relevant planning item when created from that context.
* **Work notes:** Internal notes to record progress, approvals, and modifications for audit and communication purposes.

## Key Outcomes

Using the RIDAC Change Request form ensures structured change management by linking change requests directly to execution and planning items. This structured approach facilitates prioritized scheduling, clear accountability, financial oversight, and comprehensive tracking of change implementation status, helping ServiceNow customers maintain control and visibility over their project and demand changes.  
Use the RIDAC Change Request form to document and track proposed changes to your demand or project planning items. Manage change requests and monitor implementation status.
{#ridac-change-request-form-ppw__table_ridac_change_form__entry__2}

| Field | Description |
|-|-|
| Number | Unique identifier for the change request. This field is auto-generated when the change request is created. |
| State | Current status of the change request. The available options are Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped. |
| Title | Brief, concise summary of the proposed change. This field is required and appears as the title of the change request record. |
| Description | Detailed information about the proposed change, including the rationale, scope, expected benefits, and any relevant context. |
| Business Justification | Business rationale and justification for the proposed change. Explains why the change is needed and what problems it solves or opportunities it enables. |
| Priority | Priority level of the change request. The available options are 1 - Critical, 2 - High, 3 - Moderate, 4 - Low, and 5 - Planning. This helps with change prioritization and scheduling. |
| Estimated Cost | Estimated cost in currency (for example, USD) to implement the change. Helps with financial tracking and planning. |
| Impact | Potential impact of implementing the change. The available options are 1 - High, 2 - Medium, 3 - Low. This helps assess the magnitude of change. |
| Approval | Approval status of the change request. Options include Not Yet Requested, Requested, Approved, and Rejected. Tracks whether the change request requires or has received approval. |
| Assigned to | User or team responsible for implementing the change. |
| Due date | Target date by which the change should be implemented. |
| Category | Category or type of change request. The available options are Resource, Scope, Schedule, and Cost. Helps classify and route change requests appropriately. |
| Parent | Execution item (such as a project or demand) that this RIDAC item was created on. This field is automatically populated with the execution item when you create the RIDAC item. The RIDAC item is then linked to the corresponding planning item, ensuring it appears in related lists at the execution level and in reports at the planning level. |
| Planning Item | The planning item (project or demand) that this change request is associated with. This field is auto-populated when a change request is created from a planning item context. |
| Work notes | Internal notes and updates about change implementation progress, approvals, and any modifications. Used to track work history and communication. |
[Table 1. RIDAC Change Request form]

{#ridac-change-request-form-ppw__table_ridac_change_form}