Communicate across time zones with explicit dates

‘Friday afternoon’ can describe different hours, working days and even dates for colleagues in different regions. Use explicit dates and time zones for commitments that depend on a particular moment. The extra words are usually cheaper than a missed review.

Write the calendar date rather than relying solely on ‘tomorrow’ or ‘next week’. Those phrases lose their reference point when a message is forwarded or read later. Include the year when records may be revisited over time or when the date could be ambiguous.

Avoid ambiguous shorthand

Use a month name where numeric date order could be misunderstood. ‘6 November’ is easier to interpret across regions than a numeric form whose month and day can be reversed. For a timed event, name the relevant location-based time zone or provide an unambiguous offset appropriate to that date. Do not assume that a familiar abbreviation means the same thing to every reader.

Calendar invitations can display an event in each participant's local time, but check that the invitation itself uses the intended zone and date. For an important deadline, repeat the essential timing in the written request. The invitation and message should agree.

Define what must happen by that time. ‘Draft due’ may mean uploaded for internal review or ready for a client to receive. A precise timestamp does not repair an unclear deliverable. State the action and the version expected alongside the timing.

Plan for the gap between working days

A question sent at the end of your day may arrive after someone else's working hours. Build a response window around the actual overlap, not the assumption that everyone checks messages continuously. If a task must move between regions, include a handover that lets the next person proceed without waiting for basic clarification.

For a hypothetical review, you might ask for comments by a stated date and local time, then explain that the editor will consolidate them in the next working session. This makes the reason for the deadline visible. It also helps reviewers understand whether a later reply can still be included.

When recurring meetings or deadlines cross seasonal clock changes, check the relevant dates rather than assuming the difference between locations stays constant. If a time changes, update the invitation and send a clear correction that identifies the new timing. Do not leave competing versions in separate messages.

Good time-zone communication is not about making every sentence technical. It is about removing ambiguity where coordination depends on it, while respecting that another person's working day may not match your own.