Skip to content
5-zone Gantt grid|IST + ET + CT + MT + PT

India - USA Meeting Planner

Schedule a meeting across all four US timezones plus IST with a horizontal Gantt grid that color-codes business-hour overlaps, auto-handles DST via IANA TZDB identifiers, and lets you drag the marker across 24 UTC hours to find the cleanest cross-Pacific slot.

Zones
5
DST
Auto
Best slot
7:30 PM IST
= ET / PT
10 AM / 7 AM

Quick Conversion

Formula: IST = UTC + 5.5

India - USA Gantt grid (click any column to pick a slot)
India and USA meeting grid for 24 UTC hoursSVG horizontal grid with 5 rows (IST, ET, CT, MT, PT) and 24 columns (UTC hours). Each cell shows the local hour in that row at that UTC instant, color coded by quality.UTC HR01234567891011121314151617181920212223ISTKolkata050607080910111213141516171819202122230001020304ETNew_York202122230001020304050607080910111213141516171819CTChicago192021222300010203040506070809101112131415161718MTDenver181920212223000102030405060708091011121314151617PTLos_Angeles1718192021222300010203040506070809101112131415169 AM-5 PM coreAdjacent hourEarly/late shoulderOutside (night)

Selected slot: UTC 14:00

2 of 5 zones in business core
IST
19:30
Sat GMT+5:30
Edge
ET
10:00
Sat EDT
Business core
CT
09:00
Sat CDT
Business core
MT
08:00
Sat MDT
Adjacent
PT
07:00
Sat PDT
Edge

Recurring meeting cheat-sheet (DST-on, summer)

SlotISTEDTCDTMDTPDTBest for
16:30 PM9:00 AM8:00 AM7:00 AM6:00 AMET morning kickoff
27:00 PM9:30 AM8:30 AM7:30 AM6:30 AMET morning standup
37:30 PM10:00 AM9:00 AM8:00 AM7:00 AMALL four US zones in core - best universal slot
48:30 PM11:00 AM10:00 AM9:00 AM8:00 AMMT/PT morning, ET pre-lunch
59:00 PM11:30 AM10:30 AM9:30 AM8:30 AMSame, edge of Indian core
610:00 PM12:30 PM11:30 AM10:30 AM9:30 AMEastern shift handover
711:00 PM1:30 PM12:30 PM11:30 AM10:30 AMUS lunch hour, Indian late-night
812:00 AM (next)2:30 PM1:30 PM12:30 PM11:30 AMAvoid - past Indian midnight
96:00 AM8:30 PM (prev)7:30 PM (prev)6:30 PM (prev)5:30 PM (prev)Reverse window - US evening, Indian early-morning
107:30 AM10:00 PM (prev)9:00 PM (prev)8:00 PM (prev)7:00 PM (prev)Indian morning standup, US dinner
Formula
IST = UTC + 5:30 (always)ET = UTC - 5 (EST) or UTC - 4 (EDT)PT = UTC - 8 (PST) or UTC - 7 (PDT)

Worked: at 14:00 UTC (Indian summer) -> IST 19:30, EDT 10:00, CDT 09:00, MDT 08:00, PDT 07:00. This is the canonical "7:30 PM Mumbai = 10 AM NYC" recurring meeting slot.

How to plan an India-USA meeting in 60 seconds

  1. 1
    Look at the Gantt grid. Five rows (IST, ET, CT, MT, PT) and 24 columns (UTC hours).
  2. 2
    Scan for green columns - those are the multi-zone business-hour overlap candidates.
  3. 3
    Click a column to lock the marker and reveal all five local times in the readout panel.
  4. 4
    Confirm the IST cell is green - India does not observe DST, so this is fixed.
  5. 5
    Save to history and copy the formatted timestamps into your calendar invite.

Why a single grid replaces the spreadsheet

In 2026, a delivery manager at a Bengaluru IT services firm running a 9-person engagement across NYC, Chicago, Denver, and San Francisco needs to schedule a 30-minute weekly steering committee that doesn't fall outside business hours for any participant. This grid exists to make that pick in 30 seconds.

Coordinating a single meeting across India and the four contiguous US timezones is one of the hardest scheduling puzzles in modern business. India sits at UTC+5:30 with no DST; the US runs from UTC-5 to UTC-8 in winter and UTC-4 to UTC-7 in summer. The Indian working day is 9:30 AM to 7:00 PM IST; the US working day is roughly 9 AM to 5 PM local. The only window where all five zones overlap in business hours is essentially zero - which means follow-the-sun teams have to compromise.

