Blog › Remote Work & Productivity
The Time Zone Problem
Nobody Talks About in Remote Teams
Scheduling across time zones sounds simple until someone misses a call, a contractor invoices the wrong hours, or a deadline lands at 3am. Here's what's actually going wrong - and how to fix it in 30 seconds.
It's not the maths. It's the assumptions.
Every distributed team has had the same meeting. Someone sends a calendar invite for 10am. Half the team joins on time. The other half is missing because the invite said 10am Sydney and they read it as 10am London. Nobody specified. Everyone assumed.
Time zone errors aren't caused by people being careless. They're caused by systems that make assumptions invisible. A meeting invite that says "10:00am" with no time zone attached is a trap waiting to close on whoever reads it last.
For remote teams, contractors billing across borders, and anyone coordinating with offshore partners, the cost of these errors adds up fast - missed meetings, duplicate work, invoices with the wrong hours, and deadlines that quietly land at a time nobody intended.
Where it goes wrong most often
Four recurring failure modes in distributed work.
Daylight saving transitions
Australia, the US, and the UK all change their clocks - but on different dates. For three to four weeks twice a year, every time zone offset you've memorised is wrong by an hour.
Contractor invoicing
A contractor in Manila billing "9am to 5pm" when the client is in Melbourne needs someone to do the conversion correctly, every time. One wrong assumption compounds across a whole invoice.
Deadline communication
"End of day Friday" means something different in Sydney than it does in Auckland, Singapore, or London. Without a specified time zone, it's a guess wrapped in a commitment.
Mental arithmetic fatigue
Doing the conversion in your head works fine once. Do it ten times a day across four time zones and errors creep in. The maths isn't hard - the repetition is.
The underlying issue: time zones aren't static offsets. They shift with daylight saving, and not all regions observe it. Any mental model built on "Sydney is always X hours ahead of London" will be wrong for several weeks every year.
What actually helps
Three approaches in order of effort.
Always specify the time zone in writing
The cheapest fix. Every meeting invite, every deadline, every contractor brief gets a time zone attached. "10am AEST" not "10am." Takes two seconds and removes the ambiguity entirely. Requires discipline but no tools.
Use a time zone converter for quick checks
A browser-based converter lets you enter a time in one zone and see the equivalent in multiple others instantly. No mental arithmetic, accounts for daylight saving automatically, takes about ten seconds. Best for ad hoc checks throughout the day.
Set a team standard time for async comms
Some distributed teams pick one reference time zone (UTC is common) for all async communication - Slack messages, project updates, documentation. Everyone converts to and from their local time. Eliminates ambiguity at the cost of a small habit change.
A note on Australian time zones specifically
It's more complicated than most people realise.
Australia has five active time zones in regular use - AEST, AEDT, ACST, ACDT, and AWST. That's before you factor in Queensland not observing daylight saving (while New South Wales and Victoria do), or the Northern Territory sitting permanently on ACST.
For anyone coordinating between Sydney, Brisbane, Adelaide, and Perth on the same project, the offset between those cities changes twice a year when daylight saving starts and ends in some states but not others. A Melbourne team and a Brisbane team can be on the same offset for part of the year and an hour apart for the rest.
It's not complicated once you know it - but it catches people out constantly, including people who've lived in Australia their whole lives.
Stop doing the maths in your head
Free browser-based time zone converter. Enter a time, pick your zones, get the answer. No sign-up, no install.
Open the Time Zone Converter →