Calculate every recurring meeting in local time, group live work into the smallest sustainable window, and make the rest asynchronous.
Who this is for
People whose destination and employer, team, or clients are far enough apart that meetings could damage sleep, relationships, or the reason for traveling.
Reject any schedule that requires both early-morning and late-night live work on most days. One bounded overlap block is the sustainability test.
Work through it step by step
Conceptual planning sceneMap a representative month
Include recurring meetings, deadlines, escalation, and daylight-saving changes.
Illustrated Buenos Aires exampleChoose one live block
Avoid scattering calls across both early morning and late night.
Illustrated Lisbon exampleRedesign asynchronous work
Use written decisions, handoffs, office hours, and response expectations.
Illustrated Tokyo exampleTrial the schedule at home
Work destination hours for several days before paying for the stay.
Picture the ordinary week, then test the constraints.
The illustrations help you imagine the decision. Open each field file for the city-specific tradeoffs and reviewed source status.
Buenos AiresIndependent workers wanting dense city life, late culture, and easy overlap with the Americas.LisbonEurope-facing professionals, coastal access, transit, and a slower rhythm than the largest capitals.TokyoOperational reliability, rail-based life, dense convenience, and deep neighborhood exploration.A realistic example
A product lead tests Tokyo while supporting California. The calendar converts to several meetings after midnight, so she proposes two shared late-afternoon California windows, written handoffs, and rotating attendance. The trial still harms sleep, making a shorter stay or a better-aligned destination the honest choice.
Mistakes to avoid
- Checking only the offset
- Ignoring daylight-saving dates
- Normalizing midnight calls
- No escalation coverage