CrossClock

Guide · async work

When the meeting should be a handoff instead

A cross-zone call is not just 45 minutes. For the person joining at 22:00 it is an hour of their evening; for the team it is the most expensive channel it owns. Here is how to tell whether this particular topic deserves it.

What the call actually costs

Multiply the number of attendees by their hourly cost and by the meeting length; then add the edges — the context switch before, the summary after, the odd-hour recovery for whoever joined from the far side of the world. For a six-person team at an average loaded cost of $80 an hour, a 45-minute sync is roughly $360 before any of the edges. A one-hour weekly version is about $21,000 a year.

That number is not an argument against meetings. It is an argument for spending them on things that only a live conversation can do. The planner's cost card does the multiplication for you, and keeps the rate in the tab — it is not stored or sent anywhere.

Three questions

Before booking, answer these in order. If all three are “no”, a written handoff will be faster and better.

  1. Does something need to be decided, with people who disagree? Decisions benefit from the back-and-forth that text flattens: reading the room, testing a half-formed idea, resolving a conflict that would otherwise fester in a thread. If nobody disagrees and the answer is already clear, you need a decision record, not a call.
  2. Is the information ambiguous enough that questions will follow? A short, well-structured update answers predictable questions on its own. A topic where you cannot predict the second question — a design review, a postmortem, a negotiation with a partner — usually needs a live pass.
  3. Does the relationship need the live signal? Tone, hesitation and enthusiasm do not survive a summary. A new joiner, an unhappy client, a sensitive performance conversation: those justify the hour even when the content could be written.

If the answer is “we meet because it is Tuesday”, that is the clearest signal of all. A recurring call with no decision on its agenda is a tax paid in the team's best hours.

The handoff that survives a 14-hour gap

The alternative to a cross-zone call is not silence. It is a written handoff that the next region can pick up without asking a single clarifying question. In practice that means four fields and one deadline:

What changed — facts since the last update, each with a link to the source. Two or three lines, not a status essay.

What I need from you — a numbered list. “Approve the vendor”, “confirm the launch date”, “tell me which of these two designs to build”.

By when — the deadline in UTC plus the local time of the person who owns it, and what happens if it slips.

What I already decided — so nobody reopens a question that is closed. Include the reason in one line.

Post it at the end of your own working day, which is the start of someone else's. That is the one scheduling rule that makes a 14-hour gap an advantage: the work moves overnight, and by the time you wake up the answer is waiting.

When a call is still right

Keep the live hour for: a decision with a real disagreement, a first meeting with someone new, anything where trust is the actual deliverable, and the periodic moment where a distributed team remembers it is a team. One well-run weekly call with an agenda and a written outcome beats five calls that exist because nobody wanted to write the summary.

Make the async option easy to choose

The reason teams default to meetings is that a meeting is one click and a written handoff is twenty minutes of writing. Reduce that gap:

And when you do book the call, book it honestly: use the CrossClock planner to see who is at work, who is awake and who is asleep, and rotate the awkward hour instead of always spending the same region's evening. The scheduling guide walks through the arithmetic.

See what your next call would cost — and who it would wake up.

Open the planner