RIDAC Decision form

Use the RIDAC Decision form to document and track critical planning decisions related to your strategic planning items, goals, or EAP iterations. Manage decision rationale and implementation status.

Table 1. RIDAC Decision form

Field	Description
Number	Unique identifier for the decision. This field is auto-generated when the decision is created.
State	Current status of the decision. The available options are Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped.
Short description	Brief, concise summary of the decision to be made. This field is required and appears as the title of the decision record.
Description	Detailed information about the decision, including the problem statement, decision context, available options, and any relevant background information.
Priority	Priority level of the decision. The available options are 1 - Critical, 2 - High, 3 - Moderate, 4 - Low, and 5 - Planning. This helps with decision sequencing and resource allocation.
Decision status	Current status of the decision process. Options include Pending, Approved, and Rejected. This field tracks the approval status of the decision.
Impact	Potential impact of implementing the decision. The available options are 1 - High, 2 - Medium, 3 - Low. This helps assess the magnitude of decision.
Approval Required	Indicates whether approval is required for the decision. Select Yes or No to specify if the decision needs formal approval from stakeholders or decision authority.
Estimated Cost	Estimated cost in currency (for example, USD) associated with implementing the decision. Helps with financial tracking and planning.
Due date	Target date for decision implementation or effective date.
Assigned to	User or team responsible for implementing the decision and tracking its outcomes.
Planning Item	The planning item (project, demand, epic, feature, or custom planning item) that this decision is associated with. This field is auto-populated when a decision is created from a planning item context.
Enterprise agile iteration	The EAP iteration associated with this decision. This field is auto-populated when a decision is created from an EAP iteration context.
Goal	The goal (portfolio plan goal or board goal) that this decision is associated with. This field is auto-populated when a decision is created from a goal context.
Parent	Parent decision, if this decision depends on or relates to another decision. Used for decision hierarchy and dependency tracking.
Work notes	Internal notes and updates about decision evaluation, discussions, approval status, and implementation progress. Used to track decision history and communication.