Lisbon and Seattle share no standard 9–5 working hours; the least disruptive option is 3:00 PM GMT+1 (7:00 AM PDT).
Plan a meeting →| Detail | Value |
|---|---|
| Time difference | 8h (Lisbon is ahead) |
| Lisbon 9–5 in Seattle time | 1:00 AM–9:00 AM PDT |
| Seattle 9–5 in Lisbon time | 5:00 PM–1:00 AM GMT+1 |
| Overlap window | None during standard 9–5 hours |
| Least disruptive slot | 3:00 PM GMT+1 = 7:00 AM PDT |
| DST transitions (this year) | Lisbon: March 29 / October 25; Seattle: March 8 / November 1 |
Lisbon and Seattle are 8h apart. When it's 9 AM in Seattle, it's already 5:00 PM in Lisbon — meaning Lisbon's working day is well underway before Seattle's morning has properly started.
There is no overlap during standard 9–17 business hours. Every synchronous meeting requires someone to work outside normal hours. The fairest approach is to rotate that burden: one week Lisbon takes the early call, the next week Seattle does. TimeSync's standup planner computes the exact rotation automatically.
Recurring calendar invites for Lisbon–Seattle meetings need a DST audit every year. If one city's clocks change before the other's, there's a window — sometimes three weeks, sometimes five — where the same calendar slot lands an hour earlier or later than intended. Always schedule with explicit timezone labels, not just clock times.
For truly zero-overlap pairs, the most important investment is async infrastructure: a written daily digest each team can read at the start of their day, a shared decision log so nothing critical gets blocked waiting for a live reply, and a clear escalation path for genuine emergencies. With those in place, most distributed teams find they need far fewer live calls than they assumed.
Lisbon is UTC+1 and Seattle is UTC-7, a difference of 8h. This gap may shift by 1 hour during DST transitions.
There is no overlap during standard 9–17 hours. Consider a rotating schedule or an early/late meeting. TimeSync's standup planner can find the least-painful slot.
Yes. Both cities observe daylight saving time, but on different schedules. Seattle springs forward on March 8 and Lisbon on March 29, so the gap between them shifts by 1 hour during the spring and fall mismatch window.
Lisbon and Seattle have no overlap during standard 9 AM–5 PM business hours.
Under standard 9–5 schedules, no. The 8h gap means the two cities' business days do not overlap. Teams that need synchronous collaboration typically shift one side's hours, rotate the inconvenient slot fairly, or rely on async-first workflows with structured handoffs.