The Simple Math Behind London and New York Scheduling
London is UTC+0. New York is UTC-5. That gives you a five-hour difference when both cities are on standard time. When daylight saving shifts hit, the gap changes temporarily because the UK and US don't always switch on the same weekend. This matters more than people realize. I learned that the hard way during a client rollout in March 2022 when the clocks shifted one week apart and every scheduled standup for three days landed in the wrong time slot. Nobody noticed until the New York team showed up at 2 PM their time to find the Londoners already wrapped for the weekend. Most teams think the solution is just to schedule overlapping hours. That works until it doesn't. Here is what actually happens when you try to coordinate daily across this gap. London business hours run roughly 9 AM to 5 PM GMT. New York runs 9 AM to 5 PM ET. Overlap is 1 PM to 5 PM London time, which is 8 AM to 12 PM New York time. That is a four-hour window. Four hours for two offices worth of people to align, make decisions, and move work forward. It is tighter than it sounds. I used to run a project where my London team and New York contractors had to ship features together. We tried rotating the overlap window every week so one group wasn't always sacrificing mornings or afternoons. It sounded fair. It was exhausting. By week three, people were showing up to meetings half-asleep or half-checked out. We switched to a fixed overlap of 9 AM to 11 AM ET, which is 2 PM to 4 PM London time, and communicated everything else async. Output went up. Complaints dropped. Nobody became a morning person against their will.
How Async Changes Everything
The five-hour gap is not a problem to solve. It is a structure to work with. Most people approaching global coordination treat it as a scheduling puzzle. The smarter move is to treat it as a workflow design problem. London finishes its day. New York picks it up. New York finishes. London starts fresh the next morning. That is a twenty-four-hour cycle with real handoff points. It only works if your documentation is actually usable by someone reading it twelve hours later. I keep seeing teams build shared Slack channels and expect real-time responses to flow naturally. They do not. A message sent at 6 PM London time hits the New York team at 1 PM their time. If the context is missing, that message sits there until someone reads it, figures out what is going on, and responds. That is four to six hours of dead time depending on how thorough the original message was. I started requiring a one-line summary at the top of every handoff message. Not a greeting. Not a status update. Just what needs to happen next and why. Response time dropped from an average of six hours to under two.
The Overlap Meeting Strategy
You still need live syncs. Scheduling them efficiently matters. The overlap window is small, so every minute inside it should count. I avoid putting more than two live meetings per day in the shared window. Anything more and people start treating the time as background noise rather than focused collaboration. Two meetings, thirty minutes each, with a clear agenda sent twelve hours before. That is the ceiling I stick to. One meeting goes to decision-making. The other goes to blockers. Everything else stays async. This cuts meeting load by roughly seventy percent compared to teams that schedule daily all-hands across both offices. The teams that keep trying to replicate the old in-office rhythm end up burning out faster and producing less. The five-hour gap punishes bad coordination habits quickly.
Get the Full Details
Tools That Actually Help
World time buddy or everytimezone work fine for checking current offsets. Calendar tools like Google Calendar and Outlook both handle timezone conversion automatically if you set your primary timezone correctly and invite people with their local timezones selected. The default setting in most calendar apps is to display event times in your own timezone only. Change that. Inviting someone in New York to a 3 PM London meeting without showing both timezones means they might show up at the wrong hour. I have seen this happen repeatedly. For async communication, Loom and Notion save more time than any scheduling tool ever will. Record a two-minute screen walkthrough instead of calling a meeting. Document decisions in a shared space with timestamps so the other office knows exactly what changed while they were asleep. I replaced roughly eight hours of weekly sync meetings with recorded updates and threaded comments. The quality of discussion actually improved because people had time to think before responding instead of reacting in real time.
Where This Breaks Down
The five-hour gap model does not work for everything. Live customer support across both cities during peak hours requires staggered shifts that eat into personal time. Real-time collaborative coding sessions suffer unless you use tools like GitHub Codespaces or GitPod that decouple the environment from the individual machine. High-frequency trading desks treat this gap as a critical information window and build entire infrastructures around it, which is why that industry invests so heavily in fiber routes between London and New Jersey. If your work depends on instant back-and-forth negotiation or creative brainstorming, this gap is a genuine disadvantage. No amount of async documentation replaces the speed of two people in the same room hashing something out. In those cases, consider flying people in quarterly for a two-day working session and keeping the rest of the time async. One trip per quarter costs less than the cumulative meeting load of trying to stay constantly aligned across the gap.
The Daylight Saving Trap
This deserves its own section because it trips up everyone at least once. Both the UK and the US observe daylight saving time. The UK switches on the last Sunday in March. The US switches on the second Sunday in March. For roughly one to two weeks each spring and autumn, the gap is four hours instead of five. Schedules built around the five-hour offset throw off by an hour during these windows. Calendars do not auto-adjust for temporary offset changes in most enterprise tools. I send a calendar reminder to the whole team every March and October reminding everyone to verify meeting times for that two-week window. It takes thirty seconds per person and prevents the kind of confusion that makes teams lose trust in the scheduling system. People stop showing up late or early once they learn the pattern. After that, it becomes second nature.
What I Would Do Differently
When I first started managing cross-Atlantic teams, I over-indexed on availability. I wanted everyone reachable at all hours. That approach burned people out and created false expectations about response times. The second time around, I enforced strict boundaries. London team does not message after 7 PM London time. New York team does not message after 9 PM ET. Overlap window is sacred. Async is the default. Meetings are rare and purposeful. Output improved within two months. Not because people worked harder. Because they stopped wasting energy on coordination overhead. The five-hour gap is not an obstacle to global work. It is the foundation of it. Teams that fight it lose. Teams that design around it win.
