(upbeat music) Let's discuss what is and is not a risk, how to identify risks, and how to document known risks. These first steps are instrumental in making sure everything ultimately runs smoothly. We'll explore how to confidently identify, categorize, and document risks so you can be confident that you have a comprehensive list of risks to address. When should you perform risk identification for your project? If you said this should happen at the beginning of the project, you'd be partly right. Most risk identification is done during the planning stage of the project management life cycle. There are several reasons for that. The first is that you have the entire project in front of you so this is the point of the life cycle where all risks are still in play. The second reason is because the earlier you identify a risk in the project life cycle, the less impact it will have on the project itself. Consider when most risks occur since that's when the larger number of unknowns exists. In most cases, this is in the concept and development stages. As you move through the project, the number of risks will decrease because you'll close any risk that is no longer relevant. Think about the example of building a house. Is too much rain going to impact the project once the building is under a roof? Probably not. However, any risk you incur as part of the latter stages of the project will have a greater impact on the project as a whole. Risks that occur earlier can be mitigated and adjustments in the project plan could happen. The later you get into the project, any risk that occurs may require significant work to remedy. So let's revisit the initial question of when you identify risk. As you recall, most of the risk identification process is done in the beginning of the project. However, risks can be identified at any point within the project. The key is that when anyone identifies a risk, it should follow the same process as the risks identified in the planning stage. This brings us to a final question about risk identification, who can identify risks in a project? The answer is simple. Any stakeholder, regardless of influence, impact, or involvement in the project can raise a risk. If you're a stakeholder in a project and see something that may be a risk, you may be obligated to raise this concern through the appropriate channels.