The core problem
Most U.S. teams stretch across at least two zones. The wide cases — say, New York to Los Angeles — span three hours, which means a 9 a.m. start on the East Coast is a 6 a.m. start on the West Coast. Add Hawaii or Alaska and the gap grows to five or six hours. There is no neutral middle that's morning for everyone; somebody is always closer to the edge of their workday.
The right approach isn't to optimize for "fairness" in the abstract. It's to be deliberate: pick the smallest set of windows that cover your team, name them clearly, and stick to them so people can plan around them.
The overlap rule
Start by drawing the overlap. If your team works a typical 9-to-5 in their local time, the overlap window is the time when everyone is at their desk simultaneously. The width of that window is determined by the widest gap in your team.
- Eastern + Central: 7 hours of overlap (9 a.m.–5 p.m. ET = 8 a.m.–4 p.m. CT). Plenty of room.
- Eastern + Pacific: 5 hours of overlap (noon–5 p.m. ET = 9 a.m.–2 p.m. PT). Mid-day for everyone.
- Eastern + Hawaii: 2 hours of overlap (3 p.m.–5 p.m. ET = 9 a.m.–11 a.m. HST). Very narrow.
- Eastern + Alaska: 4 hours of overlap (1 p.m.–5 p.m. ET = 9 a.m.–1 p.m. AKDT in summer; 8 a.m.–noon AKST in winter).
The overlap window is where group meetings belong. Push outside it only when there is a specific reason — and make the cost explicit.
The two-window pattern
For teams that span more than 4 hours, a single shared window is too narrow to fit everything. Two windows work better:
- Window A: early in the East Coast day. Good for planning conversations that East Coast people drive and West Coast people listen in on.
- Window B: late in the East Coast day, mid-day for the West Coast. Good for collaborative work and decisions where West Coast input is load-bearing.
Naming the windows internally — "morning sync" and "afternoon block" — gives the team a vocabulary so the calendar isn't a constant negotiation.
The decision rules
Rule 1: Anchor to the local 9-to-5, not to any one time zone
The most common scheduling mistake is anchoring everything to the loudest time zone (often Eastern, because more of the country is on it). That works fine for the East Coast and slowly degrades the further west you go. After six months of "9 a.m. ET" all-hands, your Pacific colleagues have done dozens of 6 a.m. starts. Anchor to the 9-to-5 instead: the meeting is at "10 a.m. ET / 7 a.m. PT" and it shifts seasonally only if you decide it should.
Rule 2: Reserve the overlap window for synchronous work
Anything that needs back-and-forth — design reviews, planning, anything where a debate could break out — goes in the overlap window. Anything that doesn't (status updates, FYIs, recordings) goes outside it.
Rule 3: Rotate the burden when the overlap is too narrow
For teams with Hawaii or international participants where the overlap is under 2 hours, fairness comes from rotation, not from finding a perfect time. Alternate which side starts early.
Rule 4: Lead with the participant's own zone
When you send a calendar invite, write the time in the recipient's zone first. "10 a.m. PT (1 p.m. ET)" is friendlier to a Los Angeles colleague than the reverse. Modern calendar tools handle this automatically, but plain-text confirmation messages don't.
Rule 5: Always include the date alongside the time
"Tuesday at 4 p.m. ET" is ambiguous near a daylight saving transition. "Tuesday, March 11 at 4 p.m. ET (which will be EDT)" or, even better, "Tuesday, March 11 at 4 p.m. ET / 1 p.m. PT" leaves no room for confusion.
The DST transition trap
Twice a year, U.S. zones change their offsets. The transitions happen on the same date but at local 2 a.m., not simultaneously. For a roughly two-week window in March and another in November, calendar software and humans both stumble.
- Spring forward (second Sunday of March). Eastern Time loses an hour first, then Central, Mountain, Pacific. For one hour, the country is briefly on a different offset pattern. Recurring meetings that "always run at 10 a.m. ET" stay correct in calendar systems that store the IANA zone, but break in systems that hard-code an offset.
- Fall back (first Sunday of November). Same mechanic in reverse. The 1 a.m. hour repeats. Avoid scheduling anything in that window.
For the full picture of how DST works in each zone, see the daylight saving time guide.
Worked example: a team in NY, Chicago, Phoenix, and San Francisco
Phoenix is the wrinkle. From November to March, Arizona is on Mountain Standard Time, two hours behind New York. From March to November, when the rest of the country springs forward, Phoenix doesn't — so it's effectively on Pacific Time for half the year. Same office, same wall clock, two different offsets to New York.
For this team:
- Winter overlap: 11 a.m.–5 p.m. ET = 9 a.m.–3 p.m. MST (Phoenix) = 9 a.m.–3 p.m. PST (San Francisco).
- Summer overlap: noon–5 p.m. EDT = 9 a.m.–2 p.m. MST (Phoenix) = 9 a.m.–2 p.m. PDT (San Francisco).
The fixed all-hands lives at 1 p.m. ET year-round. In winter that's 11 a.m. for Phoenix and San Francisco; in summer it's 10 a.m. for Phoenix and San Francisco. Both are inside the morning block for the western participants and after lunch for the eastern ones. No one ever has to start before 9 a.m. local.
Common scheduling mistakes
- Treating ET as the default and adding "PT for our West Coast colleagues" as an afterthought. If half the team is on the West Coast, lead with both equally.
- Forgetting Arizona doesn't observe DST. A Phoenix colleague's offset to you changes twice a year even though their clock doesn't.
- Booking the same recurring slot through DST transitions without checking. The week of the transition often produces a 6 a.m. or 6 p.m. participant who didn't sign up for that.
- Putting Hawaii in a 5 p.m. ET meeting. That's noon HST — fine. Putting Hawaii in a 10 a.m. ET meeting is 5 a.m. HST. Don't.
- Skipping the date. "Tuesday at 4" with no zone and no date is a guaranteed missed meeting.
Tools to lean on
For a single ad-hoc conversion, the converter on the homepage handles every U.S. zone. For checking what time it is now in each zone, the live clocks are always current. For looking up which zone a state actually uses (and which states are split), see the state-by-state reference. For the underlying mechanics of UTC offsets, see UTC and U.S. time.
The one-line takeaway
Pick the meeting time once, by overlap, and write it with both the local time and the date — every time. Most scheduling errors trace back to skipping one of those three.