Best Time to Schedule Calls Between Dubai and Los Angeles

Dubai sits at UTC+4 year-round; Los Angeles flips between UTC−8 in winter and UTC−7 in summer. That gives you a 12-hour gap during US standard time and 11 hours during daylight saving — almost as bad as time zones get. The two cities are nearly antipodal in the sense that one's morning is the other's late evening, and one's late evening is the other's bedtime.

The result: there is no single hour at which both cities are inside a normal working day. You can keep pretending one exists, or you can accept the constraint and design around it. This post is about the second option.

The four scheduling options, ranked by who pays the cost

Option A — Morning LA, midnight Dubai

08:00 PT / 19:00 GST is the closest you get to a "real" overlap, and even that puts Dubai at 7 PM — after dinner, after kids' bedtime in most households, and squarely outside what anyone would call work hours. It works for a one-off, but not as a recurring slot. Push it any earlier in LA and Dubai is in the middle of the evening; push it later in LA and Dubai is asleep.

Use this when the LA side is the decision-maker and the Dubai side is providing input rather than driving the meeting.

Option B — Evening Dubai, dawn LA

18:00 GST / 07:00 PT (during US summer) gives Dubai a reasonable end-of-workday slot and lands in LA at 7 AM. That's tough but not impossible — many West Coast execs are awake and triaging email by then. The Dubai side will be tired (it's after a full workday) but at least functional.

This is the inverse of Option A and the one to pick when the Middle East team is driving the agenda.

Option C — The split-sacrifice compromise

15:00 PT / 03:00 next-day GST is sometimes proposed as "fair" — both sides get a slot that's just barely workable. In practice it's terrible: 3 AM in Dubai isn't an acceptable meeting time for anyone, regardless of how "fair" the maths claims it is. Don't use this. The fairer-sounding compromise is rotating between Option A and Option B every other meeting, so each side bears the cost half the time.

Option D — Async-first with a 30-minute live cap

This is what most Dubai–LA teams settle into once they've tried the rest. The pattern looks like this:

Dubai team records a video update at 18:00 GST (end of their day), 5–10 minutes covering decisions, blockers, and questions.
LA team watches that video in their morning, 10:00 PT or so, and records a response video covering their answers, next steps, and any new questions.
Dubai watches the response the following morning and another loop begins.
Optional live touchpoint — a 30-minute live call once a week at 15:00 PT / 03:00 GST is bearable, or 09:00 PT / 21:00 GST works if Dubai's lead can take an evening call once weekly.

This loses you maybe one decision-cycle per week relative to a hypothetical "perfect" meeting time, but it doesn't burn anyone out and it scales. Most teams find they were over-meeting anyway and the async version is faster than they expected.

Practical scheduling rules

A few rules that tend to hold across Dubai–LA coordination:

Avoid Friday afternoon Dubai / Friday morning LA. Friday is the start of the weekend in the UAE (the work week runs Monday–Friday now, but Friday afternoons are widely treated as half-days). Schedule live touchpoints Sunday through Thursday on the Dubai side.
Ramadan changes everything for a month. Daytime work hours shrink, productive output shifts to late evening, and afternoon meetings get noticeably harder. If the Dubai side observes Ramadan, push your live touchpoints later — 21:00 GST works well after iftar — and accept that morning windows are off the table.
DST asymmetry catches teams every year. LA gains an hour in March and loses it in November; Dubai does not change. That means an "08:00 PT / 19:00 GST" slot becomes "08:00 PT / 20:00 GST" for half the year. Either book recurring meetings in one side's clock and let the other side absorb the drift, or rebook twice a year.

What to communicate in the invite

Whenever you send a Dubai–LA invite, write both times in the body of the meeting description, in this exact form: "Wednesday 09:00 PT (Los Angeles) / Wednesday 20:00 GST (Dubai)." Don't rely on the calendar tool to render the time correctly on both sides — Outlook, Google Calendar, and most CRM-integrated invitations all get this right on average but fail visibly often enough that a written confirmation saves you from at least one missed meeting per quarter.

For one-off cross-team meetings, attach an exact-time-now compare link so the recipient can see the live difference rather than doing the maths in their head.

The honest summary

A 12-hour gap doesn't have a good answer. It has a least-bad answer, which is async-first communication with a short, weekly live touchpoint that rotates the burden between morning-LA and evening-Dubai. Stop searching for the magic time slot — it doesn't exist — and design around the constraint instead.

Related:

Compare Time

General