Nine columns and a Monday morning. What a RAID log can do.

Who this is for

Anyone who runs delivery projects and keeps a RAID log that someone rebuilds by hand before every weekly review.

The problem

Every delivery team keeps a RAID log: actions, risks, issues and decisions. Before every review, someone opens the spreadsheet and rebuilds the picture by hand. What slipped, who owes what, what is waiting on the customer, what changed since last week. Then it gets copied into slides. That work happens every week, on every project, and it tells the team nothing the log did not already know.

What we did

• Started from a standard nine-column log and kept it as it is. No new columns.
• Filled it with 34 invented items for a made-up Workday deployment, in the middle of testing and 105 days from go-live.
• Built the Monday review on top of it. It opens on what to escalate, what is late, what has no owner and what the customer owes, and every number opens the items behind it.
• Kept last Monday's copy of the log and compared the two: what is new, what closed, what moved to the customer, whose due dates slipped, and what was overdue last week and is still overdue now.
• Made the customer-facing status report come from the same rows, in one click, so nothing gets copied into slides.
• Tried to break it three ways before anyone saw it: read the way a senior Workday project manager would, every sentence checked against what the screen actually does, and checked for a phone and a keyboard. Everything found was fixed.

What it would take for you

Bring the thing your team already keeps: the log, the tracker, the sheet that gets rebuilt every week. Not a new platform. We build the review around how your team actually runs, for a fixed price agreed before the work starts. Your data stays where you decide it lives.