Conference Planning Work Breakdown Structure
This is a practical guide to building a work breakdown structure for a conference planning project — a deliverable-oriented decomposition of the whole scope into manageable work packages, adapted to the realities of organising a conference.
What a Work Breakdown Structure is
A work breakdown structure is a deliverable-oriented decomposition of the whole scope into manageable work packages. For the full concept and how it works in general, see Work Breakdown Structure. 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 work breakdown structure 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
- Top-level deliverables
- Sub-deliverables
- Work packages (8–80 hours)
- WBS numbering
- WBS dictionary entries
Conference Planning-specific considerations
Tailor the work breakdown structure 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 work breakdown structure 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.