Daylight Saving Changes Keep Causing Missed Calls: How to Schedule Across Countries
Clocks change on different Sundays in Australia, the UK and the US, and some places never change at all. Here is how to spot the risky weeks, fix standing calls set in the wrong zone and re-confirm before anyone sits in an empty meeting.
Daylight saving causes missed calls because countries change their clocks on different dates, so for a few weeks each spring and autumn the gap between you and a client is an hour different from usual. The fix is to know the change dates for every country you deal with, anchor each standing call to one named time zone, and re-confirm calls with both local times during the change weeks.
Software helps, but it does not think for you. Calendar apps handle the arithmetic for events created properly, yet calls agreed by email, times copied by hand and standing calls created in someone else's zone still go wrong. This guide sets out the 2026 change dates, the regions that do not change, a checklist for change weeks and the anchor-zone rule. For the broader basics of overlap windows and writing times clearly, see our guide to scheduling meetings across time zones.
Why does daylight saving keep causing missed calls?
Daylight saving moves clocks forward an hour in each region's spring and back an hour in its autumn. The problem for anyone working across countries is that the northern and southern hemispheres change in opposite directions, and even countries in the same hemisphere pick different Sundays.
The change dates that matter in late 2026
- Sunday 4 October 2026: New South Wales, Victoria, the ACT, Tasmania and South Australia moved clocks forward an hour.
- Sunday 25 October 2026: the UK changes from BST back to GMT, along with most of Europe on the same day.
- Sunday 1 November 2026: most of the US goes back an hour.
In early 2027 the order reverses: US clocks go forward on Sunday 14 March, the UK on Sunday 28 March and south-east Australia goes back on Sunday 4 April. Between each pair of dates there are one to three weeks when the usual gap is wrong.
Places that do not change at all
Queensland, Western Australia and the Northern Territory do not use daylight saving, and India has no daylight saving either. That stability is useful, but it also means a Brisbane or Townsville business is an hour behind Sydney for half the year and level with it for the other half. Singapore and most of Asia also stay put.
Where calls actually go wrong
- Standing calls created in another zone. A weekly call set up by a London client in their calendar follows London time. When the UK changes, it moves in your calendar, which is correct, but any manual copy you keep does not.
- Times agreed in words. 'Let's keep 10 o'clock' means different things before and after a change.
- Hand-copied blocks. If you copied a client's meeting into your diary as a busy block, it stays at the old time. Our Google Calendar scheduling guide shows where to set an event's own time zone.
- Confirmations without a zone. A time with no zone written next to it invites each side to assume their own.
What a booking tool does and does not do
A booking made through a booking page is created as a calendar event at a fixed moment, so it usually lands correctly for both sides, provided your account's time zone setting matches where you work. Calenix has a time zone setting and email confirmations and reminders, but it does not send automatic alerts about daylight saving changes. The change-week checks below are a habit you run yourself.
Why a one-hour slip costs more than an hour
A missed call across countries is rarely a quick fix. By the time either side realises, the other person has often moved on to their evening or their next meeting, and the next shared window may be a day away. A call that slips by an hour can easily slip by a week.
It also lands unevenly. The person who turned up on time feels their time was wasted, and they rarely blame daylight saving. They blame the person who was not there. For freelancers and small firms, being the one who missed the call is a reputational cost that no apology fully repairs.
The illustrative maths: if you bill A$140 an hour, a missed call costs the hour you set aside, plus perhaps 20 minutes of emails to rebook, so around A$185 of time. Three misses across the spring and autumn changes is about A$555 a year, before counting any client who quietly decides you are hard to work with.
Reminders help, but only if they show the right time. A reminder for a call that is in your diary at the wrong hour simply reminds you of the wrong hour. That is why change-week re-confirmations matter more than extra reminders, a point our guide to email appointment reminder best practices touches on when it covers what each reminder should say.
What a daylight saving routine gives you
No surprise empty rooms: change weeks are flagged in advance, not discovered on the day.
Standing calls that stay put: each one has a named anchor zone, so everyone knows which clock it follows.
Clearer confirmations: both local times are written in every re-confirmation during change weeks.
Fewer late-night slips: you notice when a call has moved into your evening and can renegotiate it early.
Less reliance on memory: a twice-yearly checklist replaces trying to remember four countries' rules.
A calmer relationship with clients abroad: they see you handling the time difference, not tripping over it.
How to stop daylight saving causing missed calls in 6 steps
Diary the change dates for every country you work with — Add each region's change date for the year as an all-day note in your calendar, set to free so it does not block bookings. For late 2026: 4 October (south-east Australia), 25 October (UK) and 1 November (US).
List your standing calls and who created them — For each weekly or monthly call with someone abroad, note whose calendar it was created in and which zone it follows. That zone is where the call's time is fixed.
Agree an anchor zone for each standing call — Decide with the other person which clock the call follows, and add it to the invitation title, for example 'Weekly review (London time)'. The other side accepts that their local time will move twice a year.
Replace hand-copied blocks with real invitations — If you copied a client's call into your diary as a busy block, ask for a proper invitation instead, or recreate the block in the client's time zone so your calendar app adjusts it.
Run the change-week checklist — On the Monday before each change, list every call in the next fortnight with someone in a changing zone, recheck the local times and flag any that now fall outside working hours.
Re-confirm in both local times — Email each affected person with the date and both times, such as 'Thursday 29 October, 8am GMT London / 6pm AEST Townsville'. Keep it to one line so it is read.
How the gap from Townsville changes through late 2026 (illustrative)
| Feature | Until the first change | After the change | Change date |
|---|---|---|---|
| Sydney or Melbourne | Same time as Townsville | 1 hour ahead of Townsville | Sunday 4 October 2026 |
| London | 9 hours behind Townsville | 10 hours behind Townsville | Sunday 25 October 2026 |
| Denver | 16 hours behind Townsville | 17 hours behind Townsville | Sunday 1 November 2026 |
| Perth | 2 hours behind Townsville | No change | No daylight saving |
| Mumbai or Bengaluru | 4.5 hours behind Townsville | No change | No daylight saving |
Best practices for scheduling through clock changes
Always write a time with its zone, and during change weeks write both local times.
Name the anchor zone in the title of every standing call with someone abroad.
Create events in the zone the call follows rather than converting the time in your head.
Show a second time zone in your calendar app's settings if most of your calls involve one other country.
Check that your booking tool's time zone setting matches where you work, especially after travel.
Re-confirm calls in the weeks between one country's change and another's, when the usual gap is wrong.
Review the spring and autumn change dates each January and July, because they differ every year.
Common daylight saving mistakes
Assuming everyone changes on the same weekend because your own country does.
Thinking Queensland, Western Australia or India change their clocks, when they do not.
Keeping a hand-copied busy block for a client's standing call, which stays put when the real call moves.
Agreeing to 'keep the usual time' without saying whose usual time.
Adding more reminders instead of fixing the time in the calendar, so you are reminded of the wrong hour.
Ignoring a call that has quietly moved into your evening until the day it happens.
Example: a technical writer in Townsville with clients in four countries
Take a fictional freelance technical writer in Townsville who documents mining software. Her clients are in Sydney, Perth, London and Denver. Because Queensland does not use daylight saving, her clock never moves, but the gaps to three of her four clients do. She bills A$140 an hour.
Earlier in the year, during the spring changes, she missed one call and turned up an hour early to another. This October she tried a routine instead.
- Sydney: her Wednesday call with a Sydney product manager was agreed as '10am' in an email thread. From Sunday 4 October, 10am in Sydney is 9am in Townsville. She caught it on Monday 5 October because the change was in her calendar, and the call on Wednesday 7 October went ahead at 9am her time.
- London: a weekly Thursday call at 8am London time sits in her calendar from the client's invitation, titled 'Docs review (London time)'. On Thursday 22 October it is at 5pm in Townsville. From Thursday 29 October it is at 6pm, which clashes with her evening swim squad. She raised it on Monday 19 October, and the client agreed to move to 7:30am London, 5:30pm Townsville, from 29 October.
- Denver: the Monday 4pm Denver stand-up is 8am Tuesday in Townsville until US clocks go back. From Tuesday 3 November it is 9am. She re-confirmed with one line: 'Monday 2 November, 4pm MST Denver / Tuesday 3 November, 9am AEST Townsville'.
- Perth: no change, because Western Australia does not use daylight saving either.
New clients book her through Calenix, where her time zone is set to Brisbane time and each event description says 'All times AEST (Queensland, no daylight saving)'. Those bookings land correctly. The risky calls were all the ones agreed outside the booking page, so the checklist focuses on them.
The illustrative maths: the spring misses cost about A$370 in lost time and rebooking at A$185 each. The October routine took about 30 minutes in total. For more on keeping confirmations clear, see our guide to what to include in an appointment confirmation email, and for the wider cost of empty slots, our guide to reducing appointment no-shows.
FAQ
Frequently asked questions
Fewer missed calls
Keep your bookings right whichever clock moves
Start free with a booking page set to your time zone, email confirmations and basic reminders. Add more event types and advanced reminders on the Individual plan. No card needed.