---
name: event-planning
description: Use when asked to plan a one-off event — a party, offsite, conference, or wedding-adjacent gathering — covering guest list, venue, date, budget, and day-of run-of-show, as distinct from [[travel-itinerary]], which applies similar day-of logistics discipline to a trip rather than an event.
---

# Event Planning

Event planning is the work of organizing a one-off gathering — personal
or professional — from an idea into a specific date, place, guest list,
and timeline that actually comes together on the day. It applies
whether the event is a birthday party, a team offsite, a conference, or
a wedding-adjacent gathering, though scale and formality vary widely.

## Key components

- **Guest or attendee list** — who's invited, and a headcount confirmed
  by a real deadline (an RSVP cutoff), not an estimate carried all the
  way to the event itself.
- **Venue and date** — locked in early, since both constrain nearly
  everything else that follows (see below).
- **Run-of-show / timeline** — the day itself broken into a schedule:
  what happens when, who's responsible for each segment, and when
  transitions (setup, arrivals, program start, meal, teardown) happen.
- **Budget** — tracked against actual vendor commitments as they're
  made, not estimated once at the start and left unchecked until the
  event is over.
- **Vendors and logistics** — catering, venue staff, AV, decor,
  transportation, and anyone else contracted to deliver something on the
  day, each with a confirmed booking, not a tentative hold.

## Why venue and date come first

Nearly every other decision depends on both being fixed. Venue caps the
guest list capacity, catering and vendor options, and available dates;
date determines who can actually attend, which vendors are free, and how
much lead time is left for everything else. Planning invitations, a
budget, or a run-of-show before venue and date are locked produces work
that has to be redone once they're actually confirmed — so settle these
two first, even before other details feel resolved.

## Run-of-show as a shared document

A day-of timeline is only useful if the people executing it — vendors,
co-organizers, a wedding party, volunteers — actually have it in hand.
Write it as a document with real times (not just "morning" or
"afternoon") and share it with everyone who needs to act on a piece of
it, well before the event, the same way a [[meeting-agenda]] needs real
lead time to do its job.

## Common pitfalls

- **Headcount never actually confirmed** — catering quantities, seating,
  and rentals end up guessed rather than booked against a real number,
  and the gap shows up as either waste or a shortfall on the day.
- **Timeline that exists only in the organizer's head** — if the run-of-
  show isn't written down and shared, everyone else is guessing at
  timing, and the organizer becomes a single point of failure for
  answering "what happens next."
- **Budget tracked only at the end** — checking spend against budget
  after vendors are already booked means overruns are discovered too
  late to do anything about; track it against each commitment as it's
  made.
- **Venue or date left open too long** — holding off on either to keep
  options flexible delays every downstream decision that depends on
  them.
- **No buffer in the day-of schedule** — a timeline with zero slack
  between segments turns any single delay (a late vendor, a slow
  transition) into a cascading delay for the rest of the day.
- **Vendor bookings left as tentative holds** — treating a verbal
  agreement as a confirmed booking risks losing the slot to another
  client who actually confirms.

## Learn more

- [[travel-itinerary]] for the same day-of logistics discipline —
  timed, confirmed items with buffer built in — applied to a trip
  instead of an event.
- [[meeting-agenda]] for the same principle of sharing a timed plan far
  enough in advance that people can actually act on it.
- [[budget-forecasting]] for tracking spend against a budget in more
  detail than a single event typically needs.