A brief closes in New York at six in the evening. By the time the team returns, production has finished in Singapore and the campaign is being trafficked in London.
That is the promise of the follow the sun model for global agency work. With 30% of meetings now spanning multiple time zones, coordinating work across regions has become a growing challenge.
Sequential handoffs can accelerate campaign production, but they can also create rework when teams lack clear instructions or decision-making authority.
For marketing operations and agency leaders, the question is which tasks benefit from overnight handoffs and which require continuous ownership.
This article examines where the model works for creative, production, and media teams, where it breaks down, and how to structure handoffs without sacrificing quality.
Yes, but only for part of the work.
The follow the sun model is a globally distributed workflow in which a single site owns the work at any moment and hands it daily to a site several time zones west, so that progress continues around the clock.
It was formalized in software development research, which separates it from ordinary global teams and from overnight shift coverage.
The defining feature is ownership. At any hour, exactly one region holds the baton for a piece of work, and the rest are either finished with it or waiting for it.
Translated to an agency, a New York creative lead owns the campaign until the close of the day, then a Singapore production studio owns it. Two studios editing the same files at the same time is collaboration. Follow the sun needs one owner per hour.
The second feature is a scheduled transfer every working day, in one direction. Each region receives the work at the start of its day and leaves it in a defined state at the end.
This is what distinguishes the model from having people in several countries. Regional teams serving their own markets in parallel never transfer anything, and 24/7 support with shared queues transfers everything without a single owner.
The typical arrangement uses three regions: the Americas take the first wave of the day, APAC takes over as the Americas close, and EMEA covers the remaining hours before the Americas reopen.
Three zones roughly eight hours apart give each region a full working day.
What changes for agencies is how much context a creative handoff has to carry.
Sequential handoffs are faster for bounded work that can be checked before it moves. Parallel regional teams are safer for anything ambiguous, because any reinterpretation stays inside one team.
The structural choice for a global marketing leader is between two architectures. One passes work sequentially across time zones every day; the other gives each region an autonomous team with minimal cross-regional dependencies, held together by one shared strategy and quality standard.
The case for sequential handoffs rests on continuity.
The same researchers measure it as calendar efficiency. A 40-hour week uses only 23.8% of the 168 hours in a calendar week, so a clean daily handoff puts idle hours to work on any step that can be completed and verified before the next region starts.
The condition matters more than the headline. A weekly social-asset resizing run handed to Singapore at the New York close is finished when New York reopens; a campaign concept handed over at the same hour comes back reinterpreted.
Every boundary carries a cost: the next region must reconstruct what the last one meant.
Lab evidence shows how quickly that cost adds up. In a 2007 experiment with 42 two-person teams split across four levels of time-zone overlap, a small separation had no effect on accuracy, and larger separations reduced it significantly.
In agency work the loss shows up as rework, and the warning-signals section below shows how to spot it.
The worst candidates are tasks that need live collaboration, frequent scope renegotiation or decisions that depend on tacit context. That is a fair description of most creative development, where the brief, the idea and the client's reaction move together.
Overlap hours do not fix this cleanly, for the reasons set out in the overlap rule further down.
Score each cross-regional workflow on three things: how ambiguous the task is, how stable its ownership is, and whether done can be evidenced without a call. Work that scores well on all three belongs in a sequential lane; anything else belongs with one autonomous owner.
| Dimension | Sequential follow the sun handoffs | Autonomous parallel regional teams | Evidence or condition |
|---|---|---|---|
| Calendar speed | Work advances overnight relative to the client's home region | Work advances only within each region's day | Gain depends on each step being verifiable before transfer |
| Rework risk | Rises with ambiguity at every boundary | Contained within the owning team | Weak evidence multiplies rework while volume stays flat |
| Ownership | One owner per step, changing daily | One owner per region, stable | Shared ownership is the common failure in both |
| Coordination cost | Daily handoff records and overlap exceptions | Shared strategy, periodic alignment | Overlap burdens fall asymmetrically on the two regions |
| Cost saving | Unquantified | Unquantified | No rigorous estimate for agency settings; speed, not cost, is the supportable claim |
Neither architecture is free. Sequential handoffs trade a daily context transfer for continuous progress, while parallel teams trade a slower calendar for fewer reinterpretations. Judge your own workflows on how often the next person can act without a call.
Media operations suit overnight transfer best, production and versioning suit it once the master is locked, and concept and strategy should stay with one team.
Classify each recurring workstream into one of three lanes: sequential-fit, conditional-fit and parallel-only. The test is whether the next region can act on what it receives without a conversation.
Media operations are the strongest candidates. Trafficking approved creative, running QA on tags and placements, overnight pacing checks and reporting builds all have explicit specifications and a verifiable end state, which is what the model needs to work.
A media team can pass the trafficking and pacing checks westward each evening while the planning and budget decisions stay with the strategist who owns them. That split keeps performance media decisions with a single accountable owner while the repeatable operations use the extra hours.
Production fits on one condition. When the master creative is locked, specs are explicit and the language or format matrix is defined, versioning and creative localization move cleanly between regions.
The condition is the lock. If the master is still changing after the first region closes, every version produced overnight is built on a moving target, and the handoff produces work that must be redone.
Published case studies show what thin specs cost. In two 2006 follow-the-sun programs, a US-Australia team delivered well, while a set of US-India web projects struggled because specifications left room for guesswork: with no instruction to left-justify web content, the remote team centered it and the code had to be reworked.
Concept, positioning and strategic planning are parallel-only. They depend on tacit context, live debate and scope that is meant to shift as the idea sharpens, which are the properties that make a task a poor candidate for daily westward transfer.
These belong with one small team and its client, working in whichever region the client and the decision live. Other regions contribute local insight and adapt the result, but they do not take a turn owning the idea.
| Work type | Ambiguity | Acceptance evidence available | Recommended lane |
|---|---|---|---|
| Ad trafficking and tag QA | Low | Yes, placements live and verified | Sequential |
| Pacing checks and reporting builds | Low | Yes, defined report and thresholds | Sequential |
| Asset versioning and localization | Low to medium | Yes, if master is locked and specs exist | Conditional |
| Production from approved master | Medium | Partly, depends on spec completeness | Conditional |
| Copy adaptation for tone | Medium to high | Weak, judgment based | Conditional, with stop rule |
| Campaign concept and creative development | High | No, intent still forming | Parallel only |
| Positioning and strategic planning | High | No, decision depends on tacit context | Parallel only |
Treat the matrix as a sorting tool. Any workstream that lands in the conditional column is a candidate for a short pilot before it moves overnight.
In a three-region schedule, New York locks the master on Monday, Singapore versions and checks it overnight, and London traffics it before New York's Tuesday is half over.
The schedule below is illustrative. It follows the Americas, APAC and EMEA rotation westward and shows what each region must receive and what it must leave behind.
Monday in New York, the creative lead owns the campaign. By the close of the day the master assets are locked, the client's open questions are answered and the version matrix is written down.
This is where the whole schedule is decided. An unlocked master or an unanswered client question at the New York close costs a full day, because Singapore either waits or guesses.
Tuesday morning in Singapore, while New York sleeps, the production lead takes the baton. The studio produces the versions in the matrix, runs QA against the specs and leaves a checked asset set with a QA record by the Singapore close.
Singapore's working day falls entirely inside New York's night, so any question the master leaves open waits a full day.
A clear design system with locked masters reduces how often Singapore needs New York at all.
Tuesday in London, the media operations lead takes the baton as Singapore closes. The team traffics the checked assets, runs launch checks and completes the first pacing read by the London close, early afternoon in New York.
Relative to the client's home region, production completed overnight and trafficking finishes by Tuesday lunchtime. That is the gain the model promises, and it comes from two steps whose inputs were locked and whose output could be checked.
Map one live campaign onto this timeline and mark where the baton would actually pass today. The pass from Americas to APAC is the likeliest to slip, because that is where creative judgment and production meet.
Write a one-page handoff record with the five fields below, and require it before any asset crosses a region. The record is the mechanism that keeps context from being lost at the boundary.
A review of follow-the-sun research catalogued 36 best practices and 17 challenges, grouped under coordination, communication and culture. The five fields cover the coordination side for agency work.
Each handoff names one person who owns the next step, by name and role. A team name is too vague. Shared ownership lets work fall between regions, because each side assumes the other is holding it.
The owner also inherits the right to decide. If Singapore's production lead finds a spec conflict, the record tells them whether to resolve it or stop.
The receiving region checks a short list before touching the work:
If any item is missing, the work is not ready, and the record says so.
For creative assets, the lock is the critical item. A master that the creative team has signed off, with its rationale captured, lets the next region adapt without reinterpreting.
Each step defines what done means and what evidence proves it: a QA log, a placement screenshot, a checked version list. The evidence must be strong enough that the next region can act without a call.
Regions also need consistent definitions.
In agency terms, two studios must agree on whether a client comment is a tweak or a reconcept before either acts on it.
When scope, tone or strategic intent changes mid-lane, the work exits the sequential lane and returns to the owning team. The stop rule is written in advance so that the region holding the baton does not have to negotiate it at midnight.
A stop is the lane recognizing that the task has become a poor candidate. Stopping costs one day; continuing costs several rounds of rework.
Overlap hours are for exceptions. Routine review scheduled into the overlap means one region is always starting its day with the other region's leftovers. An overlap window falls at the start of one site's day and the end of the other's, so the burden lands unevenly.
A Microsoft Research study of sixteen people working across gaps of about eight hours found they still met live, often outside the normal workday and from home.
Reserve the window for stop-rule escalations and client questions that cannot wait. If the record is complete, most days the window goes unused.
| Handoff field | What it must contain | Who verifies it | Failure if missing |
|---|---|---|---|
| Next-step owner | One named person and their decision rights | Sending lead | Work waits or two people edit the same files |
| Ready-to-start checklist | Locked master, specs, version matrix, client contact, answered questions | Receiving lead at start of day | Receiving region guesses and produces rework |
| Definition of done and evidence | End state and the proof artifact for the step | Receiving lead at end of day | Next region cannot act without a call |
| Priority and change definitions | Shared scale for urgency and for tweak versus reconcept | Both leads, agreed once per lane | Regions act on the same comment differently |
| Stop rule and return path | Conditions that exit the lane and who receives the work | Baton holder | Ambiguous work keeps moving and multiplies revisions |
Each field closes a specific gap: the owner stops work falling between regions, the boundary and evidence fields let the next studio start without a call, and shared definitions keep two regions from disagreeing about whether a client comment is a tweak or a reconcept.
Add three numbers per workstream to your production dashboard and review them at each monthly routing decision: revision rounds per asset, time to next action after a handoff, and cycle time against asset count.
Each one points to context loss at a boundary.
When revisions rise and the number of assets does not, the brief or master is unstable. A capacity problem would show up as a backlog. The same asset being redone points to the brief.
The response is to tighten the ready-to-start criteria, usually the lock on the master, or to pull the workstream back to a single parallel owner.
When work sits after it has been handed over, ownership is unclear or the evidence is not enough to act on. The receiving region is waiting for a call that the record should have made unnecessary.
The response is to name the owner more precisely and strengthen the acceptance evidence for that step.
When end-to-end time climbs while volume is steady, the lane is paying the handoff cost described earlier.
A versioning lane whose cycle time moves from two days to four on the same asset count, traced to a master that changed after the Americas close, has a routing problem. Adding staff will not fix it.
These numbers earn their place only if they change a decision. Reading them against the routing choice, lane by lane, is the kind of measurement that tells you what the data supports and what to test next.
At Fieldtrip, we work with small specialist teams that maintain clear ownership of creative, production, and media execution, supported by shared strategy and quality standards.
For global marketing teams, effective coordination starts with identifying which activities can move across time zones without compromising creative consistency or campaign performance. Repeatable production and media tasks may benefit from sequential handoffs, while strategy and creative decisions need consistent ownership.
The goal is to reduce unnecessary delays, limit rework, and help campaigns move from planning to execution more efficiently.
If your marketing team is struggling with cross-regional coordination, production bottlenecks, or delayed campaign launches, contact us to discuss how we can help streamline your marketing operations and improve global campaign delivery.
Yes. A global brand can coordinate several agencies across regions without consolidating them under one provider. However, contracts should clarify which partner controls shared assets, manages approvals, and resolves disputes. These arrangements help prevent conflicting instructions and duplicated work.
Not necessarily. Marketing teams can initially redistribute existing workloads across regional offices or agency partners. Additional staffing may become necessary if workloads exceed regional capacity or require specialist skills unavailable in the receiving location.
The model can change how agencies allocate production hours, project management costs, and regional resources. Brands should examine additional coordination fees, local labor rates, and contract terms before expecting savings. Faster campaign delivery does not automatically reduce total spending.
Global marketing teams should apply role-based access controls, approved file-sharing platforms, and contractual confidentiality requirements. They should also review applicable data protection obligations before transferring customer information, unpublished creative assets, or confidential campaign materials between countries and external partners.
Yes. Global product launches can use teams across time zones for launch monitoring, technical checks, and regional execution. However, brands must coordinate embargoes, local publishing schedules, and market-specific requirements to prevent campaigns from going live prematurely.
