Skip to content
The arithmetic of a good time
My Snags Surprise me

Production & Hosting

The Event Planning Checklist That Starts With the Decisions That Cost Money

Most checklists have you choosing napkins before transportation is solved. This one is ordered by what locks money, space and guest expectations first.

Pin it on Pinterest (opens in a new tab)

Most event checklists are excellent at producing motion. They are less reliable at producing order. A list can tell you to choose napkins in the same month that you still have not solved transportation, venue access or the number of people the room can comfortably hold.

This version is organized by consequence. The decisions that lock money, space or guest expectations happen first. Decorative finishing comes later, when it has real information to respond to.

Before you book anything

  • Write the one-sentence guest experience you are trying to create.
  • Set a likely, minimum and maximum guest count.
  • Set an all-in spending ceiling and a contingency reserve.
  • Choose a realistic geographic area and date window.
  • List non-negotiables: accessibility, indoor backup, noise needs, cultural or ceremony requirements, transportation limits, lodging needs.
  • Identify who has final decision authority when opinions conflict.

If these answers are still moving dramatically, do not rush into decorative purchases. Use The First Five Decisions to stabilize the premise.

Once you are ready to choose a venue

  • Confirm usable capacity, not just advertised maximum capacity.
  • Review arrival, parking, drop-off and accessible routes.
  • Ask what is included and what must be rented separately.
  • Confirm load-in, setup, vendor access, service routes and strike timing.
  • Understand weather exposure and the actual alternate space.
  • Check sound, curfew, power, lighting and installation restrictions.
  • List every question that still requires direct confirmation before signing.

Test a venue as a place people have to work in, not a set of photographs. Space Lab walks through what to check.

After the date and venue are credible

  • Create the master planning calendar.
  • Secure long-lead vendors and venue-required services.
  • Track deposits, payment dates, cancellation terms and deliverables in one place.
  • Create a vendor contact list with one current phone number and email for each team.
  • Start the lodging and transportation plan if guests are traveling.
  • Decide where guest information will live: invitation, website, email or a combination.

None of this is glamorous and all of it is load-bearing. Every decision above it gets easier once these exist.

Build one guest list everyone trusts

  • Create one master guest list rather than several competing versions.
  • Track household, guest name, email, phone, invitation status and RSVP status as needed.
  • Record plus-one, child or participation policies consistently where they apply.
  • Track accessibility and transportation needs.
  • Track meal or dietary information only when it is actually needed by the event plan.
  • Create a clear process for late or changed RSVPs.

Your guest list will later drive seating, transportation, rentals, staffing and final counts. Keep it current as if everything depends on it, because a surprising amount does.

The decisions that lock money, space and guest expectations happen first. Napkins do not.

Organized by consequence

Develop the design direction

  • Define the visual thesis in one or two sentences.
  • Choose a limited palette with clear leading and supporting colors.
  • Assign jobs to materials, florals, lighting and repeated motifs.
  • Design for the actual venue architecture and available light.
  • Choose focal moments instead of spreading equal decorative effort everywhere.
  • Test every installation against sightlines, access, weather, setup time and removal.

Once the practical limits are known, Design Atelier is where the look gets built.

When the event is several months out: turn the plan into movement

  • Map arrival, ceremony or opening moment, transitions, meal, speeches or program, dancing or activity, and departure.
  • Draft a room plan with guest circulation and service routes.
  • Identify queue risks at bars, restrooms, coat areas, shuttles or check-in.
  • Decide whether seating is open, assigned by table or assigned by exact seat.
  • Confirm transportation assumptions with real travel times.
  • Create a weather decision tree for exposed portions of the event.
  • List every item that must be delivered, installed, moved or removed.

Now the event is a sequence instead of a date. Sequences can be tested. Dates cannot.

As final counts approach: close the gaps

  • Reconcile RSVPs and follow up on genuine missing information.
  • Build the seating plan from the current guest list where seating is assigned.
  • Confirm final vendor scopes and identify overlaps or gaps.
  • Confirm rental quantities and dimensions against the current layout.
  • Confirm setup and strike owners.
  • Write the first complete event-day timeline.
  • Confirm who makes decisions if weather or timing changes.
  • Check that guest-facing information matches the current plan.

Every gap still open here becomes somebody’s improvisation later, usually somebody who was not in the planning meetings.

The final production period

  • Provide final counts when contracts require them.
  • Issue one current timeline to the people who actually need it.
  • Confirm arrival windows, access instructions and onsite contacts with vendors.
  • Print or save offline copies of critical documents.
  • Pack personal or program items by destination rather than in one miscellaneous box.
  • Prepare payments or envelopes only where they are actually required or intended.
  • Confirm who takes gifts, personal items, decor and rental-sensitive objects at the end.

Everything here is about making the event survive contact with people who did not plan it.

The week of the event

  • Check the weather and use the pre-agreed decision triggers.
  • Confirm transportation and important arrival times.
  • Share changes through one source rather than scattered texts.
  • Remove obsolete files and old timelines from active circulation.
  • Give the host or event lead a short contact list and send practical questions to whoever owns them instead of to the host.

One source, one timeline, one owner per question. The week of the event is when parallel versions do their real damage.

After the event

  • Return rentals and borrowed items.
  • Confirm that personal belongings reached the intended person.
  • Save final contracts, invoices and notes while they are easy to identify.
  • Record what worked and what created friction if the event is part of a recurring family, organizational or hosting pattern.

A good checklist should reduce decisions as the event approaches. If it is still producing big new questions in the final week, more boxes will not help. Somewhere upstream, a decision that should have been made months ago is still sitting open.

Atmosphere OS · Arc Studio

Give the evening a shape it can hold.

Arc Studio builds the energy curve, marks the turn, and produces the run sheet and production brief from it. The timings come out of published rules, and the rulebook is explicit about which parts are judgment rather than arithmetic.

Free to use, local-first in your browser, and there is no account until you ask for one.

Field notes and corrections

When a number here turns out to be wrong, you hear about it.

Three things arrive and nothing else. The new field note — bar rates, cover widths, service clearances, the arithmetic worked through on one real evening. A line when a World opens, because a night only goes up once it can actually be thrown. And a correction whenever a rule in the published rulebook changes, or a number the tools rely on turns out to have been wrong. There is no weekly slot, because there is nothing weekly to put in it.

One email per field note or opening, plus corrections when a published figure moves. Unsubscribe from any of them.

Continue through the system

Pretty is still not a plan.

A party gets planned in roughly this order. Pick the chapter where your next problem lives.

See the complete five-chapter Event Design Intelligence map →