RAID Logs: Your Project's Secret Weapon
(In Case You Missed the Series)
We’ve summarised RACIs and provided examples. Before that we detailed RAIDs. Since RACI and RAID sound so similar (and can both be used for project and operations management), it’s worth showing how they work side by side:
🧩 RACI = Defining the Work
Use a RACI matrix to define tasks and processes - who’s Responsible, Accountable, Consulted, and Informed.
It helps your team stay aligned, prevents things from slipping through the cracks, and minimises arguments over ownership.
(It’s always awkward when you’re the witness to that one…)
💥 RAID = Managing the Chaos
Use a RAID log to capture and handle all the stuff that might - or has already - gone wrong.
If you’ve ever found yourself firefighting, confused about why something’s delayed, or feeling like your project has gone rogue… this is your sign to start using one.
Here’s what we covered in the full series:
💥 What is a RAID Log?
RAID stands for:
Risks - things that might happen
Assumptions - things you’re treating as true (but haven’t confirmed)
Issues - things that are happening now and need fixing
Dependencies - things that need to happen before something else can move
We kicked things off with a full breakdown of what a RAID log is and why it’s more than just “project admin.”
☁️ Risks: What Might Go Wrong
Risks aren’t just things to list - they need owners, mitigation plans, and attention.
Bonus: Not all risks are bad. Some are opportunities in disguise.
💡 Assumptions: The Invisible Gremlins
Assumptions are the unconfirmed truths your plan quietly relies on.
If they turn out to be wrong? They become risks, or worse, issues.
⚠️ Issues: What’s Happening Right Now
The key difference between a risk and an issue?
Risks = might happen.
Issues = are happening now.
🁢 Dependencies: What You’re Waiting On
“If I can’t start until they finish” - that’s a dependency.
We explored how dependencies relate to critical path, blockers, and timeline delays.
🚀 So what now?
Start small. Choose one project and build a simple, living RAID log.
Update it weekly. Mention it in your stand-ups.
Make it normal. Then roll it out across more teams or projects.
🛠 Where should you track RACIs & RAIDs?
RACIs can live happily in:
Word docs
Spreadsheets (ideal if you want filters or formatting)
Notion or similar lightweight tools
(You can use tools like Asana - and of the lot, Asana’s visual layout works best - but keep it simple.)
RAID logs, on the other hand, thrive in Project & collaboration software
If you use Asana, ClickUp or Monday, which should hold all your projects of work and tasks, this means that you can in one place tag those as risks, issues, assumptions or dependencies directly in tasks, and generate reports across all projects.
Suddenly, you’ve got business-wide visibility with a single click.
👋 Need help?
If you’re ready to bring structure to the chaos, that’s literally what we do.
📩 Book a free 30-minute call and let’s turn your firefighting into forward planning.