How Successful Companies Coordinate 100+ Workers Across 8 Time Zones
From GitLab's 1,300+ employees to Automattic's "work from anywhere" model, discover the exact systems successful remote-first companies use to coordinate globally distributed teams.
Victor
Creator and maintainer, City Clock
Victor builds and maintains City Clock. He writes the guides and articles here, and maintains the city and time zone dataset the site runs on.
The Scale Challenge: When "Just Schedule a Meeting" Breaks Down
Coordinating 5-10 people across 2-3 time zones is challenging. Coordinating 100+ people across 8+ time zones? That requires completely different systems, workflows, and cultural norms. Traditional "office-first" approaches simply don't scale.
Why this matters: Companies like GitLab (1,300+ employees, 65+ countries), Automattic (1,800+ employees, 95+ countries), and Zapier (700+ employees, all remote) don't just "make it work"—they thrive with productivity and employee satisfaction scores higher than traditional office companies.
Their secret isn't expensive enterprise software or perfect coordination—it's systematic workflows, clear communication protocols, and a few key tools used religiously.
After analyzing dozens of successful distributed companies and speaking with remote work leaders, we've identified the exact systems they use. Here's what actually works at scale.
The Five Pillars of Distributed Team Coordination
Async-First Communication (The Foundation)
The single most important principle: assume communication will happen asynchronously, design for it, and treat real-time sync as the exception.
GitLab's "Handbook First" Approach
GitLab maintains a public handbook with 5,000+ pages documenting everything from company values to specific workflows. Before asking a question, employees search the handbook. Before answering a repeated question, employees update the handbook.
Results:
- • Markedly fewer "quick questions" interrupting focused work
- • New employees can onboard across any time zone at their own pace
- • Information is accessible 24/7 without waiting for someone to wake up
- • Clear source of truth reduces conflicting information
Automattic's "P2" System
Instead of Slack for internal communication, Automattic uses P2 (internal blog-style posts). Every project, team, and discussion has a dedicated P2 where updates are posted with full context.
Why it works:
- • Written updates force clarity and completeness (vs. scattered Slack messages)
- • Threaded discussions keep context together
- • Searchable history prevents information loss
- • Anyone can catch up on their schedule without synchronous presence
Async Communication Rules:
- • Write thorough initial messages (no "hey, you there?")
- • Include all necessary context so recipients can respond without follow-ups
- • Specify deadlines clearly ("by end of day Thursday UTC" not "ASAP")
- • Document decisions where others can find them later
The "Overlap Hours" System
Even with async-first communication, successful teams establish core overlap hours when most people are available for synchronous collaboration.
Zapier's 4-Hour Overlap Window
With employees across 27 countries, Zapier identified that 11 AM - 3 PM Pacific Time provides maximum overlap across US, Europe, and some Asian time zones.
Who This Works For:
Buffer's "Two Overlap Periods" Approach
Buffer recognized that no single 4-hour window works for all global employees, so they established two overlap periods:
Americas/Europe Overlap
9 AM - 12 PM EST (2 PM - 5 PM GMT)
For: US East Coast, Canada, UK, Europe
Europe/Asia Overlap
8 AM - 11 AM GMT (4 PM - 7 PM IST)
For: Europe, Middle East, India, SE Asia
Teams are assigned to one primary overlap period. Cross-period coordination happens async or via recorded meetings.
Mandatory Meeting Protocols
When meetings are necessary, strict protocols ensure they're worth everyone's time regardless of time zone.
The "Meeting Bill of Rights"
Basecamp, Doist, and other remote-first companies enforce these non-negotiable meeting rules:
1. Agenda Required
No agenda = meeting automatically canceled. Agenda must be shared 24+ hours in advance with expected outcomes defined.
2. Recording Always Available
Every meeting recorded and shared within 2 hours. Attendance is optional if recording + notes provided.
3. Written Notes Required
Designated note-taker posts summary with decisions, action items, and owners within 1 hour of meeting end.
4. Time Zone Display
Meeting invites show times in all relevant zones: "2 PM EST / 7 PM GMT / 6 AM AEST+1"
5. "Could This Be Async?" Test
Before scheduling, meeting organizer must answer: "Could this be accomplished via document with comment threads?" If yes, no meeting scheduled.
The "Team Hubs" Structure
Instead of organizing by time zone, successful distributed companies organize by "team hubs"— groups with naturally overlapping schedules.
How InVision Structured 700+ Employees
Rather than "US Team" vs "Europe Team," InVision created functional teams with deliberate time zone clustering:
Product Team "Americas Hub"
Engineers: 60% US West Coast, 30% US East Coast, 10% Latin America
Overlap: 11 AM - 5 PM EST (comfortable for all)
Daily standup: 12 PM EST async or 2 PM EST sync (optional)
Why it works: All members have at least 6 hours daily overlap for collaboration, reducing need for async handoffs on urgent issues.
Customer Success "Europe/Asia Hub"
Team: 50% Europe, 30% India, 20% Australia
Overlap: 9 AM - 2 PM GMT (2:30 PM - 7:30 PM IST)
Provides 24/7 customer coverage through planned handoffs
Why it works: Europe → India → Australia natural handoff creates "follow-the-sun" support without forcing anyone into bad hours.
Essential Tools Stack
Successful distributed companies use surprisingly few tools—but use them religiously.
Time Zone Visibility
Every employee has City Clock or equivalent pinned in browser showing all team members' current times in real-time.
"Before sending a Slack message, I glance at their current time. If it's 11 PM for them, I write a thorough async message instead of expecting a quick reply." — GitLab engineer
Shared Calendar with Time Zones
Google Calendar or Calendly configured to show each person's local timezone alongside events.
Pro tip: Zapier created a company-wide calendar showing all team members' "available hours" blocks (not specific events, just when they're typically working). Prevents scheduling outside someone's normal day.
Async Communication Platform
Slack (with aggressive notification management), Twist (async-first Slack alternative), or internal tools like Automattic's P2.
Critical setting: "Do Not Disturb" auto-enabled outside each person's work hours. No one gets pinged at 2 AM their time.
Collaboration Documentation
Notion, Confluence, or Google Docs as single source of truth. Meetings don't make decisions— documents do. Meetings discuss what's in documents.
GitLab rule: "If it isn't documented, it didn't happen." Verbal decisions don't count until written down.
Real-World Example: How a 150-Person Team Coordinates Daily
Let's look at a concrete example from a mid-sized tech company with 150 employees across 8 time zones:
Daily Workflow
6 AM UTC: Sydney/Tokyo team starts
- • Check overnight updates in project documents
- • Post daily standup updates in team channel (async written format)
- • Begin work on tasks, document progress as they go
9 AM UTC: Europe team starts
- • Read Asia team's standup updates and progress docs
- • Post their own standup updates
- • 30-min optional overlap call with Asia team (2 PM Asia, 9 AM Europe)
- • Focus work continues async
2-5 PM UTC: Prime overlap window
- • US East Coast, Europe, some Latin America all online
- • This is when synchronous meetings happen (max 2 hours daily)
- • "Office hours" for quick questions and collaboration
6 PM UTC: US West Coast continues
- • Europe team ending day, posts wrap-up updates
- • US teams read updates, continue work
- • End-of-day: all work documented so Asia can pick up tomorrow
The key: Work follows the sun naturally. No one waits for someone to wake up because everything is documented. Urgent issues get flagged explicitly and someone from the current shift picks them up.
Common Pitfalls (And How to Avoid Them)
❌ Pitfall: "HQ Time Zone Bias"
Scheduling all meetings for HQ convenience, expecting non-HQ employees to accommodate.
✅ Solution:
Rotate meeting times monthly. Track "inconvenient meeting hours" per employee—if anyone exceeds 40% of meetings outside 9-5 their time, rebalance immediately.
❌ Pitfall: "Sync-First Culture"
Defaulting to "let's hop on a call" for every question or decision.
✅ Solution:
Enforce "async-first" attempts. Before scheduling a meeting, the organizer must post the topic with full context and give 24 hours for async responses. If 80%+ consensus reached async, no meeting needed.
❌ Pitfall: "Information in Silos"
Important decisions made in Slack DMs, hallway conversations, or meetings without notes.
✅ Solution:
"If it's not documented, it didn't happen" policy. All decisions must be recorded in central documentation within 2 hours. Meeting recordings auto-posted to project channel.
Getting Started: Your 30-Day Implementation Plan
You don't need to implement everything at once. Here's a phased approach:
Week 1: Visibility
- • Set up team time zone dashboard
- • Add time zones to all calendar invites
- • Create "team roster" document with everyone's typical working hours
Week 2: Meeting Protocols
- • Implement "agenda or cancel" rule
- • Start recording all meetings automatically
- • Assign designated note-taker rotation
Week 3: Async Foundation
- • Create central documentation for each project/team
- • Establish daily async standup format
- • Test "async-first" decision-making on one project
Week 4: Optimize & Measure
- • Survey team on meeting time fairness
- • Identify and fix "HQ time zone bias" patterns
- • Document what's working for future reference
Conclusion: It's About Culture, Not Just Tools
Companies that successfully coordinate 100+ people across 8 time zones don't succeed because they have better tools—they succeed because they've built cultures that respect time zones as much as they respect people.
The tools are simple: a world clock, good documentation, and meeting recording software. The hard part is the discipline to use them consistently and the cultural shift to assume async-first.
Start small: implement the visibility tools this week, add meeting protocols next week, and gradually shift toward async-first communication. Your distributed team will thank you—and your productivity metrics will prove it.