Education Programme Issue Log
This is a practical guide to building a issue log for an education programme project — a register of problems that have occurred and need resolving, adapted to the realities of delivering an education or training programme.
What a Issue Log is
A issue log is a register of problems that have occurred and need resolving. For the full concept and how it works in general, see Issue 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 issue 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
- Issue description
- Priority and severity
- Owner
- Resolution and status
Education Programme-specific considerations
Tailor the issue 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 issue 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.