How does a team stay in step across time zones with agents?
By Soumen Sarkar · October 2026
Short answer: A team stays in step across time zones by making the work explain itself: every session leaves a handoff, every change carries its reasons, and every assumption is written down where the next person sees it. Then nobody waits for someone else to wake up.
Why do time zones hurt more with agents?
Agents make each person's working day more productive, which also means more happens between the moments two teammates are both awake. A question left for a colleague in another region waits half a day, and during that half day dozens of changes land around it. The fix isn't more overlap hours. It's work that answers its own questions, so the next region never has to ask.
What should every piece of work leave behind?
Three things, written for someone who can't ask you.
- A handoff when a session stops: what's done, what's unfinished, the next step, the open questions and the traps. The handoff template gives the shape.
- Reasons with every change: what it's for, the calls made, what was assumed and what was tried and dropped. A reviewer eight hours away reads these instead of messaging you.
- Assumptions in the open: when something was unclear, the one-line assumption the work rests on, so the person who knows can correct it during their day.
If those exist, the end of one region's day is the start of the next one's, with no gap.
What does a handover between regions look like?
Picture a hypothetical team split between Lisbon and Singapore. At the end of the Lisbon day, an agent working in Exports · lib/exports stops halfway through adding CSV exports. Its handoff says the export builder is done and tested, the download button isn't wired up yet, the next step is to add the button to the reports page, and it assumed exports are capped at 50,000 rows. The trap: don't stream from the read replica, it lags by minutes.
The Singapore developer starts their morning with that handoff. Their agent continues from the next step, avoids the replica, and finishes the button. Meanwhile the person who owns reporting confirms the 50,000-row cap. By the time Lisbon wakes up, the work has landed, with its reasons attached, and nobody had to wait for anyone.
How do you keep the morning from becoming catch-up?
Read what changed, not everything. Each person should start with what's waiting for them: handoffs meant for them, corrections to their assumptions, work they built on that has landed. Everything else can be read when it matters.
Watch pick-up time, how long a handoff sits before someone continues it. Across time zones it should be about one night, not two days.
Does Campfyrr help with this?
In Claude Code, Campfyrr writes the handoff from the session when it stops, attaches each change's reasons on commit, and opens the next session with a brief of what happened since your last one, with your handoffs and unfinished work at the top. Daily updates are written in plain words at each person's end of day, so each region reads the other's day without anyone writing a status report.
Words used here
- Handoff: A handoff is what unfinished work carries for whoever continues it: what's done, what's left, the next step, and what to watch out for.
- Reasons: Reasons are what a change is for, the calls made in it, and what was assumed, attached to the change for whoever reviews it.
- Landed: Landed means work that finished, shown with what it turned out to be compared with its plan.
- Pick-up time: Pick-up time is how long a handoff waits between being left and someone picking it up to continue the work.
The principle behind this: Let the work speak: Our work explains itself, so nobody ever has to come and ask us.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).