RIDAC Change Request form

---
title: RIDAC Change Request form
description: Use the RIDAC Change Request form to document and track proposed changes to your strategic planning items, goals, or EAP iterations. Manage change requests and monitor implementation status.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-business-management/strategic-planning/ridac-change-request-form-spw.html
release: australia
product: Strategic Planning
classification: strategic-planning
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 2
keywords: [RIDAC, change, change request, form, planning item]
breadcrumb: [Reference, RIDAC, Strategic Planning, Strategic Portfolio Management]
---

# RIDAC Change Request form

Use the RIDAC Change Request form to document and track proposed changes to your strategic planning items, goals, or EAP iterations. Manage change requests and monitor implementation status.

|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, demand, epic, feature, or custom planning item\) that this change request is associated with. This field is auto-populated when a change request is created from a planning item context.|
|Enterprise agile iteration|The EAP iteration associated with this change request. This field is auto-populated when a change request is created from an EAP iteration context.|
|Goal|The goal \(portfolio plan goal or board goal\) that this change request is associated with. This field is auto-populated when a change request is created from a goal context.|
|Work notes|Internal notes and updates about change implementation progress, approvals, and any modifications. Used to track work history and communication.|