Why Remote Teams Get Meeting Times Wrong — and How to Fix It

Someone schedules a meeting for 10am and sends the invite without specifying a time zone. Half the team shows up at the right time. The other half shows up an hour early, an hour late, or not at all — because one of them is on daylight saving and one is not, and no one thought to check.

This is not an edge case. It happens constantly to distributed teams, and in 2026 the problem is larger than ever. Nearly a third of all workplace meetings now span multiple time zones — a 35% increase since 2021. Remote work has fundamentally changed how teams operate, but the tools and habits for managing time zones have not kept pace.

Why it keeps going wrong

The root cause is not that people do not know what time zones are — it is that time zone reasoning is cognitively expensive, and people default to their own local time without realising they are doing it. When you think "10am", you mean 10am where you are. Your colleague in another city does the same. When those two mental models do not match, the meeting breaks.

Several factors make this worse in practice:

• Daylight saving time shifts are not synchronised globally. Australia transitions in October and April. The US transitions in March and November. The UK uses March and October. During the weeks around each transition, the offset between countries changes, so an overlap that worked last week may no longer work this week.
• Not all regions observe daylight saving at all. Queensland (Australia), most of Arizona (US), and many countries worldwide do not shift their clocks. A meeting that works between Sydney and New York in July may not work the same way between Brisbane and New York, because Brisbane does not shift.
• Half-hour and 45-minute offsets catch people off guard. India is UTC+5:30. Nepal is UTC+5:45. Australia's Lord Howe Island is UTC+10:30 in summer. Anyone doing mental maths on whole-hour offsets will be wrong for these locations.
• Calendar apps default to the sender's time zone. An invite sent at "10am" from Sydney appears as "10am" in the calendar of someone in London — until they open it and realise their calendar has converted it, which not everyone checks carefully.

The hidden cost: temporal cognitive load

Beyond missed meetings, there is a subtler cost to constant time zone management. Researchers call it temporal cognitive load — the mental overhead of continuously converting between time zones, tracking which team members are in which zone, and keeping track of who is in a transition period and who is not. This mental overhead is real and measurable. It consumes focus that could go toward actual work, and it disproportionately affects team members who are always at the edge of the overlap window — often those in Asia-Pacific or European time zones working with teams based in North America.

A practical system for getting it right

1. Always find the overlap window before proposing a time

Before you open a calendar invite, find the window where all attendees are within normal working hours. This is not mental arithmetic — use a tool. WorldTimeHub's timezone overlap scheduler lets you add all the cities your team is in, set working hour boundaries, and immediately see the windows where everyone overlaps. If there is no overlap in business hours, that is the information you need before you start negotiating.

2. Always include the time zone in every meeting invite title or description

Do not rely on the calendar app to convert correctly, and do not assume everyone's calendar is configured the same way. Include the time zone explicitly: "Design review — 10:00 AEST / 01:00 BST / 20:00 EDT (previous day)." Yes, this looks clunky. It prevents the meeting from being missed.

3. Rotate the inconvenience fairly

If your team spans time zones where no overlap exists within everyone's normal working hours, someone will always have an early or late meeting. Rotating who takes the inconvenient slot — rather than always defaulting to whoever is furthest from headquarters — is both fairer and better for long-term morale and retention.

4. Know your team's public holiday schedule

Scheduling a critical meeting on a public holiday in one team member's country is a version of the same problem. Before scheduling something important, check whether it conflicts with a holiday in any team member's location. WorldTimeHub's holiday finder covers 60+ countries and shows upcoming public holidays by country side by side.

5. Default to async for anything that does not need live discussion

A 2026 McKinsey study found that teams using async-first communication practices saw a 40% increase in productivity. Not every conversation needs a synchronous meeting. Status updates, progress reports, and decisions with sufficient context can often be handled asynchronously, reducing the number of cross-timezone meetings that actually need to happen.

The daylight saving problem deserves special attention

Every year, there are two to four weeks (depending on which countries are involved) when the offset between your team's time zones changes. The Sydney-to-London offset is different in September than it is in November. If your team has a recurring weekly meeting and both cities change their clocks at different times, the meeting will appear to shift by an hour for a period.

The only reliable way to handle this is to either confirm the meeting time in UTC (which does not change with daylight saving) or to check a live world clock before every meeting during transition periods. UTC is the common ground that removes ambiguity entirely — "14:00 UTC" means the same thing in every country.