How to hand off work across time zones without losing a day

Working across time zones has a hidden cost. When your teammate starts their day as yours ends, every unclear question costs a full day: they ask, you're asleep, you answer, they're asleep. A task that should take two days takes six, and nobody did anything wrong.

The fix isn't more meetings or longer overlap hours. It's a handoff that answers the next person's questions before they have to ask them, plus a rule for what happens when they can't reach you.

Write a handoff note at the end of your day

A handoff note is short and written for someone who wasn't there. It takes five minutes and saves the next person an hour of guessing. Write it in the same place every day, in the task itself or a shared channel, not in a private message.

Handoff: [task], [your name], [time with time zone]

Where it stands: [one or two lines]
Next step: [the very next thing to do]
Decisions needed: [question] (default if no answer by [time, zone]: [what happens])
Files and links: [where everything is]
Don't touch: [anything mid-change or waiting on someone]
I'm back at: [time with time zone]

The decide-or-default rule

The most expensive handoff is the one that ends in a question. If your teammate needs your decision to continue, and you're asleep, they wait a whole day.

So never hand off a bare question. Hand off a question with a default: what you'd like them to do if you haven't answered by the time they need it. “Use the blue header unless I reply by 10am your time” lets them keep working. If you do reply in time, they follow your answer. If you don't, the work moves anyway, and the default was your call.

• Pick defaults that are easy to undo. If the choice can't be reversed, say so, and ask for something else to work on while they wait.
• Put the deadline in their time zone, not yours.
• If you change your mind after the default kicks in, treat it as a normal change, not a mistake on their side.

Write times with zones, every time

“Tomorrow morning” can mean two different days in two time zones. Write times with the zone: “Thursday 9am London” or “16:00 UTC”. If your team spans many zones, pick one reference zone for deadlines and write it everywhere, so nobody has to convert in their head.

Use the overlap for what needs it

If you share an hour or two of working time, protect it for the things that are hard to do in writing: a disagreement, a new piece of work being explained, a review where the back-and-forth matters. Don't spend it reading status aloud. Status travels well in writing.

1. Agree on the overlap window and put it in everyone's calendar as a recurring block.
2. Bring a list. Each person writes down what they need from the others before the window opens.
3. End the overlap with written decisions, so the person whose day is ending can log off with nothing hanging.

When you pick up a handoff

Receiving a handoff well matters as much as writing one. Start your day by reading the notes addressed to you before anything else, then reply to the handoff with one line: what you're doing first, and whether any default kicked in. The person who wrote it wakes up to an answer, not a silence.

Picked up: [task], [your name], [time with time zone]
Doing first: [next step]
Defaults used: [none, or which one]
Questions for you: [question] (my default: [what I'll do])

A worked example

Maya in New York finishes a client proposal draft at 6pm. Ravi in Bangalore starts work a few hours later, when it's late evening in New York. Without a handoff, Ravi opens the doc, doesn't know whether the pricing section is final, and messages Maya. She replies the next morning, her time. Ravi has lost his day on that task.

With a handoff, Maya's note says: “Pricing section is a placeholder. Next step: tighten sections 2 and 3. Decision needed: two or three package options? Default if no answer by 11am Bangalore: three. Don't touch the cover page, the client is sending a new logo.” Ravi works through his whole day, uses the default, and leaves a pick-up reply. Maya wakes up to a better draft and one line telling her what changed.

Habits that make it stick

• One place for handoffs per project, not scattered across messages, email and comments.
• Every handoff has a next step, even when the answer is “wait for the client”. Then say what to work on instead.
• Short beats complete. Five lines that get read are better than a page that doesn't.
• Thank people for good defaults. It tells the team that moving forward without you is the point, not a risk.

None of this needs new tools. It needs a template, a rule about defaults and the habit of writing times with zones. After a couple of weeks, your team will stop losing days to questions that could have been answered the night before.