Planning dates run from Thu, Jan 1, 2026 through Mon, Dec 31, 2035. Future rules can be revised; review the data version when a distant schedule matters.
More context and planning advice
Same Brazilian clock, changing overseas gap
São Paulo is UTC−03:00 on all four displayed dates. That does not make its difference from London constant. A 09:00 São Paulo meeting is 12:00 in London in the January sample and 13:00 there in July, because the London rule changes. Choose the meeting date before calculating the gap.
A dated view of the local clock
Four examples at 13:00 UTC, calculated with IANA 2026f. These are selected dates, not a live clock.
UTC date
UTC offset
Abbreviation
Local date and time
2026-01-15
UTC−03:00
-03
Thu, 15 Jan 2026 · 10:00
2026-07-15
UTC−03:00
-03
Wed, 15 Jul 2026 · 10:00
2026-10-27
UTC−03:00
-03
Tue, 27 Oct 2026 · 10:00
2026-11-03
UTC−03:00
-03
Tue, 3 Nov 2026 · 10:00
Keep the intended city when clocks match
São Paulo and Buenos Aires display the same local time in these 2026 examples, but their IANA identifiers are different. Retaining the city in a saved plan records which place you intended and lets later data updates apply the appropriate rule set. You do not need duplicate meeting slots merely because two rows match.
Build a plan for this city
Select São Paulo, add the other participants, and enter the actual meeting date. The planner uses America/Sao_Paulo; the abbreviation in the table is a display label. Adjust working days, hours, and meeting length before choosing a shared window. The supported planning range is 2026–2035.