Watch the video
Player by YouTube. Open original video ↗
A regular evening call can become an hour late without anyone changing their routine. When daylight saving begins in Sydney, a family member in Nepal still sees the same local clock. The Australian caller has moved relative to them. A message saying only “same time on Sunday” leaves both people to decide which clock is meant.
For families living between Nepal and Australia, the useful habit is to save the date, Australian city and Nepal time together. This also helps when a student moves interstate, a parent travels or relatives join from several places. The suggestions below are an original planning checklist, rather than a report of a particular family's experience.
Australia does not have one clock
NSW Government's daylight-saving guidance says NSW moved clocks forward on 4 October 2026 and will move them back on 4 April 2027. Queensland, Western Australia and the Northern Territory do not observe daylight saving. Other jurisdictions and special locations need their own local check.
Nepal Tourism Board describes Nepal's time as GMT plus five hours and 45 minutes. That quarter-hour component is easy to lose when somebody rounds a conversion in their head. Keep the minutes when recording a call, appointment or travel connection.
For 21 October 2026, 8 pm in Sydney corresponds to 2.45 pm in Kathmandu. On the same date, 8 pm in Brisbane corresponds to 3.45 pm in Kathmandu. These are date-specific conversions calculated from the cities' offsets, not a permanent rule that applies everywhere in Australia. They show why writing the city is more useful than writing “Australian time”.
Choose whose routine the call follows
A recurring call needs one agreed starting point. A family might prefer 7 pm in Kathmandu because that fits the household's evening. Another might protect a student's Australian lunch break. Either can work, but they produce different local times when a participating city changes its clock.
Ask whose routine should stay fixed before creating the recurring event. Write that decision in the invitation description. If Kathmandu evening is the anchor, check that the event was created in Kathmandu's time zone rather than entering a converted Sydney time and assuming it will stay equivalent throughout the year.
Leave enough room for everyday interruptions. Agreeing on a short arrival window can be more practical than treating a social call like an interview. A time-zone correction should make a routine easier, rather than create another obligation when study or work becomes busy.
Use city-based calendar settings

Google Calendar's instructions explain how to select an event's time zone and display additional zones. Invited people normally see the event in their own local zone. Other calendar products have their own settings, so check the product in use instead of assuming every invitation behaves identically.
Create one trial event before relying on a long series. Ask each person to read back the date and time shown on their device. Then inspect an occurrence after the next Australian clock change. A correct first occurrence does not, on its own, establish that the recurring event follows the routine you intended.
When changing a series, look carefully at whether the calendar is editing one occurrence or future occurrences. If someone has copied the time into a paper diary, send a plain-language update as well. A silent calendar edit will not update that separate note.
Make the message readable without a calendar
A useful invitation might say: “Sunday 25 October, 8 pm Sydney, 2.45 pm Kathmandu. Please check the calendar invitation on your device.” This is a worked example for that date. Replace every part when organising a different call, especially if the Australian participant is in another city.
Write the full month when the message crosses borders. A short numeric date can be misread when people use different date conventions. For an appointment near midnight, show both local dates. A correct hour beside the wrong day is still a missed appointment.
Avoid filling a family group with identity documents or detailed itineraries just to arrange a call. A city and agreed time usually provide the necessary context. Share private appointment information only with the people who need it, using a suitable private channel.
Recheck travel and important appointments separately
A family-call template should not become the authority for a flight, medical appointment or examination. Read the organiser's actual confirmation, including its city, time zone and date. Where the confirmation is unclear, ask the organiser directly instead of relying on a converted time forwarded by somebody else.
After travel, check the device's displayed zone and the event itself. Automatic location settings are useful, but the important evidence is what the appointment now shows. Keep a separate reminder to review recurring family calls when an Australian clock change approaches.
A small shared note is enough to maintain the arrangement: the anchor city, usual local time, next call date and who will send changes. That gives a new participant something definite to check without turning a family routine into a spreadsheet.
If a relative does not use a calendar app, agree on one person to send a dated reminder in the familiar messaging channel. Ask for an acknowledgement when a time changes. For a missed social call, agree on a simple follow-up message rather than assuming silence means a time-zone problem or an emergency.
Related video: Tej. Independent interface demonstration, not government time-zone advice. Verify current settings against Google's linked help page.
This article was prepared with AI assistance.
Image credits
- Laptop, notebook and pen on a desk beside a chair.: Illustrative photograph, not a reported event or endorsement. Photo: nicoll camacho / Unsplash. https://unsplash.com/photos/laptop-notebook-and-pen-on-a-desk--Z8cI1gs4zk (Unsplash License: https://unsplash.com/license).




