Salt Lake City ↔ San Diego

Salt Lake City sits 1 hour ahead of San Diego. The overlap window runs from 10:00 to 17:00 Salt Lake City time — a 7-hour bridge that keeps both cities in the same daily rhythm with no meaningful phase-shift. A 6.4/10 call score reflects a workable window, but the lunch-conflict modifier means the midpoint of the shared band overlaps the nominal lunch period for both cities. The dominant scheduling constraint is not the offset — it is the compressed midday zone that forces one team into an off-peak meal window whenever a meeting falls in the center of the band.

The 10:00–17:00 Salt Lake City window translates to 09:00–16:00 San Diego. Salt Lake City teams start and finish slightly earlier in absolute terms; San Diego teams carry a slightly later afternoon close. The 1-hour gap is small enough that both teams operate in the same part of their workday — the offset is not the constraint here. The lunch-conflict modifier is the binding factor: whichever team hosts a meeting near the middle of the shared band is eating outside their preferred midday window. The etiquette-sensitive modifier means local norms around lunch timing can erode the nominal overlap faster than the raw numbers suggest.

> Anchor block: 10:00–12:00 Salt Lake City / 09:00–11:00 San Diego — captures morning focus before the midday compression and before either team hits their post-lunch cognitive trough. > Afternoon option: 14:00–16:00 Salt Lake City / 13:00–15:00 San Diego — usable for follow-up and review items, but confirm San Diego team has not already contracted their window due to etiquette norms around end-of-day. > Protect the 10:00–12:00 Salt Lake City slot as the recurring anchor. The 1-hour offset means no team stretches their day meaningfully; the scheduling cost is entirely about which side accommodates a non-standard lunch.