Raid Log Template

---
title: "Raid Log Template"
methodology: "traditional"
complexity: "advanced"
owner: "mirichard"
updated: "2025-08-05"
primary_principles: ["risk-optimization", "systems-thinking"]
secondary_principles: ["stewardship"]
principle_rationale: "Distinguishes risks, assumptions, issues and dependencies while assigning owners, reviews and escalation across related records."
---

# RAID Log Template

## When to Use

- During planning and execution when risks, assumptions, issues, and dependencies need coordinated tracking.
- When each record type needs an owner, review, and escalation path.

## When NOT to Use

- To mix actual issues and uncertain risks without distinguishing their response needs.
- Do not use a completed template or example configuration as proof of fitness for the actual environment. See [Template as substitute for judgment](../../../../../../docs/principles/anti-patterns.md#template-judgment).

## Pairs Well With

- [Issue Log Template](../../../../../../domains/delivery/templates/traditional/Traditional/Templates/issue_log_template.md).
- [Risk Register Template](../../../../../../domains/uncertainty/project-lifecycle/02-planning/risk-management/risk-register-template.md).

Selection context: Delivery domain; traditional methodology; advanced complexity. Match the situations above to project phase, risk, team size, and industry using the [decision-engine context model](../../../../../../meta/architecture-research/800-801-context-assessment-model.md).

## Document Information

| Field | Details |
|-------|---------|
| **Project Name** | [Insert Project Name] |
| **Project Manager** | [Insert PM Name] |
| **Document Version** | 1.0 |
| **Last Updated** | [Insert Date] |
| **Review Frequency** | Weekly |

---

## Overview

The RAID Log is a consolidated project management tool that tracks four critical project elements:
- **Risks** - Potential future problems that may impact the project
- **Assumptions** - Things we believe to be true but haven't verified
- **Issues** - Current problems that need immediate attention
- **Dependencies** - External factors the project relies on

---

## How to Use This Log

1. **Review weekly** during team meetings or status reviews
2. **Assign owners** for each item to ensure accountability
3. **Update status** regularly and close items when resolved
4. **Escalate** high-priority items to project sponsor/steering committee
5. **Archive** closed items for lessons learned

---

## RISKS

| ID | Risk Description | Probability | Impact | Risk Score | Mitigation Strategy | Owner | Status | Date Identified | Target Resolution |
|----|------------------|-------------|--------|------------|-------------------|-------|--------|------------------|-------------------|
| R001 | [Risk description] | High/Med/Low | High/Med/Low | [P×I] | [How to prevent/reduce] | [Name] | Open/Closed | [Date] | [Date] |
| R002 | | | | | | | | | |
| R003 | | | | | | | | | |

### Risk Scoring Guide
- **High**: 3 points
- **Medium**: 2 points  
- **Low**: 1 point
- **Risk Score**: Probability × Impact (Max score = 9)

---

## ASSUMPTIONS

| ID | Assumption Description | Validation Required | Owner | Status | Date Added | Validation Date | Notes |
|----|----------------------|-------------------|-------|--------|------------|----------------|-------|
| A001 | [What we're assuming to be true] | Yes/No | [Name] | Open/Validated/Invalid | [Date] | [Date] | [Additional info] |
| A002 | | | | | | | |
| A003 | | | | | | | |

### Assumption Status Guide
- **Open**: Not yet validated
- **Validated**: Confirmed to be true
- **Invalid**: Proven false - may become risk or issue

---

## ISSUES

| ID | Issue Description | Priority | Impact | Owner | Status | Date Raised | Target Resolution | Resolution Notes |
|----|------------------|----------|--------|-------|--------|-------------|-------------------|------------------|
| I001 | [Current problem description] | High/Med/Low | [Impact on project] | [Name] | Open/In Progress/Resolved | [Date] | [Date] | [How it was resolved] |
| I002 | | | | | | | | |
| I003 | | | | | | | | |

### Issue Priority Guide
- **High**: Project timeline or budget significantly impacted
- **Medium**: Minor impact, workaround available
- **Low**: Minimal impact, can be resolved in normal course

---

## DEPENDENCIES

| ID | Dependency Description | Type | External Party | Required Date | Status | Owner | Notes |
|----|----------------------|------|----------------|---------------|--------|-------|-------|
| D001 | [What we're waiting for] | Internal/External | [Who provides it] | [When we need it] | Not Started/In Progress/Complete/Blocked | [Name] | [Additional details] |
| D002 | | | | | | | |
| D003 | | | | | | | |

### Dependency Types
- **Internal**: Within our organization/team
- **External**: Outside organization (vendors, partners, etc.)

---

## Summary Dashboard

### Current Status Overview
- **Open Risks**: [Count] (High: X, Medium: Y, Low: Z)
- **Unvalidated Assumptions**: [Count]
- **Open Issues**: [Count] (High: X, Medium: Y, Low: Z)
- **Pending Dependencies**: [Count]

### This Week's Actions
- [ ] [Action item 1]
- [ ] [Action item 2]
- [ ] [Action item 3]

### Escalation Required
- [List any items that need sponsor/steering committee attention]

---

## Review History

| Date | Reviewed By | Key Changes | Next Review Date |
|------|-------------|-------------|------------------|
| [Date] | [Name] | [Summary of changes] | [Date] |

---

## Instructions for Team

### Adding New Items
1. Assign unique ID (R for Risk, A for Assumption, I for Issue, D for Dependency)
2. Fill in all required fields
3. Assign to appropriate owner
4. Set realistic target dates

### Updating Items
1. Change status as progress is made
2. Add notes to track progress
3. Update target dates if needed
4. Close items when fully resolved

### Weekly Review Process
1. Review all open items
2. Update status and progress
3. Identify new RAID items
4. Escalate high-priority items
5. Archive completed items

---

*This RAID Log should be maintained as a living document throughout the project lifecycle.*