How to schedule international meetings people don’t hate

Somebody always eats the bad hour. That's the physics of a spherical planet, and no scheduling app changes it. What you can control is who eats it, how often, and whether the invitation itself creates confusion. A few rules cover almost everything.

Know the golden windows

US East Coast ↔ Europe is the easy pairing: 8-11 AM in New York lands at 1-4 PM in London and 2-5 PM in Berlin — comfortable for everyone. US West Coast ↔ Europe is tighter: 8 AM in San Francisco is already 5 PM in Paris; you get about a one-hour civilized window. US ↔ East Asia has no good window at all — morning in New York is night in Tokyo — so someone joins outside work hours, full stop. And US ↔ India: the least-bad slot is early US morning, which hits Indian mid-evening.

Use the meeting-planner slider on our homepage to test a proposed hour before sending the invite; ten seconds of checking beats a reply-all correction.

Rotate the pain

For recurring global meetings, fairness beats optimization. A meeting that's always 7 AM for Sydney tells the Sydney team exactly where they stand. Teams that work rotate the slot — this month friendly to Asia-Pacific, next month to Europe — or alternate between two times. The signal matters as much as the sleep.

Better yet, ask whether the meeting needs to be live at all. Distributed-first companies handle most coordination in writing precisely because the planet made the alternative expensive.

Write times people can’t misread

State the time in the receiver's zone ('3 PM your time, Berlin'), or give one anchor plus an explicit zone and city — '9 AM Eastern (New York)'. Never say 'EST' in July; Eastern DAYLIGHT time is what's running, and the wrong abbreviation genuinely bites during the mismatched DST weeks. For anything near midnight, name the day in both zones: 'Friday 11 PM New York / Saturday 4 AM London.' Calendar invites handle conversion automatically — the traps live in the prose around them.