A RAID Log tracks four types of project information: Risks, Assumptions, Issues and Dependencies. Keeping them on separate worksheets helps teams distinguish potential events from existing obstacles, unverified premises and work that depends on another party. This workbook is designed for recurring project reviews and explicit decisions; it does not automate forecasting or replace professional risk assessment.

What a RAID Log is for

A risk is an event that could occur in the future. An assumption is an unverified premise in the plan. An issue has already happened or is currently blocking progress. A dependency is a deliverable or input needed before another task can proceed.

The log provides a shared reference for project managers, PMOs and workstream owners ahead of status reviews. Each entry should have a named owner, a review date and a practical next action.

• Separate possible events from issues already happening.
• Assign accountability and review dates to open items.
• Capture decisions in the context of ongoing project governance.

Worksheets and available fields

The workbook includes Project Overview, Risks, Assumptions, Issues, Dependencies and Dashboard. Each working log includes an ID, owner, status and review date.

Risks include probability, impact, response actions and an early warning indicator. Assumptions record how a premise will be validated, Issues track next actions and decisions, and Dependencies identify predecessor work and blocking conditions.

• Project Overview: project name, manager, sponsor and last updated date.
• Risks: description, probability, impact, owner, response and status.
• Assumptions, Issues and Dependencies: separate lists designed for their own follow-up actions.
• Dashboard: status counts calculated from the Risks worksheet.

Worked example: CRM rollout

The filled example describes a regional CRM implementation. Risk R-01 is a possible delay in customer data migration. It has High probability and impact, an IT Lead as the owner, a trial migration as a response and a review date of November 2, 2026.

Issue I-01 is different: approval for CRM API access is already missing and needs an immediate action. Assumption A-01 requires validation of customer data readiness, while Dependency D-01 requires an integration team deliverable. These four items demonstrate why a RAID Log should not be treated as one generic risk list.

• R-01 represents a potential future event.
• I-01 represents an existing issue requiring action.
• A-01 represents an assumption that needs evidence.
• D-01 represents a predecessor dependency.

How the dashboard formulas work

The Dashboard uses standard Excel COUNTIF formulas to count risk entries by the status labels Open, In Progress and Closed. The formula references the Status column in the Risks worksheet and can update after Excel recalculates the workbook.

Probability and impact are selected manually. The workbook does not automatically calculate numerical risk priority, predict delivery dates or derive a critical path. Organizations should apply their own assessment scales where needed.

• Choose statuses from the configured dropdown lists.
• Keep the Risks worksheet name or update affected references if you rename it.
• Check that formulas recalculate after bulk edits.

Governance tips and common mistakes

A good RAID review focuses on items that changed, upcoming review dates and decisions awaiting attention. Keep owners accountable for factual updates instead of treating the file as a static weekly report.

One common mistake is to keep treating a risk as a future possibility after it has materialized. Record the active obstacle as an issue and retain a cross-reference to the original risk where appropriate.

• Write clear descriptions and observable warning indicators.
• Assign a single owner for keeping each record current.
• Close entries only when the outcome and decision are confirmed.

What's included in the Excel template

An editable XLSX workbook is available in English. A separately prepared filled example shows realistic records without changing the blank template. Project Overview prints in portrait orientation; wider registers use landscape with paper size selected to fit their columns.

The workbook is intended for maintaining a working RAID register in Excel. Separate Word or PDF editions are not needed: wide tables, status fields and formulas are more practical in a spreadsheet.

• Blank template and filled example are separate files.
• Six worksheets cover project overview, four RAID areas and a dashboard.
• Filters and dropdown status options support regular project reviews.

How to use this template

1. Download the XLSX workbook and enter the project name, manager, sponsor and date in Project Overview.
2. Add records to Risks, Assumptions, Issues and Dependencies according to what each item represents.
3. Give every record a unique ID, clear description, accountable owner and review date.
4. For risks, assess probability and impact manually and document the response and early warning indicator.
5. Use Dashboard to review risk status counts and recalculate workbook formulas when appropriate.
6. At recurring reviews, update owners and actions and close only items with confirmed outcomes.
7. Use the separate filled example workbook to see realistic records before entering your own.

Download and start using the template Project RAID Log

Download a ready-made template and use it in your project without lengthy preparation. The format is optimized for quick edits, clear structure, and professional presentation. Suitable for both IT projects and classical PMBOK management.

Filled example

See how the template works with sample data before adapting it to your project.

Download filled example XLSX

Want to adapt the document to your processes? Contact us and get a personal consultation from an expert in project management.

Book Consultation