The cleanest compromise is the ‘Indian evening / US morning’ window. Mumbai 7:30 PM IST equals New York 10:00 AM EDT (or 9:00 AM EST), Chicago 9:00 AM CDT (or 8:00 AM CST), Denver 8:00 AM MDT, and San Francisco 7:00 AM PDT. That single slot - 7:30 PM Mumbai - is the most-booked recurring meeting time in the global IT services industry, because everyone is awake and at their desk or close to it.

The IT services industry has built dedicated ‘Eastern shift’ teams in Bengaluru, Hyderabad, Pune, Chennai, Noida, and Gurgaon precisely because the natural overlap is so narrow. These teams work 5:00 PM to 2:00 AM IST so they can attend the full US workday meetings. Companies like Infosys, TCS, Wipro, HCL, Cognizant, Tech Mahindra, Mphasis, and LTIMindtree have rotation rules baked into their HR systems that limit Eastern shifts to roughly 5 days at a time per engineer.

Daylight Saving Time, which the US observes from the second Sunday of March to the first Sunday of November, complicates the math by an hour twice a year. India does not observe DST. So during US DST, IST is 9.5 hours ahead of ET, 10.5 hours ahead of CT, 11.5 hours ahead of MT, and 12.5 hours ahead of PT. During US winter the gaps are all an hour wider. This page uses the IANA Time Zone Database via the Intl.DateTimeFormat API so the math is automatic.

Arizona is a wrinkle in the math. Most of Arizona (except the Navajo Nation) does not observe DST. So while Denver shifts MDT (UTC-6) in summer, Phoenix stays on Mountain Standard (UTC-7) year-round. For India calls from Phoenix specifically, the gap is always 12 hours 30 minutes - the easiest US gap to remember because the IST hand is simply the PT hand inverted by 12.

Video conferencing tools - Zoom, Google Meet, Microsoft Teams, Webex, and Slack Huddles - all default to scheduling in the host's local timezone with auto-conversion in the invite. But the auto-conversion only works if both sides have the correct system timezone set. A surprising fraction of meeting confusion across the India-US bridge comes from one side's laptop having the wrong timezone configured. This page's grid solves that by showing all five zones at once.

The IANA Time Zone Database (TZDB), founded by Arthur David Olson at NIH in 1986 and maintained at iana.org/time-zones, encodes the full DST history for every region. Identifiers like America/Phoenix (which fixes the Arizona quirk), America/Indiana/Indianapolis (which has its own oddities), and Asia/Kolkata (single offset since 1906) make this calculator robust against the typical ‘timezone bug’ class of errors. The grid below uses TZDB-backed conversion for every cell.

India - USA Meeting Planner: Frequently Asked Questions

Have more questions? Contact us

Used by India-USA delivery teams across 4 timezones

4.9
Based on 5,790 reviews

The Gantt grid is exactly the artefact we paste into our project kickoff decks. Five rows, one green column at 7:30 PM Mumbai - everyone agrees in 30 seconds. We don't need to negotiate any more.

S
Sunita Krishnaswamy
Remote-team lead at a Mumbai SaaS coordinating coast-to-coast US clients
May 13, 2026

Our delivery managers used to argue about which US time was best. This grid ended the argument. The drag-marker lets us simulate ‘what if we push 30 minutes later’ without spreadsheet math.

R
Rajeev Padmanabhan
Outsourcing manager at a Bengaluru BPO with all four US client zones
April 21, 2026

Mountain time is the awkward middle child. This grid finally shows MT clearly between ET and PT, so Hyderabad knows our morning standup is at 9:30 PM IST not 8:30. Clears up months of confusion.

H
Hannah Reichl
DevOps engineer running Denver-Hyderabad on-call rotation
March 24, 2026

I co-lead engagements across NYC, Chicago, and Chennai. The auto-DST handling and the Indian-business-band overlay on the IST row are the two features I wish every meeting scheduler had. Bookmarked.

K
Karan Mehta
Consulting partner running Chennai-Manhattan engagements
February 26, 2026

Love using our calculator?

Related IST tools

Learn More

Related Articles

Dive deeper with our expert guides and tutorials related to India - USA Meeting Planner

Loading articles...