Workshop · Project kickoff
Risks, assumptions, issues and dependencies on one live board, reviewed in a tight 20-minute weekly meeting with owners and escalations.
Free to open and edit. Running it live needs Pro, free for 14 days on every new account.
A RAID log tracks a project's risks, assumptions, issues and dependencies in one place. This template puts the four lists on a live board the team updates from their phones, with a Closed column, and a 20-minute weekly review agenda that checks last week's actions, adds new items and escalates what the team can't solve.
01Inside
RAID log with 5 areas, and a 20-minute agenda that runs it.
“Add a new risk, assumption, issue or dependency: what it is, the impact and who owns it”
By the end of this meeting, every open item has an owner and a next step, and anything we can't solve ourselves is escalated.
02In the room
The shared screen, every phone and the summary afterwards, drawn from this template.
On the shared screen
Ideas land on the board from every phone, with no names on the notes. Then everyone dot-votes what matters most.
On every phone
People scan the code or tap their invite and answer in the phone's browser. No app to install, no account to make.
Afterwards
Decisions and actions are captured as they're said. When the meeting ends, everyone gets the summary, and one link shares it.
03How to run it
Keep the same board every week; Closed cards show progress and the summary keeps the history.
Start with last week's actions, then collect new items from phones in five minutes.
Talk about issues first, then only the risks and dependencies that changed. Don't re-read the whole log.
End with escalations and owners. If the meeting runs over 20 minutes, the log is too long; split it by workstream.
04Questions
Still deciding?
Run your next meeting on it. Every new account gets Pro free for 14 days, no card.
A project management log of Risks (might happen), Assumptions (believed true but unproven), Issues (happening now) and Dependencies (things you're waiting on). Some teams use the D for Decisions instead.
A risk register tracks only risks, usually with likelihood, impact and responses. A RAID log is broader and also covers assumptions, issues and dependencies.
A short description, the impact, the date raised, an owner, the next action with a due date, and the status. Close issues when they're resolved, don't delete them.
Weekly for most projects, in a short meeting. Review the full log at major milestones or phase gates.
The structure, wording and safety points in this template follow these published sources.
Keep going
Change anything in the editor. When you're ready, press Run live: everyone joins with a scan and answers on their phone.
Free forever · Pro free for 14 days · No card needed · Guests never sign up
RAID log reviewRuns with Pro