Planning schedule
The tasks most events share, dated back from your event date, with a checklist to put your own due dates and names on.
For a first pass, the dated table and the planning tasks are essential: every task that applies to your event has a date, and the first one is not already past. That is the Start here result of The planning schedule. Ask each supplier and agency for its own deadline and use that date in place of the default.
Planning tasks
The tasks most events share. Write a due date and a name on each that applies; mark a task "not part of this event" in its notes if it does not. Ask each supplier and agency for its own deadline and use that date.
How to use these sheets
- Start from the slowest booking. The place, the caterer or a permit sets the start. Put its deadline first.
- A due date and a name on each task. Write "not part of this event" in the notes of a task that does not apply.
- One weekly check. Look at this page once a week: what is due, what slipped, what to decide.
The dated table uses the date in your setup. For the Ortiz party (fictional; a Saturday in June), the caterer row falls eight weeks ahead, the invitations three weeks ahead, the final count a week ahead and the debrief a week after; Elena replaced the final-count row with the caterer's own date once the contract arrived.
Lead times here are conventions and examples. A supplier's or agency's own deadline replaces them, and a schedule shows when a task is due; it does not make a late booking available.