Conference speaker scheduling: the coordination problem nobody talks about

I work as a conference producer. One of the less glamorous parts of the job is getting a panel of senior industry figures onto a call together before the event. Briefing calls, planning sessions, prep meetings. They all need to happen, and they all need to be coordinated.

This sounds manageable. It rarely is.

The panel that took two weeks

Last year I was trying to set up a planning call with five speakers. California, New York, London, Germany, and Beijing.

I sent the first availability email on a Monday. The last confirmation came through on the Friday of the following week. Two weeks, give or take, for a one-hour call.

The timezone spread was brutal. California to New York is three hours. New York to London is five. London to Germany is one. California to Beijing is fifteen — which means that by mid-afternoon on the West Coast, it's already the early hours of the following morning in China.

Every time someone replied with their availability, I had to work out whether it actually overlapped with everyone else. Every time I proposed a slot, at least one person had already told me that week wasn't good. So I'd adjust, recalculate, and go again.

We did eventually find a time. But only because our speaker in Beijing offered to join before dawn. That's not a scheduling success — that's someone doing us a favour.

Two weeks of emails, timezone calculations, and revised proposals. And it still only worked because one person agreed to set an alarm for before dawn. The back-and-forth didn't go away. It just eventually stopped.

Why this doesn't get easier

I've done this dozens of times. It doesn't get faster. Every new panel is a different combination of people with different constraints and different weeks. The problem resets from scratch every time.

Most scheduling tools aren't much help here either. They're built around one person sharing their availability with one other person. Clean, simple, solved. But coordinating five people from five different organisations across five timezones isn't a single-person problem. It's a logistics problem, and it still gets solved the same way it always has — one human, reading emails, doing the maths by hand.

Nobody in the industry really talks about how much time this costs. It just gets absorbed. Another thing on the list, another afternoon eaten up by availability emails and timezone calculations.

What I've taken from it

A few things, after enough of these:

Never say "morning" without specifying whose. Someone will always assume it means theirs.

The person joining at an awkward hour to accommodate everyone else deserves acknowledgement. It's easy to overlook when you're the one who sorted it.

And the coordination overhead of setting up a group meeting across organisations is real, measurable, and mostly invisible. It doesn't show up on a project plan. It just shows up as time that's gone.

It's also, largely, a solved problem — just not by most of the tools that claim to solve it.

That's what Whenn was built to fix. If any of this sounds familiar, it's worth a look: meetwhenn.com.

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.