Best Time to Schedule Calls Between Singapore and London

Singapore sits eight hours ahead of London during UK winter (SGT vs GMT) and seven hours ahead during UK summer (SGT vs BST). Singapore itself does not observe daylight saving — it stayed on UTC+8 even when its colonial-era clock briefly drifted to UTC+7:30 in the 1980s — so the entire DST burden lands on the London side. The practical consequence is that twice a year, your standing 2 PM London call abruptly becomes an hour worse or better for the Singapore team, and you'd better notice.

What follows is a brief and honest map of which slots actually work, which look workable but fail in practice, and what to do when the workday doesn't span both cities cleanly.

The only sane real-time window

There is exactly one time of day where Singapore and London are both inside something that could be called a workday: roughly 13:00 to 17:00 London / 21:00 to midnight Singapore. Outside that window, one side is unambiguously off-hours.

The strongest single slot inside that window is 14:00–15:00 GMT / 22:00–23:00 SGT. London is mid-afternoon — fully warmed up, still energetic, with two or three hours of useful workday left for follow-up. Singapore is post-dinner — late by Western standards but well within the cultural norm for working-late professionals in the city. It's the slot most Singapore–London teams settle on for recurring weekly meetings, and the one most well-run consultancies, banks, and tech firms use for trans-shore syncs.

A tighter alternative is 13:00–14:00 GMT / 21:00–22:00 SGT. London gets immediate post-lunch — slightly worse for energy, slightly better for productivity (more workday remaining). Singapore gets an hour earlier evening, which is materially easier on family life. If your Singapore team has caregiving responsibilities, this is the more humane choice.

Slots that look workable but aren't

A common mistake is proposing 08:00 GMT / 16:00 SGT as a "morning London, afternoon Singapore" overlap. On paper it works. In practice it's a trap. London at 8 AM is sluggish — people are still triaging email — and Singapore at 4 PM is winding down for the day, with the post-school-run cognitive drop most office workers feel after a full day. Engagement on both sides is noticeably weaker than the late-afternoon-London / late-evening-Singapore window.

Another tempting-but-bad slot is 17:00 GMT / 01:00 SGT for "London end-of-day with Singapore overnight." It's bad. 1 AM is not a meeting time, regardless of what anyone says they're willing to do, and once-weekly midnight calls compound into burnout faster than people realise. If you find yourself proposing this slot, the meeting probably shouldn't be live.

The async layer that makes everything else workable

Singapore–London teams that work well rarely rely on a single weekly call. The teams that produce real cross-shore output run an async loop underneath the live meeting:

The Singapore team writes a short end-of-day update (15–20 minutes' work) and posts it to a shared channel before they leave for the evening. London opens to it the next morning.
London responds with questions, decisions, and unblock-the-next-step direction during their morning. Singapore picks it up at the start of the next day.
The live meeting — usually at the 14:00 GMT slot — handles only the items that genuinely need real-time back-and-forth. Most weeks that's 20 minutes of content, not an hour.

Without this layer, an 8-hour gap eats half the working week in transit. With it, the gap shrinks to one decision cycle per day, which is roughly what a co-located team produces anyway.

How DST changes the recurring slot

When London springs forward in late March, the gap shrinks to 7 hours and a 14:00 BST meeting becomes 21:00 SGT — actually an improvement for Singapore. When London falls back in late October, the gap grows back to 8 hours and 22:00 SGT returns.

If your meeting is set in London time, Singapore will silently absorb the shift. If it's set in Singapore time, London will. Most teams pick whichever side the meeting owner is on, but the better practice for fairness is to alternate ownership every six months so the DST shift is shared.

Singapore-specific things that catch outsiders off guard

A few cultural points worth knowing if you've not worked with a Singapore team before:

Chinese New Year moves every year (typically late January or February) and effectively wipes out a full week of productive work. Plan around it.
Hari Raya Puasa, Vesak Day, Deepavali, and Hari Raya Haji are all public holidays in Singapore that don't exist in the UK. Check the Singapore holidays calendar before booking anything important.
Late-evening meetings are culturally normal in Singapore in a way they're not in much of the UK. You're not asking for an unreasonable favour by proposing 22:00 SGT — but you are asking for a sustained one, so build in some give-back.

What to put in the invite

Always write both times explicitly: "Tuesday 14:00 GMT (London) / Tuesday 22:00 SGT (Singapore)." Calendar tools generally render correctly, but the one in twenty cases where they don't are exactly the calls you can't afford to miss. For ad-hoc cross-shore meetings — especially with new external counterparts — link to the live Singapore–London compare page so the recipient can see the current offset and validate the slot themselves.

The honest takeaway

Eight hours is a hard gap but it has exactly one good answer: 14:00 GMT / 22:00 SGT for recurring meetings, plus a solid async update loop carrying the day-to-day work. Anyone proposing morning-London or pre-dawn-Singapore slots is either new to the gap or solving for a problem they shouldn't be solving for. Pick the one slot, build the async loop, and stop looking.

Need more timezone coordination?

Compare Time

General