Calendar Best Practices for Remote and Hybrid Teams

Always create events in the organiser's local timezone using the IANA name — not a fixed UTC offset. Calendar apps will automatically convert to each invitee's local time when they open the invite. If you use UTC offsets (e.g. 'UTC-5'), the event will shift when DST transitions happen and your recurring Monday standup will suddenly appear at the wrong time.

Include the time zone name in the event title or description as a fallback — e.g. '(10:00 America/New_York)' — so people can double-check without opening the event details. This is especially useful when someone receives a forwarded invite outside their calendar app, or when joining from a personal device that may have the wrong timezone set.

A 15-minute reminder works fine for an office meeting. But for a colleague joining at 11 PM, a 30-minute reminder lets them wrap up their evening and prepare properly. Consider setting reminders at both 1 hour and 10 minutes for cross-timezone calls.

For recurring meetings, review the full series after each DST transition (March and November for US, March and October for EU). Some calendar apps handle this gracefully; others require manual updates to the series. A five-minute audit twice a year saves hours of confusion.

Block focus time just as you would a meeting. When teammates in other timezones see your calendar is full, they'll look for other slots rather than booking over your deep-work time. Name these blocks clearly — 'Focus: Deep Work' or 'Do Not Book' — so collaborators understand the intent.

Keep ZoneMeets open while scheduling. The five seconds it takes to glance at live clocks before sending an invite has saved countless hours of rescheduling. Make it a habit: open ZoneMeets first, find your window, then open your calendar.

Use Google Calendar's 'Working hours' or Outlook's 'Work hours' feature to publish your available window. Automatic 'outside working hours' warnings when someone tries to book you make it easy for collaborators to self-correct without you needing to decline and explain.

A recurring event follows the time zone it was created in. If the organizer in Singapore, where clocks never change, creates a weekly call, it stays at the same Singapore time all year, and attendees in London and New York will see it jump by an hour when their clocks change. If the organizer is in New York, the call stays fixed in New York time and the Singapore attendees see it move.

Neither is wrong, but the choice should be deliberate. A good rule is to create the series in the time zone of the largest group of attendees, or of the people with the least flexibility, and to say so in the description: 'This series follows New York time and will shift by one hour for Asia in March and November.' That single sentence prevents a round of confused messages twice a year.

Both Google Calendar and Outlook can show a second time zone alongside your own in the week view, which turns every scheduling decision into a side-by-side comparison. Add the home city of your most frequent collaborators, label it with a city name, and you will stop converting in your head. Set your own working hours as well, so colleagues get a warning when they try to book you outside them. When you need to compare more than two regions, a dedicated converter such as ZoneMeets makes the overlap visible at a glance before you open the calendar at all.

A shared calendar works best when it carries information people would otherwise have to ask for:

• Public holidays for every region on the team.
• Planned leave and out-of-office days.
• Recurring team meetings, each noting which time zone anchors the series.
• Release and launch dates, written in UTC.
• On-call handoff times, also in UTC, so they do not drift with daylight saving.

Keep it owned by one person or rotating role, and review it monthly so it does not fill up with stale entries.

A good invite answers the questions attendees would otherwise send back: what the meeting is for, what decision or outcome is expected, what to read beforehand, how long it will last, where to join, and whether it will be recorded. Give the start time in the organizer's named time zone and in UTC. Keep the default length short; a thirty-minute slot that ends on time is worth more than an hour that fills itself. If someone is joining outside their normal hours, say so and offer a recording as an alternative.

Ten minutes once a month keeps a calendar trustworthy. Delete recurring series that no longer have a purpose. Check whether any region changes its clocks in the next month and note which meetings will move. Look at the coming holidays for each region and move or cancel anything that lands on one. Finally, look at who has taken the most off-hours meetings in the past month and offer them the easier slot next time.