Plan a Progressive Dinner Across Hosts' Homes

A progressive dinner is a meal a group of friends plans together, with each course prepared and served at a different host's home. A plan for one works when three things are settled: every participating household owns exactly one course, everyone works from a single shared schedule, and each stop is ready before the group arrives. The template below gives you a page to fill in and save as a PDF. It covers the stop schedule, headcount, each host's prep sheet and transfers.

What changes the plan most

Three inputs drive almost every other decision. The first is the number of host households, because it sets how many stops and courses you have. The second is the distance between homes, because it sets how much of the evening goes to travel. The third is the confirmed guest count, because it sets food quantities and whether each home can seat everyone at once.

Published hosting guides give examples rather than rules. One suggests coordinating with three to four other households that live relatively close together. Another describes eight to ten people, or four to five couples, as a comfortable size. Use these figures as starting points only. The right numbers for your group depend on your homes, your route and how many people each host can seat.

Information to gather before filling in the plan

Keep three kinds of information separate. Inputs are facts only your group can supply, such as headcount, travel times, seating and portion sizes. Planning allowances come from published guides: each host prepares one course and has it prepared ahead of time, and course options include appetizers and soup or salad alongside a main course. Calculated results are the numbers you work out from the inputs, such as servings and recipe batches. This guide does not supply default portion sizes, stop lengths or travel times. Leave those as blanks until your group fills them in.

Calculating quantities for each course

Diners at a stop        = confirmed guests + hosts eating at that stop
Servings needed (each)  = diners at the stop x portions per diner
Recipe batches (each)   = servings needed / servings per batch, rounded up

Units: diners and servings are counts of people or portions.
Assumption: portions per diner is set by the host for that course;
no default is provided here.

Run the calculation separately for each stop. Hosts normally travel with the group, so the number of diners can be the same at every home. If someone joins late or leaves early, adjust the count for those stops.

How the inputs become one shared plan

Organize the plan by stop, in route order. Each stop gets one row showing its host, course, arrival and departure times, the verified travel time to the next home, and the seats available. That row-by-stop schedule is the master document, and everyone gets the same version. Two other pieces sit alongside it and serve different readers. Each host gets a prep sheet covering only their own course. Guests get a simpler card with times and meeting points. Keeping these separate means that when a time changes, you edit the master schedule first and then update the other two from it.

To make a PDF, copy the template below into a document or spreadsheet, fill in the blanks, and export or print it to PDF. Share the updated file every time the schedule changes.

PROGRESSIVE DINNER PLAN

Date: __________          Backup date: __________
Theme (optional): __________
Day-of contact for changes: __________

HEADCOUNT
Confirmed diners: ____     Final count due by: __________
Dietary needs / allergies (person - need - courses affected):
  - ______________________________
  - ______________________________

STOP SCHEDULE (route order)
Stop | Host household | Course | Arrive | Leave | Travel to next (verified) | Seats
 1   |                |        |        |       |                           |
 2   |                |        |        |       |                           |
 3   |                |        |        |       |                           |
 4   |                |        |        |       |                           |

HOST PREP SHEET (one per household)
Course: __________
Diners: ____  x  portions per diner: ____  =  servings needed: ____
Servings per batch: ____  ->  batches (round up): ____
Make-ahead tasks and finish-by time: __________
Last tasks before serving: __________
Ready-to-serve check done before leaving home? [ ]
Items borrowed / to return: __________
Next host notified when group departs? [ ]

TRANSFERS
Leg | Method | Drivers / riders | Parking or access notes
1->2|        |                  |
2->3|        |                  |
3->4|        |                  |

Steps in order

• 1. Gather the host households. Done when every household has agreed to host one stop.
• 2. Assign one course to each home and set the route order. Done when every course has a host and no home has two.
• 3. Choose a theme if the group wants one. This step is optional. Done when each host knows the theme or knows there isn't one.
• 4. Pick the date and start time, then invite guests with an RSVP deadline. Done when all invitations are out and include that deadline.
• 5. Collect RSVPs, dietary needs and allergies, and lock the headcount. Done when every host has the final number and the full allergy list, because a guest's restriction affects every course they eat.
• 6. Verify travel and access on the actual route, ideally at a similar time of day. Check parking, steps and who is driving whom. Done when every leg has a confirmed travel time and transport arrangement.
• 7. Build the stop schedule. Give each stop arrival and departure times and insert the verified travel time between stops. Done when the times add up end to end without overlaps.
• 8. Plan each menu and calculate quantities. Done when every host's prep sheet shows servings needed and recipe batches.
• 9. Prepare ahead. Each host should have their course prepared so the stop runs smoothly. Hosts of later stops will be away at earlier stops, so their prep must cover the time they're gone. Done when only the final serving tasks remain.
• 10. Share the final schedule as one file. Done when every household confirms they have the same version.
• 11. Hand off on the night. Notify the next host as the group leaves each stop. Done when each host has received a heads-up before guests arrive.

Gaps to fill with your own information

The evidence behind this guide does not set how long each stop should last, how much of each course to serve, or how long travel between homes should take. Those depend on your group, so record them as inputs. The guide also does not cover how long food can safely sit while hosts are away, how to transport dishes, or how to prevent allergen cross-contact. Check current authoritative food-safety and allergen guidance for those decisions. A completed planning template keeps everyone coordinated, but it does not by itself make food safe to serve.