What is time zone overlap?

It is the part of the working day when people in different time zones are both at work, so they can collaborate in real time. Outside that window, work is handed off and answered later.

How many hours of overlap do remote teams need?

There is no universal number. Decide which tasks need live interaction, agree a window that covers them, and measure missed handoffs and delayed decisions. Roles with frequent decisions need more shared time than roles with clear written briefs.

How do I calculate overlap between two locations?

Convert both sets of working hours to UTC for the actual dates, then find the hours they share. Remember that some countries change their clocks and others do not. The Time Zone Overlap tool on this site does the calculation.

Does daylight saving time change the overlap?

Yes. Where one location changes its clocks and the other does not, the gap changes by an hour. Different countries also change on different dates, so the gap can differ for part of the year. For example, India stays on UTC+5:30 all year, while New York moves between UTC-4 and UTC-5.

How do you make low-overlap teams work?

Use complete written briefs, name who decides, document handoffs, agree response times and protect the shared window for discussion. Agree any shifted hours openly and check the working-time rules that apply rather than extending someone's day by default.

Should I require offshore staff to work my hours?

Only by agreement. Shifted hours should be discussed in advance, be lawful where the person works, and be sustainable. Model the proposed schedule on real dates before assuming it creates the overlap you want.

Which roles can work with little overlap?

Roles with clear written briefs and defined outputs, such as data entry or content production, can often work with limited overlap. Roles that depend on frequent discussion, such as pair programming or live customer support, need more. Test with a trial before committing.

Is time zone overlap more important than cost?

It depends on the work. For collaborative roles, poor overlap can cost more in delay than it saves in pay; for work that can be documented and handed off, overlap matters less. Compare scenarios in the Remote Hiring Cost Calculator and the Time Zone Overlap tool.

Time Zone Overlap for Remote Teams

What time zone overlap is

Time zone overlap is the set of hours in a day when working hours in two or more locations coincide, so people can talk, decide and review work in real time. Outside that window, people work asynchronously: one person leaves information and the other responds later. How much overlap you need depends on the work, not on a universal number.

To find the overlap, convert each person's working hours to one reference time, usually UTC, and take the hours that both share. Do it for actual dates, because clocks change in some countries and not in others. Our Time Zone Overlap tool does the calculation for you and shows the shared window for any pair of locations.

Why the date matters: daylight saving

The time difference between two places can change during the year. India observes India Standard Time, UTC+5:30, all year with no daylight saving. Colombia likewise observes Colombia Time, UTC-5, all year. The United States, by contrast, moves between standard and daylight time: New York is on Eastern Daylight Time, UTC-4, as of 13 October 2026, and returns to Eastern Standard Time, UTC-5, later in the year. On that date timeanddate.com shows New York 9 hours 30 minutes behind New Delhi, and the gap becomes 10 hours 30 minutes when New York moves back to standard time.

In winter the UK is on Greenwich Mean Time (UTC+0), and in summer on British Summer Time, one hour ahead. The clocks go forward on the last Sunday in March and back on the last Sunday in October: on 29 March and 25 October in 2026, and on 28 March and 31 October in 2027, per GOV.UK. Countries change on different dates, so the gap between two places can differ for part of the year. Check the actual dates for any schedule you commit to.

Examples of offsets

These examples, from timeanddate.com pages checked on 13 October 2026, show how different places relate to US Eastern time. Use them to understand the idea, then check the offsets for your own cities and dates.

Colombia: UTC-5 all year. Same as US Eastern Standard Time, and one hour behind US Eastern Daylight Time.
Mexico: the country has three time zones. Mexico City is on UTC-6, and Mexico abolished daylight saving time in most of the country on 30 October 2022, although most municipalities near the northern border follow the United States schedule. Pick the city before calculating.
Brazil: São Paulo is on Brasília Time, UTC-3.
India: UTC+5:30 all year; 9 hours 30 minutes ahead of New York while New York is on daylight time.
Philippines: Manila is UTC+8, 12 hours ahead of New York while New York is on daylight time.

