Running Meetings Across US and European Time Zones: What Actually Works

I have been the person scheduling across five time zones for three years. Most advice on this topic is written by people who have never done it. Here is what survived contact with reality.

The US East Coast to Western Europe gap is 5 to 6 hours. That is the good news: unlike US-Asia, there is real overlap to work with. The bad news is that teams squander it with meeting sprawl, fairness theater, and a refusal to admit that some meetings should not exist. What follows is the system I actually use.

Step 1: Map the real overlap, not the assumed one

Do not assume 9 to 5 on both sides. Ask people their actual working hours first. You will discover things: the Berlin engineer who starts at 10, the Boston parent who logs off at 3:30 for school pickup, the London contractor on a 4 day week. Your true overlap is the intersection of real hours, and it is almost always smaller than the theoretical one.

For a typical US East Coast (9-5 ET) and Central Europe (9-5 CET) team, the overlap is about 3 hours: 9:00 AM to 12:00 PM ET is 3:00 PM to 6:00 PM CET. For US East Coast to London it is the same 3 hours shifted: 9:00 AM to 12:00 PM ET is 2:00 PM to 5:00 PM London. Guard this window. It is the most expensive real estate on your team's calendar.

Step 2: Establish core hours and defend them

Pick a consistent window when most of the team is available and declare it sacred. For a US-Europe team, something like 9:00 to 11:00 AM ET / 2:00 to 4:00 PM London / 3:00 to 5:00 PM Berlin works as core sync time. Rules for the window:

• Only meetings that need both sides go here. A US-only status update does not get to spend transatlantic overlap. This is the rule teams break most, and it is the one that matters most.
• Batch them. Three 30 minute meetings scattered across the window fragment everyone's day. Stack them into a block so the rest of the overlap stays usable for real work.
• Protect one meeting free day. If every day's overlap is fully booked, nobody has deep work time during the only hours their colleagues are awake. I keep Fridays meeting free in the overlap, and it is the most productive day of my week.

Step 3: Differentiate meeting types ruthlessly

Not every meeting deserves the overlap window:

• Daily standups: run them regionally. A Berlin standup at 10 PM their time is cruelty, not collaboration. Run parallel standups and share notes async.
• Weekly planning: worth the overlap. This is the meeting that actually needs everyone.
• Monthly all hands: record the presentation. Use live time only for Q and A. Nobody's evening is worth a slide deck they could watch at 1.5x speed.
• Quarterly strategy: rare enough that asking someone to join at 7 AM or 8 PM is reasonable. Say so explicitly so it does not become a habit.

The mistake I see everywhere is treating every meeting with the same urgency and requiring the same live attendance. Tier them, and the calendar gets dramatically lighter.

Step 4: Rotate the pain, and mean it

For the meetings that must happen at an edge hour, rotate who takes the hit. If your weekly all hands alternates between 8:00 AM ET (good for the US, late for Europe) and 4:00 PM ET (good for Europe, early for the US), people notice the fairness. If it is always convenient for headquarters, people notice that too, and they stop coming.

One team I worked with did a 4 week cycle: week 1 favored the Americas, week 2 favored Europe, week 3 was recorded with async Q and A, week 4 the meeting was cancelled entirely. Attendance went up. Resentment went down. The cancelled week turned out to be everyone's favorite feature.

Step 5: Write the time zone on everything

Every invite, every Slack message about a meeting, every doc: "2:00 PM ET / 7:00 PM London." Never a bare time. Bare times are how someone joins an hour late and everyone pretends it was a calendar bug. During the March and October daylight saving transitions, when the US-Europe gap temporarily narrows by an hour, double check every recurring meeting. I have seen this break a sprint planning meeting two years running on teams that should know better.

The async escape hatch

The best meeting across time zones is the one you do not hold. Status updates, design reviews with written feedback, decisions with a 24 hour comment window: all of these work async, and they work better, because people respond when they are sharp instead of when the calendar says so. My rule: if a meeting's output could be a document, make it a document. Reserve the overlap for the things that genuinely need live humans: disagreement, brainstorming, and bad news.

How many overlap hours do US and Europe share?

Typically 2 to 3 hours for US East Coast to Western Europe within standard 9 to 5 hours on both sides. US West Coast to Europe is worse, often 1 hour or zero, which is why West Coast members of transatlantic teams usually shift their hours earlier.

Should standups include all time zones?

No. Run standups regionally and share notes async. A standup's value is frequency and brevity; forcing it across 6+ hours of time difference destroys both.

How do you handle daylight saving transitions?

The US and Europe change clocks on different weekends in March and October/November, so the gap between them temporarily shrinks by one hour. Audit every recurring cross Atlantic meeting during both transition windows each year.