Your AI-drafted invite says “Fridays at 9 in New York, 2 in London.” The first Friday goes fine. The next week, the London approver is still at lunch when the call starts. Would you move the whole series or just one Friday?
The quick fix: Ask AI for a date-by-date review sheet. Check the conversions in your calendar, then change only the dates that fall outside someone’s agreed hours.
Fictional workplace scenario. The sample wording is written for this article. The time conversions were checked against time-zone data.
Find the Friday that breaks the rule
A New York team holds a 30-minute release review at 9:00 a.m. every Friday. Its London approver can join from 1:30 to 4:00 p.m. The team wants to keep the New York start time when possible.
Pick one: keep all three invites as drafted, move just October 30, or move every Friday.
Reveal the answer
Move just October 30 for these three dates. The UK had already changed its clocks that week, while New York had yet to change. On October 30, 9:00 a.m. New York was 1:00 p.m. London. A 9:30–10:00 a.m. New York slot would have been 1:30–2:00 p.m. London, subject to both teams’ availability. The other two dates already fit.
Give AI the rule behind the invite
“Write a weekly invite for 9 New York / 2 London” looks specific. It leaves out which city’s clock sets the series. If New York’s 9 a.m. stays fixed, London’s local time can move when the cities change clocks on different dates.
Try this instead: “Keep the series at 9:00 a.m. in America/New_York. Flag each occurrence when the full 30 minutes falls outside London’s 1:30–4:00 p.m. window.” Add the first date, the dates you want checked, and any days people are unavailable.
If nobody has decided which local time should stay fixed, let the AI turn that gap into one question for the organizer. If both cities’ local times must stay fixed, plan to review exceptions or consider an asynchronous approval on the affected dates.
Check the output before you send it
Check actual dates. Open the first occurrence and the dates on either side of the next clock change in each location. Use the city time zones and the actual start and end dates, especially if the meeting crosses midnight for someone.
Check the whole window. An invite can start during working hours and still run past them. Apply the start and end constraints, then check calendars for conflicts before accepting a proposed move.
Keep the invite clean. Put the recurrence and any approved exception in the calendar itself. A description that repeats the same converted hour every week can become misleading. If you need to share a local time in chat, include the specific date and city.
Copy the AI review prompt
Prepare a review sheet for a recurring meeting. Keep the calendar untouched. Anchor city time zone: [IANA zone] First date, local start, duration, recurrence: [fill in] Dates to review, including clock changes: [fill in] Other participant city zones and allowed hours: [fill in] Return one row per date: anchor start and end, each participant's local date and start/end, availability fit, and next action. Ask if the anchor is missing. Flag unknowns and mark any time conversion that still needs verification. Keep the original rule on dates that fit. For a conflict, propose an exception for human review. Do not claim calendar availability unless supplied.
Copy a blank row for your next invite
Worked row: Oct 30, 2026 · New York 09:00–09:30 · London 13:00–13:30 · Outside agreed hours · Review a one-off move.
Copy the blank row
Date: Anchor zone and local start/end: Participant zone and local date/start/end: Agreed hours: Fits? Yes / No / Needs verification Action and owner:
You only need one confirmed schedule before anyone gets an invitation. The review sheet shows exactly where the series needs an exception and gives the organizer a concrete decision to make.
If the teams can approve the release asynchronously, start with this checklist for writing a handoff someone can follow.
Sources and editorial notes
Checked November 6, 2026. Technical references: Google Calendar’s recurring-event time zone documentation and IANA’s Time Zone Database. The example conversions were independently checked using Python’s zoneinfo with America/New_York and Europe/London.
Editorial reading: Zapier on working across time zones and Team TimeZone on scheduling across time zones. The cover and the three-date graphic are original WorkTool Note artwork.