Skip to content
Asian Leader HubPeer recognition and leadership discourse for Asia-Pacific executives

Time zone meeting planning for Asia-Pacific teams

Time zone meeting planning starts with one rule: pick the hours that suit the most people, then share the pain by turns. Teams in Singapore, India, Japan and Australia sit across up to four and a half hours of clock difference in August, and five and a half after Sydney changes its clocks. Without a method, the same people always join early or late.

Start with the offsets

Write every city as a distance from UTC, the world's common reference time. Singapore is UTC+8. India is UTC+5:30, a half hour step that many calendar tools get wrong by hand. Japan is UTC+9. Sydney is UTC+10 in winter and UTC+11 in summer.

India and Japan keep one offset all year. Singapore does too. Only Sydney changes, so it is the zone that causes surprises. Check Sydney every time you plan a call that falls near a clock change.

Source: IANA Time Zone Database, Asia and Australasia data files, https://ftp.iana.org/tz/data/asia and https://ftp.iana.org/tz/data/australasia

Know when Sydney changes

Sydney moves its clocks forward one hour on the first Sunday in October and back on the first Sunday in April. This year the change is on Sunday 7 October. From that day Sydney is UTC+11, so it is three hours ahead of Singapore instead of two. Japan to Sydney grows from one hour apart to two.

A call that suits everyone in August can drift out of fit in October. If Singapore, India and Japan keep the same clock time, the call lands an hour later for Sydney. Rebuild the schedule in the week before each change, and tell the whole team the new local times in writing.

Source: IANA Time Zone Database, Australasia data file, rule for New South Wales, https://ftp.iana.org/tz/data/australasia

Find the shared window

Lay out each city's normal working day, say 09:00 to 18:00, on one line in UTC. Then find where they overlap. In August the overlap for all four cities is small, but it exists. Start the window from the city that begins work last.

Here is the winter math. Say nobody should start before 08:30 or be on a call after 16:00 Sydney time. India at 08:30 is 11:00 in Singapore, 12:00 in Japan and 13:00 in Sydney. Sydney at 16:00 is 14:00 in Singapore, 15:00 in Japan and 11:30 in India. Sydney's late limit decides where the window closes.

  • India 08:30 to 11:30
  • Singapore 11:00 to 14:00
  • Japan 12:00 to 15:00
  • Sydney 13:00 to 16:00

Each line shows the same three hours in a different city. This is the shared window. Anything outside it costs someone a very early start or a late finish.

Pick the slot and rotate the burden

A good default is 12:00 in Singapore. That is 09:30 in India, 13:00 in Japan and 14:00 in Sydney. Nobody is up before breakfast, and only the lunch hour in Japan is touched. A second option is 13:00 in Singapore, which is 10:30 in India, 14:00 in Japan and 15:00 in Sydney.

If a meeting must fall outside the window, rotate it. Hold one call early for Sydney and Japan, then the next late for India. Keep a short log of who took the awkward slot last. Fairness is easy to see when it is written down, and hard to argue with.

Not every meeting needs live attendance. Record decisions in writing after the call. Send a short summary with the agenda first, so people who miss the slot can still add comments.

Share times without confusion

Always write the time with its city and the UTC offset, for example "12:00 Singapore time (UTC+8)". Never write "IST" alone, because that abbreviation can mean more than one zone. Put the date next to the time, since a morning meeting in Sydney can fall on the previous evening in India.

Use a calendar invite that converts time to each person's own zone. A free converter such as the one on timeanddate.com is handy for checking a slot before you send it. Check the invite once on the day it is sent, and again after any Sydney clock change.

A short checklist keeps the habit simple.

  • List every city as UTC offsets.
  • Note any clock change coming within four weeks.
  • Find the shared window.
  • Pick the slot and record who took the hard one last time.
  • Send the time with city, offset and date.

Source: timeanddate.com, World Clock and Time Zone Converter, https://www.timeanddate.com/worldclock/converter.html; IANA Time Zone Database, https://www.iana.org/time-zones

Sources

  • IANA Time Zone Database, https://www.iana.org/time-zones
  • IANA tz data, Asia, https://ftp.iana.org/tz/data/asia
  • IANA tz data, Australasia, https://ftp.iana.org/tz/data/australasia
  • timeanddate.com World Clock Converter, https://www.timeanddate.com/worldclock/converter.html