Scheduling Between London And Atlanta Looks Simple Until It Isn’t
London runs on Greenwich Mean Time in winter and British Summer Time in summer. Atlanta runs Eastern Standard Time in winter and Eastern Daylight Time in summer. That gives you what looks like a clean five hour gap most of the year. It is not clean. Not even close. Here is what actually happens. The UK switches to BST on the last Sunday in March and goes back to GMT on the last Sunday in October. The US switches to CDT on the second Sunday in March and back to EST on the first Sunday in November. Those dates do not line up. Sometimes they are a week apart. Sometimes two weeks. During those mismatch windows the difference between the two cities shrinks to four hours instead of five, then snaps back. If you schedule recurring calls without accounting for this you will show up an hour early or late every single time until someone notices. I learned this the hard way in 2023. I set up a weekly standup at 2 PM London time for my Atlanta based contractors. For seven weeks it ran fine at 9 AM their time. Then the UK switched to BST a week before the US did. Suddenly the call was at 8 AM Eastern instead of 9. Two of my contractors missed it for three weeks straight because their calendar app had already cached the old offset and refused to nudge the event automatically. The fix was brutal and simple: I deleted the recurring event entirely, recreated it using UTC timestamps instead of local time, and forced everyone to resubscribe to the calendar invite rather than accepting it into their existing local-time-based calendars. After that the drift stopped.
The core mechanics here are straightforward. London is UTC+0 or UTC+1. Atlanta is UTC-5 or UTC-4. When both are on standard time the gap is five hours. When both are on daylight time the gap is also five hours. The problem exists only in the overlap periods where one city has shifted and the other has not. That overlap lasts roughly ten to thirteen weeks per year split across spring and fall. During those windows the difference is four hours. There is a second nuance most people miss. The UK does not call its offset "BST" in API land. Systems like Java, JavaScript, and Python reference it as Europe/London. Atlanta is America/New_York. If you are building any kind of scheduling tool and you store times as naive local strings without timezone context, you are already broken. You need to store everything in UTC and convert at display time. I have seen teams waste three sprints debugging why a booking engine showed the wrong time on certain Tuesdays in April. The root cause was always the same: a hardcoded +5 offset that silently failed during the DST transition weeks. If you just need to know what time to call someone right now, check whether either location is currently observing daylight saving. Right now most years that means London is either one hour ahead of UTC or zero, and Atlanta is either four or five hours behind UTC. Do a quick mental math check: current London hour minus current Atlanta hour should equal either four or five. If it equals six or four incorrectly, one of your systems is reading stale offsets.
Let me be blunt about what this approach cannot do. Knowing the time difference does not solve crossAtlantic meeting fatigue. A 3 PM London slot that works for your team is a 10 AM Atlanta slot. Flip it and Atlanta gets 8 AM while London gets 1 PM. There is no perfect middle ground unless you accept a 12:30 London / 7:30 Atlanta window that still punishes one side. The honest answer is rotating the inconvenience quarterly or accepting async communication for nonurgent threads. For flights the math changes again because airport codes do not carry timezone data. LHR to ATL is a roughly eight hour flight, but your watch will show a five hour time change. Landing in Atlanta at 4 PM local after taking off from London at 11 AM local feels like you arrived in the past if you do not adjust immediately. Jet lag hits harder on eastbound trips, but the direction of the time shift matters less than the number of zones crossed and whether you are sleeping through the overnight segment. I always book red-eyes on this route and keep my watch on destination time from boarding. It cuts adaptation time by roughly a day compared to keeping home time visible. Some tools make this easier. WorldClock, TimeAndDate.com, and the built-in clock apps on iOS and Android handle the DST transitions automatically if you add both cities. Calendar platforms like Google Calendar and Outlook convert invites correctly when the organizer uses timezone-aware scheduling. The moment you export to CSV or share a plain text timestamp without the Z suffix or an explicit offset, you are on your own. I keep a personal reference table mapped to the exact 2024 and 2025 transition dates because trusting automated tools during the two week mismatch windows has burned me enough times that I verify manually before sending anything external.
Get the Full Details
London to Atlanta time difference, five hours normally, four hours during the DST gap. That is the entire thing reduced to its skeleton. Everything else is just avoiding the edge cases where a simple number stops being simple.