For a pair of places with a large difference, there may be little or no overlap in ordinary working hours. One side then has to shift its hours, or the work has to be organised so that handoffs replace live conversation.

How much overlap different work needs

Work that needs more live contact

Pair programming, joint design reviews and other interactive problem solving.
Customer-facing roles such as live chat or phone support, which must match customer hours.
Executive and administrative support that depends on same-day coordination with a manager.
Teams with frequent dependencies and short decision cycles.

Work that needs some live contact

Developers on teams that hold regular stand-ups and reviews.
Marketing and project work with frequent approvals.
Finance and accounting around approvals, close deadlines and exceptions.

Work that tolerates little live contact

Tasks with a clear written brief and a defined output, such as data entry or content production.
Background processing and routine administration with scheduled check-ins.

These groups are guidelines. A role's real need depends on how often decisions are needed, how clear the brief is and how mature your documentation is. Test the arrangement with a trial period and measure delays rather than assuming.

A worked example

This example is calculated by this site from the offsets above; replace the hours with your own. Suppose a business in New York works 9:00 to 17:00 Eastern Daylight Time (UTC-4), which is 13:00 to 21:00 UTC.

A worker in Colombia on 8:00 to 16:00 local time (UTC-5) is working 13:00 to 21:00 UTC, so the overlap is the whole day.
A worker in India on 9:00 to 17:00 India Standard Time (UTC+5:30) is working 03:30 to 11:30 UTC, so there is no overlap in ordinary hours.
If the India-based worker moves to 15:30 to 23:30 IST, that is 10:00 to 18:00 UTC, and the overlap with New York is 13:00 to 18:00 UTC, or 9:00 to 14:00 in New York. The cost is a working day that ends late in the evening in India, which has to be agreed and sustainable.
A worker in Manila on 9:00 to 17:00 (UTC+8) is working 01:00 to 09:00 UTC, so there is no overlap in ordinary hours either.

The exercise shows that a nearby location can overlap with no change to anyone's hours, while a distant one only overlaps if someone moves their day. That is the central trade-off, and why the next sections matter. Before you commit, run the same calculation for your own cities and for the dates when either side changes its clocks, and ask the candidate how a shifted schedule would fit their other commitments.

Agreeing a schedule

Write the core hours in one reference time zone and state it, so everyone reads the same schedule.
Use the same reference time for deadlines and for measuring response targets in a service level agreement.
Record each person's local public holidays and leave. The leave comparator shows how entitlements differ between countries.
Review the schedule when clocks change in either location.

Meetings across time zones

Keep live meetings for the topics that need them: kick-offs, sensitive conversations and decisions that are hard to settle in writing. Circulate an agenda in advance, record the meeting or take notes, and publish decisions afterwards so that people who could not attend are not left behind. Rotate the inconvenient slot so the same people are not always asked to join early or late.

Making low overlap work

Protect the shared window: use it for decisions and discussion, not for solo work or status updates.
Write things down: decisions, requirements and context in a shared place. See asynchronous communication.
Make handoffs explicit: end each day with notes on what was done, what is blocked and what comes next. See follow-the-sun.
Set response expectations: say how quickly each kind of message should be answered, and how to reach someone urgently.
Name decision owners and deadlines: so work does not wait for a meeting that cannot happen.
Share the inconvenience: rotate awkward meeting times instead of always asking the same location to stretch.
Agree shifted hours openly: if someone works outside normal local hours, agree it in advance, check the working-time rules that apply, and make it sustainable.

Our guide to managing remote teams across time zones goes through the practices in more detail.

Overlap, cost and talent

Overlap is one of three variables to weigh when choosing where to hire, alongside cost and the depth of the local talent pool. A location with strong overlap may cost more for a given role, and a location with low overlap may suit work that can be handed off. Neither is correct for every role. Compare real figures in the Remote Hiring Cost Calculator and the salary benchmark explorer, and see offshoring vs nearshoring for the main trade-offs. If you use more than one location, read multi-shore strategy.

Sources

References checked on 13 October 2026. Clock rules change, so verify offsets for the dates you plan to work. This page is general information, not legal or tax advice.

Time Zone Overlap

Definition