Time Zone Etiquette: Scheduling Global Meetings That Don't Hurt

Rule 1: Check time zones before booking

This sounds obvious. It is not always done. The most common etiquette failure is booking a meeting in your own time zone without checking what hour that is for the other attendees. Most calendar apps display in your local time, so a 10 AM meeting feels reasonable — until you realize it's 2 AM for your colleague in Tokyo.

Before sending an invite, use our timezone converter to verify the time in every attendee's location. Or browse the world clock for a sanity check.

Rule 2: Know what "reasonable hours" means

Standard reasonable working hours: 8 AM to 6 PM local time for the attendee.

• Acceptable extensions: 7 AM-7 PM, occasionally.
• Use only for emergencies: Before 7 AM, after 8 PM, or anytime on a weekend.
• Never: Between 11 PM and 5 AM unless someone explicitly volunteered.

Some cultural variations to know:

• Spain, Italy: Lunch is 2:00-3:30 PM. Don't book then.
• India: Many companies start at 10:30 AM IST. 8 AM IST meetings can be hard.
• Latin America: Afternoon meetings (2 PM onward) are normal; early morning is less so.
• UK: 12:00-1:00 PM lunch is sacred. 4:30 PM onwards is often "head home" time.

Rule 3: Rotate the inconvenience

For unavoidable cross-zone meetings (e.g., NYC and Sydney), someone is going to take the bad slot. Rotate who:

• Week 1: Sydney comes in early (7 AM their time = 5 PM NYC the day before).
• Week 2: NYC stays late (8 PM NYC = 10 AM Sydney the next day).
• Document the rotation publicly so it's clear and fair.

Default behavior is that whoever has the most power in the relationship (the headquarters, the buyer, the senior person) makes others adapt. Rotation pushes back on this.

Rule 4: Always offer options

When proposing a meeting across zones, suggest 2-3 candidate times in both time zones. Example:

"Could we do one of these for the kickoff?
• Tuesday 9 AM PT / 12 PM ET / 5 PM London
• Wednesday 7 AM PT / 10 AM ET / 3 PM London / 8:30 PM Mumbai
• Thursday 8 AM PT / 11 AM ET / 4 PM London
Let me know what works."

This is fundamentally more respectful than "Tuesday 9 AM." It lets the other person choose what fits their day, and it signals that you've already thought about their time.

Rule 5: Recurring meetings are different

A one-off 7 AM call is fine. A recurring 7 AM weekly meeting is a slow erosion of someone's sleep schedule.

• For recurring cross-zone meetings, insist on rotation or async alternatives.
• Schedule recurring meetings in UTC rather than local time, so DST shifts don't create chaos.
• Revisit recurring meetings every 6 months. Is this still needed? Could it be async?

Rule 6: When in doubt, async

The most courteous thing you can do for a colleague in a difficult time zone is not need a meeting at all. Before scheduling, ask:

• Could this be a Loom video with comments?
• Could this be a written proposal with a comment thread?
• Could this be a Slack thread where everyone responds in their morning?

If the answer to any is "yes, with some loss of quality," consider whether the quality loss is worth less than the cost of forcing someone to a 6 AM meeting.

What to say in tricky situations

When you need a meeting at someone's awkward hour

"I know 7 AM your time isn't ideal — I appreciate you being flexible. We can keep this to 30 minutes and I'll make sure we cover everything that needs your input first, so you can drop after that if you want."

When a meeting got scheduled at YOUR awkward hour

"Hi — that's 11 PM for me, which is past my normal working hours. Could we do an hour earlier (10 PM for me, 5 PM for you)? If not, I can join async by recording a video instead."

When proposing async over a meeting

"Given the time-zone spread, I'd suggest we handle this async. I'll write up the proposal in a doc and tag everyone for comments. Decisions made by Friday. Let me know if you'd rather schedule a call instead."

When the meeting is unavoidable

"Since this will be 6 AM for our Singapore team, I want to keep it tight: 25 minutes, agenda below, decisions tracked in writing. If we run over, we'll move overflow to async."

Cultural sensitivities to watch for

• Friday afternoons in Muslim-majority regions. Friday prayers (Jumu'ah) are typically 12:00-2:00 PM local. Many people leave work for the day after.
• Sunday is a working day in Israel, UAE (most), Egypt. Avoid Friday meetings instead.
• Chinese New Year shuts down work for 1-2 weeks in late January/February.
• Ramadan shifts working hours in many countries. Iftar (sunset meal) is non-negotiable.
• Golden Week in Japan (late April/early May) and China (early October).
• August in Europe — most of southern Europe takes the entire month off.

Check our holidays page for the specific country before scheduling.

Defending your boundaries

Etiquette goes both ways. If you're routinely getting booked into your night or early morning, you're allowed to push back:

• Set clear "available hours" in your calendar profile. Make it visible.
• Decline politely. "I'm not available before 8 AM or after 7 PM my time. Could we find a slot in those hours, or handle this async?"
• Don't accept "just this once" too often. One-offs become patterns. After the third 6 AM meeting "just this once," it's a default expectation.
• Talk to your manager if structural meetings are stacking on your worst hours. They might not realize.

The principle behind the rules

All of this comes down to one principle: treat your colleagues' time and energy as a real resource, not as something that magically expands to fit your scheduling preferences.

Half of remote work etiquette is mechanical (use the right tools, do the time-zone math). The other half is empathy: imagine your colleague's day before you book the meeting. If you wouldn't want it, neither do they.