External group meetings: a practical guide for event producers

The meetings the programme runs on

Before an event happens, there are dozens of meetings that have to happen first. Panel briefings. Speaker prep calls. Advisory sessions with steering committee members. Coordination calls with sponsors who are contributing to the programme. Pre-event planning calls between panellists who haven't met before.

These aren't administrative tasks. They are the work. The programme quality of a conference is directly connected to how well these calls are run — and whether they happen at all before the day itself. A panel that has never spoken together before taking the stage produces a different outcome than one that has had forty-five minutes to align on key themes and agree on their approach.

Getting these meetings confirmed is where a significant amount of producer time goes. Not because producers don't know what they're doing — but because the tools and processes most events organisations use weren't designed for the specific problem of coordinating external group meetings across multiple organisations.

Why external group meetings are different

The meetings a producer coordinates for an event are not internal meetings. Every participant is from a different organisation. They don't share a calendar system. They have no particular obligation to respond to the producer's scheduling request on the producer's timeline. They are senior, busy people who have agreed to participate in an event, not to make a producer's logistics problem easier to solve.

This creates a coordination dynamic that internal scheduling tools don't address. You cannot see their calendars. You cannot send a direct calendar booking. You cannot rely on an automated reminder from your own calendar system to chase them. You are, effectively, working through email or polling grids and waiting.

The participants themselves are often coordinating across timezones. A five-person panel might have speakers in London, New York, Dubai, and Singapore. A time that works for London at 10am doesn't work for Singapore at 5pm. The producer does the timezone arithmetic, or forgets to, or gets it wrong, or gets it right and then someone drops out and it has to be done again.

The coordination cycle — what actually happens

An event producer coordinating an external group meeting typically goes through a version of the same process every time.

They send an initial availability request — a poll, a shared grid, a direct email asking for available windows. They wait. One or two participants respond immediately. The others don't. A follow-up goes out, politely. Another response arrives. A week later there is still one person who hasn't replied and the window the producer was hoping to use is now half gone.

Eventually enough responses arrive to make a decision. The producer reviews the results, works out which slot has the best overlap, picks it, and writes a confirmation message. They create the calendar event, add the participants, include the video link, and send the invites. Three participants accept. One accepts tentatively. One doesn't respond to the invite either.

This process, repeated for forty or fifty sessions across an event cycle, produces a measurable overhead. For a producer running three events a year, it adds up to roughly 45 hours annually — an entire working week spent on logistics that produce no content, no speaker relationship, and no programme value.

The timezone layer

Timezone coordination in event production deserves separate attention because it compounds the problem in a way that's easy to underestimate.

An availability poll that shows everyone as free on Tuesday at 2pm looks like a solution. It is, until the producer realises that one speaker is in Tokyo, where Tuesday at 2pm London time is Tuesday at 11pm. The poll asked for availability in local time.

Getting timezone coordination right requires the producer to know which timezone each participant is working in, convert all the proposed times accordingly, and identify windows that are genuinely reasonable for everyone — not just technically overlapping. This calculation has to be done fresh for every meeting, because the participant group changes between sessions.

A scheduling system that reads calendar data directly and is timezone-aware by design removes this from the producer's workload entirely. The system knows where each participant is, or can infer it from their calendar data, and identifies slots that work across all timezones rather than requiring the producer to do that arithmetic manually.

What a better process looks like

The better version of external group meeting coordination for event producers is one that reduces the producer's active involvement to a single step: adding participants and setting the scheduling window.

Participants receive a personal link and connect their calendar — Google or Microsoft — in under a minute. The scheduling system reads everyone's free/busy availability directly — never event titles, attendees, or any other meeting detail — identifies the best slot across all timezones, confirms the meeting, and sends calendar invites automatically. Participants who haven't connected their calendar receive automatic reminders.

The producer doesn't monitor who has responded. They don't do timezone arithmetic. They don't write confirmation messages or build calendar events. They add the participants and wait for the meeting to confirm itself.

For forty or fifty sessions across an event cycle, the difference between this process and the manual version is the working week that goes back to the work that actually builds the programme.

The same principle applies beyond event production to any professional who regularly coordinates external meetings across different organisations and calendar systems — recruiters managing panel interviews, consultants bringing client groups together, lawyers coordinating multi-party calls. The problem is the same. So is the solution.

Read next

Whenn handles the entire coordination process — automatically.

Add participants by email, they connect their calendar, AutoWhenn finds the best slot and sends everyone an invite.