The calendar invite said 3 PM. You joined on time. The meeting room was empty. Twenty minutes later, you realized: 3 PM their time. You were in a different time zone. No one mentioned which 3 PM. You missed the entire meeting because of three letters that weren't there.
Time zones don't cause confusion—ambiguous communication about time zones causes confusion.
Working across time zones is now normal, but most people still treat it as an exception. We've missed meetings, scheduled calls at 3 AM for colleagues, and learned every lesson the hard way. This guide shares what actually works for coordinating across the planet.
Time Zone Fundamentals
UTC: The Universal Reference
UTC (Coordinated Universal Time) is the global standard. Every time zone is defined as an offset from UTC:
- UTC+0: London (when not in daylight saving)
- UTC-5: New York (Eastern Standard Time)
- UTC-8: Los Angeles (Pacific Standard Time)
- UTC+1: Paris, Berlin
- UTC+8: Singapore, Hong Kong
- UTC+9: Tokyo
- UTC+5:30: India
Pro tip: When scheduling internationally, communicate in UTC. "Meeting at 14:00 UTC" is unambiguous. "Meeting at 2 PM" requires follow-up questions.
Standard Time vs. Daylight Saving Time
Many regions shift clocks twice a year:
- Standard Time: Winter months
- Daylight Saving Time (DST): Summer months (clocks move forward 1 hour)
This creates chaos because:
- Not all countries observe DST
- DST changes on different dates in different hemispheres
- For 2-4 weeks per year, relative time differences shift
Example: New York and London are usually 5 hours apart. But when the US changes clocks before the UK, they're briefly 4 hours apart.
Time Zone Abbreviations
| Abbreviation | Full Name | UTC Offset |
|---|---|---|
| EST | Eastern Standard Time | UTC-5 |
| EDT | Eastern Daylight Time | UTC-4 |
| PST | Pacific Standard Time | UTC-8 |
| PDT | Pacific Daylight Time | UTC-7 |
| GMT | Greenwich Mean Time | UTC+0 |
| BST | British Summer Time | UTC+1 |
| CET | Central European Time | UTC+1 |
| CEST | Central European Summer Time | UTC+2 |
| IST | India Standard Time | UTC+5:30 |
| JST | Japan Standard Time | UTC+9 |
Warning: IST means India Standard Time or Irish Standard Time. Context matters.
Using Our World Clock
Our World Clock helps with time zone coordination:
Features
- Multiple cities: Add the cities you work with
- Current time display: See all times at a glance
- Time planning: See what time it will be elsewhere at a given local time
- Daylight saving handling: Automatic DST adjustments
How to Use It
- Add cities where your team members are located
- See current times across all locations
- Plan meetings by finding overlap windows
- Convert specific times between zones
Finding Meeting Overlap
The Overlap Window Problem
Scenario: Team members in San Francisco (PST), London (GMT), and Singapore (SGT).
The math:
- San Francisco: UTC-8
- London: UTC+0
- Singapore: UTC+8
That's a 16-hour spread. There's no "reasonable" hour that works for everyone.
Strategies for Difficult Spreads
Rotate the pain:
- Meeting 1: Good for US/Europe, early for Asia
- Meeting 2: Good for Asia/Europe, late for US
- Alternate who gets the bad time slot
Async-first, sync when necessary:
- Record meetings for those who can't attend
- Make synchronous meetings optional for distant zones
- Use documents instead of meetings when possible
Split the team:
- Regional sub-teams that meet locally
- Cross-regional meetings only when necessary
- Representatives attend on behalf of regions
Realistic Overlap Examples
US + Europe (5-8 hour difference):
- Overlap window: 8-11 AM US Eastern / 1-4 PM UK
- Best meeting times: 9 AM Eastern / 2 PM London
US + Asia (13-16 hour difference):
- Minimal overlap
- Options: Very early US morning or very late US evening
- Better: Async communication, rotating meeting times
Europe + Asia (6-8 hour difference):
- Overlap window: Morning Europe / Afternoon Asia
- Best meeting times: 8-10 AM London / 4-6 PM Singapore
Communication Best Practices
Always Specify the Time Zone
Bad: "Let's meet at 3 PM" Good: "Let's meet at 3 PM EST (8 PM UTC)" Best: "Let's meet at 20:00 UTC"
Use Shared Calendars Properly
- Ensure your calendar time zone is set correctly
- Calendar invites should auto-convert to recipient's zone
- Double-check that the converted time is reasonable
Include Multiple Time Zones in Invites
For important meetings, include times in all relevant zones:
Team Meeting Wednesday, January 22
- 9:00 AM PST (Los Angeles)
- 12:00 PM EST (New York)
- 5:00 PM GMT (London)
- 6:00 PM CET (Berlin)
- 1:00 AM +1 SGT (Singapore) - recording available
Acknowledge Time Zone Sacrifices
When someone takes a call at 6 AM or 10 PM, acknowledge it:
- "Thanks for joining early, Sarah"
- Move important items to accommodate distant colleagues
- Don't schedule their time zone's bad slot repeatedly
Common Time Zone Mistakes
Mistake 1: Assuming Everyone Knows Your Zone
Problem: You say "3 PM" assuming everyone knows you mean EST.
Solution: Always include the time zone. Always.
Mistake 2: Forgetting Daylight Saving Changes
Problem: You scheduled a recurring meeting. When DST changes, it's suddenly an hour off.
Solution: Use UTC for recurring meetings, or verify times after each DST transition.
Mistake 3: Booking "First Thing" or "End of Day"
Problem: "Let's talk first thing Monday" means vastly different times globally.
Solution: Specify exact times with zones. "First thing" is not a time.
Mistake 4: Half-Hour and 45-Minute Offset Zones
Problem: Assuming all time zones are on the hour.
Reality:
- India: UTC+5:30
- Nepal: UTC+5:45
- Iran: UTC+3:30
- Newfoundland: UTC-3:30
Solution: Use a world clock tool. Don't assume.
Mistake 5: The Date Line Trap
Problem: Scheduling for "Monday" but it's already Tuesday in Sydney.
Solution: Include the date and time zone. Check if the date differs.
Time Zone Etiquette
Respect Others' Hours
- Check what time it is for them before messaging
- Use scheduled send for non-urgent messages
- Don't expect immediate responses outside business hours
Meeting Scheduling Norms
- Whoever calls the meeting proposes a time
- Consider all attendees' zones when proposing
- Default to the requester's inconvenience, not the recipient's
Handling Urgent Across Zones
For true emergencies:
- Call or text (don't wait for async response)
- Acknowledge the intrusion
- Keep it brief
- Follow up with details they can read later
For non-emergencies that feel urgent:
- It can probably wait until their morning
- Send now with "no response needed until your morning"
- Question whether it's really urgent
Tools and Techniques
Mental Shortcuts
US East Coast to London: Add 5 hours (EST) or 4 hours (EDT) US West Coast to East Coast: Add 3 hours London to Central Europe: Add 1 hour Singapore to London: Subtract 8 hours
The "Follow the Sun" Model
For teams spread globally, work literally follows the sun:
- Asia works, hands off to Europe
- Europe works, hands off to Americas
- Americas works, hands off to Asia
This enables 24-hour coverage and natural async handoffs.
Time Zone in Your Signature
Include your time zone in your email signature:
Jane Smith Product Manager UTC-5 (Eastern Time)
This helps recipients know when to expect responses.
Practical Scenarios
Scenario: Scheduling a Job Interview
Situation: You're interviewing with a company in a different zone.
Best practice:
- Propose times in both your zone and theirs
- Use a tool to verify conversion
- Confirm which zone the calendar invite reflects
- Set a reminder in your local time
Scenario: Client Calls Across Zones
Situation: Regular calls with international clients.
Best practice:
- Establish a standing time that works for both
- Document the time in UTC and both local zones
- Have a protocol for DST adjustments
- Send reminder with time in both zones
Scenario: Announcing a Product Launch
Situation: Launch "at midnight" but your users are global.
Best practice:
- Pick one time zone for the launch
- Announce with multiple zone conversions
- Consider staggered rollouts by region
- Don't say "midnight" without specifying where
Conclusion
Time zones aren't complicated. Communicating about time zones clearly is the challenge—and it's completely solvable with simple habits.
Always include the time zone. Use UTC for international scheduling. Check our World Clock before proposing meeting times. Rotate the inconvenience fairly. Respect that your 2 PM might be someone's 11 PM.
The remote work era requires time zone fluency. The tools exist. The courtesy exists. The only thing missing is the habit of always, always specifying the zone.
Keep Reading
- Remote Collaboration Productivity Guide - Full remote work strategies
- Work From Home Digital Tools Guide - Complete remote toolkit
- Meeting Productivity Guide - Run better meetings
Related Tools
- World Clock - See times across zones instantly