USM Content
This section will explore how to effectively use RAID logs to track and manage critical project elements.
RAID Logs
USM Content
A RAID Log is a project management tool that tracks and manages four critical aspects of a project: Risks, Actions, Issues, and Decisions. It serves as a repository for project managers and teams to monitor and address potential problems, tasks, and decisions that could impact the project’s success. The primary purpose of a RAID Log is to record, review, and manage critical elements that influence your project. RAID Logs help minimize risks, ensure actions are completed, address issues promptly, and document decisions clearly for future reference.
Overview of Risk, Action, Issue, and Decision Components:
- Risks: Potential events or conditions that could negatively affect your project. Start building your RAID log by identifying these risks and entering a description in the RAID Log. For each risk, assign an owner responsible for managing it, set a priority (high, medium, or low), and note its current status (e.g., open, closed). Include a due date for mitigation efforts and note the actions needed to reduce or eliminate the risk.
- Actions: You must complete actions to ensure the project remains on track. Document each action in the RAID Log, including the person responsible, priority level, status, and expected completion date.
- Issues: Challenges that have already occurred and require immediate resolution to prevent further project impact. Use the RAID Log to describe each issue, assign it to a team member, categorize its priority, and update its status. Include the due date for resolving the issue and note the steps you will take to fix the problem.
- Decisions: Critical choices made during the project can affect its direction or outcome. You should record decisions in the RAID Log. Decisions should include relevant details such as who made them, the context in which they were made, and any actions or consequences resulting from them.