Seating a conference dinner
A conference dinner is judged on one thing: whether people met someone useful. The seating plan is the whole mechanism for that, and most events waste it.
The default is wrong
Left to itself, a conference dinner seats people by the company they arrived with. Colleagues sit together, the same four people who have spent all day together spend the evening together, and nobody meets anybody. Delegates paid to be in the room with the others, and the seating plan is the only tool you have for making that happen.
So the working principle is the opposite of a wedding: split the groups you would normally keep together, and mix deliberately.
How to mix without making it awkward
Random mixing produces tables where nobody has anything in common, which is worse than cliques. Mix along one shared axis and vary the rest.
| Axis | Works when | Watch for |
|---|---|---|
| By topic or track | The conference has streams and people self-selected into them | Competitors in the same niche seated together |
| By seniority band | You want frank conversation rather than pitching | A table of ten people all waiting to be deferred to |
| By region | International events, or where language matters | Isolating a single non-native speaker |
| Deliberate cross-mix | Small dinners where you know the room | Time — this one has to be done by hand |
Whatever axis you pick, break up each company across at least two tables. Two colleagues at one table is fine and gives each of them a safe harbour; four is a private dinner.
Seat the people who came alone
This is the single highest-value thing on the page. Solo delegates are the most likely to have a bad evening and the most likely to remember it. They should never be the tenth person added to a table of nine who already know each other.
Build one or two tables deliberately out of solo attendees, mixed by topic, and put a host on each — an organiser, a speaker, a board member — whose actual job that evening is to start conversations. Tell them that is the job.
Speakers and sponsors
- Spread the speakers. A speakers' table is a waste of the most valuable people in the room. One per table, and tell delegates who is where — several will choose their seat for it.
- Sponsors get access, not a corner. A sponsor who bought a table wants to meet delegates. Seat their people across tables of the delegates they want to meet, and give them the front-centre table for the branding.
- Keep the keynote near an exit. They often have a train, and a keynote crossing the room mid-service is a distraction.
- Do not seat the person who is speaking next to the loudest speaker stack. They need to hear their cue.
Worked example: 120 delegates, 12 tables of ten. Table one, front centre, headline sponsor plus the chair. Two tables built from solo delegates, each hosted by a speaker. Nine mixed tables, each seeded with one speaker and no more than two people from any one company. The dietary list goes to the caterer as a CSV, and the table-by-table list goes to the front-of-house team who will be asked "where am I" forty times.
Awards nights have one extra rule
If there are awards, the shortlist sits where it can reach the stage without crossing the room. That means aisle seats on tables near the front for every shortlisted person or team — not the back, and not the middle of a ten-top where five people have to stand up.
Nobody should be told they are shortlisted by their seat position, though. Seat all the shortlisted tables the same way, including the ones who will not win.
The list the caterer actually needs
Conference dinners carry more dietary requirements than weddings, and the caterer needs them by table and by seat, not as an alphabetical list of allergies. The usual failure is a spreadsheet of names and requirements with no table numbers on it, which means a server walking the room asking who is the vegan.
Export the guest list as CSV once the plan is settled, and send the table-by-table version rather than the A–Z one. Then add the requirements column yourself if the tool does not carry it — tablout tracks names and groups, not dietary needs, so that column is a manual join in a spreadsheet. It takes ten minutes and saves an hour on the night.
Doing it in tablout
Place the tables in the room's real arrangement, then paste the delegate list with the mixing axis as the group — Ana Ferreira, Infrastructure, Tom Everitt, Infrastructure — and auto-seat. It fills by group, so you get topic tables immediately; you then move people to break up companies and to seed each table with a speaker.
The honest limitation: there is no rule engine, so "no more than two from one company per table" is something you enforce by eye rather than something the tool guarantees. With 120 people that is about twenty minutes of moving names. Corporate event seating covers the daytime layouts, and how to seat 100 guests walks a room of this size end to end.
Mix the room deliberately
Paste the delegate list with a topic or track as the group, auto-seat by group, then break up the companies by hand.
Open the planner →Common questions
- Should colleagues sit together at a conference dinner?
- No more than two from the same company per table. Delegates paid to meet the other people in the room, and left alone a dinner seats everyone with the colleagues they spent all day with. Two gives each person a safe harbour; four is a private dinner.
- How do you seat delegates who came alone?
- Build one or two tables deliberately from solo attendees, mixed by topic, and put a host on each — an organiser, speaker or board member whose job that evening is to start conversations. Never add a solo delegate as the tenth person at a table of nine who know each other.
- Where should speakers sit?
- One per table, spread across the room, and publish who is where — several delegates will choose their seat for it. A speakers' table wastes the most valuable people in the room.
- How should awards shortlists be seated?
- On aisle seats at tables near the front, so nobody has to cross the room or make five people stand. Seat every shortlisted table the same way, including those who will not win, so the seating does not leak the result.
- What does the caterer need from the seating plan?
- Dietary requirements by table and seat, not an alphabetical list. A server should never have to walk the room asking who ordered the vegan option. Export the table-by-table list and join the requirements column to it.