Time Zone Guide for Remote Teams — US, UK, India, Australia (2026)

Before we get into overlaps, here's what we're working with. Each location's offset from UTC changes depending on whether daylight saving time is active.

Notice that India and Western Australia don't observe DST. And Australia's DST runs opposite to the Northern Hemisphere — clocks go forward in October and back in April. This means the US-Australia gap is at its widest during Northern Hemisphere winter (when the US falls back but Australia springs forward).

This is the most common three-way combination for tech teams. Here's the overlap during Northern Hemisphere summer (EDT + BST active):

The three-way window is roughly 7:00–8:30 AM Eastern / 12:00–1:30 PM UK / 4:30–6:00 PM India. That's about 90 minutes. During winter (EST + GMT), the window shifts: 7:00 AM EST = 12:00 PM GMT = 5:30 PM IST, and 8:00 AM EST = 1:00 PM GMT = 6:30 PM IST. You lose half an hour because the US-India gap widens.

Here's where it gets brutal. When it's 7:00 AM in New York during summer, it's midnight in Sydney (AEST, no DST in summer). Nobody's taking a midnight call.

The uncomfortable truth is that a four-way overlap across US, UK, India, and eastern Australia does not exist during normal business hours. The US-Australia gap alone is 14–16 hours depending on season. When it's daytime in New York, it's the middle of the night in Sydney, and vice versa.

Teams that span all four regions typically use one of these strategies:

Strategy 1: Two overlapping meetings. Hold one sync at 7:30 AM ET / 12:30 PM UK / 5:00 PM IST (without Australia). Hold a second at 8:00 PM ET / 10:00 AM AEST next day (without UK/India). Someone in each meeting shares notes with the other group.

Strategy 2: Async-first with one sacrifice slot. Default to async communication (recorded Looms, shared docs, threaded chat). When you must meet live, rotate who takes the inconvenient hour. One week it's early morning for the US + UK and evening for India + Australia. Next week, flip it.

Strategy 3: The 6 AM / 8 PM split. Some teams find a slot around 6:00 AM US Eastern / 11:00 AM UK / 3:30 PM India / 8:00 PM AEST. It's not ideal for anyone — early for the US, late for Australia — but everyone is at least awake. This only works during Australian DST (AEDT, October–April) when Sydney is UTC+11 instead of +10.

The overlap isn't static. Here's how the US-UK-India three-way window moves through the year:

The summer window is wider (90 minutes) because the US and UK are both on daylight saving, keeping them only 5 hours apart instead of 5. In winter, the three-way window shrinks to about an hour.

Core hours model. Define 2–3 hours per day where everyone overlapping must be available. For US-UK-India, that's typically 7–9 AM ET. Outside those hours, people work whenever they're most productive. This respects the fact that a developer in India shouldn't have to be online at 11 PM just because someone in California wants a 1 PM meeting.

Follow-the-sun handoffs. Instead of forcing synchronous overlap, structure work so that India hands off to UK, UK hands off to US, US hands off to Australia. Each team picks up where the last left off. This works well for support, DevOps, and any process that benefits from 24-hour coverage.

Meeting-free days. If you only have 60–90 minutes of overlap, protect it. Designate two or three days per week as meeting-free, and batch all syncs into the remaining days. You'll have fewer but more focused meetings, and people get uninterrupted deep work time on the off days.

The dirty secret of distributed teams: most meetings should have been a recorded Loom or a well-structured Slack thread. When your overlap window is 90 minutes, every meeting that could've been async is stealing from the few synchronous minutes you have.

What works async: status updates (use a daily standup bot instead of a live meeting), code reviews, design feedback on mockups, decision-making where people need time to think (write an RFC, give 24 hours for comments, then decide). What genuinely needs sync: brainstorming sessions where ideas build on each other, conflict resolution, onboarding new team members, and anything where tone matters more than content.

The best distributed teams treat their overlap hours like a scarce resource. They have a standing rule: if it doesn't require real-time interaction, it goes async. The overlap window is reserved for things that actually benefit from everyone being in the same virtual room at the same time.

Doing UTC arithmetic by hand is error-prone, especially with half-hour offsets like India's +5:30 and Nepal's +5:45. A time zone converter lets you plug in multiple zones and see the exact local time for each person. It accounts for DST automatically based on the date you select.

When you're coordinating calls between the US and India specifically, the US-India calling guide has detailed hour-by-hour tables for every US time zone.

Is there any hour where US, UK, India, and Australia are all in business hours?
Not during standard 9–5 hours. The closest you can get is a slot around 6:00 AM Eastern / 11:00 AM UK / 3:30 PM India / 8:00 PM Sydney, and that only works during Australian daylight saving time (October–April). Someone is always outside normal hours.

Which countries don't observe DST?
India, China, Japan, South Korea, Singapore, and most of Africa and South America. A full list is maintained in the IANA Time Zone Database. Scheduling with these countries is simpler because their offset from UTC never changes.

Why does India have a half-hour offset?
IST (UTC+5:30) was chosen in 1947 as a compromise between Kolkata time (UTC+5:54) and Mumbai time (UTC+4:51). The half-hour puts the solar noon roughly in the center of the country. Nepal goes further with UTC+5:45, and the Chatham Islands use UTC+12:45.

How do I handle a team member in Arizona?
Arizona doesn't observe DST (except the Navajo Nation). During winter, Arizona matches Mountain Standard Time (UTC-7). During summer, the rest of Mountain Time springs forward to UTC-6, but Arizona stays at UTC-7 — so it effectively matches Pacific Daylight Time. Double-check with a converter before assuming.

Do the UK and EU change clocks on the same date?
Yes, currently. Both observe summer time from the last Sunday in March to the last Sunday in October, governed by EU Directive 2000/84/EC. The EU proposed abolishing DST changes in 2019, but the legislation has stalled. If it ever passes, the UK may or may not follow suit since it left the EU.