A workweek that survives time zones

A schedule built for a fixed desk breaks on the first travel day. The fix is not a more detailed calendar. It is a small number of anchors that survive a new city, a new time zone and a week of bad wifi.

This is a working shape, not a prescription. Take the parts that fit your clients and leave the rest.

Pick three anchors

An anchor is something that happens at the same local time regardless of the city. Three is enough. More becomes a schedule you maintain instead of a life you live.

• A start. Coffee, a walk, a stretch, the same playlist. The point is a cue, not a ritual.
• A deep block. One protected period for the work that needs your full attention. Put it where your energy is best, not where the client's time zone is most convenient.
• A shutdown. A short, repeatable end to the working day: close the laptop, write tomorrow's first task, leave the desk.

The anchors are local-time habits. The client meetings float around them. That order matters: if the meetings set the anchors, the first late call takes the week.

Protect one deep block

Most remote weeks fail because the deep work is scheduled last. Put one block in the calendar before the meetings, and treat it as a meeting with someone you cannot reschedule.

If a day has no deep block, it is an admin day. Say so, and do not expect a creative output from it.

Make the time zone visible

The most common coordination failure is not a missed call; it is a message sent at the wrong local hour and read as urgency. Put the time zone in your calendar and in your update format.

• Use one calendar in UTC and one in local time. Check the conversion before you agree to a recurring slot.
• Write deadlines with the zone: “Friday 17:00 CET”, not “Friday”.
• In a weekly update, state your local working hours and the overlap window. It saves a round trip every week.
• When a client changes the meeting time, repeat it back with the zone in the reply.

End the day on purpose

Without a commute, the day has no edge. A shutdown is the edge. It does not need to be long; it needs to be the same.

1. Write the first task for tomorrow. One line, specific.
2. Close the tabs that belong to tomorrow.
3. Leave the desk, even if the desk is a kitchen table. A short walk is enough.
4. Do not check the client channel “one last time”. It turns the evening into a low-grade standby shift.

The weekly review

Once a week, spend fifteen minutes on three questions:

• What moved? One outcome, not a list of activity.
• What is blocked? Name the person and the date you asked.
• What is the next deep block? Put it in the calendar before the week fills.

If the answer to the first question is “nothing”, the week was probably admin. That happens. The review is there to notice it before it becomes a month.

Adapt it to your work

• If you work across many time zones: move the client window, not the anchors. Keep the deep block local.
• If you have a family: make the deep block the first thing, before the school run if possible, and protect the shutdown for the family instead of the desk.
• If you are in a coworking space: use the commute as the anchor. The walk to the space is the start; the walk back is the shutdown.

What this page is not

It is not medical advice, a treatment for sleep problems, or a claim that a routine fixes a bad client. If your sleep or mood is affected by travel, talk to a qualified professional. The page is a shape for the working day, nothing more.

Related

• The 20-minute reset between cities
• Write a weekly update that prevents scope creep
• A portable agent setup