Async Handoffs Across Time Zones: The Four-Field Format

An async handoff is a written note that passes work from one person or time zone to the next without a meeting. It works when it answers four questions: what changed, what is blocked, what was decided, and what the next person should do first.

On a team split across time zones, the work changes hands every day. When the Tokyo office logs off, Amsterdam is halfway through its morning, and the people there cannot ask a question and get a reply until the next day. A weak handoff costs them hours of rebuilding context, or a day of waiting. A good one lets them start working the moment they finish reading.

The four fields

Field	What to write	Example
Changed	What moved since the last handoff	Payment retries are live on staging
Blocked	What is stuck, on whom, and what unblocks it	Prod deploy waits on security sign-off from Nina
Decided	What was decided, by whom, and why	We will keep the old endpoint until Q1 for the partner app
Next	The one or two things the next person should do first	Rerun the load test after the config change, then merge PR 482

Most handoffs cover the first field and skip the other three. "Changed" is easy, because it is a list of what you did. "Blocked," "decided" and "next" take thought, and they are what the reader needs.

A simple handoff protocol

1. One place: every handoff goes in the same channel, doc or tool.
2. One time: each shift posts its handoff by a fixed time before logging off.
3. One format: the four fields, in the same order, every time.
4. Read before asking: the incoming shift reads the handoff before sending any question.
5. Close the loop: questions the handoff did not answer go back in writing, and the answer goes into the next handoff.

That is the whole protocol. Teams that add more steps usually stop following them.

Ten habits that make handoffs work

1. Write state, not activity. "PR 482 needs one approval" beats "worked on PR 482."
2. Name people. "Blocked on security" is vague; "blocked on Nina in security" is a next step.
3. Put decisions in the handoff, with the reason, and in the team's decision log.
4. Say what can wait, so the next shift does not rush on things that do not matter.
5. Flag anything that looks broken but is expected.
6. Link, do not paste. Point to the ticket, the thread and the dashboard.
7. Keep it short. If it takes more than a few minutes to write, it will be skipped on busy days.
8. Write for someone who was not there. Spell out names the reader may not know.
9. Agree who may decide what while you are offline, so questions do not wait a full day.
10. Hand off at the end of the week too, with a short summary of what shipped and what slipped.

How to tell your handoffs are working

You do not need a dashboard. Watch for these signs over a month:

• The next shift starts work without sending questions to the people who just logged off.
• Nothing gets done twice because one shift did not know the other had done it.
• Decisions made in one time zone are not reversed in the next.
• People stop messaging colleagues who are asleep or on leave.
• New team members can follow the handoffs without a guide.

If questions keep arriving after every handoff, look at which field they are about. That tells you what the handoffs are missing.

Rolling the practice out

Start with one team and one week. Agree the four fields and the time, and have the team lead post the first few handoffs as examples. At the end of the week, ask the receiving shift what was missing, and adjust. Most teams settle into the habit within two weeks. Make the handoff part of how work is done, not an extra report: if a decision is not in the handoff, it did not reach the other time zone.

Common mistakes

• Writing a diary of the day instead of the state of the work.
• Handing off in a meeting that half the team cannot attend.
• Leaving decisions in chat threads the next shift will never see.
• Treating every handoff as urgent, so the important ones get lost.
• Changing the format every month.

For a copy-and-paste version for engineers, use the engineering handoff template. If you are choosing software for handoffs, see the comparison of tools for async handoffs. When context still goes missing between handoffs, the field guide to context lost between handoffs helps find where. And for the related case of covering someone's work while they are on leave, see the guide to covering for a teammate on leave.

Where StandIn fits

StandIn is a personal knowledge base, built on the work that you already do, that answers your teammates when you're away, in chat and email. When Sarah logs off in Tokyo, Alex in Amsterdam can ask her StandIn what is blocked or what she decided, and get the answer from her brief, in her words, with the source. When the answer is not there, it never guesses: it says so and points to the person who knows. See how this works for teams working across time zones.