Schedule a meeting across time zones
Scheduling across time zones is hard because everyone thinks in their own local time. Overlap handles the conversion automatically: everyone sees the grid in their own timezone, and when two people paint the same row they’re agreeing on the same instant.
How it works
- Create the event in your timezone. Pick the dates and times you’re considering. The app detects your timezone and uses that as the starting point.
- Everyone sees their own times. When you share the link, each person sees the grid in their local time. A row that says "Monday 9:00" for someone in London says "Monday 4:00" for someone in New York.
- Availability syncs automatically. When two people in different time zones paint the same row, they’re agreeing on the same moment — the times are already converted behind the scenes.
- The calendar invite is correct for everyone. When you pick a time and send the invitation, each person’s calendar shows the meeting at the right hour for their timezone.
Schedule across time zonesFree. No account. Works now.
Why time zones make scheduling hard
Asking "can everyone do 2pm?" in a group chat breaks down when half the group is in Europe and half is in America. 2pm is a different hour for everyone, so the person answering has to ask "2pm where?" and then do the conversion themselves. By the third person, half the replies are wrong.
A shared grid solves this because everyone sees the times they understand — their own — and the app handles the conversion. Nobody has to remember whether London is 5 or 6 hours ahead right now, or whether daylight saving has switched yet.
What makes Overlap good for multi-timezone scheduling
Automatic timezone detection. The app detects each person’s timezone from their browser and draws the grid in that time. No settings, no asking where everyone is.
Manual timezone picker. If someone is travelling or planning ahead, they can change their timezone manually. The grid redraws instantly.
Everything is absolute UTC underneath. When you paint a row marked "2pm" in New York and someone else paints the same row marked "7pm" in London, the system records the same absolute moment. There is no ambiguity and no drift.
Calendar invites work correctly. When you send the invitation, each person’s calendar entry shows the meeting at the correct local time, even if they’ve moved timezone between answering and receiving the invite.
Common time zone scheduling mistakes
Asking for times in one timezone only. "Can everyone do 3pm GMT?" forces half the group to convert, and someone will get it wrong.
Listing candidate times in multiple timezones. "2pm New York / 7pm London / 8pm Paris" is clear but doesn’t scale past three people, and one wrong conversion poisons the whole list.
Assuming everyone knows the offset. Most people don’t know whether the UK is 5 or 6 hours ahead of New York off-hand, and daylight saving makes it worse. Tools that make you calculate offsets get answered slowly or wrong.
When to use Overlap vs asking in the chat
If everyone is in the same timezone, a quick chat message works fine. Use Overlap when the group is spread across time zones, especially if there’s more than one conversion to do. A grid that shows everyone their own times is faster and less error-prone than a thread full of offset arithmetic.
Compared to other scheduling tools
Many scheduling tools show times in one fixed timezone and leave the conversion to the participants, which is exactly the problem you’re trying to avoid. When2meet and Doodle both support timezones, but neither sends the calendar invitation — the organiser still has to make the entry and hope everyone adds it correctly in their own timezone.
Try it with your next meetingFree. No sign-up.
