Event Management Issue Log
This is a practical guide to building a issue log for an event management project — a register of problems that have occurred and need resolving, adapted to the realities of planning and delivering an event.
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 event management project it plays the same role, tuned to this kind of work.
Why it matters for an Event Management project
Event Management projects live or die on planning and delivering an event. 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 event management projects drift into avoidable delay and cost.
What to include
- Issue description
- Priority and severity
- Owner
- Resolution and status
Event Management-specific considerations
Tailor the issue log to the risks that most often derail event management projects:
- Fixed date pressure
- Vendor coordination
- Attendee experience
Example
On a real event management project, the issue log would be shaped by planning and delivering an event. In particular, it should explicitly account for the project’s biggest risks — fixed date pressure, vendor coordination, attendee experience — rather than treating them as afterthoughts.