English for communicating across time zones

Learning objective

By the end of this lesson you will be able to use English to schedule, confirm and hand over work across time zones without confusion.

Stating times clearly

Always include the time zone when you communicate across regions. "Let's meet at 3 p.m." is ambiguous; "3 p.m. CET / 9 a.m. EST" is clear. If your audience is global, use UTC as a reference and include local equivalents. A simple format is "15:00 UTC (10:00 New York, 23:00 Tokyo)." This reduces the risk of missed meetings.

Proposing and confirming slots

Offer two or three options rather than asking an open question. "Would Tuesday 14:00 UTC or Wednesday 09:00 UTC work for you?" is easier to answer than "When are you free?" When someone proposes a time, confirm explicitly: "Tuesday 14:00 UTC works for me. I will send the calendar invite." Avoid vague confirmations such as "Sounds good" without the time.

Asynchronous messages that age well

In distributed teams, messages may be read hours later. Write them so they make sense without additional context. Include the background, the specific question and the deadline: "Background: the client asked for a revised timeline. Question: can we move the delivery to Friday? Please reply by Thursday 12:00 UTC." This format lets people respond efficiently.

Handing over work

A clean handover saves the next person time. State what is done, what remains and what decisions are needed. "Status: draft complete. Next: legal review. Owner: Maria. Blocker: waiting for budget approval." Use consistent labels so teammates can scan quickly. If the handover is complex, add a short voice note or a shared document link.

Managing delays

Time zones can cause delays, so build buffers into deadlines. If a response is late, follow up politely with the time zone included: "Following up on the question below; could you reply by tomorrow 10:00 UTC?" Avoid blaming time differences; instead adjust the process.

Common mistakes

• Omitting time zones.
• Offering too many options.
• Writing messages that require immediate context.
• Assuming everyone works the same hours.
• Leaving handovers incomplete.

Practical tips

Create a small table of your regular collaborators with their time zones and working hours. Use calendar tools that display multiple zones. Standardise your handover format. Review a week of messages and identify where a time zone or deadline was missing.

Summary

Clear cross-time-zone communication uses explicit time statements, limited options, self-contained async messages and structured handovers.

Worked example

A vague message: "Can we meet tomorrow?" A clearer message: "Could we meet on Tuesday at 14:00 UTC (09:00 New York, 22:00 Tokyo)? If that does not work, Wednesday 09:00 UTC is also possible. Please confirm by Monday 12:00 UTC." The second message gives options, zones and a deadline, so it can be answered quickly.

Practice task

Rewrite three recent scheduling messages with explicit time zones, two options and a confirmation request. Check that each message can be understood without follow-up questions. Save the best version as a template.

Further practice

Create a time-zone table for your regular collaborators. For each, note their working hours and preferred contact method. Use it to plan one week of meetings and messages, then review whether any communication failed because of time differences.

Extension

For one upcoming meeting, send the agenda with times in three zones. After the meeting, note whether anyone missed or misunderstood a time. Use the result to improve your next invitation.

Related lessons

Continue with English for multilingual workplaces, English for business meetings, and English for project updates.