FigJam
Track your project’s progress from start to finish with a RAID log template

From every step of the project planning process to ensuring its timely completion, use FigJam’s workflow process templates to help you get the job done.

RAID log exampleRAID log example

RAID log template

Track and manage risks, actions, issues, and dependencies for every project, with contributions from every project team member.

Identify the best plan of attack

Ensure your next project goes smoothly by mitigating potential threats and capitalizing on opportunitiesa with a project raid management tool.

Keep track to stay on track: Record the project’s risks, actions, issues, and dependencies to stay one step ahead.

Organize meeting information: Keep your regular project meetings brief and organized by quickly referencing the different areas of a project.

Align with your allies: Share status updates with your team and re-strategize as necessary.

RAID template with FigJam's collaboration toolsRAID template with FigJam's collaboration tools
magnified section of raid templatemagnified section of raid template

FigJam
Alert your team to what’s coming next

Develop detailed RAID log templates to share at your next project meeting with managers and key stakeholders. Use FigJam’s Stark widget to create role-specific checklists, use poll responses and emotes to solicit feedback, and generate priority matrices that keep everyone informed and aligned.

No issues here—just action

Don’t risk it! Keep a close eye on every detail of your project. Take advantage of FigJam’s other templates to organize your decisions every step of the way.

FAQs

A RAID log is a tool that helps teams prepare for a project, whether that’s a product launch, software development, or marketing campaign. By tracking risks, actions, issues, and dependencies, you can stay up to date about potential problems or roadblocks and solve them as a team.

The RAID acronym stands for risks, actions, issues, and dependencies. As a team, you’ll brainstorm any possible project risk that may disrupt or derail the process and their likelihood of materializing. The more risks you identify at the onset, the more response plans you can create and employ when necessary.

You or other team members take actions while the project is in motion. If a predicted risk rears its ugly head, you can include the risk response actions your team would take to correct the issue, including who’s responsible and the timeline for completion.

It’s essential to identify issues, which are triggered risks, project restraints or other problems. You’ll want to record what happened, who fixed it, and how.

Lastly, include the dependencies that will allow you to complete the project as planned. These are factors, outcomes, or situations that your process depends on, whether that’s data input, a particular task completed by another department, or an external event that prompts something internally.

In project management, RAID log examples are used to plan ahead and stay on track for success. In addition to creating the log before the project begins, you can use it throughout to assess your progress, change course as needed, and as evidence for stakeholders who like to keep an eye on internal development.

Get started with templates

Design sprints

Explore 1,000+ templates on the Figma community

Explore even more templates, widgets, and plugins—all built by the Figma community.

Figma communityFigma community