You accept an invite for 3 PM. Your calendar says 4 PM. Your colleague in Dubai swears they sent it for 3. Nobody's lying, and nothing's broken. Somewhere between their calendar and yours, a time zone got read differently.
Calendar invites don't store "3 PM"
When someone sends you an invite from Google Calendar, Outlook or Apple Calendar, the event isn't saved as a time on a clock face. It's saved as a moment in time, tied to a time zone, using the iCalendar format (published by the IETF as RFC 5545) that almost every calendar app shares. Your app then converts that moment into your local time.
That's what makes cross-border meetings work most of the time. It's also why, when one setting is off, the whole invite slides by an hour or more without anyone noticing.
The good news is that the cause is nearly always one of a handful of things, and each one takes a minute to check.
The five usual causes
- Your calendar's own time zone is wrong. Google Calendar and Outlook both have a time zone setting that's separate from your device clock. If you travelled, moved or set the account up abroad, it may still be set to somewhere else.
- The sender's calendar time zone is wrong. If they live in London but their account is still set to New York, they'll create a "3 PM" event that's really 3 PM New York time, and you'll see 8 PM.
- The event was created with a fixed zone or with no zone at all. Some apps let you pin an event to a specific time zone, and some booking tools send "floating" times with none. A floating 3 PM shows as 3 PM for everyone, wherever they are.
- A clock change fell between the invite and the meeting. If someone sends a recurring invite in September and the UK clocks go back in October, the meeting can shift for people in countries that didn't change, like India or the UAE.
- Your device's automatic time zone is off. Phones normally set their zone from the network. If that's switched off, the phone may show the right hour for where you were, not where you are.
How to fix it
Start with your own settings, because that's the only side you control. In Google Calendar, open Settings and check the time zone under General. In Outlook, it's under Calendar settings. On an iPhone, check that Set Automatically is on under Date and Time, and that Time Zone Override is off in the Calendar settings.
If your settings are right, open the event itself. Most apps show the time zone the event was created in somewhere in the details. If it says something you didn't expect, the problem's on the sender's side, and a quick message is quicker than rebuilding the invite.
For recurring meetings across borders, it's worth naming the anchor zone in the invite title or description. "Weekly sync, 10 AM London" leaves no room for doubt when the clocks change in one country and not the other.
Why it keeps happening
The deeper issue is that calendars quietly translate time for you, which is brilliant until the translation's wrong. Because you only ever see the converted time, you've got no reason to question it until someone's sitting alone on a call.
This gets worse when the conversation that set up the meeting happened somewhere else entirely. Plenty of meetings get agreed in a WhatsApp thread and only turned into an invite afterwards, by one person, from memory. If that person reads "3 PM" as their own 3 PM rather than the other person's, the invite is wrong before it's even sent.
The fix isn't to stop trusting calendars. It's to make the time zone visible at the moment the time gets agreed, so the invite is just a record of something both sides already confirmed.
What this means for anyone working across borders
Wrong-time invites are rarely a tech failure. They're a handoff failure, where a time agreed in one place gets re-entered somewhere else with an assumption baked in. The more borders a team spans, the more of those handoffs there are.
That's also why they tend to cluster around the clock changes in March and October. Every recurring meeting gets re-translated at once, and any invite with a shaky zone setting shows its hand on the same week.
Why does my Outlook invite show a different time to Google Calendar?
Usually because the two accounts are set to different time zones. Each calendar converts the event into its own setting, so if Outlook is on GMT and Google is on Eastern Time, the same invite will show two different local times.
Why did my meeting move by an hour after the clocks changed?
Because the meeting was anchored to a time zone that changed its clocks, and yours didn't, or the other way round. A 10 AM London meeting stays at 10 AM in London after the clocks go back, but it moves by an hour for anyone in India, the UAE or Singapore.
How do I stop calendar invites showing the wrong time?
Check that your calendar's time zone setting matches where you are, keep your phone's time zone on automatic, and name the anchor city in the invite for any recurring cross-border meeting. Those three habits catch almost every case.
The Bottom Line
Wenya lets you agree a time inside WhatsApp, iMessage or Telegram with each person's own time zone shown, so the invite matches what everyone actually said yes to. Try it free at wenyawanna.ai