Why there is no overlap, and the 12 vs 13 hour gap
The math leaves no room. Singapore is UTC+8 all year and does not observe daylight saving. New York is UTC-4 on Eastern Daylight Time (March through early November) and UTC-5 on Eastern Standard Time (November through March). So the gap is 12 hours in summer, 13 hours in winter.
Check it: 9 AM Monday in New York is 9 PM Monday in Singapore during daylight saving, 10 PM in winter. And 9 AM Monday in Singapore is 9 PM Sunday in New York (summer) or 8 PM Sunday (winter). Standard 9-to-6 working hours on both sides share exactly zero minutes. The calendar question is never "when suits everyone." It is "whose evening is it this week."
| New York | Singapore | Verdict |
|---|---|---|
| 8:00 PM (EDT) | 8:00 AM next day | Best: NY end of evening, SG start of day |
| 9:00 PM (EDT) | 9:00 AM next day | Good: still inside both comfort zones |
| 8:00 AM (EDT) | 8:00 PM | Tolerable occasionally, asks SG for the evening |
| 9:00 AM (EDT) | 9:00 PM | Edge of acceptable for Singapore |
| 12:00 PM (EDT) | 12:00 AM next day | No: midnight in Singapore |
Times shown for EDT (12-hour gap). After New York falls back to EST in early November, add one hour to the Singapore side, or equivalently shift the New York time one hour earlier to hold Singapore steady.
The November wrinkle, and it is soon
Because Singapore never moves, the entire gap shift comes from the US side. When New York falls back to Eastern Standard Time in early November, the 8 PM meeting that was landing at 8 AM in Singapore now lands at 9 AM, which the Singapore side will experience as an extra hour of sleep. The trap is for the calendar: recurring meetings stored as fixed New York times silently move for Singapore attendees who converted once and stopped thinking about it.
The fix is boring and it works. Store the meeting with both time zones written out, "8 PM ET / 8 AM SGT+1", and re-confirm the Singapore-side time the week after the November change. Our daylight saving guide for recurring meetings covers the same failure mode across every pair.
Rotating the late slot
When the only workable window still stretches someone's day, the fair system is rotation. The 8 PM New York slot is mildly inconvenient for nobody: it is the tail of one side's day and the start of the other's. But the moment you need a third meeting in a week, or the conversation runs past 10 PM New York time, someone is paying for it, and it should never be the same someone every week.
Default everything you can to async. Loom-style video updates, written decisions, shared docs: none of them care about the 12-hour mirror. Reserve the live window for the conversations that actually need two brains at once, keep them short, and alternate the direction when you meet often. For the same playbook on other brutal pairs, see San Francisco to Singapore and New York to Sydney.
Check the live overlap for any two cities.
Computed from the real tz database, with automatic daylight saving handling.
Open the Timezone Overlap Planner