The RAID register or the RAID Card View shows all Risks, Assumptions, Issues, and Dependencies items recorded directly under the current initiative and within its sub initiatives.



When you access the card view for the first time, you will see all RAID items, but you could list only the type of classification that you require to see, using the filter text field. For example, with All RAID Items selected in the first field, if you select Risk in the adjacent field, you will be able to filter out only Risk cards. Similarly, you could select Dependencies in the field to see all dependencies cards.

By default, the cards are sorted by the item classification, but you can sort them by name, owner, status, approval status, impact, likelihood and review date.

To create a new RAID item, click on the New button.

RAID Card

Each card in the RAID card view represents an individual RAID item. It shows the RAID item name and owner at the top. Labels under this row will show the RAID item classification, internal ID, status, approval status and review date.

The card also displays the mitigation plan, rating, impact and likelihood of the RAID item. If it is a dependency item, you will see the names of the linked initiatives and the corresponding tasks and owners on the card.

The action buttons on the card will allow you to:

• View the dashboard for a RAID item - To open the risk dashboard of a RAID item, click on its name.
• modify the RAID item settings - Click on the Edit"pen" icon to access the edit form.
• Archive a RAID item.

Dependency Relationship

Dependency items carry a Dependency Relationship value that states how the initiative being viewed relates to the dependency. The value is worked out from the Predecessor Initiative and Successor Initiative already recorded on the item. It is not stored and cannot be edited.

On the initiative where the dependency lives, the value is one of:

• Same-Initiative — the Predecessor Initiative and the Successor Initiative are the same initiative.
• Predecessor — the initiative being viewed is the Predecessor Initiative, and it differs from the Successor Initiative.
• Successor — the initiative being viewed is the Successor Initiative, and it differs from the Predecessor Initiative.

On roll-up initiatives, where the dependencies were created on lower-level initiatives, the value is one of:

• Same-Initiative — the Predecessor Initiative and the Successor Initiative are the same initiative.
• Cross-Initiative — the Predecessor Initiative and the Successor Initiative are different initiatives.

The value is blank for Risk, Assumption, Issue and Other items.

Where Dependency Relationship is available

• RAID Register table — Dependency Relationship is a column and a filter. It is listed above Successor Initiative and is not selected by default in existing views. The checkbox filter offers Select All, Blanks, Same-Initiative, Cross-Initiative, Predecessor and Successor. Only the options that apply to the items on the register are listed, so Same-Initiative does not appear where no item has that value.
• Project Brief — a column and filter option on the RAID Items: All and RAID Items: Dependency widgets, including in the template builder. It is not enabled on existing widgets.
• Status reports — a column and filter option on the Featured RAID widget, including in the template builder. It is not enabled on existing widgets. The value is stored with the status report when the report is published, so a reviewer under Manage Status Updates sees the Predecessor and Successor values as they were for the requesting initiative.

Dependency Relationship applies to both the Classic Model and the Program Model.