Write the calendar date, the clock time and the location or zone that owns the deadline. For a global handoff, include the UTC equivalent too. “Friday at five” leaves people in other offices to choose which date and zone you meant.
At 17:00 in New York, the equivalent UTC time is 21:00 while the offset is UTC−04:00 and 22:00 while it is UTC−05:00. The IANA Time Zone Database tracks changes to local offsets and daylight-saving rules. Set the event in the owning location's zone and let the calendar calculate the offset for that date.
Decide whether the deadline is an instant
A filing portal that closes at a fixed time needs an instant. A team's “review this by the end of your own Friday” can be a local date rule. Give a date-only instruction the relevant locale, especially if someone will turn it into an automated reminder. RFC 5545 distinguishes date-only values and date-times, including floating clock times with no zone. An all-day label does not by itself establish a single moment everywhere.
Imagine that a review closes at 17:00 New York time on a day when the offset is UTC−04:00. It is 21:00 UTC and 06:00 the following morning in Tokyo at UTC+09:00. A line in the handoff document can read “Review closes at 17:00 America/New_York on the stated date. In Tokyo that is 06:00 the next day.” Give the actual dates in a real message. Avoid loose zone abbreviations that could identify multiple places.
Check the invitation and the text
Google Calendar can store an event in a specific zone and show it in each invitee's local zone. Set the owning zone before sending the event. Open the calendar in a second display zone or ask an invitee to confirm both the date and the displayed time. The event description still needs an explicit deadline because pasted text does not convert with the event.
Set a second display zone to the receiving office and keep the sender's zone in the written deadline. If someone edits the event, compare the UTC instant before and after. A change in the displayed clock time can come from changing the display zone alone.
Put both dates in the handoff
Here is an example you can use to check an invitation. Choose Friday, July 10, 2026 at 5 p.m. in New York. In the example, New York is four hours behind UTC. Tokyo is nine hours ahead of UTC, so the deadline reaches Tokyo on Saturday at six in the morning. The reading window for the Tokyo team closes before many people begin their Saturday. If Friday afternoon in Tokyo is their last useful time to respond, add a separate internal target for their comments.
| View | Calendar date | Displayed time |
|---|---|---|
| New York, the owning zone | Friday, July 10 | 17:00 |
| UTC, for systems that use it | Friday, July 10 | 21:00 |
| Tokyo, the receiving office | Saturday, July 11 | 06:00 |
Ask the recipient to confirm the date as well as the time. If someone answers only “yes, at six,” you still cannot tell which day their calendar shows. For a recurring handoff, test what happens if the receiving colleague is travelling. Their calendar can change its display, but the acceptance message should identify the deadline in the owning zone even while they are on the move.
Find out which clock the system uses
A human email and an automated submission portal might use different calendars. Inspect the actual closing message on the portal. If it gives a UTC clock time, copy the full date and time verbatim into the work instructions and calculate local equivalents separately. If the system names its business location, let your calendar resolve that location's offset for the day. Screenshots of settings can help when a team is trying to reconcile two displays. A screenshot is most useful when it includes the date, the application or account, and the configured display zone alongside the clock.
Verify a weekly recurrence in winter and summer. For a meeting intended to remain at 17:00 New York, January 9 at the same local hour gives 22:00 UTC under the standard offset. Tokyo sees 07:00 the following day. A server process that must run at 21:00 UTC every Friday has a different requirement. In the January example it reaches New York at 16:00. Before editing, ask the owner which clock should stay fixed. Where the local meeting time is the contract, replace any hard-coded offset with a location-based zone supported by the calendar.
Clocks that repeat or skip a local hour during a change call for extra care. If a policy says “1:30 a.m.” on a day when clocks move back through that time, ask for the UTC time or an explicit offset for that occurrence. Two instants can share one displayed clock time. For deadlines that people set by hand, a business-hour cutoff away from the change is easier to express and check.
Preserve the cutoff during rescheduling
Copy the owning date and zone from the existing event before anyone moves it. When the edit is done, have a second person open the updated event in their own display zone and compare it with the written cutoff. This is most useful at month-end and around dates when offices change clocks on different weekends. If the timestamp on the recipient's reply looks wrong by a full day, check whether they read the display time without its date.
Record which of the two times the person editing the event was allowed to change. A work block can move when its owner has a conflict. The cutoff follows the person or system that accepts the finished work. If your team needs help finding a new working time before that cutoff, use the workday capacity example to check which blocks can move.
For handoffs that go into a shared document, use a small check before posting the date on several surfaces. Have one person write the cutoff in the owning zone and another calculate the instant from the calendar event. Publish only when those two agree. Give chat reminders the same date and zone and keep them linked to the calendar event. When a client changes a cutoff, update the invitation and the source document together. A reminder already copied into a third person's task list may need a separate message.



