Conference Planning RAID Log
This is a practical guide to building a raid log for a conference planning project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of organising a conference.
What a RAID Log is
A raid log is a consolidated log of Risks, Assumptions, Issues and Dependencies. For the full concept and how it works in general, see RAID Log. On a conference planning project it plays the same role, tuned to this kind of work.
Why it matters for a Conference Planning project
Conference Planning projects live or die on organising a conference. A well-built raid log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how conference planning projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Conference Planning-specific considerations
Tailor the raid log to the risks that most often derail conference planning projects:
- Speaker and agenda logistics
- Registration and venue
- Budget control
Example
On a real conference planning project, the raid log would be shaped by organising a conference. In particular, it should explicitly account for the project’s biggest risks — speaker and agenda logistics, registration and venue, budget control — rather than treating them as afterthoughts.