Progressive dinner rules and schedule: how the evening works
A progressive dinner (also called running dinner or safari supper) sounds complicated but follows a simple pattern: three courses, three addresses, new faces at every table. Once you understand the flow, it works with 12 or with 120 participants. Here is the complete schedule plus the rules that have proven themselves in practice.
The basic flow in one sentence
Every couple (or two-person team) cooks one course at home and is a guest for the two other courses at other participants' homes — each time at a different table, with different tablemates. At the end, everyone gathers for a closing party.
The typical schedule
A proven timeline for a Saturday evening:
| Time | Item | Duration |
|---|---|---|
| 5:30 pm | Optional: joint aperitif at a central venue | 45 min |
| 6:30 pm | Starter at host 1 | 60 min |
| 7:45 pm | Main course at host 2 | 75 min |
| 9:15 pm | Dessert at host 3 | 60 min |
| 10:30 pm | Closing party — everyone in one place | open end |
The rules that matter
1. Punctuality is everything. The schedule only works if every course ends on time. Hosts clear the table if needed before the last guests have left.
2. One address per course. Each host cooks exactly one course and stays home for it — for the other two courses they travel.
3. The route stays secret. Participants only learn at the start of each course where they are going (classically by envelope, today often digitally). That keeps the surprise alive.
4. No repeated tablemates. That is the goal of the planning: new faces at every course. With small groups this cannot be fully avoided — one overlap is fine, two is a planning error.
5. Allergies are reported in advance. Hosts cook for guests they don't know. Dietary requirements belong in the sign-up, not at the door.
6. Keep it doable. Starter and dessert can be fully prepared ahead; the main course must be "wait-proof" because guests may arrive late.
The right group size
The maths is simple: with three courses you need a number of teams divisible by three — 9, 12, 15, 18 and so on. Then at every course one third of the teams are hosts and two thirds are guests.
- 9 teams (18 people): every table seats 6. The minimum for a genuine progressive dinner.
- 12 teams (24 people): the classic for friend groups, neighbourhoods and small clubs.
- 18–24 teams: street parties, sports clubs, student societies. From here on digital planning pays off, because routes and overlaps can no longer be overseen by hand.
What the host needs to know
The host learns in advance how many guests with which dietary needs are coming — but not who they are. They set the table for that number, cook with a time buffer and ideally have a note ready for where the next route leads (or rely on the organiser's envelope cards).
What the guest needs to know
The guest brings nothing but good spirits — at most a bottle of wine as a thank-you. They leave the table on time, even when it is just getting cosy. And: the closing party is the real highlight, because only there do you see everyone again you ate with along the way.
Conclusion
The rules and schedule of a progressive dinner can be explained in ten minutes — the challenge is the planning: who cooks which course, who sits where and when, and how do the routes stay short? Exactly that can now be solved automatically, including envelope cards and a digital route per participant.