RIDAC Change Request form

  • Release version: Australia
  • Updated August 4, 2026
  • 1 minute to read

    • 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.

    Table 1. RIDAC Change Request form
    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.
    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.
    Change Type Type of change being requested (for example, scope change, schedule change, resource change, requirement change). Helps categorize and manage different types of changes.
    Estimated Cost Estimated cost in currency (for example, USD) to implement the change. Helps with financial tracking and planning.
    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.
    Parent Parent change request, if this change request is dependent on another change. Used for change hierarchy and dependency tracking.
    Work notes Internal notes and updates about change implementation progress, approvals, and any modifications. Used to track work history and communication.