Meeting Time Planner: Finding a Time That Works for Everyone

Scheduling a meeting across time zones is one of those tasks that looks trivial until three people in three cities are involved. A time that is a comfortable mid-morning for one person is lunch for another and late evening for a third, and a careless invitation can land at midnight for someone who was only supposed to listen in. The confusion grows because clock times are local: "2 pm" means nothing on its own. It only becomes a real moment in time once you attach a place to it. The Meeting Time Planner does that work by showing the same moment in each participant's local time, so you can see the overlap window where everyone is awake, working, and reasonably alert, instead of guessing from memory.

The core idea is simple: do not look for a time that suits one person and hope the rest can adapt. Look for the window where all the working days overlap, then pick the best moment inside that window. For teams spread across neighbouring zones, that window is wide and the choice is easy. For teams spread across the globe, the window may be narrow, or it may not exist at all on a normal working day. In that case the honest answer is to rotate the inconvenience, split the meeting, or replace it with written updates. A planner makes that trade-off visible instead of leaving one person to silently absorb every awkward slot. Fairness in scheduling is not just politeness; it affects who can contribute well, and a participant joining at midnight will not contribute as well as one joining at mid-morning, however dedicated they are.

How time zone overlap works

Every participant has a working window, typically something like 9 am to 5 pm local time, and the overlap is the set of moments that fall inside everyone's window at once. To find it, convert each person's window into a single reference, such as Coordinated Universal Time (UTC), and look for the shared stretch. The size of the overlap depends on the spread between the earliest and latest zones. If the spread is eight hours or less, a comfortable overlap usually exists. If the spread is twelve hours or more, the overlap shrinks to an hour or two at the edges of the day, and someone will be starting early or finishing late. If the spread approaches a full day, as with participants on opposite sides of the globe, there may be no overlap within normal hours at all, and the meeting needs a different design.

Daylight saving time is the trap that catches even experienced schedulers. Zones do not all change their clocks on the same date, and some zones do not change at all, so the difference between two cities can shift by an hour for a few weeks each year. A recurring meeting that worked perfectly in winter can suddenly start an hour early or late for one group in spring. A planner that uses real zone rules handles this automatically, but you should still double-check the first meeting after a clock change, and always send invitations that carry the time zone with them. A calendar invitation that says only "2 pm" without a zone is an accident waiting to happen; an invitation that says "2 pm London time" can be converted correctly by every recipient's calendar.

Planning a fair meeting

Start by listing every participant and their city, not just their country, because large countries span several zones. Then define what counts as acceptable: a core working window for most people, with a small amount of flex at the edges if needed. Rank the candidate slots by how many people fall inside their core window, and treat a slot that pushes someone outside working hours as a cost, not a detail. If the meeting recurs, rotate that cost. One week the early slot can fall to one region, and the next week it can fall to another, so no single group always bears the awkward hour. Rotation is a small administrative effort that pays for itself in goodwill and in the quality of contributions from people who are not exhausted.

Also consider whether the meeting needs everyone at once. Many meetings have a core group that must decide and a wider group that only needs the outcome. Splitting the meeting, or holding a short decision session followed by a written summary, can remove the hardest scheduling problem entirely. Shorter meetings are also easier to place: a thirty-minute slot fits into a narrow overlap window far more easily than a ninety-minute one. When you combine a tight agenda with a short duration and a fair slot, attendance improves, punctuality improves, and the meeting itself tends to stay focused, because everyone knows the window is precious.

Worked example with sample values

Suppose a sample team has three people: one in New York, one in London, and one in Dubai. Use the sample zone differences: London is 5 hours ahead of New York, and Dubai is 4 hours ahead of London, which makes Dubai 9 hours ahead of New York. Consider a candidate slot of 14:00 to 16:00 London time. Convert it step by step. Subtract 5 hours for New York: 14:00 minus 5 hours is 09:00, and 16:00 minus 5 hours is 11:00, so the slot is 09:00 to 11:00 in New York. Add 4 hours for Dubai: 14:00 plus 4 hours is 18:00, and 16:00 plus 4 hours is 20:00, so the slot is 18:00 to 20:00 in Dubai. All three conversions describe the same two-hour window, just read on different clocks.

Now judge the slot. New York at 09:00 to 11:00 is a strong morning slot. London at 14:00 to 16:00 is a solid afternoon slot. Dubai at 18:00 to 20:00 runs into the evening, which is acceptable occasionally but tiring as a weekly pattern. A fairer alternative might be 13:00 to 14:00 London time: that is 08:00 to 09:00 in New York and 17:00 to 18:00 in Dubai, which shortens the Dubai evening stretch but asks New York to start earlier. Neither slot is perfect, and that is the point: the planner does not hand you a perfect answer, it shows you the trade-off clearly so the team can choose it deliberately and rotate it fairly, rather than discovering it by accident when someone joins from home at night.

Common mistakes to avoid

The first mistake is sending a time without a zone, which guarantees confusion for at least one recipient. The second is assuming the zone difference never changes, which daylight saving will eventually punish. The third mistake is always placing the meeting at the organiser's convenience and never rotating an awkward slot, which quietly burns out the distant team. The fourth is inviting the whole group to a meeting that only a few people need, which multiplies the scheduling problem for no benefit. The fifth is forgetting the date line: a meeting on Monday evening in one city can be Tuesday morning in another, and a date that looks right in one place can be wrong in the other. Always check the date as well as the time for every participant. Finally, do not schedule back-to-back across zones without breaks. A participant who finishes one call at midnight and starts another at 1 am is not really attending either of them well.

Try it next

Plan your next cross-zone meeting with the Meeting Time Planner, then check the countdown and working-day side with the Date Countdown Timer and the Working Days Calculator. For a related read on working with dates, see the guide at /blog/date-calculator-guide/. State the zone in every invitation, rotate any awkward slot, and keep the meeting as short as the decision allows: those three habits remove most scheduling friction before it starts.