RAID register

The RAID register keeps risks, assumptions, issues and dependencies in one place, instead of scattered across documents. Each item has an owner, a due date and a history, and can be linked to an engagement, an ARB item and repository elements. Risks and issues are scored so the worst rise to the top. This module needs to be switched on for your organisation.

RAID

A short panel that appears on an engagement page and on the Outputs dashboard.

• On an engagement it lists that engagement’s open items with their score, and has Add a RAID item (contributors and above) and a link to the full register for that engagement.
• On Outputs it shows counts of open items, risks, assumptions, issues, dependencies, high-rated and overdue items, plus the heat map.

Use it as a quick check; open the register for the full picture. See Outputs and dashboards.

RAID register

All items in one table: reference, kind, title, rating, status, owner, due date and linked engagement or ARB item. The figures at the top count open items, risks, issues, high-rated and overdue items.

1. Filter by kind, status, rating or search text. Tick Mine for items you own or raised, or Overdue only.
2. Select a reference to open an item.
3. Add an item creates one; Download CSV exports the current filter.

By default closed items are hidden. Overdue items show the word overdue beside the date.

Architects also see Email reminders to owners: when on, the owner of an open item is emailed shortly before it falls due, when it is overdue, and again after the repeat period until it is closed or updated. You set the days; owners need an email address on the item. Reminders are off until an architect switches them on.

Heat map

A five by five grid of open risks and issues, with likelihood down the side and impact across the top. Each cell shows how many items sit there and is coloured by band: High (score 15 and over), Medium (8 to 14) or Low (below 8). The score is likelihood multiplied by impact.

Use it to see at a glance whether risk is clustering in the top right, and to spot items whose rating has crept up. Assumptions and dependencies are not scored, so they do not appear.

Add to the RAID register

Use this form to record a new item.

1. Choose what it is: Risk, Assumption, Issue or Dependency.
2. Give a title and a description.
3. For risks and issues, choose likelihood and impact from 1 (very low) to 5 (very high).
4. Name the owner, add their email so they can update it, and set a due or review date.
5. Write the mitigation, the action you will take, or what it depends on.
6. Optionally link an engagement (for example ENG-0001) and an ARB item (ARB-0001).
7. Choose Add.

Any contributor can add items.

A RAID item

One item in full: kind, status, rating and score, owner, due date, links, who raised it and, once closed, when and why. Beneath are the sections for linking repository elements, updating, closing and commenting.

Architects, the person who raised the item and its owner can edit it. Anyone who can see it can comment. A closed item can be reopened.

Mitigation, action or dependency

What is being done about the item. For a risk this is how you will reduce or respond to it; for an issue, the action to resolve it; for an assumption or dependency, what it relies on and what happens if that fails. Keep it specific enough that someone else could pick it up. Update it from the Update section as things change.

Repository elements

The applications, technologies or other elements this item affects. Linking them means anyone looking at an element can see the risks against it.

1. Enter an element reference (for example APP-0001) and choose Link.
2. Choose Remove beside an element to unlink it.

Only people who can edit the item see these controls. See An application or technology record.

Update

Change an open item.

1. Edit the title, description, owner, email, due date, mitigation, or the engagement and ARB links.
2. Set the status to Open, In progress or Accepted.
3. For risks and issues, revise likelihood and impact; the score and rating update.
4. Choose Save changes.

Every change is written to the history. To finish with the item use Close it below.

Close it

When an item is resolved or no longer matters, close it.

1. Write how it was resolved, or why it is closed. This is required.
2. Choose Close.

The item leaves the open counts and the heat map but stays in the register, with the reason and date. Choose Reopen if it comes back.

History and comments

A running record on each item. Every change is logged with who and when, so you can see how a rating moved. To discuss the item, write in Add a comment and choose Comment; comments appear in the same list, marked as comments. Anyone who can see the item may comment, even if they cannot edit it.