Managing Time Zones: Frameworks That Work for India-Remote Teams

IST is UTC+5:30. US East Coast is UTC−5 (or −4 in summer). The overlap window — where both locations are in business hours — is 30 minutes in winter, 90 minutes in summer. UK to India is more forgiving: 4.5–5.5 hours of overlap.

Companies that build India teams and then try to run them with the same meeting culture they use for a co-located team in San Francisco burn their India engineers out within 18 months. Those that design around the constraint thrive. Here are the three models that work.

Model 1: Minimal Overlap (Async-First)

Best for: engineering teams doing deep individual-contributor work; mature product codebases where requirements are clearly specified.

The India team works IST business hours (9am–6pm). US team works their local hours. Overlap is intentionally minimal — one 30-minute standup at 6pm IST / 7:30am ET on alternating days. Everything else is async: written specs, Loom video updates, GitHub comments, Notion docs.

This model requires strong documentation discipline. Teams that adopt it successfully invest heavily in written culture: RFCs (Request for Comment) for architectural decisions, detailed PR descriptions, weekly written updates.

Model 2: Shifted Overlap (Core Hours)

Best for: product teams, cross-functional squads, or situations where real-time collaboration significantly improves output quality.

India team adopts slightly shifted hours: 12pm–9pm IST, giving 3–4 hours of overlap with US East Coast (7:30am–11:30am ET). This requires an explicit agreement with employees and compensation for the schedule shift — an afternoon/evening allowance or flexibility in lieu.

Model 3: Follow-the-Sun

Best for: support, DevOps, incident response, or any function where continuous coverage adds value.

India team handles 8pm–8am ET (their 9am–9pm IST). US team handles 8am–8pm ET. No overlap is the design goal — India team has full ownership of their window. Handoff rituals (written run-book, async video summary) become critical.

The companies that struggle most aren't the ones with the worst time zone gap — they're the ones that haven't made an explicit choice about which model they're running. Pick one and design your rituals around it deliberately.