While you deliver
RAID Log Analyzer
Read a RAID log the way a careful reviewer would: what has no owner, what is past due, what nobody has touched, what is written twice, and what is filed under the wrong letter.
Read a .xlsx or .csv RAID log, or any single log of risks, issues, actions or decisions, inside your browser. Nothing is uploaded.
RAID log
Drop a spreadsheet here
One row per item. A type column (R, A, I, D or the words), plus whatever you keep: owner, status, dates, priority.
What a RAID log review looks for
Every open item should have one named owner, a date, and an update more recent than last month. The tool checks each of those, and treats “TBD”, “TBC” and “n/a” as the blanks they are. It lists owners shared between two people or given to “All” separately, because an item everyone owns is one nobody chases. Due dates that have moved are counted from an original due date column, if the log keeps one.
The same log, written several ways
Logs kept by several people drift. “In Progress”, “In-progress” and “WIP” are one status to a person and three to a filter, so every count taken from the file is quietly wrong. The tool reads them as one, shows each spelling it found, and lets you change how any status is counted. Owners are matched the same way, so “Shah, Priya” and “Priya Shah” share one row.
What the letters mean
RAID stands for risks, assumptions, issues and dependencies in some organizations, and for risks, actions, issues and decisions in others, so a bare A or D in the type column is ambiguous. The tool reads the wording of the items that carry each letter (“agreed to” sounds like a decision, “waiting on” like a dependency), says which way it went and why, and lets you override it.
Filed under the wrong letter
A risk is something that might happen; an issue is something that has. A risk written as “the test environment has been down since Tuesday” is an issue being managed as a possibility. The tool flags wording that points one way when the item is filed the other, and flags actions worded as activities with no finish line (“look into”, “follow up”). These are prompts for the owner of the log, never a reclassification.
Decisions
Decisions with no date, no one who made them, or no rationale; decision requests still open after the date they were needed; and decisions superseded by a later one (“supersedes D-03”) whose status was never changed, so the log still offers both as current.
What this does not do
It does not judge whether a risk is scored correctly or a response is adequate; the Risk Register Scorer looks at scoring. Wording checks are pattern matches on English phrasing and will miss some items and question a few that are fine. It reads one version of the log, so it sees a due date moved only through an original due date column.