Scheduling Support Shifts Across the US, India and the Philippines: A Practical Guide

The core constraint: one side moves, the other two do not

India Standard Time is UTC+5:30 and Philippine Time is UTC+8, all year. The gap between your India and Manila sites is therefore a constant 2 hours 30 minutes, with Manila ahead. The US is the variable: Eastern, Central and Pacific time each shift by one hour on the second Sunday of March and the first Sunday of November. In 2026 those were March 8 and November 1; the next change is March 14, 2027.

Everything in this guide follows from that fact. Whatever you decide for your Asian staff, one of two things must give twice a year: either your agents' clock hours change by an hour, or the US hours you cover change by an hour. Operations that do not make that choice deliberately end up making it by accident, usually when someone notices on the first Monday after the change that the queue is unstaffed for sixty minutes at the start of the US day.

If you are looking only at one-off meetings rather than rosters, our guide to calling India from the US and the remote work time zone guide are better starting points. This page is about continuous coverage.

Coverage windows: US hours in IST and PHT

The table below converts two common US service windows, standard business hours (9 AM to 5 PM) and extended hours (8 AM to 8 PM), into Indian and Philippine time for each US zone. Winter means US standard time (November to March) and summer means US daylight time (March to November).

Read across any row and you can see the DST effect on its own: the US columns move, the IST and PHT columns for the same US hours move by exactly one hour. Reading down shows how much harder the Pacific zone is. A Pacific 9-to-5 shift in winter is 10:30 PM to 6:30 AM in India and 1:00 AM to 9:00 AM in Manila, which is effectively a full overnight roster for both sites.

For an Eastern-hours queue, India is the easier site in practice: the shift starts at 6:30 or 7:30 PM, a shift that is late but not past midnight at the start. Manila starts at 9:00 or 10:00 PM. Central hours are a half step later in both. You can check individual conversions with the EST to IST, CST to IST and PST to IST converters, and confirm the current Manila clock on the PHT time now page.

The DST problem and the two ways to handle it

Suppose an Eastern-time queue is staffed from India from 6:30 PM to 2:30 AM IST. While the US is on standard time that covers 8:00 AM to 4:00 PM Eastern. When the US moves to daylight time in March, the same agent hours cover 9:00 AM to 5:00 PM Eastern. Nothing changed in India, but the US day you are covering moved by an hour. There are two ways to respond.

Option 1: Fix agent hours, let US coverage move

The roster stays identical all year and employees enjoy predictable schedules. The cost is that your coverage sits one hour later on the US clock during daylight time (about eight months of the year) than during standard time (about four). In summer the first hour of the US day is uncovered, and in winter the last hour is. This is fine when contact volume peaks mid-morning and mid-afternoon in the US, and a poor fit when your service level promise is tied to US opening hours.

Option 2: Fix US coverage, move agent hours

The roster shifts by an hour in March and November so the US hours stay the same. This is correct for SLAs and forecast accuracy but costs you in the long run: staff are asked to start an hour earlier or later twice a year, which affects employer-provided night transport, childcare and sleep schedules. Plan the change with at least four weeks notice and treat it as a formal roster revision, not a note on a noticeboard.

What experienced planners do

• Pick one option per queue and write it in the operating procedure so it is not argued every March.
• Define the roster in the US time zone in the workforce management (WFM) tool, and display India and Philippine local times alongside.
• Put the three change dates (the second Sunday in March and the first Sunday in November, plus the UK and EU dates if you also serve Europe) on the planning calendar a year ahead.
• Freeze leave approvals and shift swaps in the week around a change, because the same Monday has different meanings for each site.
• Re-forecast: US call arrival curves are tied to US clock time, so interval forecasts must be shifted by an hour when agent hours are fixed.

A 24-hour coverage grid

For round-the-clock US support, a common structure is three eight-hour shifts that rotate through the Asian day. The key observation for planners who are new to this is that US overnight is Asian daytime. A day shift in India covers the US evening and night, and the Indian night shift covers the US business day.

For a 24-hour view in three-hour steps, here is every IST hour against the Philippines and two US zones.

The grid assumes fixed Asian hours. Notice that Shift 1, the Asian morning, covers the US evening and overnight, which is why it is often the easiest to staff, and why many operations keep their most experienced agents on Shift 3 (US daytime), where volume is highest. The summer column moves by an hour, which is the DST effect described above.

A sample roster for an Eastern-hours queue

Here is a concrete example. The queue is open 8:00 AM to 8:00 PM Eastern, Monday to Friday in winter, and the operation uses one site in India and one in Manila.

The two shifts overlap for four hours, from 12:00 noon to 4:00 PM Eastern in winter, which matches the volume peak for most consumer support queues. Put the stronger team there. The India and Manila rosters cover the same US hours, so you can split volume between the sites by skill, language or queue rather than by time of day.

Handover timing

If you pass work between sites, remember that Manila's clock is always exactly 2.5 hours ahead of India's, so 2:30 PM in Chennai is 5:00 PM in Manila. A handover between the two sites is simple arithmetic. A handover to a US team is not, so write the handover instant in UTC or in US Eastern time on the handover note. Leave 30 minutes of overlap between outgoing and incoming shifts for live case review, and 15 minutes at the end of the incoming shift for written notes while the context is still fresh.

Weekend, holiday and calendar mismatches

A US business week does not line up with an Asian calendar week, and the mismatch catches managers who have not thought about it carefully.

In practice this means that an Eastern-hours queue from Asia is staffed on Saturday morning (the end of the US Friday) and starts on Monday morning in India or Manila (the start of the US Monday, which is still Sunday evening in New York). Staff who think of Saturday as a day off will find that the US Friday ends on it. Agree in the contract which days the roster is Monday to Friday in US time, and which in local time.

Holidays: three calendars, almost no overlap

The US observes holidays such as Thanksgiving (November 26, 2026), Christmas Day, New Year's Day, Memorial Day and Independence Day. India has three national holidays (January 26, August 15 and October 2) and many regional and festival days such as Diwali, which falls in October or November. The Philippines has a long list of regular and special days, including January 1, Holy Thursday and Good Friday, April 9, May 1, June 12, November 30 (Bonifacio Day), December 25 and December 30 (Rizal Day), and movable days such as Eid'l Fitr, which follow the lunar calendar and are announced late. The Philippines' Labor Code also sets premium pay for work on regular holidays, so a roster that ignores the holiday calendar becomes a payroll problem as well as a coverage problem.

Two rules help. First, a US holiday is a holiday on the US date, which means a Thursday-evening Thanksgiving shift in Asia is already Friday morning there. Second, Christmas week is when many staff in the Philippines and India ask for leave, so open leave requests early and confirm which sites are staffed. Check each country's official holiday proclamations each year, because the Philippines announces some special days at short notice.

Common mistakes

• Quoting "the US" as one zone. Eastern, Central and Pacific hours differ by up to three hours, and a promise to "cover US hours" needs the zone in it.
• Using a fixed offset in the WFM tool. If the tool uses a fixed UTC-5 for Eastern, it will be an hour wrong from March to November. Use named zones, such as America/New_York.
• Forgetting the other side's change date. The US and Europe change on different dates, and an operation that also serves UK customers has an extra few weeks of different gaps.
• Treating the Philippines and India as the same. The 2 hours 30 minutes between them is a constant, but it is not an hour you can round: shift start times need to be written in each site's own time.
• Announcing the change too late. People with caring duties or transport arrangements need weeks, not days.

When in doubt, check the actual times for a specific date with the IST to EST converter before you publish a roster, and compare against the live US time now page on the first day after a change.

Frequently Asked Questions