Scheduling With India: A Guide for Distributed Teams

The hard part of scheduling with India is not the arithmetic. Indian Standard Time is UTC+5:30 and never moves, so the conversion is the easiest part of the whole exercise. The hard part is that against an American team the overlap of ordinary working hours is one or two hours at the very edges of both days, and whoever loses that negotiation loses it every single week. Distributed teams that work well with India have usually made a deliberate choice about who absorbs that cost.

This guide covers rotating the awkward slot fairly, building a handover that does not depend on being in a call together, planning around a holiday calendar that varies by state, and the invitation etiquette that stops a schedule quietly landing on the wrong day. Everything below assumes you are scheduling with India rather than merely converting a time. Both clocks are shown together on the India and USA time page.

How Big Is the Overlap Really?

It depends entirely on the other end. From the Gulf the Indian working day is almost fully shared; from the United Kingdom it covers a British morning and an Indian afternoon; from the American west coast it is barely an hour at each extreme.

• Gulf states: Dubai is 1 hour 30 minutes behind India and Riyadh 2 hours 30 minutes, with no daylight saving anywhere in the region, so the days overlap almost completely. The weekend differs, though, with several Gulf states resting on Friday and Saturday.
• United Kingdom: India is 5 hours 30 minutes ahead of GMT and 4 hours 30 minutes ahead of British Summer Time, giving a comfortable shared afternoon.
• Australia: the east coast is 4 hours 30 minutes ahead of India, so an Indian morning meets an Australian afternoon.
• United States: India is 9 hours 30 minutes to 13 hours 30 minutes ahead depending on zone and season, which leaves only the early American morning and the late American evening.

The American case is the one that needs real scheduling discipline, and the exact figures are set out in IST to EST and PST. Everything below assumes that harder case.

How Do You Make Scheduling With India Fair?

Rotate the unsociable slot rather than assigning it. If a weekly call must sit at 20:30 IST for the Indian team, alternate it with a slot at 07:30 in the morning for the American team, and publish the rotation months in advance so nobody has to negotiate it each time.

Three rules make rotation work in practice. First, cap the number of out-of-hours calls any individual takes per month, and hold to the cap even when a deadline is close, because the alternative is that the offshore team absorbs all of them by default. Second, schedule the expensive meeting into the fair slot and let the cheap one flex: a two-person sync can sit anywhere, while a large all-hands cannot. Third, record anything that runs outside someone's working hours, with a written summary, so that missing it carries no career cost.

It is worth being honest about why this matters. Indian teams working with foreign clients are usually flexible, and business process outsourcing and IT services have built entire operating models on night shifts covering American daytime. That willingness is easy to exploit without noticing. A team that never asks itself who is taking the 22:00 call will find that it is always the same people, which is the commonest failure in scheduling with India over the long run.

Building a Handover Instead of a Meeting

The best answer to a narrow overlap is to need less of it. Follow-the-sun handover treats the gap as an advantage: work is passed on at the end of one day and picked up at the start of the next, so a task progresses for sixteen hours instead of eight.

A handover that works has a few consistent features. State lives in the ticket or the document, never in a conversation, so that the next person can reconstruct where things stand without asking. The person going off shift writes a short note covering what changed, what is blocked and what the next decision is. Questions are written so they can be answered without a call, which means including the options rather than just the problem. And a short joint window, thirty minutes rather than an hour, is held at the seam of the two days for the small number of things that genuinely need a voice.

Done properly this removes most of the pressure from the schedule. It also suits the geography: a handover at 20:00 Pacific reaches India at the start of its morning, which is precisely the overlap described in the best time to call India from the US.

Scheduling With India Around the Holiday Calendar

Before scheduling anything, ask every Indian office for its published holiday calendar in December or January, and treat that list as authoritative. India has only three holidays observed everywhere, and all the rest are regional, employer-set or movable, so no generic calendar will be correct.

The three fixed national days are Republic Day on 26 January, Independence Day on 15 August and Gandhi Jayanti on 2 October. Everything else needs checking. Diwali falls in October or November and can close offices in the north and west for several consecutive days; Holi falls in March; Durga Puja empties Kolkata for the better part of a week while barely affecting Chennai; Onam, Pongal, Ganesh Chaturthi and Bihu each dominate their own regions. Because most of these follow lunisolar or lunar calendars, last year's dates are not this year's. One further date is worth marking even though it is not a holiday: the Indian financial year ends on 31 March, so the last week of March is a poor moment to schedule anything demanding of a finance or compliance team. The fuller picture is in Indian business hours and holidays.

Invitation Etiquette and Tools

Write both local times and the date into every invitation you schedule. A line reading 09:00 EST Tuesday, 19:30 IST Tuesday costs nothing and prevents the most common failure, which is a meeting that is right to the hour and wrong by a day.

A few further habits are worth adopting:

• Turn on a secondary time zone in your calendar so Indian hours are visible while you schedule an event, rather than discovered afterwards.
• Name the zone, not the abbreviation: IST also means Irish and Israel Standard Time, so write Asia/Kolkata or UTC+5:30 in anything technical.
• Avoid 13:00 to 14:00 IST, a genuine lunch break in most Indian offices, and the commute peaks around 09:00 and 19:00 IST in Bengaluru, Mumbai and Delhi.
• Re-check standing meetings on your own daylight saving changeover weekends, since India never moves and the Indian local time of your recurring call will shift by an hour.
• Confirm before travel bookings, using an IST time zone converter rather than a mental estimate, because every Indian-American conversion crosses midnight.

Conclusion

Scheduling with India succeeds or fails on fairness and on writing things down. Rotate the unsociable slot and publish the rotation, replace as many meetings as possible with a written handover at the seam of the two days, collect each office's holiday calendar in January and take Diwali and the end of March seriously, and put both local times and the day name in every invitation. The arithmetic itself never changes, because Indian Standard Time holds at UTC+5:30 all year. Compare both clocks on the India to USA time page, check the live reading on the IST clock, or work through any other pairing on indiatime.now.