Time zone etiquette for remote teams
When you work with colleagues in other time zones, the small etiquette choices add up. A casual "quick question" at 9 PM their time disrupts dinner. A meeting scheduled for 7 AM eats their morning routine. A "respond by EOD" deadline gives someone in a different zone 2 hours of working time.
The fastest way to find a meeting time that works for everyone is the meeting planner. The rest of this post covers the human side.
The basic rules
1. Know everyone's working hours. Add their time zone to your status, calendar, or world-clock. The fastest way to fail at remote work is treating colleagues as if they're available whenever you are.
2. Don't ping at someone's late evening. If you wouldn't call your colleague at 10 PM in your own timezone, don't ping them at 10 PM in theirs. Slack at 10 PM is a notification on a phone they were trying to ignore.
3. Don't expect instant responses outside their working hours. If you message at 7 PM their time, expect a reply tomorrow morning. If you really need a same-day response, use a sync channel or call.
4. Respect their morning routine. A 9 AM meeting in someone's zone interrupts breakfast, gym, school drop-off, or commute. Default to 10 AM at the earliest.
5. Mind their evening commitments. Children, dinner, gym, family time. Anything after 6 PM their time is intrusion territory unless they've signaled otherwise.
Working hours norms
The widely-accepted "respectful working hours" window:
- 9 AM-6 PM their local time: normal working hours; ping freely
- 6 PM-9 PM: light contact OK; no expectation of response
- 9 PM-6 AM: no contact unless emergency
- Weekends: no contact unless explicitly agreed
These vary by culture (some countries have stricter norms about weekend contact than others) and by team agreement.
Specific behaviors to avoid
The "EOD" deadline. "Send me the doc by EOD" is unclear if you're in different zones. Specify: "EOD my time" (your timezone) or "by 5 PM your time" (their timezone) or — best — "by 18:00 UTC."
The "let's hop on a quick call" reflex. If a question can be answered async, do it async. Calls are intrusive to whoever isn't expecting them.
The "you should have responded already" attitude. If you sent a question 30 minutes ago to someone whose day is just starting, don't follow up impatiently. Allow at least 24 hours for response on non-urgent matters.
The recurring meeting at someone's awful hour. A weekly recurring meeting that's at 9 PM for one team member becomes a slow drain over months. Either rotate the bad slot or move to async.
The "we discussed this in the meeting"-as-decision pattern. If decisions are made in a synchronous meeting that excludes someone, document them in writing so the excluded person can engage. Otherwise you're systematically sidelining them.
The Slack DND override. Modern Slack respects DND settings; abusing the "this is urgent" override for non-urgent things destroys trust quickly.
Specific behaviors to adopt
Set explicit working hours in your tools. Slack has working hours; Google Calendar has working hours; most platforms support it. Set them. Respect them when others set them.
Add timezone to your username or signature. "Maria López (Madrid, GMT+1)" tells anyone messaging you when she'll respond. Reduces confusion dramatically.
Use scheduled send. If you write a message at 11 PM your time, schedule it to deliver at 9 AM their time the next day. Modern Slack/Gmail/Outlook support this.
Default to async. Even when sync would be faster, the default should be "write it down." Sync only when async would lose information.
Ask before pinging during their off-hours. "Is now a bad time?" or "Quick question — answer when you can" both signal respect.
Provide context in async messages. Don't just say "Hi" or "Got a sec?" — that's a sync pattern asking for instant response. Say "I have a question about [project], here's what I'm wondering, no rush."
Document decisions in writing. Even decisions made in sync meetings should be written down somewhere findable.
Cultural variations
Etiquette norms vary by culture:
Northern European (Scandinavia, Germany): strict separation of work and personal time. Don't expect responses after work hours.
East Asian (Japan, Korea, China): longer working hours expected, but evening-into-night meetings are unusual.
Indian and South Asian: often comfortable with evening calls (9-10 PM IST is common for global teams), but mornings before 9 AM are usually off-limits.
Latin American: evening hours can be more flexible; siesta (1-3 PM) is sometimes a quiet period in some countries.
Middle Eastern: Friday is the weekend in most Muslim-majority countries; Sunday is often a working day.
If you're working with a culture you're unfamiliar with, ask about norms rather than assuming.
Difficult cases
The colleague who responds at midnight their time. They might be naturally a night owl, or they might be burned out trying to keep up. If you're a manager, check in. If you're a peer, don't reward 11 PM responses with continuation.
The team that schedules across zones unfairly. Some teams keep meeting times that always work for the home office and always burden the remote folks. Push back; suggest rotation or async.
The client/vendor expecting your zone's hours. When working with external parties, set expectations early. "We'll respond within 24 business hours of [your zone]" is reasonable. "We'll be available at all hours of our zone" is unsustainable.
The "always on" colleague. Some people respond at all hours regardless of zone. This is often a coping strategy or a status signal. Don't normalize it; respect everyone's right to be offline.
Tools for managing this
Slack working hours. Set in profile preferences. Sets auto-DND outside hours; shows colleagues your status.
Google Calendar working hours. Set in calendar settings. Shows colleagues your hours; prevents accidental scheduling.
The meeting planner. Pick cities, see when each person's day is. Pick a time that's reasonable for everyone.
The world clock. Glance at multiple zones to verify what time it is for each colleague before pinging.
Loom or recorded video. Record a quick async update instead of scheduling a meeting. Saves everyone's time-zone alignment headaches.
Manager-specific etiquette
If you're a manager:
1. Don't model bad behavior. If you ping at midnight, your team will too. They'll match your hours, even unhealthy ones.
2. Schedule 1:1s within both parties' working hours. No 9 PM 1:1s for your remote team members.
3. Acknowledge time-zone burden in performance reviews. A team member who has been on the late-evening call rotation for 6 months has paid a real cost. Recognize it.
4. Rotate inconvenience. If the team has a weekly meeting that's awful for one zone, rotate it.
5. Trust async output. Don't penalize team members for being unavailable in real-time when their working hours don't align with yours.
FAQ
Should I respond to messages outside my working hours?
If it's truly urgent (production fire, family emergency), yes. Otherwise, no. Setting boundaries is healthy. Most "urgent" pings can wait until your working hours.
What if my company culture expects 24/7 availability?
Push back gently if you can. Document expectations explicitly. Consider whether the company's culture is sustainable. Many "24/7 expectations" cultures lead to burnout-driven turnover.
How do I respond to repeat off-hours pings from one colleague?
Have an explicit conversation. "Hey, I noticed you're often messaging me at [late hour] my time. Is something specific causing this? I generally respond next business day to non-urgent things — would that work for you?"
How do I handle clients in difficult time zones?
Set explicit response-time expectations in your contract or agreement. "We respond within 4 business hours of [your zone]" is reasonable. Clients respect clarity.
Should I work at unusual hours occasionally for a meeting?
Sometimes, yes — flexibility is part of distributed work. The key is rotation: don't let one team member always be the one taking the bad slot.
What about timezone differences within the same company?
Same rules apply, but the threshold is lower. Don't ping at 7 PM their time; don't expect responses outside their working hours; document decisions made in sync meetings.
Bottom line
Time zone etiquette is mostly common sense applied across hours. Know everyone's working hours. Don't ping outside them. Respect that "EOD" means different things to different people. Default to async for anything not requiring real-time response. Rotate the burden of meetings that fall in awkward hours.
For finding meeting times that respect everyone's hours, the meeting planner is the practical tool.