How to run a remote creative team across time zones
A crew spread from Toronto to Berlin to Sydney can ship faster than one in a single office, if the day is designed for it. Here is how to design it.
On this page
- Start by mapping the real overlap
- Design the day around the overlap
- Written stand-ups people actually read
- Handovers: follow the sun without dropping the ball
- Presence without surveillance
- Feedback loops for creative work
- Deadlines and time zones
- Checklist: a weekly rhythm for a distributed team
- Frequently asked questions
The short answer: find the real overlap between your team’s working hours and protect one short window of it for live conversation. Move everything else to writing: a daily written stand-up, clear handover notes at the end of each person’s day, and deliverables that carry their own context. Show who is online without watching anyone’s screen, and always write deadlines with a time zone. Done well, work moves forward while half the team sleeps.
Start by mapping the real overlap#
Before you change any process, look at the hours. The table below shows typical differences between common agency locations. Daylight saving starts and ends on different dates in North America, Europe, Australia and New Zealand, and the southern hemisphere moves the opposite way, so the gap shifts during the year.
| Locations | Typical difference | A workable overlap (9:00 to 18:00 days) |
|---|---|---|
| New York / Toronto and London | 5 hours (briefly 4 in spring and autumn) | About 9:00 to 13:00 in New York, 14:00 to 18:00 in London |
| London and Berlin | 1 hour | Almost the whole day |
| Los Angeles and London | 8 hours (briefly 7) | About an hour: early morning in LA, late afternoon in London |
| London and Sydney | 9 to 11 hours | Little or none; a short early-London, late-Sydney slot |
| New York and Sydney | 14 to 16 hours | Early morning in Sydney is the previous evening in New York |
| Sydney and Auckland | Usually 2 hours | Most of the day |
Check these against a time zone converter each spring and autumn. The point is not the exact numbers; it is knowing which pairs of people can talk live and which never really can.
Design the day around the overlap#
Once you know the overlap, treat it as the scarcest resource you have.
- One protected window. Pick an hour or two inside the overlap for live conversation. No routine status meetings in it.
- Live time is for decisions and feedback. Creative reviews, tricky client calls, and anything where tone matters. Updates go in writing.
- Rotate the inconvenient slot. If someone has to join early or late, share that around rather than always asking the same region.
- No-meeting blocks. Editors and designers need long stretches. Keep meetings out of each region’s mornings where you can.
Written stand-ups people actually read#
A daily call stops working when the team spans more than a few hours: someone is always at dinner or not yet awake. A written stand-up replaces it well, if it is short and consistent.
- Yesterday: what I finished, with links.
- Today: what I will work on, in priority order.
- Blockers: what I need, and from whom, by name.
Post it at the start of your own day, and read the others’ at the start of yours. Leads answer blockers first. Keep it in the same place as the work, not in a separate app nobody opens. Crewqo has written daily stand-ups built in, next to the task board and team chat.
TipIf a blocker sits unanswered for a full cycle, it goes into the next overlap window automatically. That one rule stops most “waiting on someone overnight” delays.
Handovers: follow the sun without dropping the ball#
The promise of a spread-out team is that work keeps moving around the clock. That only happens if each hand-off carries enough context for the next person to start without asking a question. A handover note needs five lines:
| Line | Example |
|---|---|
| Where it is | First cut exported, 60% of colour grade done |
| What is next | Finish grade on scenes 4 to 7, then export v2 |
| Where the files are | Link to the project folder and the latest export |
| Decisions pending | Client hasn’t confirmed the end card; use version A for now |
| Who to ask | Maya for creative calls, Emma for anything client-facing |
Write it on the task itself, not in a private message, so anyone picking it up sees it.
Handover when someone is on leave
Leave is a planned handover. Make approved leave visible on a shared calendar, and move the person’s clients or tasks to a named cover before they go. In Crewqo, leave requests are approved by a lead and show on the calendar, and leads can hand over an editor’s clients while they are away; see attendance and leave and weekly output.
Presence without surveillance#
People on a spread-out team need to know who is around right now. They don’t need to be watched. Simple signals do the job:
- Status: online, away, busy or offline, set by the person.
- Clock-in: a start and end to the working day, from anywhere, so hours are fair and visible.
- Read receipts: sent, delivered and seen ticks, so nobody wonders whether a message landed.
Crewqo’s team chat shows status and read ticks, and attendance lets people clock in from anywhere. Its performance view is built on delivered work: tasks done on time, work approved at first review, revisions and missed deadlines; see performance.
Feedback loops for creative work#
- Review windows in the client’s time zone. Send work for review at the start of the client’s day, not the end of yours.
- Version everything. Every deliverable keeps its versions, so a reviewer on the other side of the world comments on the right one.
- Use voice notes for nuance. A 40-second voice note explains a creative direction better than five paragraphs.
- One thread per client. Feedback in one place, not spread across email and chat. More in our guide to faster client approvals.
Deadlines and time zones#
If a New York client asks for something by “end of day Friday”, that is late Friday night in London and Saturday morning in Sydney. Write every deadline as a time and a zone, and use the client’s time zone for anything client-facing. For internal hand-offs, set the deadline at the start of the receiver’s day, not the end of the sender’s.
Checklist: a weekly rhythm for a distributed team#
Set these up once, review each quarter
Frequently asked questions
How much overlap does a remote team need?
One to two hours a day of shared time is usually enough for decisions and feedback, as long as updates and hand-offs are written. Pairs with no natural overlap need especially clear handover notes.
Are async stand-ups better than daily calls?
Once a team spans more than a few hours, usually yes. A short written update with yesterday, today and blockers reaches everyone at the start of their own day, and leaves a record.
How do we handle deadlines across time zones?
Always write the time and the time zone. Use the client’s time zone for client-facing deadlines, and set internal hand-offs for the start of the receiving person’s day.
Should we track remote workers’ screens?
That is a decision for each agency, but many teams find simple signals work better: a status, a clock-in and a focus on delivered work. Crewqo’s performance view is built on delivered work, such as tasks done on time and work approved at first review.
Written by the Crewqo team. Spotted something out of date? Tell us at hello@crewqo.com.