How to Coordinate Meetings Across Time Zones

Quick answer

Coordinate meetings across time zones using an exact date, a named time zone for each participant, and an event whose final time is checked before sending. Do not rely on a remembered offset or assume daylight-saving changes happen on the same day everywhere.

The assistant's brief should identify whose working hours take priority and what happens when there is no comfortable overlap. Time conversion solves only part of the scheduling problem.

Collect the right location information

Ask for the participant's working time zone, not only the headquarters city. A person may be traveling or working remotely. If the meeting is next month, the relevant zone is the one they will use on that date.

Use names such as America/Los_Angeles or Europe/London in the planning brief where your tools support them. In external communication, include a readable zone and date. Avoid “morning” without specifying whose morning.

Google's Calendar time-zone guidance explains event and calendar time zones and how events appear for people using different zones. Check the actual event settings rather than assuming the invitation's typed description determines its scheduling behavior.

Define the overlap policy

Give each participant's acceptable hours and identify required attendees. A technically available 3 AM slot is usually not a sensible recommendation merely because a calendar is empty.

Decide how to handle inconvenient overlap. You might alternate the burden for a recurring meeting, limit early starts to a specific day, or ask the owner to choose between an early call and asynchronous work.

Set the duration before searching. A 20-minute overlap may accommodate a short decision call but not a one-hour workshop. If the task can be shortened, that should be an explicit owner choice.

An illustrative three-location review

A team in Los Angeles, London, and Singapore wants a product review. The assistant receives each participant's working zone and acceptable hours for the specified dates. It discovers no slot that fits all three preferred windows.

The useful output is not a falsely confident conversion table. It is a decision: choose a short call with one participant outside their preferred window, split the discussion, or use an asynchronous brief and collect decisions later.

For a recurring review, the team might rotate the inconvenient slot. The assistant should document the rule and check future dates individually, since offsets can change. It should not extrapolate one week's conversion across an entire season without verification.

A time-zone scheduling brief

Coordinate a 30-minute review on the supplied dates with the three required participants. Use the named time zones and acceptable working windows in this brief. Show each proposed time in every participant's local zone. Do not book outside those windows without approval. If no overlap exists, return the closest two options and identify who would be affected. Verify the final event time, attendee list, and time-zone setting before sending.

This illustrative example keeps conversion, preference, and authority separate. The assistant can prepare options while the owner decides which inconvenience is acceptable.

Check daylight-saving boundaries

For a meeting near a seasonal clock change, inspect the specific date in your calendar or another authoritative time-zone-aware tool. A familiar city-to-city offset may differ from the previous week.

For recurring events, decide whether the meeting follows a fixed local time in one reference zone or should be reconsidered after clock changes. Those policies can produce different local times for other participants.

Communicate the choice plainly. “Every Tuesday at 9 AM in the organizer's zone” is different from “a mutually convenient weekly slot that we revisit when working hours stop overlapping.”

Verify the invitation, not only the email

Open the created event and inspect its date, start, end, and zone. Confirm that each person is seeing the intended local time if the meeting is especially constrained. A correctly written email can accompany an incorrectly configured event.

Include time-zone context in the completion report and mark any pending attendee response. If somebody replies with a bare “10 works,” ask which offered option they mean when more than one interpretation is possible.

Keep future travel changes visible in the task. A participant moving zones after accepting may need another check even when the original conversion was correct.

FAQ

Can I use a fixed UTC offset?

It may be sufficient for a specific verified instant. Named zones are more useful for future dates and recurring schedules because offset changes can matter.

What if there is no reasonable overlap?

Return the tradeoff for a human decision. Shortening, splitting, or asynchronous preparation can be better than routinely imposing an unreasonable hour.

Where can Righthand fit?

Explore meeting scheduling, calendar sync, and smart scheduling, then verify the final event against the named zones.