In the complex world of project management, keeping track of potential issues, uncertainties, and dependencies is essential for delivering projects on time and within budget. That’s where the RAID log comes in — a simple yet powerful tool that helps project managers control and communicate risks, assumptions, issues, and dependencies throughout the project lifecycle.asfsadfaf
In this blog, we break down what RAID stands for, why each component matters, how to build and use a RAID log, and how it enhances governance, visibility, and decision-making.
RAID is an acronym that represents four key categories of project control:
| RAID Element | Description |
|---|---|
| R – Risks | Potential events that could affect project success if they occur. |
| A – Assumptions | Things believed to be true at the time of planning but not yet confirmed. |
| I – Issues | Current problems that are impacting the project right now. |
| D – Dependencies | Tasks, decisions, or events that the project depends on, or that depend on it. |
These elements form the core of a RAID log — a central register that project teams and sponsors use to maintain awareness and control over project conditions.
Definition: Future events that may have a positive or negative impact on the project.
Examples:
Potential delay in vendor delivery.
Scope creep due to unclear requirements.
Opportunity to use a new tool that could speed up development.
A risk log includes: