Vietnam sits three hours behind both Melbourne and Brisbane for half the year. When Victoria moves to daylight saving in October, Melbourne jumps to four hours ahead of Vietnam. Brisbane stays at three, because Queensland does not observe daylight saving. As a result, a Melbourne team's shared working window with a Vietnam team shrinks by about an hour and slides later into the afternoon. Every recurring meeting, release window or handover anchored to Melbourne time also moves for everyone else.
724SOFTWARE runs all of its delivery from offices in Hanoi and Ho Chi Minh City on Indochina Time (UTC+7) for clients in 10+ countries, including Australia. For our teams, the twice-yearly changeover is a scheduled operating event, and it affects more than which day a meeting falls on.
TL;DR
Vietnam (UTC+7) never changes its clocks. Brisbane (AEST, UTC+10) never changes. Melbourne switches between AEST and AEDT (UTC+11).
In the illustrative schedule below, a Melbourne team loses about one hour of overlap with Vietnam from October to April, and that hour comes out of the Melbourne morning.
Meetings set up by Melbourne organisers move by an hour for Vietnam and Brisbane attendees. Deployment windows, cron jobs and on-call handovers can drift too.
One block works all year: 08:00 to 13:00 Vietnam time always falls inside a normal Australian business day in both cities.
Treat overlap hours as time for collaboration. Treat incident coverage as a separate commitment.
About the Author: This guide comes from the delivery team at 724SOFTWARE, a Vietnam software team of 200+ professionals (58% senior-level). We run dedicated teams for Australian and international clients under a Follow-the-Sun model with a <10 minute incident response commitment.
What actually changes between AEDT vs AEST?
The whole overlap problem comes from one region changing its clocks while the other two stay put.
AEST (Australian Eastern Standard Time): UTC+10. Queensland uses it all year. Victoria, NSW, the ACT and Tasmania use it outside daylight saving.
AEDT (Australian Eastern Daylight Time): UTC+11. Used by the daylight-saving states in summer.
Queensland daylight saving: not observed. Brisbane stays on AEST all year.
Indochina Time (ICT): UTC+7. Vietnam does not observe daylight saving.
For Australia daylight saving 2026, the observing states follow the usual pattern. Daylight saving ends on the first Sunday in April (5 April 2026) and starts on the first Sunday in October (4 October 2026). Check state government sources each year before you lock in schedules.
Period | Melbourne | Brisbane | Melbourne ahead of Vietnam | Brisbane ahead of Vietnam
|
|---|---|---|---|---|
April to October | AEST | AEST | 3 hours | 3 hours |
October to April | AEDT | AEST | 4 hours | 3 hours |
How much overlap does a Melbourne team lose with a Vietnam team?
With the offsets set, the next step is to turn them into working hours. Converting AEST to Vietnam time is simple: subtract three hours. During AEDT, subtract four. The table below assumes an Australian 09:00 to 17:00 day and a Vietnam team working 08:00 to 17:00 ICT. These are illustrative hours, not a fixed schedule.
Brisbane (all year) | Melbourne (AEST) | Melbourne (AEDT)
| |
|---|---|---|---|
Vietnam 08:00 start, in local time | 11:00 | 11:00 | 12:00 |
Australian 09:00 stand-up, in Vietnam time | 06:00 | 06:00 | 05:00 |
Shared window (local time) | 11:00 to 17:00 | 11:00 to 17:00 | 12:00 to 17:00 |
Shared hours | 6 | 6 | 5 |
The lost hour does not come from the end of the Melbourne day. It comes from the start of the overlap. Picture two rulers laid side by side. The Vietnam and Brisbane rulers never move. Melbourne's ruler slides one notch to the right in October. Anything pinned to Melbourne's ruler slides with it. Anything pinned to Vietnam's ruler now lines up one hour later on Melbourne's.
Next, subtract lunch breaks on both sides. If the Vietnam team takes lunch at 12:00 ICT, that hour falls at 16:00 in Melbourne during AEDT. The real shared time can then be closer to four focused hours.
Why does the shift break more than meeting times?
Losing an hour is easy to see. The harder problem is everything that moves without anyone noticing. The common failure modes are:
Recurring invites. Calendar tools keep an event in the organiser's timezone. A 13:00 Melbourne retro moves from 10:00 to 09:00 in Vietnam and from 13:00 to 12:00 in Brisbane.
Change windows. A rule like "deploy after 18:00 Melbourne" moves from 15:00 to 14:00 in Vietnam, which pulls it an hour deeper into active development hours.
Scheduled jobs. A job set to 22:00 UTC produces an "08:00 report" in winter. During AEDT it arrives at 09:00 in Melbourne.
On-call handovers. Rotas written in local time can leave a one-hour gap, or a double-booked hour, on the Sunday of the change.
Reporting timestamps. Incident logs that mix local times make response-time reviews unreliable.
How should a business with both Melbourne and Brisbane staff plan around one offshore team?
Building on those failure modes, mixed Australian teams have an extra complication. From October to April, the Australian side runs on two clocks one hour apart, and the offshore team has to fit both.
Author's opinion: anchor shared ceremonies to Brisbane time or UTC, not Melbourne time. AEST and ICT never move, so the Vietnam team keeps a fixed schedule all year. Only the Melbourne staff see a one-hour shift, and they already expect one.
Then put critical ceremonies in the window that is safe all year:
08:00 to 13:00 Vietnam time = 11:00 to 16:00 Brisbane all year.
The same block = 11:00 to 16:00 Melbourne in winter and 12:00 to 17:00 Melbourne in summer.
Sprint planning, reviews and architecture discussions belong in this block. Async work such as code review, specs and QA notes can fill the rest.
What should you do before each changeover?
All of the above turns into a short routine to run about two weeks before the first Sunday in April and the first Sunday in October.
List every recurring event and note which timezone it is anchored to.
Move automation to UTC and write down the local equivalent for both periods.
Republish the overlap table in the team wiki with the new times.
Reconfirm deployment and change windows with the offshore delivery lead.
Check the on-call rota and escalation contacts for the changeover weekend.
Review the first week for missed stand-ups or late reports, then fix the anchor rather than the symptom.
One further distinction matters here. Overlap hours are for collaboration. They are not your incident coverage. 724SOFTWARE's Follow-the-Sun model keeps a <10 minute incident response commitment 24/7, so production support does not depend on whether Melbourne is in AEDT that month.
Frequently Asked Questions
Does Brisbane observe daylight saving time?
No. Queensland does not observe daylight saving, so Brisbane stays on AEST (UTC+10) all year.
What is AEST to Vietnam time?
Vietnam is three hours behind AEST. 09:00 in Brisbane is 06:00 in Ho Chi Minh City.
How far ahead of Vietnam is Melbourne during daylight saving?
Four hours during AEDT. During standard time it is three hours.
Does Vietnam change its clocks?
No. Vietnam stays on Indochina Time (UTC+7) all year.
When does Australia daylight saving 2026 start and end?
In the observing states it ended on 5 April 2026 and started on 4 October 2026. Confirm future dates with official state sources.
Is five hours of overlap enough for a dedicated offshore team?
In our experience it is, if ceremonies sit in the all-year block, handovers are written down, and incident coverage is handled separately from overlap.
About 724SOFTWARE
724SOFTWARE is an offshore IT company in Vietnam that builds web and mobile applications as dedicated teams, embedded staff augmentation and offshore development centres. All delivery comes from our own offices in Hanoi and Ho Chi Minh City. Australian clients get a Follow-the-Sun model with a <10 minute incident response commitment, and pre-vetted engineers can scale from 1 to 50+ in 2 to 4 weeks. We are a selected Anthropic partner and train engineers to use Claude Code in delivery work, and our processes are aligned with ISO 9001 and ISO 27001:2022 standards and GDPR compliant.
If your Melbourne or Brisbane team is planning an offshore team with genuine timezone overlap, talk to 724SOFTWARE about mapping your sprint calendar to both clocks: https://724software.com.vn/
