Quick answer
7 AM PST is 3 PM GMT in London (winter). In summer, 7 AM PDT is 3 PM BST. The 8-hour gap between Pacific and UK time holds year-round because both zones observe daylight saving together and shift their clocks by the same amount each spring.
The 7 AM Pacific sweet spot for London
7 AM PST landing at 3 PM London is a well-regarded configuration on the Pacific–to–London route. London receives the call at mid-afternoon — past the post-lunch dip and before the mental shift toward end-of-day tasks. The UK team has two full hours (3–5 PM) after the call to act on outcomes before the working day closes. From the Pacific side, 7 AM is a real-morning sacrifice rather than the very early pre-dawn push of 6 AM, but it is sustainable for a recurring weekly meeting in a way that 6 AM rarely is.
Compare this to the next slot: 8 AM PST reaches London at 4 PM, giving London only one hour of follow-up time. For decisions requiring the UK team to execute something complex the same day, 7 AM Pacific is meaningfully better: two hours of follow-up versus one hour is the difference between completing a task and beginning it.
Who uses this slot
Engineering leads and DevOps teams with a Pacific-heavy core and a significant London cluster often use 7 AM Pacific as the engineering standup. The ratio that makes this work: when a team has two or three Pacific engineers and eight or more London engineers, it is reasonable to ask the Pacific leads to start slightly earlier in exchange for a London-comfortable 3 PM call. The London majority drives the scheduling logic.
Sales and account management teams with account executives in San Francisco or Los Angeles and clients or colleagues in London use 7 AM Pacific for pipeline reviews and client update calls. Starting earlier gives the Pacific team the entire rest of their morning free for follow-up actions and client calls in their own timezone.
Product and design teams doing cross-Atlantic collaboration use 7 AM Pacific for creative reviews and sprint planning. The 3 PM London arrival time means UK designers and product managers join the call fresh from their afternoon energy, not fatigued from a long day. Two hours for async follow-up before London close is enough for most review-and-comment cycles.
Scheduling advantages
- London receives the call at 3 PM — mid-afternoon, one of the more productive slots for most UK workers
- Two full hours (3–5 PM) for London to act on outcomes before end of day
- 7 AM Pacific is sustainable as a recurring weekly meeting in a way that 6 AM is not for most teams
- When the team is London-majority, asking Pacific leads to join at 7 AM is a reasonable trade-off
Scheduling drawbacks
- 7 AM Pacific still requires an early start before a full morning routine is complete
- Participants dialling in from Southern California (Pacific time, warmer mornings) find 7 AM more tolerable; Seattle or Vancouver in winter (Pacific time, dark at 7 AM) is harder to sustain
- Only suitable for tasks where 30–60 minute calls suffice — longer sessions push into London's final working hour
- Does not work when the Pacific team includes participants regularly in meetings from 7:30 AM onward — back-to-back conflict risk is high
Daylight saving time
The 8-hour gap is stable for most of the year. PST becomes PDT in mid-March; GMT becomes BST in late March. Both shift forward, keeping the gap. The brief exception: for roughly two weeks in late March after the US has moved to PDT but before the UK has moved to BST, 7 AM PDT = 2 PM GMT instead of 3 PM. In late October, a mirror window briefly makes it 4 PM. Check the specific date for calls in those transition periods. Set calendar events to America/Los_Angeles timezone so the software manages DST transitions automatically year-round.
Practical guidance
Write invites with both city times: "7:00 AM San Francisco / 3:00 PM London." Keep the call to 60 minutes or under so London retains at least one hour for follow-up. If the London team consistently needs more than 60 minutes to complete the meeting, consider splitting into two shorter sessions or shifting to 8 AM Pacific where the time pressure is shifted explicitly rather than discovered mid-meeting.
What is 7 AM PST in London?
7 AM PST is 3 PM GMT in London during winter. In summer, 7 AM PDT is 3 PM BST. The 8-hour gap is stable year-round for most of the calendar, with brief exceptions during the clock-change transition windows in late March and late October.
Is 7 AM Pacific better than 8 AM Pacific for London meetings?
For London, yes: 7 AM Pacific gives London two hours of same-day follow-up time (3–5 PM) versus one hour at 8 AM Pacific. For the Pacific side, 7 AM requires a slightly earlier start. Whether the tradeoff is worth it depends on how much same-day London follow-through the meeting decisions require. If the outcomes are mostly async, 8 AM Pacific is simpler to sustain.
When should a Pacific team hold a recurring 7 AM PST meeting?
When the team is London-majority (more participants in UK than Pacific) and meeting outcomes routinely require same-day London action. In that configuration, asking Pacific leads to start at 7 AM is a reasonable trade-off for the majority-London team. If the team is Pacific-majority, 8 AM Pacific with 4 PM London is typically more sustainable long-term.
How does DST affect 7 AM PST in London?
For most of the year, the result stays at 3 PM London. The exception is two brief windows: late March (US on PDT, UK still on GMT: 7 AM PDT = 2 PM GMT) and late October (UK on GMT, US still on PDT: 7 AM PDT = 4 PM GMT). Both windows last about one to two weeks. Set calendar timezone to America/Los_Angeles to handle this automatically.