THE MEETING FIELD GUIDE

A good time
for everyone.

An overseas meeting needs more than a clock conversion. You need to agree which city's time controls the invitation, keep the date clear, and decide who takes the early start or late finish. Here is a practical way to do that.

By FPF Trust · Updated 10 September 2026

Start with the organiser's city and date

If someone says “Tuesday at nine”, ask which city, which Tuesday, and whether they mean AM or PM. Enter that city as the source in the converter. Then enter the actual meeting date before choosing the other person's city. A current world clock cannot answer a question about a meeting next month reliably if a clock change falls between now and then.

Choose the suggestion with the correct country and region. Cities can share names, and a nearby place across a state or national border may follow different rules. If a small town is missing, confirm that a larger city uses the same time zone before substituting it.

Find overlap, then ask about availability

Try a morning, midday and late-afternoon option in the organiser's city. Compare the destination date as well as its time. The map's green markers indicate 9 AM to 6 PM only: they do not account for weekends, public holidays, school runs or individual working hours.

For a Brisbane–London call on 15 July 2026, 6:00 PM in Brisbane is 9:00 AM in London. That may be a better starting point than 9:00 AM in Brisbane, which is midnight in London. Ask both guests before treating that overlap as an agreed time.

With three widely separated regions, there may be no comfortable slot for everyone. Rotate inconvenient times across recurring meetings, keep the live discussion short, and send a written decision summary to people who cannot attend. A recording is useful only when participants agree and can access it afterwards.

Recurring meetings can drift locally

A weekly meeting fixed to one city's local time does not necessarily stay at the same local time elsewhere. Brisbane at 9:00 AM on 15 January 2026 corresponds to 11:00 PM on 14 January in London. Brisbane at 9:00 AM on 15 July corresponds to 12:00 AM on 15 July in London. Both the clock reading and the displayed date change in this example.

Decide which city's time should stay fixed. When creating the recurring event, select that time zone in your calendar and inspect occurrences around seasonal changes. This converter handles one chosen date at a time; it does not create or manage a recurring calendar series. Recheck each affected occurrence rather than copying one result across the whole year.

When a local time is missing—or appears twice

A forward clock change can skip a local time altogether. In New York on 8 March 2026, 2:30 AM does not occur. Moving the meeting to a valid time is necessary; silently interpreting it as another hour would change the organiser's request.

A backward change can repeat a time. In New York on 1 November 2026, 1:30 AM occurs first at UTC−04:00 and again at UTC−05:00. Those are two different moments, one hour apart. The converter asks you to choose an occurrence. If the invitation is unclear, ask the organiser which offset they intend.

Write the date next to midnight

12:00 AM is the beginning of the date shown; 12:00 PM is noon. Avoid “midnight Wednesday” in an invitation because people may read it as the start or end of Wednesday. Write “12:00 AM on Wednesday 15 July” and include the guest's local date and time.

A previous-day or next-day result is part of the answer, not an error. Travelling east or west on the map is not enough to predict the calendar date. Read the complete converted result, especially when the two cities are far apart or near the International Date Line.

Send an invitation that survives forwarding

Include both cities, both dates, AM or PM, duration and a calendar invitation with its time zone set. For example:

Avoid relying on abbreviations alone: CST can refer to different time zones. A city plus a dated UTC offset makes the intended time clearer. If you later change the meeting date, recalculate the conversion before sending an update.

How these examples were checked

The examples use the same bundled IANA data, edition 2026c, as the converter and are checked against the local clock readings for the stated dates. They are examples for 2026, not permanent offsets between cities. The IANA Time Zone Database is updated when authorities change civil-time rules. Future meetings use the rules known to this edition; important dates should be reconfirmed after a rule change.

Read about our data and accuracy. Spot a problem? Email fpeverini@gmail.com with the cities, date and time you entered.

Try your meeting in the converter → · About · Privacy