Free guide - Northbench

Event planning checklist: the order that actually works

Most event checklists fail, and not because they forget the napkins. They fail because they are lists of things instead of an order of operations. The cake ordered before the guest count is known, the venue booked before the budget ceiling exists. This is the checklist that respects dependencies - do it in this order and most emergencies never happen.

The three numbers that run every event

Before any checklist item, three numbers must exist, because every later decision hangs on them:

RSVP math that saves money: roughly 15-20% of yeses will not show. Plan catering and seating for the confirmed count, not the invited count - but keep a 10% buffer of seats, not meals. Seats are cheap; wasted plates are not.

The checklist, in dependency order

8+ weeks out: the frame

6 weeks out: the commitments

4 weeks out: the counts

2 weeks out: the reconciliation

Week of: the run sheet

The day after: the close-out

Why a checklist is not a workbook

A checklist tells you what to do. An event still needs a living document - one guest list everyone updates, seating that checks itself against table capacity, a budget that shows quotes versus plan as they arrive. The checklist is the order; the workbook is the machine that runs it.