Event Management Decision Log
This is a practical guide to building a decision log for an event management project — a record of the key decisions made, by whom and why, adapted to the realities of planning and delivering an event.
What a Decision Log is
A decision log is a record of the key decisions made, by whom and why. For the full concept and how it works in general, see Decision 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 decision 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
- Decision
- Date and owner
- Rationale
- Alternatives considered
- Impact
Event Management-specific considerations
Tailor the decision 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 decision 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.