R. Risks

<aside> 💡 • Risks are anything that may have a positive or negative impact on your project if they happen. • Risks are evaluated on the likelihood the events will happen times the impact on the project if they do happen. • If the likelihood of the event happening and impact on the project are both high, identify the event as a serious risk. • In the log, capture your plan to address the risk (mitigation plan), who will address it (owner), where they are in the process (status), and when the issue was closed.

</aside>

RAID Log: Risks

A. Assumptions

<aside> 💡 • An assumption is anything you and your team believe will be in place that will contribute to the successful outcomes of your project. • In the log you'll include a description of the assumption and where the assumption comes from (reason) • You'll also capture what you need to do in order to confirm the assumption (action to validate), and any important impacts if the assumption is valid (impact).

</aside>

RAID Log: Assumptions

I. Issues

<aside> 💡 • An issue is something that is going wrong on your project that you need to address. • You'll document a description of each issue, the impact it is having on the project , the severity of the impact (impact), its seriousness (priority) and actions to eliminate it (mitigation plan).

</aside>

RAID Log: Issues

D. Dependencies

<aside> 💡 • A dependency represents any event or work that are either dependent on the result of your project, or that your project will depend on. • You'll document who or what you are dependent on (or who or what is dependent on you), what they should deliver (deliverable) and when (delivery date).

</aside>

RAID Log: Dependencies