Login

RAID Log Analysis

A project-management format that puts the spotlight on what could derail delivery. The team logs its risks, the assumptions it's relying on, the issues already in play and the dependencies on other teams or systems. Reviewing all four regularly keeps surprises to a minimum and makes planning conversations far more grounded.
Risks
Assumptions
Issues
Dependencies
Try Template

What is a RAID Log Analysis?

A RAID Log Analysis is a project management session that captures everything threatening or shaping delivery in four buckets: Risks, Assumptions, Issues and Dependencies. Reviewing them together gives the team a clear, shared picture of what could go wrong and what is already in the way. The QRetro template lays out one column per category.

  • Risks — potential future events that could hurt the project.
  • Assumptions — things taken as true but not yet verified.
  • Issues — problems happening right now.
  • Dependencies — external factors the work relies on.

Risks

Risks are events that have not happened yet but would have an impact if they did. Capture each with its likelihood, potential impact and a mitigation idea so the team can prioritize the ones worth acting on.

Assumptions

Assumptions are beliefs the plan quietly depends on. Writing them down exposes hidden bets; if an assumption later proves false, it often becomes a risk or an issue, so revisit this column regularly.

Issues

Issues are problems affecting the project today. Each card should name the issue, its current impact and an owner, so nothing active is left without a clear next step.

Dependencies

Dependencies are the people, teams, tools or deliverables your progress relies on. Tracking them prevents surprises when an external party slips and helps you plan around critical handoffs.

Benefits of a RAID Log

  • Gives the team one shared view of project health.
  • Separates future threats from problems already in play.
  • Makes silent assumptions explicit and testable.
  • Highlights external dependencies before they block delivery.
  • Creates a living record you can review at every milestone.
  • Speeds up escalation and ownership decisions.

How to run a RAID Log Analysis

  1. Create a board in QRetro using the RAID Log Analysis template.
  2. Invite the team and brainstorm cards into each of the four columns.
  3. For every risk and issue, add impact, likelihood and an owner.
  4. Challenge assumptions and flag any that look fragile.
  5. Map dependencies to dates and external contacts.
  6. Prioritize the log, assign actions and schedule the next review.
Try Template