Time Zone HQ
12h
24h
-- -- ------:--:--
Work & Travel

Time Zone Etiquette for Remote Teams

Time zone etiquette is the collection of small habits that make distributed teams feel respectful and functional rather than thoughtless and exhausting. Most of the rules are simple once you internalize the underlying principle: always consider the local experience of the person receiving your message or meeting invite.

Always Specify the Time Zone

The cardinal rule: never write a time without a time zone. '3 PM' is ambiguous for anyone not in your location. Write '3 PM ET' at minimum, '3 PM ET (UTC−5)' when writing to an international audience, or '15:00 UTC' for technical communications where precision matters.

Better still: add the local time for the recipient. '3 PM ET / 8 PM London / 9 PM Paris' removes any calculation burden and signals that you thought about the other person's schedule. Calendar tools that show the meeting time in each invitee's local zone are valuable for exactly this reason.

Don't Make People Do the Math

When proposing meeting times, offer 2–3 options converted to the other person's time zone, not just yours. 'Would 9 AM PT / 5 PM London or 7 AM PT / 3 PM London work for you?' is considerate. 'I'm free from 7–10 AM PT' forces the other party to do arithmetic and look up the current offset — a small friction that signals you haven't thought about their experience.

Avoid Last-Minute Scheduling

A meeting invite sent 30 minutes before the call is disruptive for anyone in the same office. For someone in a different time zone who is already 3 hours into their evening, it can mean scrambling to find a quiet space or missing the call entirely. Give at least 24 hours' notice for non-urgent meetings, and 48–72 hours when participants span multiple continents.

← Back to all articles
Help us make this better!