Start with shared context
Before you propose a slot, collect everyone’s city plus “willing-to-take-calls” window. Throw that list into the Timezone planner so overlap lives in a single link or screenshot. Paste it into the invite so the inevitable “why 10:30?” complaint has an answer. Keep the World Clock wallboard visible while you iterate and scan the DST Planner to see who’s about to shift an hour next week.
Example: Product or design review (San Francisco, Bogotá, Stockholm)
SF works 09:00–17:00 PT, Bogotá 08:00–17:00 COT, Stockholm 09:00–18:00 CET. Timezone shows overlap at 10:00–11:30 PT (12:00 Bogotá / 19:00 Stockholm). Instead of locking Stockholm into nightly calls, publish a rotation in the invite: Week 1 at 10:30 PT, Week 2 at 08:30 PT (Europe-friendly), Week 3 async Loom updates for whoever would lose sleep. Writing the rotation into the notes prevents the usual “why is Europe always punished?” thread.
Example: Customer support relay (New York, Nairobi, Manila)
The handoff is 30 minutes. New York 09:00–17:00 ET, Nairobi 09:00–18:00 EAT, Manila 09:00–18:00 PHT. Pure overlap lands at 09:30 ET / 17:30 EAT / 00:30 Manila—awful. Schedule two live calls per week at 08:00 ET (16:00 Nairobi / 23:00 Manila) and cover the other days with a recorded Loom plus checklist. When leadership says “just keep it daily,” share the World Clock wallboard and let them see the midnight block staring back.
Example: Advisory board (Singapore, Dubai, Chicago)
Singapore 09:00–18:00 SGT, Dubai 09:00–18:00 GST, Chicago 09:00–17:00 CT. Timezone exposes one humane window: 08:00 Chicago / 17:00 Dubai / 21:00 Singapore. Label it “live overlap” and rotate. Every third session becomes async for APAC while North America hosts a later Q&A so nobody lives in a perpetual 9PM slot. Track the rotation right in the invite description and remind the board when the next shift happens.
Checklist before hitting send
- List every city and working window in the invite notes so newcomers see the constraints instantly.
- Link to the saved Timezone planner view for self-serve conversions.
- Call out the next DST transition with “London shifts +1h on March 31” style notes.
- Document the rotation cadence (weekly/monthly) and name the person who owns keeping it honest.
Try the tools
Related guides
FAQ
- How often should we revisit the schedule?
- At least every DST season and anytime someone relocates or joins. If weekends feel different, revisit sooner.
- How many cities is “too many” for one live call?
- If the Timezone planner shows less than an hour of humane overlap, pick rotations or async updates—don’t force midnight.
- What if there is zero overlap?
- Run alternating live sessions and recorded updates so pain rotates. Publicly log who took which hit.
- What if someone’s hours change mid-project?
- Edit the Timezone view immediately, paste the new screenshot into the invite, and explain the adjustment. Transparency buys goodwill.
- Do internal tools replace calendar notes?
- No. Put the Timezone screenshot or World Clock link inside the invite so new attendees understand the math without spelunking for context.
Need to propose the next slot? Use the Timezone tool.