RAID is a [project management](https://www.masterclass.com/articles/project-management-guide) technique that assesses the risks (R), assumptions (A), issues (I), and dependencies (D) of a project. The project manager completes the assessment in the project planning phase in consultation with the project team and its stakeholders. The project manager then records the analysis in a project document, also known as a RAID log. The project manager then monitors the RAID log throughout the lifecycle of the project.\nRAID is an acronym for risk (R), assumption (A), issue (I), and dependency (D).\n\n- __Risk__: A [risk](https://www.masterclass.com/articles/how-to-take-risks) is any potential event that may adversely impact the project or delay the project timeline. The project manager’s job is to assess and identify project risks and mitigate risks if they occur. \n- __Assumption__: An assumption is a factor in the project that is assumed to be true. Project assumptions are hypothetical, so if they are true, the project will proceed as planned. If assumptions turn out to not be true, the project manager has to craft a workaround.\n- __Issues__: An issue is a problem that the project currently has that the team must resolve before proceeding. \n- __Dependency__: A dependency is a project task or deliverable required to happen before another phase can begin. The project manager needs to identify and track the dependencies and ensure things are on schedule to proceed smoothly.\nRAID analysis is essential because it can help a project manager predict any problems that might arise and prepare the project team for handling setbacks. A RAID log can keep a project on track and help prevent delays.\nA RAID document is a method for tracking the details and deadlines of a project. You do not need special project management software to create a RAID log; a simple spreadsheet will do. Follow these steps to develop and use a RAID log:\n\n1. __Set up an audit meeting__. Invite all of the project team members and stakeholders to a project audit meeting. \n2. __Identify risks, assumptions, issues, and dependencies__. Go through each component of the RAID acronym and ask participants to identify potential risks, assumptions, issues, and dependencies.\n3. __Create a RAID log__. Open a spreadsheet and add a description of each RAID item, the likelihood of it happening, the severity of impact, and the team member assigned to the risk mitigation plan. You should also log any deadlines and dates where you expect to address issues. You can also use multiple worksheets for the RAID log and organize the items based on how critical they are to project success.\n4. __Share the information__. Distribute the RAID document to all team members, stakeholders, and anyone involved in decision-making on the project. \n5. __Check-in on the RAID log__. Consult the RAID log periodically throughout the project life cycle, especially if there are any deadlines to follow. Schedule time to check the RAID document to make sure the project is on track and use it to address issues promptly.\nGet the [MasterClass Annual Membership](https://www.masterclass.com/) for exclusive access to video lessons taught by business luminaries, including Sara Blakely, Chris Voss, Robin Roberts, Bob Iger, Howard Schultz, Anna Wintour, and more.\nLearn how to use the RAID project management technique and create a RAID log to keep a project on track.