The 2 A.M. Call Was Always Mine: How Global Teams Split the Meeting-Time Tax

Disclaimer: This article is for general information only. Employment terms, overtime rules and rest-period law differ by country, and none of the advice below replaces the contract or local regulation that applies to you.

If you are trying to work out who should take the late call on a global team — or how to be fair with meeting times across time zones — the problem is almost never the arithmetic. Before you open a meeting planner to find overlapping work hours, here is the part nobody puts in the invitation: the awkward hours are usually absorbed by the same people, every single week.

Priya joined our team in Sydney in January. She was the first person we had hired in that time zone, and she was good — the kind of good that makes everyone else's job easier without anyone noticing why. We gave her a laptop, a Slack account, and a standing invitation to our weekly product review.

Our review was at 9 a.m. San Francisco. I was in Lisbon at the time, so it landed at 5 p.m. for me, which was fine. For the engineers in California it was the natural start of the working day, which was also fine. For Priya it was 3 a.m.

By October she had attended 34 reviews. Thirty-one of them started between 1 a.m. and 4 a.m. her time. She never complained about it. She complained about the roadmap, the design decisions, the priorities — all the things she was supposed to complain about. The hours were invisible, because a 3 a.m. meeting does not show up as a problem in anyone's calendar. It shows up as a person who is quieter than she used to be.

When she left, the resignation note was four lines long. The job was fine. The hours were not. I read that line twice and then went looking for the meeting series that had done it.

Quick Answer: Fair Meeting Times on a Global Team (AI Summary)

• Count the out-of-hours slots each location absorbs — the tax is invisible until it is measured.
• Rotate the anchor time monthly or quarterly, and publish the rotation in advance.
• Before rotating anything, ask whether the meeting needs to be synchronous at all.

What the Meeting-Time Tax Actually Is

Every distributed team has a schedule, and every schedule has a shape. The shape is decided by whoever sets the first meeting, and it usually follows the largest group of people or the most senior person. Once that shape exists, everyone else organizes their life around it, because that is what reasonable people do.

The meeting-time tax is what the people outside that shape pay. It is not one dramatic sacrifice; it is a slow accumulation of small ones. A call at 11 p.m. means a disrupted evening. A call at 3 a.m. means a broken night and a foggy morning. A call at 6 a.m. means setting an alarm on the one day you would normally take your kid to school.

What makes the tax unusual is that it is invisible in every system a company uses to track work:

• It does not appear in the calendar, because the calendar only knows the meeting happened.
• It does not appear in a performance review, because the person paying it is still delivering.
• It does not appear in a budget, because nobody invoices for sleep.
• It does not appear in attrition data until the person who was paying it resigns, and by then the reason sounds vague: "the hours."

That last one is why I take this seriously now. "The hours" is not a vague reason. It is a precise one, and it was visible in our calendar the whole time if anyone had looked.

Why It Always Lands on the Same Person

There is a mechanical reason the tax concentrates, and it is worth understanding because it is not caused by anyone being unfair. It is caused by anchoring.

A recurring meeting needs a stable time, so it gets set once and never revisited. The time that gets set is the one that works for whoever was in the room when the meeting was created. When the team later grows into a new time zone, the meeting does not move — the new person adapts. Then the next new person adapts to the same time. Within a year, the meeting has become an institution with a time zone baked into it, and the people outside that time zone have become the ones who stretch.

There is a second effect underneath it. The person who sets the meeting is usually the person closest to headquarters, and headquarters is usually where the loudest part of the company lives. So the anchor drifts toward the center of gravity of the organization, which is the exact opposite of where the people with the least influence are sitting. The tax is not distributed by time zone. It is distributed by distance from power.

The same logic explains why the tax is so sticky: the person paying it is rarely in the room when the time is chosen, and a person who is not in the room cannot propose moving it. If this sounds like a broader problem than scheduling, that is because it is one.

Count the Tax Before You Try to Fix It

You cannot argue about fairness in the abstract, and you do not need to. The tax is countable, and counting it takes about ten minutes.

Take every recurring meeting on the team's calendar and write down, for each location, how many hours fall outside a normal working day. Then multiply by the frequency. Here is what our product review looked like once I did it:

Forty-five hours of a person's night, a year, for one weekly meeting. Add the second-order cost — the morning after a 3 a.m. call is not a normal morning — and the real number is closer to a hundred hours. And that was one meeting. Priya was on six of them.

Once you have the number, the conversation changes shape. It is no longer "can we move the meeting?" which invites a debate about inconvenience. It is "we are spending a hundred hours of one person's sleep per year on this, and nobody decided that." Nobody argues with a ledger.

Find Out Whether an Overlap Exists at All

Before you redesign anything, check the geometry. Some teams have a comfortable overlap and simply are not using it. Others have no overlap at all, and that is a different problem with a different answer.

