How to Schedule Meetings Between the US and Europe

Find useful morning-to-afternoon overlaps and avoid the weeks when American and European clock changes do not align.

Zone & Hour editorial · Published September 30, 2026 · Examples are explicitly dated

Start with the American morning

For many US–Europe teams, the American morning overlaps with the European afternoon. That is a useful starting direction, not a universal appointment time. A New York participant is closer to a London workday than a Los Angeles participant is to a Helsinki workday.

Choose the actual cities and ask for working-hour limits before sending an invitation. If you have an hour of shared availability, a sixty-minute meeting uses every minute of it. A shorter meeting may leave a useful margin for overruns, preparation or another commitment.

The meeting planner evaluates the entire duration. Set the start and end of each city’s workday, then look at the proposed time in every row instead of relying only on a single summary label.

A dated East Coast example

On October 5, 2026, New York is five hours behind London and six behind Paris. These examples all occur on the same calendar date:

A noon New York start already reaches a typical end-of-day boundary in Paris. For an hour-long call, consider an earlier row. If the Paris participant ends at 5 PM, a 10 AM New York start is the latest in this table that finishes by that boundary.

Open the New York to London converter or New York to Paris converter to change the date. The displayed static table is a reference example, while the interactive tool recalculates the exact instant.

The Pacific coast has a narrower window

On the same October date, 8 AM in Los Angeles is 4 PM in London and 5 PM in Paris. A one-hour call may fit the end of one European workday and exceed another. Adding Helsinki moves that participant another hour later.

If the US participant cannot begin before 9 AM and the European participant cannot continue after 5 PM, an ordinary overlap may not exist. The correct response is to surface that conflict. Stretching the default working hours until the tool shows green does not make the meeting fair.

For a distributed organization, consider separate regional discussions with one short cross-region decision call. Shared notes can carry context between the two. This is often more useful than requiring every office to attend the same long weekly session.

The transition weeks deserve a calendar review

The United States and the UK currently change clocks on different Sundays. Their familiar five-hour New York–London gap briefly becomes four hours. European continental cities generally also have a different clock-change weekend from the US.

In 2026, NIST lists the US change dates as March 8 and November 1. The UK government lists March 29 and October 25. See the primary US schedule and UK schedule for the applicable rules.

For a meeting anchored to New York’s local clock, the London appearance shifts during those gaps. For a meeting anchored to London, the New York appearance moves instead. Neither calendar is necessarily wrong: the anchor determines which local hour remains fixed.

Agree on the recurring anchor

Ask a specific question when creating the series: should this remain at 9 AM New York, 2 PM London or a fixed UTC instant? Record the answer in the invitation description. If there is no business reason for one anchor, choose one and establish a review date before the seasonal changes.

A shared converter link represents one exact instant. It is useful for a particular occurrence, but it is not itself a rule for a repeating meeting. A calendar recurrence also needs a date pattern and a zone identifier to generate future occurrences correctly.

After creating a series, inspect an occurrence on each side of a transition. Check the local time displayed on a participant’s calendar rather than assuming the abbreviated zone name in the invitation tells the entire story.

Make a proposal easy to assess

Write the full date and the local start and end in at least the principal offices. Include a short agenda and a decision to be made. Someone asked to attend late in the day should be able to judge whether synchronous attendance is necessary.

For example: “October 5, 9–9:30 AM New York / 2–2:30 PM London. Decide the launch date; written comments welcome before the call.” The explicit end time and purpose reduce ambiguity that a bare “9 AM ET” message leaves behind.

Frequently asked questions

Are all European cities on one time zone?

No. London, Paris and Helsinki are an easy example of three local clock readings. Choose each city instead of writing only “European time.”

Can I keep a constant difference all year?

Some pairs stay aligned under current rules; others do not. Consult the pair’s seasonal table. Even a stable current difference should not replace an IANA zone in a recurring calendar event.

What if someone travels?

Their calendar may display the appointment in the destination zone, but the meeting instant need not move. Confirm whether travel changes their availability before changing the series for everyone.