2026-04-21 • Cyro van Malsen

Planning the Best Route for a Progressive Dinner

The route is the logistical heart of a progressive dinner. A bad route means groups cycling through the rain for twenty minutes while their soup goes cold — a good route means everyone arrives relaxed and on time. This article explains how to plan a smart route, which factors matter and how to automate the calculation.

What Makes a Good Progressive Dinner Route?

A good route meets three criteria:

1. Distances are manageable. Participants travel two or three times during the evening. In a city neighbourhood, walking is fine; in a village or rural area, cycling or driving is more realistic. The golden rule: nobody travels more than 15 minutes between two locations.

2. The route is logical. Participants don't zigzag across the area. The addresses form a reasonably connected cluster, or are deliberately grouped by course.

3. Travel time fits within the schedule. If you build in 15 minutes of travel time between courses, the route must actually make that possible — including putting on a coat and saying goodbye to the host.

Step 1: Gather All Addresses

Start with a list of all host addresses. For a progressive dinner with three courses and ten groups you need thirty host addresses (ten per course) — or fewer if some participants host more than one course.

Plot all addresses on a map before you start the seating plan. Use Google Maps or a similar tool and pin all locations. This immediately shows you:

Whether addresses are spread out or clustered

Whether there are outliers that are logistically problematic

Which addresses are close to each other and can be usefully combined

Step 2: Group Addresses by Course

The basic principle of route optimisation for a progressive dinner: groups always travel from course A to course B to course C. Each group's route must make geographic sense: the starter address, the main course address and the dessert address must be connected in a logical way.

This is exactly where manual planning goes wrong. You can easily create a good route for one group, but when you try to do it for ten groups simultaneously — while also accounting for who sits with whom and who has which dietary requirements — it becomes a puzzle that takes hours.

Rule of Thumb for Manual Planning

If you still want to plan manually: divide your addresses geographically into three zones. Assign addresses in the North zone as the starter, Central zone as the main course, and South zone as the dessert. Groups then always travel in one direction and distances stay manageable.

Step 3: Calculate Travel Times

Travel times depend on:

Mode of transport: on foot (5 km/h / 3 mph), cycling (15 km/h / 9 mph), car (urban traffic: average 30 km/h / 20 mph)
Distance between addresses
Time of day: evening traffic, parking availability

Always build in a buffer of 5–10 minutes on top of the pure travel time. People say goodbyes, find their coats, walk to the car. A total buffer of 15 minutes (travel time + buffer) is a safe standard for urban environments.

Transport	Maximum distance per leg
On foot	1.5 km / 1 mile
Cycling	4 km / 2.5 miles
Car	10 km / 6 miles

Step 4: Calculate Automatically with runningdinner.app

Manually calculating routes for 10+ groups is error-prone and time-consuming. runningdinner.app does this automatically:

You enter addresses when registering participants
The app calculates the optimal seating plan, weighted by geographic proximity
Each participant receives a personal route schedule: address A for the starter, address B for the main, address C for dessert
The app simultaneously accounts for who sits with whom (no repetitions) and dietary requirements

The result: a route that works both logistically and socially — in seconds, not hours.

Step 5: Communicate the Route Clearly

A good route is worthless if participants don't understand it. Make sure you include:

Full address per course (street, number, postcode, city)
Name of the host so participants know who to ring the bell for
Arrival time per address
Transport advice if the distance is relevant ("this address is 12 minutes by bike from the previous one")

Send the route one week in advance so participants can save it in their phones. A reminder with the schedule 24 hours before the event prevents confusion on the evening itself.

Common Route Mistakes

One address far outside the cluster. This forces one or more groups to make a long journey. Solution: assign that address to the first or last course, or ask whether that host can use a different location.

Not enough time between courses. 10 minutes is almost always too tight. Allow at least 15 minutes and communicate the mode of transport clearly.

Not accounting for parking. In busy neighbourhoods, finding parking takes extra time. Tip for hosts: mention in their confirmation where guests can best park.

Only communicating the route on the evening itself. Then participants don't have time to enter the addresses into their navigation app. Always send in advance.

Summary

A good progressive dinner route is short, logical and fits within the schedule. The core: group addresses geographically, build in sufficient travel time and communicate the route clearly to all participants. For small groups manual planning is still feasible; with 30+ participants, automatic calculation via runningdinner.app is the smart choice.

*Want your progressive dinner route calculated automatically? Get started at runningdinner.app — optimal seating and routes for all participants in minutes.*