RAID PROJECT MANAGEMENT TEMPLATE HOW TO
RAID PROJECT MANAGEMENT TEMPLATE DOWNLOAD

You can use this template to document risks, assumptions, issues, and dependencies.

RAID PROJECT MANAGEMENT TEMPLATE DOWNLOAD

We’ve included a download of a RAID log template in Microsoft Excel (you'll need to be a member to get the template). In addition to documenting risks, a RAID log also includes assumptions or actions, an issues log, and dependencies or decisions.

The difference is that a RAID log is more comprehensive. RAID logs may be confused with risk registers or risk logs as there is some overlap between the two. To avoid circular thinking over the course of a lengthy engagement, I’d recommend documenting decisions in your RAID log in addition to dependencies. In my experience, no one ever remembers why decisions were made specifically, the alternatives considered but rejected and the reasons why. If you’d like to keep your RAID log geared towards a senior audience, I’d recommend keeping action items in a separate document focused on tactical execution. I can’t tell you how many times having a list of assumptions stopped scope creep in its tracks.

RAID PROJECT MANAGEMENT TEMPLATE HOW TO

Here are my hot takes on how to approach these in your RAID log: You’ll see that the definition of RAID includes some dual acronyms: assumptions or actions, dependencies or decisions. Table showing the definition of each component of the RAID acronym, along with supporting examples. Decision: build in-house talent management system to maintain focus on high-performance culture, even though this will be more costly in the short-term Dependency: conduct alternatives analysis prior to procuring new vendor management system List activities that cannot be started or completed without another activity being started or completed document previously agreed upon courses of action and the rationale for pursuing or failing to pursue them A security breach compromises the integrity of customer dataĭependencies or Decisions.

Document events that have occurred that impact project progress and explain the path to resolution Action: engage with finance team for a cost breakdown of existing third party suppliers Assumption: required resources are available to execute project work

Document project parameters to prevent scope creep maintain a “to do” list based on ongoing project work Inclement weather delays data collection scheduleĪssumptions or Actions. Identify and categorize risks and opportunities, their probability of occurrence, their impact/severity should they occur, and the mitigation plan and actions Let’s define each of the components of the RAID acronym, along with a few practical examples to help you contextualize. When executed well, a RAID log can act as a key strategy document for summarizing project health at the leadership level. A RAID log is a project document that summarizes the following key pieces of information:Īs a project manager, you can use a RAID log to keep your stakeholders-and yourself-straight on the latest project deets. In case you’re having trouble keeping track of the many tricks of the project management trade, here’s a quick refresher on RAID logs. What Is A RAID Log In Project Management? What Is A RAID Log In Project Management?.Instead of combing through your old meeting notes to find a record of past decisions or wishing you had documented the assumptions behind that pesky requirement that is now giving you grief, a RAID log offers a single repository of project risks, assumptions or actions, issues, and dependencies or decisions that you can quickly share with your stakeholders. What’s a RAID log? Think of it as the solution to your project management organizational woes. We're running our annual salary survey! The data will help project managers worldwide find out if they are being paid what they are worth.

Raid project management template