PMOpackFree check
Article

What is a RAID log, and how do I keep it honest?

A RAID log is one list of your Risks, Assumptions, Issues and Dependencies, each with an owner, a date and a next action. It stays honest when every open row is touched every period and every closed row says why it closed.

Most RAID logs are honest for about four weeks. Then the project got busy, the log got long, and it turned into a place where worries went to be forgotten. Here is what keeps one alive.

What goes in each column

  • Risk: something that has not happened yet, and would hurt if it did. Needs a chance, an impact, and a plan.
  • Assumption: something you are treating as true without proof. Needs a date by which you will know.
  • Issue: something that has already happened and is hurting now. Needs an owner and a fix date.
  • Dependency: something you need from someone else before you can move. Needs their name and their date, not yours.

Every row gets a real person as owner. Not “TBC”, not “PMO”, not “the vendor”. A name.

The six rules that keep it honest

  1. Open rows get touched every period. If nothing changed, the row says “no change, reviewed on [date]”. Silence is not a status.
  2. A red rating needs a path to green. Problem, plan, date, named owner. A red with no plan is not a red. It is a shrug.
  3. Closed rows say why. “Mitigated”, “happened and became issue 14”, “no longer relevant because scope changed”. A row that just disappears is a question a board will ask later.
  4. Risks that happen become issues. Link them. The risk ID lives on in the issue.
  5. Dependencies carry the other side’s date. If their date slips, your row changes colour.
  6. The log matches the other reports. If the Status Report says “no critical issues” and the RAID log has a red issue, one of them is wrong. Find out which before you issue either.

A short checklist before you issue the log

  • Every open row has a named owner and a date in the future.
  • Every red has a plan with a date.
  • Nothing closed this period is missing a reason.
  • The top five rows are the same top five the Status Report talks about.
  • Nobody has an owner they do not know about.

A real example

On a take-over of a troubled programme, the RAID log had 212 rows. Forty-one were red. Only three had been updated in the last two months. The sponsor was reading a Status Report that said “amber, under control.”

We did not rewrite the log. We went through it row by row with the workstream leads, closed what was dead with a reason, merged what was duplicated, and put a name and a date on what was left. It came down to 38 live rows. Eleven were red, and each had a plan. The next SteerCo was the first in months where the pack and the log said the same thing.

Where PMOpack fits

PMOpack builds the RAID log as one of the artefacts in your reporting pack, from the file you already keep. Its checks will not let an amber or red sit on a status field without a path to green (problem, plan, date, named owner), and a placeholder owner on a decision inside a SteerCo pack, Status Report or Working Group Report is flagged. A critical finding blocks publish until a person fixes the data or accepts it with a written reason, and that acceptance is stored and cannot be edited later. It does not know whether your risk is real. It knows when your log and your Status Report disagree, and it says so.

Questions people ask

What does RAID stand for?
Risks, Assumptions, Issues and Dependencies. One list, each row with an owner, a date and a next action.
How often should I update a RAID log?
Every reporting period. Every open row is touched, even if the update is 'no change, reviewed on this date'.
What is the difference between a risk and an issue?
A risk has not happened yet and might. An issue has happened and is hurting now. When a risk happens, it becomes an issue and the two rows are linked.
Can a red risk have no plan?
It should not. A red needs a path to green: the problem, the plan, a date and a named owner. Without those it is a worry, not a managed risk.

See the checks on your own pack.

We are working with a small group of delivery professionals to prove the reporting journey on real work. One active workspace per person.

Or email [email protected]

For people who run project reporting for a living. Not for students, personal projects or coursework. We read every request and reply to those who fit.

Want to know where your data goes and who can see it? Read the Trust page.