Education Programme RAID Log
This is a practical guide to building a raid log for an education programme project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of delivering an education or training programme.
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 an education programme project it plays the same role, tuned to this kind of work.
Why it matters for an Education Programme project
Education Programme projects live or die on delivering an education or training programme. 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 education programme projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Education Programme-specific considerations
Tailor the raid log to the risks that most often derail education programme projects:
- Stakeholder diversity
- Academic-calendar windows
- Limited budgets
Example
On a real education programme project, the raid log would be shaped by delivering an education or training programme. In particular, it should explicitly account for the project’s biggest risks — stakeholder diversity, academic-calendar windows, limited budgets — rather than treating them as afterthoughts.