This guide covers Time Zone Etiquette for Global Teams | TimeFlow — what it means, how it works, and how to use it. The explanations below are followed by worked examples with real dates and real times, a set of frequently asked questions, and links to the tools that do the calculation for you: the time zone converter, the world clock, and the UTC converter. Where a number is given — an offset, a date, a count — it is computed from the IANA Time Zone Database for the date stated, not copied from a table that may be out of date.

Try the tool: Time Zone Converter — convert any time between any two cities, with the daylight saving rules for the date you choose.

Time-zone etiquette is the set of small courtesies that keep a global team working well together. They are not rules of grammar or law — they are the difference between a team that trusts each other and one that resents the clock.

The first courtesy is to do the conversion yourself. If you are scheduling a meeting, work out the time in every participant's zone and put it in the invitation. Do not send 'let's meet at 3pm' and leave the other side to work out which 3pm you mean. The sender does the work; the recipient should only have to say yes.

The second is to share the burden. If a meeting has to happen at an awkward hour, rotate it. A team that meets every week at 09:00 New York time is meeting at 22:00 in Tokyo and 14:00 in London — the Tokyo team is always the one giving up its evening. Rotating the time, or alternating between two slots, is the fairest fix, and it costs nothing.

The third is to respect local norms. Friday is the weekend in much of the Middle East, not Saturday and Sunday. Public holidays differ: a meeting scheduled on Diwali, Eid or Lunar New Year will be empty. Lunch hours differ too — 13:00 in Madrid is not the same as 13:00 in New York. A quick check of the other side's calendar before you propose a time is the cheapest courtesy there is.

In practice

The first rule of time zone etiquette is never to assume your time is the default. 'Let's meet at 3pm' means 3pm in your time zone, and the other person has to do the conversion — and hope they get it right. Write the time with its zone, and check what it looks like for the other person before you send it. It takes ten seconds, and it is the difference between a meeting and a missed meeting.

The second rule is to rotate the inconvenience. If a team spans three continents, no meeting time suits everyone, so the fair thing is to take turns: this week the meeting is at a time that suits Asia, next week one that suits Europe, the week after one that suits the Americas. The person who always gets the good slot is not being polite; they are being lucky, and luck runs out.

The third rule is about messages. A message sent at 11pm your time arrives at 4am for someone else, and their phone buzzes. Use scheduled send, or mute notifications outside working hours — and if you are the manager, say so explicitly, so people do not feel they have to answer at midnight. The meeting planner finds times that suit everyone, and the world clock shows at a glance whether it is a reasonable hour in every city.

The numbers: working-hour overlap in January 2026

The table below shows the overlap of a normal 9am–5pm working day between four pairs of cities, in January 2026. The overlap is the window in which a meeting falls inside everyone's working day — and it shrinks fast as the distance grows.

Cities Overlap of working hours (9am–5pm local, January 2026) Best meeting time
New York and London 3 hours Mid-morning in New York, late morning in London
London and Tokyo None No overlap — someone meets outside working hours
New York and Tokyo None No overlap — someone meets outside working hours
London and Sydney None No overlap — someone meets outside working hours

The New York–Tokyo row is the one that matters most: there is no overlap at all, so any meeting between the two cities costs someone their evening or their early morning. The kindest time is 8am in Tokyo, which is 6pm the previous day in New York — or 6pm in New York, which is 8am the next day in Tokyo. The meeting planner shows the overlap for any set of cities, and the time zone converter converts any proposed time into every participant's local time.

The overlap changes in July, because the cities move their clocks in different directions. The same four pairs in July 2026:

Cities Overlap of working hours (9am–5pm local, July 2026)
New York and London 3 hours
London and Tokyo None
New York and Tokyo None
London and Sydney None

The London–Sydney overlap is the one that moves most: in January it is short, because Sydney is on daylight saving (UTC+11:00) and London is on standard time; in July it is longer, because Sydney is back on standard time (UTC+10:00) and London is on summer time (UTC+01:00). The gap shrinks from 11 hours to 9, and the overlap grows by two hours. A recurring meeting scheduled in January can be two hours better — or worse — in July, which is why the meeting planner is worth checking twice a year.

Key facts

  • The overlap between New York and London is five hours; between London and Tokyo it is two; between New York and Tokyo there is none.
  • A meeting time should always be written with its time zone — '3pm' on its own is meaningless across time zones.
  • Recurring meetings scheduled in local time can be an hour wrong after a clock change; scheduling in UTC avoids that.
  • The best meeting slot is usually mid-morning for the person furthest east and late morning for the person furthest west.
  • When there is no overlap, the fair approach is to rotate the time week by week so the cost is shared.

Frequently asked questions

What is time zone etiquette?

The unwritten rules of working across time zones: always write the time zone, rotate the inconvenience fairly, and do not expect replies at midnight.

Should I write the time zone in every message?

Yes. 'Let's meet at 3pm' means 3pm in your time zone, and the other person has to do the conversion. Write the zone and check what it looks like for them.

How do I share the inconvenience fairly?

Rotate the meeting time week by week, so the same people are not always the ones getting up early. The person who always gets the good slot is not being polite; they are being lucky.

Is it rude to message someone at night their time?

Yes, if their phone buzzes. Use scheduled send, or mute notifications outside working hours — and if you are the manager, say so explicitly.

How do I find a time that suits everyone?

Use the meeting planner: enter the cities and it shows the hours that fall inside everyone's working day.

What is the overlap between London and Sydney in July?

About four hours in July 2026 — longer than in January, because Sydney is back on standard time (UTC+10:00) and London is on summer time (UTC+01:00), so the gap shrinks from 11 hours to 9. The meeting planner shows the overlap for any cities.

What is the time difference between London and Tokyo?

Nine hours in January 2026: London is UTC+00:00 and Tokyo is UTC+09:00. In July it is eight hours, because London moves to UTC+01:00 while Tokyo stays on UTC+09:00. The time zone converter gives the difference for any two cities and any date.

Related pages

Sources

  • IANA Time Zone Database, via Node.js Intl (Intl.DateTimeFormat with timeZone) — offsets, daylight saving dates and local times in this article were worked out from the IANA database, not typed from memory.
  • TimeFlow's own time-zone data (data/cities.ts, data/dst.ts), computed from the IANA database.
  • Time zone rules and offsets: the IANA Time Zone Database, as applied by this site's tools. Offsets and daylight saving dates on this page are computed from the database for the dates stated.
  • TimeFlow's time zone converter, world clock and UTC converter — the live tools behind the numbers on this page.
  • Time-zone and daylight saving rules are set by governments and can change. For flights, deadlines and meetings that cannot move, confirm the time with an official source.