Meeting etiquette for global teams: the unwritten rules

Most timezone friction is not a calendar problem. It is an etiquette problem. The tools resolve the maths; what they cannot do is decide whose evening gets sacrificed, or whether the meeting needed to happen at all. Here is the unwritten code that good distributed teams follow.

Why does cross-timezone etiquette matter so much?

When everyone shares an office, a badly timed meeting costs ten minutes. When your team is spread across continents, the same meeting can cost someone their dinner, their school run, or their sleep. The burden is invisible to the person who scheduled it and very real to the person dialling in at 11pm. Good etiquette is simply the discipline of making that hidden cost visible and sharing it fairly.

Rule 1: Quote every time in the other person's zone

The single most common mistake is writing a time in your own zone and leaving everyone else to convert it. "Let's meet at 3pm" is useless to a colleague three thousand miles away. Even "3pm GMT" pushes the work, and the risk of error, onto them.

Instead, state the time in each attendee's local zone, or send a proper calendar invite that renders automatically in whatever zone the recipient is in. If you are writing it in prose, spell out the zone clearly. For the exact wording that avoids confusion, see our guide on writing meeting times that don't get misread.

Rule 2: Never assume a fixed offset

The gap between two cities is not constant. London and New York are usually five hours apart, but for a couple of weeks each spring and autumn they drift to four or six hours, because the UK and the US change their clocks on different dates. The southern hemisphere flips the other way entirely: when the north "springs forward", Australia is "falling back".

The lesson: always calculate against the actual date of the meeting, not a remembered offset. A recurring call that was comfortable in January can quietly land an hour earlier by April. If you are unsure whether you mean UTC, GMT or local time, our explainer on UTC vs GMT untangles the difference.

Rule 3: Stay away from the edges of the day

Aim for the middle of everyone's working hours, not the fringes. A slot that lands at 8am for one person and 6pm for another looks like overlap on paper, but both ends are tired or distracted. Where a perfect overlap does not exist, get as close to the centre as you can and acknowledge openly who is stretching.

A rough sense of standard office hours helps you find the genuinely civilised windows:

Rule 4: Send an agenda, then keep it short

If you are asking people to give up part of their day, respect it. A one-line agenda sent in advance lets attendees prepare, decide whether they even need to be there, and arrive ready to contribute. No agenda signals that their time matters less than your convenience.

Then end on time, or early. Padded meetings are an everyday annoyance in one office and a real imposition when someone joined at the end of a long day. Brevity is a courtesy, not a constraint.

Rule 5: Record and write things down

Record the call and post the recording and notes somewhere durable. This does two things: it lets anyone who could not make a civilised hour catch up on their own time, and it relieves the pressure to attend live for the sake of it. A well-documented meeting is one that fewer people need to attend next time.

Rule 6: Rotate the pain fairly

Some meetings genuinely cannot suit everyone. When that happens, do not let the same people always carry the cost, and do not default to the convenience of headquarters. Rotate who takes the early or late slot for recurring meetings, so the burden circulates rather than settling permanently on your colleagues furthest from the office.

Rule 7: Default to async

The most respectful meeting is often the one that never happens. Before booking a live call, ask whether a written update, a recorded video or a shared document would do the job. The cost is real: Harvard Business Review reports that executives now spend nearly 23 hours a week in meetings, up from less than 10 in the 1960s. The further apart your team is, the higher the bar for synchronous time should be. Reserve live meetings for the things that truly need them:

1. Building trust and relationships with people you rarely see.
2. Sensitive or emotional conversations that text handles badly.
3. Genuine real-time problem-solving where back-and-forth is fast and necessary.

Status updates, decisions that can be written down, and information you are merely broadcasting almost never qualify. Some countries even enshrine a legal "right to disconnect", recognising that being available at all hours is not a virtue. Async-by-default is how distributed teams honour the same principle voluntarily.

The quick checklist

Before you send the next cross-timezone invite, run through this:

• Have I shown the time in each attendee's local zone?
• Have I checked the offset against the actual meeting date, not a remembered one?
• Is the slot near the middle of everyone's day, not the edges?
• Is there an agenda, and is the meeting as short as it can be?
• Will it be recorded for anyone who cannot attend?
• If this is recurring, am I rotating the awkward slot fairly?
• Does this actually need to be a live meeting at all?

The first three are pure logistics, and that is where a tool earns its keep. Atlas pins each person on a world map, shows their real local time with daylight saving already resolved, highlights the window where everyone is awake, and writes the meeting to your calendar in their zones in one tap. It handles the maths so you can spend your attention on the manners.