The fastest way to see it is to put every location on one 24-hour axis. A meeting planner does exactly this: add each city and it highlights the hours when all of them are inside a working day. Three outcomes are possible, and each one leads somewhere different:

• A wide overlap exists. Move the meeting into it and stop negotiating. This is the case more often than people expect, especially for Europe and the US East Coast, where the natural window is early afternoon in Europe and early morning in New York.
• A narrow overlap exists. Two hours is enough for one well-run meeting and not enough for four. Cut the agenda down, or split the meeting by topic so only the relevant people attend.
• No overlap exists. Do not solve this by asking one region to work nights permanently. Make the work asynchronous by default and hold a rotating all-hands at a time that moves each cycle.

When you do find a window, write the meeting time in every attendee's local time — "3 p.m. Lisbon / 7 a.m. San Francisco / 11 p.m. Sydney" — so nobody has to trust their own mental arithmetic. If the meeting falls near a daylight saving change, verify the offsets for the exact date, because the window itself can shift by an hour without anyone touching a clock. That is the same trap that catches travelers, which I wrote about in why a flight can land before it takes off.

Three Ways to Rotate (and One That Fails)

Rotation is the standard answer to the meeting-time tax, and it works — but only if you pick the right kind. I have tried all four of these.

1. Rotate by period

The anchor time shifts on a fixed cycle: this quarter the meeting is convenient for the Americas, next quarter for Europe, then for Asia-Pacific. This is the fairest method and the easiest to explain. Its cost is that everyone is slightly disrupted instead of one group being badly disrupted, and that cost is real — a meeting that moves every quarter never becomes a habit. Use it for meetings where fairness matters more than rhythm.

2. Rotate by meeting type

Split the meetings into categories and anchor each category to a different region. Planning calls suit the region doing the work; review calls suit the region that owns the decision; social calls get the slot that is least bad on average. This is my preferred method because it distributes the burden without moving anything mid-quarter.

3. Rotate the anchor, keep the rhythm

Keep one fixed slot for the meeting that genuinely needs a stable rhythm — a weekly team call, a monthly review — and rotate every other meeting around it. Publish the rotation for the year so people can arrange childcare, shifts and classes. Predictability is worth almost as much as fairness, and this method buys both.

What fails: rotating every week

A weekly rotation sounds fair and is quietly exhausting. Nobody can build a routine, everyone has to re-check the time before every call, and the person who forgets is blamed for missing a meeting that was at a different hour than last week. Rotation only works when the pattern is long enough to be learnable.

Whatever you choose, pair it with compensation for the people in the bad slot: a later start the following morning, an afternoon off, or an agreement that they skip the next asynchronous ritual. A tax that is acknowledged is survivable. A tax that is invisible is what makes people update their CV.

The Async Alternative: What Really Needs to Be Live

The best way to split the meeting-time tax is to shrink it before you divide it. Most recurring meetings exist for reasons that do not require simultaneous attendance, and the ones that do are usually obvious once you ask the question out loud.

Our product review was in the wrong column for two years. It was, in practice, a status meeting with a decision bolted onto the end. We split it: the status half became a written thread with a deadline, and the decisions became a shorter call with only the people who could actually decide. The call moved into the Lisbon-to-San-Francisco overlap. Sydney stopped being invited to the routine part and joined the decision part when it touched their work.

Priya's replacement joined in March. She has attended nine live reviews this year instead of thirty-four, and she has never once set an alarm for 3 a.m. The work did not slow down. If anything, the decisions got faster, because a written proposal forces the author to state what they actually want.

Five Rules I Use Now

1. Count the hours before you defend the time. One table, ten minutes, and the argument is over. Fairness stops being a matter of opinion.
2. Never let a meeting inherit a time zone. When a team grows into a new region, revisit the anchor rather than asking the new person to adapt to a decision they were not present for.
3. Publish the rotation for the year. Monthly or quarterly, never weekly, and always in writing. People can organize their lives around a schedule they can see.
4. Compensate the bad slot. A late start, an afternoon off, or a smaller share of the asynchronous chores. Acknowledged cost is manageable; unacknowledged cost is corrosive.
5. Ask the async question first. Before moving a meeting, ask whether it needs to exist in real time. Half the time, it does not — and the honest answer to that question is the cheapest fix available.

None of this requires a tool, but the tool makes the first step easy. Put the cities on a meeting planner, look at where the working hours overlap, and check the exact local time in a time zone converter before you put it in the invite. If the window you need does not exist, the planner will show you that too — and an honest empty highlight is more useful than another round of guessing. For the arithmetic behind the overlap itself, this guide to planning meetings across time zones covers the method step by step.

Frequently Asked Questions

Methodological note: This article was written and fact-checked by the Fengvi Editorial Team following a documented editorial methodology. All cited data comes from public sources.