RIDAC (Risk, Issue, Decision, Action, and Change)

maliksneha9 · 55m ago

Even with careful planning, unexpected risks, issues, or changes can arise. RIDAC helps teams track and manage these situations in a structured and transparent way.

Each RIDAC item supports downstream creation of related components, ensuring smooth governance.
A single Risk can be converted into multiple Issues, Decisions, Actions, or Change Requests as long as the Risk remains open.
An Issue can lead to multiple Decisions, Actions or a Change Request.
A Decision can trigger multiple Actions or a Change Request.
An Action can result in a follow-up Change Request.
RIDAC doesn’t have to follow a strict sequence like Risk → Issue → Decision → Action → Change. Depending on the situation and severity, the Demand Manager can create any RIDAC record directly - for example, a Change can be raised immediately based on a leadership Decision or a high-impact Risk.

Component	Description
R - Risk	• A risk is something that might happen in the future and could negatively impact the demand or project if not managed proactively. • Example: ‘There is a chance the vendor may delay delivery by 2 weeks.’
I - Issue	• An issue is a problem that has already occurred and needs immediate attention. • *Example:* ‘The API development is blocked because test credentials are not available.’
D - Decision	• A decision is a choice made by stakeholders that influences the direction, scope, cost, or delivery of the work. • *Example:* ‘Leadership decided to use Tanium Deploy instead of SCCM for provisioning.’
A - Action	• An action is a task or activity that needs to be completed, usually to support risks, issues, or project execution. • Example: ‘Update the workflow to include manager approval.’
C – Changes	• A change is any modification in scope, cost, schedule, or requirements that impacts the demand or project. • Example: ‘New requirement added: deployment notification must go to Team Leads as well.’

- Create Risk record

Task: - Demand to which this risk belongs.

Probability: - The likelihood that the event described in the risk will occur. The available options are: Absolute, High, Moderate, and Low.

Estimated Cost: - Estimated cost the risk event generates.

Assigned to: - Primary resource assigned to work on the risk.

Mitigation Plan: - This information gets added when and if the event occurs.

Impact: - Impact of the risk event on the outcome of the demand. Choice are: - High, Medium, and Low.

Click on Save button to save the risk record.

Convert one RIDAC record to another

A RIDAC record (Risk, Issue, Decision, Action, or Change) can be converted into another RIDAC type to help track how a situation evolves — without creating a new record from scratch.
Key information such as Short Description and Description is automatically carried forward during conversion.
You can choose to close the current record when creating the new one. Once closed, no further RIDAC records can be created from it.

To convert a record, click “Convert to RIDAC” under the Related Links section on the form.

Associate existing RIDAC records

You can link related RIDAC records together to show how risks, issues, decisions, actions, or changes are connected within the same demand.
Associating records helps track relationships and provides better visibility during demand monitoring and closure.
One RIDAC record can be associated with multiple related records.
RIDAC records can only be associated if they belong to the same Demand or related work item.

Use Associate RIDAC from the Related Links section on the record form to create the relationship.