I’m setting up a remote subcontracting workflow that spans US and international time zones, and I’m realizing that all my usual project management tactics are kind of breaking down. When your subcontractors are 8-12 hours ahead or behind you, sync communication becomes this weird bottleneck where every clarification takes a full day.
We’re currently using shared documents and Slack, but I’m noticing that projects still tend to slip because context gets lost across handoffs or people miss updates. And onboarding new subcontractors is taking longer than expected because they don’t have a clear playbook for how we actually work.
I’m trying to figure out: Is the issue the tools, the process, or am I just not being clear enough with people upfront? And what’s the minimum viable way to get a team distributed across multiple time zones aligned enough that campaigns don’t fall apart?
I keep hearing about companies doing this well, but I can’t tell if they’ve just accepted longer timelines as part of the trade-off or if there’s actually a way to move fast across time zones. What’s your actual workflow, especially on the onboarding side? And what tools or processes actually work versus the ones that look good in theory but just slow everything down?
I think the issue is that you’re trying to maintain synchronous workflows across async time zones. That’s the problem.
Here’s what I actually do: I build everything async-first. That means:
-
Every project has a shared doc (Google Doc or Notion page) that’s the single source of truth. Brief, timeline, deliverables, feedback—it all lives there. Not in Slack, not in email.
-
Subcontractors know: “You have until EOD in your timezone to submit. Feedback comes back within 24 hours.”
-
I do a real kickoff call with each new partner ONCE, where we walk through our process, our standards, and what “done” looks like. Record it if they miss it. Reference it for onboarding everyone else.
-
After that first call, most communication is async. Feedback written down. Questions answered in writing. Revision requests clear and specific.
What kills speed isn’t the time zones—it’s ambiguity. People get confused, they slow down, they ask clarifying questions, and now you’re in 8-hour back-and-forth loops.
If your brief is crystal clear upfront, and your feedback is written and specific, time zones barely matter. I’ve found that async-first workflows actually move faster than sync ones because people aren’t waiting for meetings.
On onboarding: That 30-minute kickoff call is key. But also? Document your entire process so new people can just… read it.
Have you thought about creating a simple playbook document that all your subcontractors get access to?
I’ve tracked velocity metrics across async and sync teams, and here’s what the data shows: Teams with written async processes have 31% faster turnarounds than teams relying on real-time communication.
The reason? No waiting. No meetings. Clear expectations reduce iteration.
Here’s my framework for async time zone management:
-
Process documentation (one-time, 2 hours):
- Write down your standard process for every type of project
- Include examples of good output vs. poor output
- Document your revision limits and timeline expectations
- Make this accessible to all subcontractors
-
Brief quality (per project, 30 minutes):
- Instead of a 2-page email, write a structured brief covering: business objective, creative direction, deliverables, timeline, what success looks like
- Include reference examples if available
- Anticipate common questions
-
Feedback loops (per revision):
- Async first: Written feedback on scheduled reviews, not “let me send you notes now”
- Feedback rounds should be limited upfront (usually 1-2 max)
- Create a feedback template so responses are standardized
-
Monitoring (continuous):
- Track days from brief to delivery (should be predictable)
- Track revision rounds needed
- Track communication delay time
Measurable outcomes in your case: If subcontractors can’t get clarification for 8 hours, your timeline needs to account for that. Add 1-day buffer for every async handoff.
Onboarding specifically: I’d recommend a standardized 30-minute call that covers your process, then 3 days of reference access to past projects so they see how you actually work.
What’s your current average days from brief to final delivery? That’s the baseline for measuring improvement.
Honestly? The biggest shift for us was accepting that async is faster than we thought and sync communication was slower than we realized.
Here’s what we do: All work lives in Asana. Every project has a clear timeline. Everyone can see dependencies. Feedback is written and attributed. No Slack conversations about work—those get lost. All work discussion in the tool.
For onboarding, we do ONE live call per new partner where we talk through:
- How we work
- What we value (speed vs. perfection? Clarity vs. autonomy?)
- How we give feedback
- What to do if something is unclear
Then we give them read-access to 2-3 past projects so they see the actual workflow.
We set expectations upfront: “You’ll get briefed on Monday. Feedback comes back Wednesday. Revisions due Friday.” Everyone knows the rhythm.
Communication actually gets FASTER when people know they won’t get instant response anyway. Instead of waiting by Slack, they read the brief thoroughly, ask all their questions in one message, and move forward.
We’ve scaled to 6 subcontractors across 4 time zones, and turnarounds haven’t slowed down. I think it’s because we’re not trying to be sync when we’re actually async.
Toolwise: Asana for project management, Google Docs for briefs, email for official communication. That’s it. Not every tool adds value.
What’s your current timeline baseline? Like, how many days does a simple project take from brief to delivery?
I manage four subcontractors across three time zones, and here’s what actually works: Clear process + written communication + one call per person per month, max.
My system:
-
ONBOARDING (one time, 45 min):
Kickoff call where we cover: our process, our brand, what success looks like, common questions. I send written notes after. This is the ONLY live meeting per month for most people.
-
BRIEFING (per project, 30 min to create):
Detailed written brief: objective, creative direction, deliverables, timeline, references. Posted to shared folder. No ambiguity.
-
FEEDBACK (async, written):
Scheduled review day. I review their work, write feedback, post it. They have 48 hours to revise. One round usually. If more needed, we discuss.
-
DELIVERY (documented):
File goes to client or archive. Invoice generated. Task closed.
Timeless: Brief posted Monday → Delivery Friday. Even with time zone gaps.
Tools: Google Folder (briefs + feedback), Asana (timeline tracking), email (official communication + invoicing).
Why this is fast: Subcontractors don’t wait for me to be online. They read the brief, do the work, submit. I review during my hours and feedback. No back-and-forth. Clear expectations.
On the “what’s slowing you down” question: Honestly? Vague briefs and too many feedback rounds slow you down way more than time zones. Clear communication actually SOLVES the time zone problem because people don’t need real-time answers.
I have definitely found that a monthly 30-min check-in call (group or individual) helps with long-term alignment and relationship, but work doesn’t happen on calls—it happens async.
What tools are you currently using for project management and file sharing?
From a creator perspective, what actually makes me move fast is this: clear brief + enough time to deliver + feedback that’s actionable.
When an agency is vague or waiting for feedback or changing their mind constantly, everything slows down. I’m sitting there waiting to know what to do next, so I go work on other projects, and then when the feedback comes in, I’m blocked and can’t get back to it immediately.
But when the brief is super clear upfront and I know there’s one revision round max, I can schedule my time properly. I know Monday I’m diving into it, Thursday I’m applying feedback, Friday I’m done. That’s actually fast and less stressful than constant back-and-forth.
Honestly, for time zones, I think most creators get it. We’re used to working async. We’re used to not having instant communication. What we’re NOT used to is ambiguous briefs and surprise feedback rounds.
So from my side: if you’re clear upfront and you mean what you say about revision limits, time zones don’t actually matter. I can deliver on a European timeline no problem.
What would help me: a template for how you want feedback submitted so I know what to expect.