The planning schedule: working back from the event date
Every task dated back from the event by its lead time, starting from your slowest booking; the deadlines that close options; the invitation, reply-by and final-count dates; and one weekly check.
- Start here: the essentials
- Working back from the date
- Deadlines that close options
- The default frame: from the date set to the day after
- The week of, the day before and the day
- The weekly check, and when the schedule slips
- A dinner party in two weeks
- Eight campus timelines, a 12-week fundraiser and an eight-day meal
- See it: Elena's party and Marcus's two weeks
- Practice: date your first five tasks
- Your event
- Check your work
- Knowledge check and scenario
Start here Essentials
For a first pass, this chapter asks you to put the event date in setup, find out each booking's own deadline, and date your tasks backward from the slowest one, with a weekly check to keep it current.
- Write the event date in setup. The schedule page dates every task from it (working back from the date).
- List your bookings and ask each for its deadline. The place, the caterer, rentals, any permit (deadlines that close options).
- Put the slowest one first and work back. Then add the invitation date, the reply-by date and the final-count date (the default frame).
- Set one weekly check. A fixed time to read the schedule and move what slipped (the weekly check).
Minimum time: about 30 minutes, plus a message to each booking. Done when: every task on the schedule sheet has a date, and the first one is not already past.
Working back from the date Understand
A planning schedule is a list of tasks, each with the date it is due, counted back from the event. Two words carry it. A task's lead time is how far ahead of the event it has to start: a caterer who needs four weeks' notice has a lead time of four weeks. Its deadline is the last date it can be done and still work: the caterer's last booking date, the city's last application date, the date the final count is due. A lead time is a length; a deadline is a date. The schedule turns the first into the second.
The start of the schedule is set by the slowest booking: the one thing with the longest lead time. For most events it is the place, the caterer, a tent, a performer or a permit. Everything else can be dated after it. That is why the university event guides disagree so widely about when to start, from four weeks before the event to a year. Each starts from its own slowest step, and on a campus that is usually an approval queue (a room request, a contract signature, a catering order cutoff) rather than the work of the event. The guides' start points are side by side under Go deeper.
The method
- Write the event date. In setup, so every dated row on the planning schedule page counts from it. No date yet? The event brief covers choosing two or three, and the schedule shows lead times without dates until you pick one.
- List everything that needs a booking, an approval or an answer. The place, food, rentals, a tent, a performer, a permit, an insurance certificate, invitations.
- Ask each one for its deadline. By phone or email, and write the answer with the date you got it. Ask the authority
- Write each task with its date. Sort by date. The earliest is your start.
- Check the first date against today. If it has already passed, the schedule has slipped before it began; when the schedule slips gives the three choices.
- Add the dates that follow from others. The invitation date, the reply-by date and the final-count date depend on the place and the food; the run sheet, the kit and the debrief depend on the day.
| Task | Whose deadline it is | What sets it |
|---|---|---|
| Book the place | The venue, the park, the hall's manager | When reservations open and when your date is taken |
| Book the food | The caterer or restaurant | Its booking lead time and its final-count date |
| Rentals and a tent | The rental company | Its stock on your date, delivery windows, and any permit |
| A permit or license | The city, the fire department, the state agency | Its application deadline, sometimes with an earliest date too |
| Invitations | You | Convention by event type, and how far ahead guests book their time |
| Reply-by date | You | A few days before the first supplier's final-count date |
| Final count | The caterer or venue | Its contract |
The schedule itself lives on the tasks sheet, one row per task with its due date, who does it, and notes. With a date in setup, the page also shows a dated table of the usual tasks and shades the row you are in now.
Deadlines that close options
Some deadlines close a door: after them, the option is gone. These are the ones to find first. Each example below is one place's or one business's rule, labelled as theirs. Your city, park, caterer or state may set a different date; ask each. Ask the authority
| What | Example deadline | Whose rule |
|---|---|---|
| Park shelter reservation | Paid shelter reservations accepted 18 months ahead (Spokane's shelters and picnic grounds page) | City of Spokane, Washington |
| Park shelter with alcohol | At least two weeks' notice for the online process and alcohol requests; one week without alcohol (Boulder's shelter rentals page) | City of Boulder, Colorado |
| Block party | Application 60 days ahead, $25 processing fee (New York City's Street Activity Permit Office); or, in another city, try to apply at least 14 days ahead, and the permit is free (Seattle's block party page) | New York City; Seattle |
| Amplified sound | Apply 14 calendar days ahead; the page says a late application will be denied (Saint Paul's amplified sound permits page) | City of Saint Paul, Minnesota |
| One-day alcohol license for a nonprofit | File at least 10 days before the event and no more than 30 days ahead (California ABC's daily license instructions) | State of California |
| Booking a caterer | Anywhere from 4 to 8 weeks ahead, by one extension writer (Iowa State's AnswerLine post); one campus caterer asks for 30 days (University of Puget Sound's booking and cancellation page) | Iowa State's writer; one caterer |
| Final count to the caterer | 48 hours before (Carnegie Mellon's catering policies); 3 pm on the Tuesday of the week before (Vanderbilt Catering's policies); two weeks before (Puget Sound) | Three campus caterers |
| Cancelling without a charge | Boulder refunds 50 percent at 15 days or more and nothing at 14 days or less; Puget Sound charges nothing if you cancel at least 14 days ahead | City of Boulder; one caterer |
| Invitations | Informal dinner a few days to 3 weeks; graduation party 3 weeks; formal dinner 3 to 6 weeks; charity ball 6 weeks to 3 months (the Emily Post Institute's invitation timing table) | Etiquette convention |
Four patterns in the table are worth carrying to any event.
- Some deadlines are windows. California's one-day license is filed no more than 30 days ahead and at least 10 days before. A task like that gets two dates on the schedule: the first day you can do it and the last.
- Some options open early and go to whoever asks first. A shelter that takes reservations 18 months ahead may be taken on a summer Saturday long before a 10-week plan starts. For a popular place and date, the slowest booking may be the reservation window, not any work.
- Cancellation dates are deadlines too. The day a deposit stops being refundable is the last day a change is cheap. Put each one on the schedule next to the booking it belongs to; Hiring suppliers has the contract questions that find them.
- The final count sets the reply-by date. Work back from the caterer's final-count date: the reply-by date goes a few days before it, so you have time to chase non-replies and count. With Puget Sound's two weeks, the reply-by date falls about 17 days before the event; with Carnegie Mellon's 48 hours, about five. Guests and invitations covers the invitation and reply-by dates in full. Convention
The lead times in this chapter are conventions and examples from named places and businesses. A supplier's or agency's own deadline replaces them; ask each one and write down its answer with the date. A schedule shows when a task is due. It does not make a late booking available: if the city needed 60 days and you have 40, the schedule cannot fix that, and the choices are in when the schedule slips. Permits and their rules are in Permits and insurance.
The default frame: from the date set to the day after
Once the bookings are dated, the rest of the work falls into stages that most event guides share. The University of New Mexico's guide runs as soon as possible, 4 to 6 weeks out, 3 weeks out, the week of, the day of and after (UNM's Event Planning Guide). Syracuse's checklist runs four to six weeks, three to four weeks, one to two weeks, the day of and after (Syracuse's Event Planning Checklist). Nicholls State adds the day before (Nicholls State's event planning guide). We use their shared stages as the default frame, and the slowest booking, wherever it falls, goes in front of them. Convention
| Stage | What usually happens | Where it comes from |
|---|---|---|
| As soon as the date is set | The brief and the budget; who decides; reserve the place; ask every booking and permit for its deadline; book the slowest | UNM: reserve space for a large event as soon as the date is set |
| 4 to 6 weeks before | Food and quotes; the budget with any outside money; who does what in the group; invitations for most parties | Syracuse (space, catering, quotes, budget at four to six weeks); Nicholls (budget and division of responsibilities at four or more weeks) |
| 3 weeks before | Supplies; supplier contracts signed; helpers asked; services and equipment arranged | Syracuse (supplies, vendor contracts at three to four weeks); Nicholls (planning meetings, services and equipment at three to two weeks) |
| The week of | Weather; final count; confirmations; the run sheet written and shared; money for the day | UNM (weather, back-up plan, final food order from a head count); Nicholls (finances in order, a schedule of who does what, one to two weeks out) |
| The day before | Confirm materials, equipment and people; review the plan; remind helpers | Nicholls (day before: confirm materials, performers and personnel; review the agenda) |
| The day | Arrive early; check the space and deliveries; someone ready for a store run | Syracuse (arrive 1 to 3 hours early for its campus events); UNM (a volunteer ready for a store run) |
| After | Return equipment; pay balances; reconcile the budget; thank helpers, suppliers and funders; notes for next time | Nicholls; UNM (update the budget, leave notes for future coordinators) |
The stage names come from the guides; the exact days do not. The dated table on the planning schedule page puts each stage on a date counted back from your event date. Where no source gives a single day (the guides give "4 to 6 weeks", not one date), the page's offsets are this manual's convention, and the table says so on each row. Where your supplier has given you a date, use theirs.
A small party compresses the frame; a large one stretches it. A dinner for six can run the whole frame in two weeks (a dinner party in two weeks). A fundraiser with a hall, a raffle and volunteers may start three months out (a 12-week version is under Go deeper). The stages stay in the same order.
The week of, the day before and the day
The last week is where a schedule meets the run sheet. The campus guides agree on what goes in it, though not on the day. Nazareth writes the day-of timeline one week before (Nazareth's event planning timeline); Northern Kentucky does it one to two weeks before (NKU's How to Plan an Event); West Chester meets its volunteers the week of and shares the schedule with the team on the day (West Chester's event planning resource).
The week of
- Weather. UNM's guide says to check forecasts the week of, and that an outdoor event needs a back-up plan. Name one person to watch the weather and say when the rain plan starts; The contingency plan has the decision points.
- Final count. Count yeses on the reply-by date and give the caterer or venue the number by its deadline. Guests and invitations turns replies into a planning number.
- Confirmations. Each supplier's arrival time, what it brings and who meets it. Nazareth confirms the room setup, technical needs, catering and payments one week before; Missouri State confirms setups and meal counts one week before (Missouri State's student organizations timeline).
- The run sheet, written and shared. Times, tasks, who and where, given to every helper. The run sheet covers building it; West Chester's guide suggests an FAQ for volunteers as well.
- Money for the day. Nicholls says to have finances in order so bills due on the day can be paid. NKU says to arrange change and a secure place for cash if you take money at the door.
- Reminders. Amherst's checklist sends reminders one week out to group members and to people who replied yes (Amherst's Basic Event Planning Checklist).
The day before
Nicholls: pick up or confirm all materials and equipment, confirm people, review the agenda. NKU: remind every volunteer when to show up. Pack the kit (the day-of kit), charge phones, print the run sheet and the contact sheet. For a meal, the make-ahead dishes are cooked and chilled.
The day and after
The run sheet takes over on the day. The schedule's last rows are for after: returns, final payments, deposits back, thanks, the budget's actuals, and a short debrief. NKU holds its evaluation meeting within a week. The run sheet lists the day after; The budget has the actuals.
The weekly check, and when the schedule slips
A schedule is only as current as the last time someone read it. Set one fixed time a week, alone or with the committee, and keep it short. This is our convention; the campus guides hold planning meetings in the weeks before without fixing how often. Convention
- Read the next two weeks. What is due, and who does it.
- Mark what is done. And what came back: answers, quotes, deposits, replies.
- Find what is overdue. Give it a new date and an owner, or move it to the decisions below.
- Check the dates that depend on others. A new final-count date moves the reply-by date.
- Write any decision in the log. The decision log keeps the answer, so the question is not reopened next week.
When the schedule slips
A slip is a task past its deadline, or a first date that was already past when the schedule was written. Nicholls's guide starts with the same test: is there enough time to make this event work? When the answer is no, there are three choices, and each changes the brief.
| Choice | What it does | What it costs |
|---|---|---|
| Move the date | Gives every task more lead time | Guests' calendars, deposits already paid, a date that mattered (a birthday) |
| Shrink the event | Drops the bookings that are too late to make (fewer guests, a home instead of a hall, no street closure) | What the event was for, if the cut part was central |
| Drop the item | Removes one task (no tent, no band, the hosts cook instead of a caterer) | The item, and whatever it was there to solve (a tent for rain needs another rain plan) |
Who chooses is set in the brief (The event brief). Going ahead without the booking (the street without the permit, the park without the reservation) is not one of the choices; the rule still applies on the day.
A dinner party in two weeks
A dinner for a few people at home has no venue, no caterer and no permit. Its slowest steps are the guests' calendars and the shopping. Two weeks is a workable frame for most; Emily Post's table gives a few days to three weeks for an informal dinner. The offsets below are our convention unless a source is named. Convention
| When | Task | Source or convention |
|---|---|---|
| 14 days before | Invite the guests; ask what each cannot eat; give a reply-by date a week out | Emily Post (informal dinner: a few days to 3 weeks); reply-by date our convention |
| 10 days before | Draft the menu around the kitchen | Our convention |
| 7 days before | Replies in; menu final; order anything bought (a bakery dessert) and ask about allergens | Our convention |
| 5 days before | Write the amounts, the shopping list and the cooking timeline; check the table, chairs and serving pieces | Our convention |
| 2 days before | Shop | The dinner plan's seed row, our convention |
| The day before | Make the make-ahead dish and chill it; set the table that night; chill drinks | Maryland's eight-day timeline (day before and night before) |
| The day | Pick up anything bought; follow the cooking timeline from the serving time | A dinner party |
| Within 2 hours of serving | Leftovers into the refrigerator | FSIS's 2-hour rule |
The cooking timeline for the day itself, worked back by the clock, is in A dinner party. A holiday meal with a frozen bird starts earlier, because thawing takes days; the eight-day version is under Go deeper.
Eight campus timelines, a 12-week fundraiser and an eight-day meal Go deeper
Eight institutions' start points, and what each governs
Eight university and extension guides give a point at which to start planning. Side by side, they range from four weeks to a year. Read the third column: most start points are set by a campus queue, not by the event.
| Institution | Start point | What the start point governs |
|---|---|---|
| Nicholls State University | Five or more weeks (goal setting) | Campus event registration at four weeks; the guide also asks whether there is enough advance time to succeed |
| Amherst College | Four or more weeks (goal setting) | Registration, approval and room reservation at three to four weeks |
| University of Portland | Six or more weeks; ten for a major event | Contact with the student activities office; check requests two weeks before the money is needed (University of Portland's planning timeline). Its text matches Amherst's almost word for word, so we count the two as one template. |
| West Chester University | Four weeks' notice | Campus approval for non-standard events; 72 business hours for a standard listing |
| Nazareth University | Two months | Finding extra funding or co-sponsors; contracts, space and food at one month |
| Northern Kentucky University | Three to six months | Program planning; food orders at least ten days ahead, larger orders a month |
| UC Cooperative Extension 4-H handbook | Six months | A committee event with presenters and awards (the Alameda and Contra Costa 4-H Event Handbook) |
| Missouri State University | One year, or at the time of booking | Booking a conference venue and its support services; it confirms when final guarantees are due five weeks out, and tells readers to set their own "ideal" and "can't-miss" dates |
The spread follows what each guide books or gets approved. Missouri State's year is a venue booking; West Chester's four weeks is an approval queue; Nazareth's two months is fundraising. That is the case for starting from your own slowest booking rather than from any one guide's number.
A 12-week version for a fundraiser
A community fundraiser has more bookings and more people than a party: a borrowed room with its own forms, food rules, a raffle, ticket money and volunteers. The offsets below are our convention, built on the stages above; each named source is the one that places a task near that time. Every rule a fundraiser meets is asked of the body that sets it (Permits and insurance).
| When (our convention) | Tasks |
|---|---|
| 12 weeks | Brief, net goal and who decides; date options; the room's request form and whether it needs a certificate of insurance; ask the health department about volunteers cooking (FSIS's Cooking for Groups booklet has a person in charge contact it); ask the state about the raffle (Permits and insurance); budget and break-even (The budget) |
| 8 weeks | Room confirmed in writing; any certificate filed; ticket price set; donors and raffle prizes asked |
| 6 weeks | Tickets or invitations out; volunteer roles written |
| 4 weeks | Volunteers asked for named shifts (Nazareth recruits volunteers a month before; West Chester three weeks); food and supplies ordered |
| 2 weeks | Follow up with every supplier (West Chester); helpers' roles confirmed |
| The week of | Final count; volunteer briefing; run sheet shared; change and a cash box ready (NKU) |
| After | Deposit money the next business day and pay the invoices (NKU); thanks and donor acknowledgments; debrief within a week (NKU) |
An eight-day countdown for any meal
Maryland's eight-day holiday timeline is a model for a meal with a frozen bird or several make-ahead dishes: start thawing the turkey six days ahead, make and freeze dishes four or five days ahead, thaw them in the refrigerator two or three days ahead, make desserts and casseroles the day before, set the table the night before, and bake desserts early on the day so the oven is free (University of Maryland Extension's 8-day holiday meal timeline). Tasting Table's timeline starts a month out: the guest list and to-do list at one month, shelf-stable shopping and equipment at three weeks, the freezer cleared and dishes frozen at two weeks, and a day-by-day plan in the last week (Tasting Table's Thanksgiving timeline). One is an extension service's, the other one food writer's; both count backward from the meal.
See it: Elena's party and Marcus's two weeks See it
Elena Ortiz is fictional, and every fact about her family here is invented for this manual. She is planning her mother Carmen Ortiz's 70th birthday with her two brothers, in her brother Luis Ortiz's backyard: a Saturday in June, 2:00 to 6:00 pm, 45 guests (eight of them children), a taco caterer serving from 3:00 pm, beer, wine and soft drinks served by the family, a rented 20-by-30-foot tent, speeches at 4:00 pm. The budget is $3,000, split three ways.
Known: the date, the times, the place, the guest count, the caterer's kind of food, the tent's size (600 square feet).
Her bookings, slowest first. She lists three things that need someone else's answer: the caterer, the tent rental company, and the fire department, which she asks whether a 600-square-foot tent needs a permit where Luis lives. She asks each for its deadline. Until they answer, she writes these assumptions.
Assumed (Elena's, until each answers): the caterer needs 8 weeks, the top of Iowa State's 4 to 8; the tent company needs the same; the fire department, if it requires a permit, needs it applied for well before the party, so she asks 12 weeks out; the caterer's final count is due 7 days before. She chooses to invite 5 weeks ahead, on the early side, since the guest list is large and the occasion matters, as Emily Post's page advises.
| When | Task | Who |
|---|---|---|
| 12 weeks before | Brief with her brothers; ask the caterer, the tent company and the fire department for their deadlines | Elena |
| 10 weeks | Book the caterer and the tent; write each cancellation date on the schedule | Elena, Luis |
| 5 weeks | Invitations out, with the dietary question and a reply-by date 10 days before | Elena |
| 3 weeks | Drinks, ice and supplies listed; helpers named for setup, drinks and children | Brothers |
| 10 days | Reply-by date; count and chase non-replies | Elena |
| 7 days | Final count to the caterer; forecast checked; tent delivery time confirmed; run sheet shared | Elena |
| Day before | Kit packed; tent delivered if the company sets up early (ask) | Luis |
| After | Returns, final payments, thanks, actuals split three ways | All three |
Under these assumptions, and assuming she starts with 14 weeks to go, the first date is 12 weeks out and nothing is already past. If the caterer answers that its final count is due two weeks before, her reply-by date moves to about 17 days before, and her invitation date may move earlier with it.
Open: whether the tent needs a permit and how long the fire department takes (settled by the fire department; Permits and insurance); the caterer's real final-count date and cancellation terms (settled by the contract; Hiring suppliers); what the family does if thunder is heard during the party (The contingency plan).
Marcus Bell (fictional) is hosting dinner for six at his apartment on a Saturday, food on the table at 7:30 pm. He has no venue, caterer or permit; his slowest steps are five guests' calendars and the bakery.
His two weeks. Fourteen days before, he invites the two couples and the coworker, asks what each cannot eat, and asks for replies within a week. Seven days before, all five have said yes; he knows one is vegetarian and one has a tree nut allergy, settles the menu, orders the dessert and asks the bakery about nuts. Five days before, he writes the amounts and the cooking timeline. Thursday, two days before, he shops. Friday he makes the side dish, chills it within two hours, and sets the table with its leaf in. Saturday he follows the timeline.
Assumed (Marcus's): the bakery takes orders a week ahead, which he confirms when he calls. Open: whether the guest with the allergy accepts the bakery's answer (settled by the guest; A dinner party).
Practice: date your first five tasks Practice
Minimum: the event date in setup, your bookings listed with a deadline asked of each, and five dated tasks on the schedule sheet. Time: about 30 minutes, plus waiting for answers. Materials: your brief, a phone or email, a calendar, and the planning schedule page.
- Enter the event date in setup. If you have two candidates, use the earlier; the schedule moves if you change it.
- List the bookings. Place, food, rentals, tent, performer, permits. For a dinner at home, the list may be one bakery.
- Send each the same question. "What is your last date to book for [date], and when is the final count due?" Write the answers and the date you got them.
- Date five tasks. The slowest booking, the invitations, the reply-by date, the final count, and the first weekly check.
- Read the first date against today. If it is past, choose: move the date, shrink the event, or drop the item. Write the choice in the decision log.
Fill the whole frame. Add every stage from the default frame to the tasks sheet with a name in the who column, then compare your dates with the dated table on the schedule page and note where your suppliers' deadlines differ from its convention.
Your event Your event
Check your work Check your work
Criteria
- Is the event date in setup, or a note saying which dates are still being chosen?
- Does every booking have a deadline that came from the supplier or agency, with the date you asked?
- Is the slowest booking first, and is its date still in the future?
- Are the invitation, reply-by and final-count dates on the schedule, with the reply-by date a few days before the final count?
- Are cancellation and refund dates written next to their bookings?
- Does every task have a date and a name?
- Is there a weekly check, with a day and a time?
Worked example
Elena's schedule has eight dated rows with a name on each. Three deadlines are marked "assumed, asked" with the date she sent the question. The reply-by date sits three days before her assumed final count. She sets her weekly check for Sunday evenings with her brothers. It passes as a draft: the three assumed rows change when the caterer, the tent company and the fire department answer, and she has written that next to them.
Common mistakes
- Starting from a guide's number. Four weeks is a campus queue. Start from your slowest booking.
- Using a lead time as if it were the supplier's deadline. Ask; write the answer.
- Setting the reply-by date after the final count. Work back from the caterer's date.
- Leaving out cancellation dates. The day a deposit stops being refundable is on the schedule too.
- A schedule no one reads. The weekly check keeps it true.
- Treating a slip as a reason to skip a rule. Move, shrink or drop; the permit still applies.
What is still unresolved
Each booking's real deadline is settled by the supplier or agency; the contract questions are in Hiring suppliers and the rules in Permits and insurance. The final number is settled on the reply-by date (Guests and invitations). The day itself belongs to The run sheet.