Follow-the-Sun Video Editing: How to Pass a Cut Across Three Time Zones Without Losing a Day

There's a version of this that sounds almost too good to be true: a rough cut leaves an editor's desk in Manila at the end of their day, lands in London a few hours later while that editor is just sitting down for breakfast, gets refined and handed back before lunch, and is sitting in a producer's inbox in Los Angeles fully polished by the time anyone on the US team has had their coffee. That's follow-the-sun editing, and when it actually works it feels close to magic, three time zones effectively turning a single eight-hour workday into something closer to a twenty-four hour production line. The catch, and there's always a catch, is that it only works if the handoff between each leg of the relay is built to survive total silence, because nobody in this chain is ever awake at the same time as the next person picking up the baton.

This is a close cousin of the two-person version of this problem, which we've written about separately in our piece on keeping a video team productive across a twelve-hour gap, and honestly a lot of the same fixes apply once you scale from two people to three, they just have to get more disciplined as you add regions.

What Follow-the-Sun Actually Means for a Video Team

The phrase gets thrown around a lot in post-production circles, usually by studios big enough to have full offices in three regions, but the underlying idea scales down just fine to a single editor working with two collaborators or even a producer who splits review duties across a couple of freelancers in different countries. The point isn't headcount, it's continuity: work keeps moving forward across the clock instead of sitting untouched for sixteen hours while everyone in one region sleeps. We built PlayPause's review layer with exactly this pattern in mind, because a lot of our best customers aren't big enough to run a real follow-the-sun operation the traditional way, they're just three or four people spread across enough time zones that the same principles apply.

Why Most Teams Get the Handoff Wrong

The most common failure mode we see is treating each leg of the relay like an independent mini-project instead of one continuous cut. The editor in region A finishes their pass and essentially throws the file over the wall, region B opens it cold with no context on what changed or why, and half their session gets burned just figuring out where the last person left off. That's not a follow-the-sun workflow, that's three separate projects wearing a follow-the-sun costume, and it costs you almost as much time as if you'd just had one editor working alone.

A Small Example That Shows the Difference

We watched a six-person agency try this with a product launch video that needed to move between an editor in Manila, a colorist in London, and a producer in Austin, all inside a five-day turnaround. Their first attempt used a shared drive and a running Slack thread, and by day three nobody could say for certain which file was the current one, so the colorist ended up grading a version that had already been superseded, costing an entire extra day just to redo the pass on the right cut. When they switched to a single project with version-locked review links, the same three-person handoff pattern took four days instead of six, purely because nobody had to guess which file to open.

The Three-Region Relay We See Work Best

Here's what we tell teams who ask us how to actually structure this. Assign each region a distinct role in the cut rather than having everyone do a bit of everything, because role clarity is what lets the next person know exactly what to check for when they open the project.

Notice that nobody in that chain is waiting on anybody else to be awake. Region A wakes up, sees exactly what Region C needs for tomorrow, and starts working immediately instead of spending the first hour of their day trying to reconstruct what happened while they were asleep.

What Actually Has to Be in the Baton

A follow-the-sun handoff is only as good as the package that travels with it, and we've found that skimping here is the single biggest reason relays break down after a week or two of otherwise promising momentum.

• A version-labeled cut with frame-accurate comments left directly on the timeline, not in a separate doc
• A short changelog covering what moved since the last handoff, three lines max
• Timecoded open questions the next region can answer without watching the whole thing again
• An expiring share link so nobody downstream is ever looking at a stale export by mistake
• A clear "due by" time stated in the next region's local zone, not the sender's

What Happens When One Region Drops Out of the Rotation

