All resources
Template or tool

RAID Log (Risks, Assumptions, Issues, Dependencies)

One workbook for risks, assumptions, issues and dependencies, with probability-impact scoring, residual risk, overdue flags and an automatic RAID summary.

Free

Free Excel workbook. One workbook for risks, assumptions, issues and dependencies, with probability-impact scoring, residual risk, overdue flags and an automatic RAID summary. Download it, add your project details and use it today: no sign-up for software, no paywall.

A complete RAID log for project and program managers. The Risks sheet uses a five-by-five probability and impact matrix to score and rate each risk, records response strategy, contingency and early-warning triggers, and tracks residual risk after your response. Assumptions carry a confidence level and a validate-by date, Issues calculate days open and flag late resolutions, and Dependencies compare need-by and committed dates to give a RAG status. The Summary rolls everything into the numbers a steering committee needs. Designed for ERP and IT programs and consistent with standard PMI risk response terminology.

What's inside

  • Risks: Uncertain events that could affect objectives. Score = Probability x Impact (1-25): High 15+, Medium 8-14, Low 1-7.
  • Assumptions: Things taken as true for planning. Validate each one by a date or convert it to a risk.
  • Issues: Problems happening now that need action. Days open and lateness calculate automatically.
  • Dependencies: What the project needs from others, or others need from it. Negative slack means the commitment is too late.
  • Summary: key numbers calculated automatically from your data
  • Drop-down lists, worked example rows and formulas you can rely on

How to use it

  1. Agree the scoring scale with your sponsor: what a 5 for impact means in cost, schedule and quality on this project. Write it in your project management plan.
  2. Write each risk as cause - event - effect, so the response targets the cause. Score probability and impact; score and rating calculate automatically.
  3. Choose a response strategy, define actions, a fallback and an early-warning trigger, then estimate residual probability and impact after the response.
  4. Log assumptions with a validate-by date. When one proves shaky, set it to 'Converted to risk' and add the matching risk ID.
  5. Move a risk to 'Occurred' when it happens and raise it on the Issues sheet with a priority and target resolution date.
  6. Record dependencies with need-by and committed dates. Negative slack turns Red and should be raised at the next status meeting.
  7. Review the log weekly with owners and bring the Summary to the steering committee.

Who it's for

Project and program managers, PMP candidates, PMOs and delivery leads.

Let's connect

I'm Pranshu Shubham, a Microsoft Dynamics 365 F&O Solution Architect and PMP-certified program lead with 8+ years of ERP and AI transformation across the USA, Europe and APAC. I created this resource from real project experience, and I'd love to hear how you use it.