Use Toronto’s own rules for a transatlantic plan

At 09:00 Toronto on 27 October 2026, London reads 13:00; on 3 November it reads 14:00. This pair resembles London–New York on these dates, but the saved plan keeps America/Toronto so the intended location remains explicit.

Compare the same local start on four dates

09:00 in London, resolved separately on each date with IANA 2026f. The final column describes Toronto relative to London.
LondonTorontoTime difference
2026-01-15 · 09:00Thu, 15 Jan 2026 · 04:005 hours behind
2026-07-15 · 09:00Wed, 15 Jul 2026 · 04:005 hours behind
2026-10-27 · 09:00Tue, 27 Oct 2026 · 05:004 hours behind
2026-11-03 · 09:00Tue, 3 Nov 2026 · 04:005 hours behind

Find a window for the whole meeting

The illustrative 09:00–17:00 overlap is four hours on the first date and three on the second. A Toronto morning and London afternoon can work, provided the whole duration fits. Add Vancouver separately if the meeting includes a western Canadian team; its 2026 November behavior differs from Toronto’s.

Make the plan specific

  • Enter each participant’s actual working days and hours. The 09:00–17:00 examples here are editable assumptions, not local business-hour facts.
  • Choose a duration from 15 to 240 minutes and check both local end times.
  • For a weekly meeting, choose one anchor city and review all twelve dates. Resolve repeated or missing local times explicitly.

Reversing the base city changes how you enter the meeting, not the pair’s information page. Share the configuration or export the resolved event after the participants agree on the time.