Every team running a real follow-the-sun relay eventually hits the week where one region can't pick up the baton, a public holiday nobody accounted for, someone's out sick, or a national outage takes down the office's internet for a day. The instinct is to just let the cut sit until that region is back, but that defeats the entire point of the relay, and it also means the next region inherits a much bigger backlog than usual once the missing leg finally returns. The better approach is to treat the rotation as a chain that can skip a link without breaking, so if Region B is out, Region C picks up directly from Region A's handoff instead of waiting, using the same version-labeled cut and the same timecoded notes Region B would have left if they'd been online. It's not a perfect substitute, Region C is covering ground outside their usual role, but a slightly rougher pass that keeps momentum beats a clean pass that arrives two days late. We tell teams to name a backup owner for each region ahead of time, someone who already has access to the project and already understands the role well enough to step in without a briefing call, because figuring that out for the first time in the middle of a real deadline is exactly the kind of scramble a relay is supposed to prevent.

Where the Relay Model Breaks

The honest truth is that follow-the-sun editing isn't free, it has a real failure mode, and it shows up the moment someone tries to run it with tools built for a single-office team. Email threads fork. Someone attaches a file instead of linking a version. A comment references "the transition around 0:45" without saying which cut that timecode belongs to. Every one of those small frictions multiplies across three handoffs a day instead of one.

That last point matters more than people expect. A lot of relay handoffs stall not because of miscommunication but because the next editor is sitting there waiting for a multi-gigabyte file to finish downloading before they can even see what they're working with, and proxy-based review closes that gap almost entirely.

Keeping Version Control Sane Across Three Cuts a Day

When a single project gets touched by three editors in one twenty-four hour cycle, version chaos is the default outcome unless you actively prevent it. We've watched teams lose track of which cut is "current" so many times that they started numbering versions with the region's initial attached, ML-v4 handed to LDN-v5 handed to LA-v6, just to keep it straight.

One studio we worked with took the region initial convention even further once they scaled to a fourth office, tagging every handoff with both the region code and a timestamp down to the hour, ML-0847 handed to LDN-1602 handed to LA-2210, so even a producer glancing at the project for the first time could reconstruct the exact order handoffs happened in without asking anyone. It looks a little clunky written out, but clunky and unambiguous beats elegant and confusing every time three people are touching the same file in one day.

Media storage that keeps every version in one place, with clear timestamps and no ambiguity about which file is current, solves most of this on its own. It sounds almost too simple, but the number one thing that kills a follow-the-sun workflow isn't creative disagreement, it's three people confidently editing three different versions of the same project without realizing it.

A lot of the writing No Film School has done on remote post-production teams touches this same tension, the fact that tooling built for one office rarely survives being stretched across three, and a follow-the-sun relay is really the stress test for whether your review process can handle that stretch.

The Sign-off Problem at the End of the Relay

Even a perfectly run relay eventually has to end somewhere, usually with a client or a senior stakeholder giving final approval, and that's the one link in the chain that can't just pass silently to the next region because it needs a real decision from a real person. The trick is treating that approval step as its own leg of the relay rather than an afterthought bolted onto the end.

Building that into your approval workflow from the start, rather than improvising it once the cut is "basically done," is what separates teams that ship on time from teams that get a beautifully polished cut sitting in someone's inbox for three extra days waiting on a signature. If you're onboarding a new editor into a relay like this, our guide on onboarding a remote editor without a single live call covers how to get someone productive in the rotation without burning a week on introductions.

Making the Relay Actually Sustainable

The teams that keep follow-the-sun editing running for months, not just for one deadline crunch, tend to share one habit: they treat the review tool itself as the source of truth rather than any single person's inbox. StudioBinder's blog has written plenty about how fragile post-production schedules get when coordination lives in someone's head instead of a shared system, and a three-region relay is exactly the scenario where that fragility shows up fastest, because there's no single person watching the whole thing at once.

We also hear from editors on the Premiere Pro plugin side of things that being able to see timecoded notes without leaving their edit software removes one more excuse for the relay to stall, since nobody has to context-switch into a browser just to find out what the last region flagged.

If your team is trying to run a real follow-the-sun operation, or even just a two-person version of one, the thing that will make or break it isn't hiring more editors, it's whether your handoffs can survive complete silence for eight to sixteen hours at a stretch. That's the exact problem PlayPause's timecoded comments, version history, and flat per-workspace pricing were built to solve, so see how PlayPause supports multi-region teams before your next cut sits idle waiting for someone to wake up.