How to schedule meetings across time zones without doing the math

The reliable way to schedule across time zones is to stop doing the conversion yourself: show each person their own availability in their own zone, with their own working hours applied as a filter, and let the overlap do the work. Doing it by hand — converting one person's “free at 2pm” into everyone else's local time, by memory or a mental UTC offset — is where the wrong meeting gets booked. This guide covers why the manual math breaks, the stopgaps people reach for, and what a structural fix looks like for both one-on-one and group scheduling.

Why manual conversion fails

Three things make time-zone math harder than a fixed offset. First, daylight saving: the offset between two zones isn't constant through the year, and the clocks don't change on the same date in every country — Europe and the US shift DST on different weekends, so for a few weeks a pairing that's normally “6 hours ahead” is briefly 5, and a calculation done from memory is wrong exactly when it matters. Second, a raw offset says nothing about whether the time lands in someone's working day — 9am in one zone can be a perfectly normal start, while the equivalent slot for someone eight hours ahead is the middle of their evening. Third, “does 9am work for you?” is ambiguous the moment either person doesn't specify whose 9am they mean, and that ambiguity is exactly what produces the meeting someone joins an hour early or a day late.

The manual fixes people reach for

• A world clock.Keeping a second clock widget set to the other person's city gets you the current offset at a glance. It doesn't tell you whether 2pm their time is inside their working day, and you still have to do the arithmetic by hand for every proposed time.
• Writing both zones in every email.“2pm CET / 8am ET” in the invite removes the ambiguity for that one message, but someone has to compute it correctly each time, for every recipient, and it silently breaks the day the DST transition dates diverge.
• A shared spreadsheet of everyone's hours. Workable for a small, stable team, and stale the moment someone changes their hours, moves, or the roster grows — nothing keeps it in sync with reality.

All three are ways of doing the conversion yourself, more carefully. None of them remove the step where a human has to get the math right.

The structural fix: render in the viewer's own zone

The alternative is to never show a time in the wrong zone in the first place. On BusyBoard's public availability page, whoever is looking at the link sees the schedule rendered in their own browser's time zone automatically — there's no offset for either side to compute, because the conversion already happened before the page painted.

Zone conversion alone still isn't enough, though — a slot can be technically free and still be 6am for the person you're asking. That's what working hours are for: each person has a working-hours configuration per weekday (Monday–Friday 08:00–18:00 in their own zone by default), and time outside those hours is treated as unavailable rather than offered as an option. The two layers together — busy/free in UTC underneath, working hours and viewer zone applied on top — are what keep a “free” slot from ever being a slot nobody should actually take.

One-on-one: send the slot, not the offset

For a single external meeting, the same rendering rule replaces the “does 2pm work for you?” message. Instead of proposing a time in your own zone and asking the other person to do the conversion, a link to your availability shows them your open slots already translated into their zone and filtered to their own working hours where relevant, so what they see is a set of times that actually fit their day rather than a number they have to re-derive. Booking from that link is approval-first — you set a minimum notice, and a request lands for you to confirm rather than landing straight on your calendar — so the zone handling doesn't come at the cost of losing control over what gets booked.

Group scheduling across zones

The same problem compounds with more people: a slot that's inside working hours for three attendees can still be outside them for a fourth in a different zone, and manually cross-checking everyone's hours against everyone else's doesn't scale past a couple of people. BusyBoard's “Find a Time” does that cross-check for a group: it looks for slots where every member is simultaneously free andinside their own working hours, in their own zone, rather than one shared window that happens to suit whoever proposed it. The search runs over a 2-week window on the Free plan or an 8-week window on Pro, so a distributed team isn't limited to whatever overlaps in the next few days.

If you already know the manual routine well enough to be reading this, the faster fix is to stop running it by hand: connect a calendar and share a link that renders correctly for whoever opens it, wherever they are.