A meeting between Sydney and Los Angeles is not a slightly worse New York–London. It is a date-line problem. When it is Monday afternoon in California, it is already Tuesday morning in New South Wales. Your “end of day Friday ping” can land on their Saturday. The Sydney verdict will say NOT NOW while you are still in a product review with sandwiches.
Melbourne uses the same DST rules as Sydney. San Francisco uses the same Pacific clock as Los Angeles. The pair you actually need is on Sydney–San Francisco (and the Los Angeles equivalent). Use it; do not trust a spreadsheet from 2024.
The two humane shapes
There is no lunch overlap that is kind to both sides. You pick:
1. California evening / Sydney next morning. Example in southern summer: 16:00–18:00 Pacific is 11:00–13:00 AEDT the next calendar day. Sydney is in a real work block; California is ending the day. 2. Sydney late afternoon / California early morning. 16:00–17:00 AEDT is 23:00–00:00 Pacific the previous calendar day — usually too late. Shift Sydney to 08:00–09:00 and you are asking California to meet at 14:00–15:00 *yesterday*, which is their afternoon... wait, the date line makes this the slot people mis-draw on whiteboards. Draw it on a pair heatmap instead.
The version that usually hurts less for US-based companies with an Australian office: US evening, AU morning. Australians already greet the date first. Asking them to stay until 19:00 so California can “jump on after school pickup” is how you lose them.
Rotate monthly if the team is evenly split. Publish the rotation. Do not renegotiate it in Slack at 21:00.
2026 clock changes that break the habit
- US spring-forward: 8 March 2026. California jumps; Sydney does not (they are still in DST until April). Offset changes by an hour. - Australia DST ends: 5 April 2026. Sydney falls back; California stays on PDT until November. Offset changes again. - Australia DST starts: 4 October 2026. - US fall-back: 1 November 2026.
Four weekends. Four chances for a recurring 07:00 “global standup” to become a 06:00 punishment. Rebuild the invite on each of those Mondays.
Brisbane sitting out DST means a three-city call with Sydney and California has a *third* offset in January. If your “ANZ team” includes Queensland, you do not have one Australian time. You have two.
What not to send on Friday
Friday 16:00 Pacific is Saturday 11:00 or 10:00 in Sydney depending on the season. That is their weekend, not a “quick ask before I log off.” Schedule send to Monday 09:00 AEDT. The same rule in reverse: Friday 16:00 in Sydney is Thursday 23:00 or 22:00 in California — also not a gift.
Public holidays diverge too. Australia Day, ANZAC Day, the Queen’s/King’s Birthday (state-dependent), and Victorian/NSW extra days will empty Melbourne while California is in a normal Tuesday. Check the holiday table before you interpret silence.
Booking copy you can paste
Title: `SYD 09:30 AEDT Wed / LA 15:30 PDT Tue`. Description: both IANA names, `Australia/Sydney` and `America/Los_Angeles`, plus a link to the pair planner. Cap at 25 minutes. No “let’s just keep going.” Record it for whoever the date line excused.
If you only take one number from this page: their 09:00–11:00. For California that is an afternoon or early evening send, dated tomorrow in Australia. Check Sydney first. Then send once.
A worked week in February 2026
Monday: California writes a brief at 16:00 Pacific. It lands Tuesday 11:00 AEDT. Sydney comments by 16:00 their time, which is 21:00 Monday in Los Angeles — too late to thread-ping. They schedule send to 09:00 Pacific Tuesday, which is 04:00 Wednesday in Sydney. That is the awkward part of the date line: even "reply in the morning" has two mornings. Agree which morning in the doc.
Wednesday: a 25-minute overlap at Sydney 09:30 AEDT / LA 14:30 PST (check the actual 2026 offset that week). Decision only. Thursday is written. Friday California does not dump work at 16:00 Pacific. That is Saturday in New South Wales.
If Perth joins, they are on UTC+8 with no DST — closer to Singapore than to Sydney. A three-city "Australia" call with Perth, Sydney, and Los Angeles is three offsets. Split Perth into the Singapore-shaped sliver or give them the recording.
The date line is not an inconvenience. It is the product. Name both dates in the title (`Tue LA / Wed SYD`) so nobody joins on the wrong civil day.
Field notes from the city desk
In Sydney, start from the CBD / Barangaroo. AEDT in summer, AEST in winter. US calls eat breakfast or dinner — never lunch. After 18:00 a ping is tomorrow. The local prior remains 09:00–17:00 (Australia/Sydney). If this article's advice conflicts with that desk, the desk wins — ask once and write it down.
Melbourne (Australia/Melbourne) does not owe you HQ hours. Same DST rules as Sydney. A 09:00 stand-up is civilized; a 07:00 California-overlap is a favor. Ping inside 09:00–17:00 around the Docklands / Collins Street offices, or schedule send. Presence dots after 17:00 are scenery.
In Los Angeles, start from Culver City. Traffic, not manners, sets the real end of day: a 17:30 ping often lands in a parked car on the 405. The local prior remains 09:00–18:00 (America/Los_Angeles). If this article's advice conflicts with that desk, the desk wins — ask once and write it down.
Treat San Francisco as a place, not a resource pool. SoMa keeps 09:00–18:00 as the honest window. Async is a religion until someone in London needs a decision; then the 08:00 Pacific standup appears. A calendar title that omits America/Los_Angeles is how this city gets pinged in the dark.
None of these notes replace the live verdict. Open the city page at send time. Clocks and holidays move; this paragraph does not.