Daylight Saving Time: When Clocks Change and How It Affects You

Daylight saving time - when clocks spring forward in March and fall back in October - is one of those events that catches people off guard if they're not paying attention. In the UK, this means more evening daylight in summer and an extra hour in bed on the night the clocks go back, but it also means scheduling complexity if you work across time zones. This guide explains when the clocks change, why it happens, and how to plan around it.
When Do the Clocks Change?
In the UK, clocks change twice a year on the last Sunday of the month:
- Spring forward (last Sunday of March): At 1:00 AM, clocks go forward one hour to 2:00 AM. You lose one hour of sleep.
- Fall back (last Sunday of October): At 2:00 AM, clocks go back one hour to 1:00 AM. You gain one hour of sleep.
In 2026, the changes were on 29 March and 25 October. The next ones are 28 March 2027 and 31 October 2027. Mark these dates on your calendar now - you'll thank yourself when you don't scramble on Sunday night wondering if your meeting times have shifted.
During the summer period (late March to late October), the UK runs on British Summer Time (BST), which is GMT+1. During winter, it's Greenwich Mean Time (GMT), which is UTC+0. So when we say "clocks change," we're talking about a one-hour shift in official time that ripples through your calendar, your sleep schedule, and your international meetings.
For official dates and times, the UK government page on clock changes has the schedule and guidance.
How Daylight Saving Time Works
Daylight saving shifts an hour of daylight from morning to evening. The sun doesn't rise or set at a different time - we just reset our clocks so that daylight hours align with when most people are awake and working.
On the spring change date in the UK, one hour literally ceases to exist. Clocks jump from 12:59 AM directly to 2:00 AM. If you've set an alarm for 1:30 AM, it won't fire at that time. If you're running a scheduled task at 1:00 AM, it may not run - the system skips that hour entirely.
On the autumn change date, one hour occurs twice. Clocks go backwards from 1:59 AM to 1:00 AM. If you've scheduled something for 1:30 AM, it technically happens twice - once on the "first" 1:30 and again on the "second" 1:30.
For most users, this is invisible. Your phone, laptop, calendar, and cloud apps all auto-update when daylight saving hits. But if you're managing times manually - scheduling batch jobs, coordinating meetings across time zones, or billing by the hour - you need to be aware of the shift.
Why We Do This, and Who Else Observes It
Daylight saving started during World War I as an energy-saving measure. The logic was that if people worked during daylight hours, they'd use less artificial lighting. That reasoning is outdated (modern energy use is dominated by heating, cooling, and electronics), but the practice stuck because it benefits retailers, tourism, and outdoor recreation - industries that prefer evening daylight during operating hours.
Not everyone observes daylight saving. Most Asian countries (China, Japan, India, Singapore) don't. Parts of Australia do, but on a Southern Hemisphere schedule, so their clocks go forward around the time ours go back. The USA observes it, but on different dates than the UK: clocks change on the second Sunday of March and first Sunday of November. This creates a scheduling mess in transition weeks.
For example, the US springs forward before the UK. In 2027, New York moves to EDT (UTC-4) on 14 March while London stays on GMT until 28 March. For those two weeks (three weeks in 2026), the time gap between London and New York is four hours instead of the usual five. In autumn the UK falls back a week before the US, so the gap is four hours again for one week. When you're scheduling meetings across time zones, these transition weeks are when scheduling errors happen.
Why Daylight Saving Affects Your Schedule More Than You Think
If you think daylight saving is a minor inconvenience, you're half right. For most people, the one-hour shift is automatic - your phone handles it. But here's where it bites hard:
Sleep disruption: The spring change genuinely affects you. Many people feel groggy for a few days afterwards. The autumn change is gentler - you gain an hour of sleep that night.
Time zone confusion: If you work with US, Australian, or Asian colleagues, the transition weeks create temporary offset changes. A 5-hour gap to New York becomes 4 hours, and gaps to other countries can move by an hour in either direction. Use a time zone converter that handles daylight saving automatically rather than calculating offsets by hand. Manual maths during transition weeks is how missed meetings happen.
Project scheduling: If your deadline straddles the daylight saving change, that day has 23 hours (spring) or 25 hours (autumn). This doesn't usually matter for normal projects, but if you're managing something time-critical - like a scheduled batch job, a live event, or a server maintenance window - it absolutely does. Calculate the exact number of days between your start and deadline, and note any transition dates in that range.
Business metrics: If your company tracks daily or hourly metrics, daylight saving creates an anomaly. A 23-hour day in March and a 25-hour day in October each differ from a normal 24-hour day by about 4% (1 hour in 24). If no one's accounting for this, it looks like something changed when really, the clock just shifted. Freelancers who track time across time zones need to be especially careful.
International travel: Clock changes shift local times but not flight durations. A 7-hour London to New York flight leaving at 12:00 lands at 14:00 New York time when the gap is five hours, but at 15:00 in a transition week when the gap is four. Check which gap applies on your travel date.
How to Prepare for Clock Changes
Update your devices early: Most modern phones, laptops, and cloud apps auto-update when daylight saving hits. Older hardware, smart home devices, and systems that don't connect to the internet might not. Check your key devices the week before each change. If you manage time in spreadsheets or databases, make sure your formulas account for the time shift.
Set a reminder: Put the next daylight saving dates (28 March and 31 October 2027) in your calendar now with a notification for the Friday before. It takes 10 seconds and saves you confusion on Sunday night. If you're planning projects, also mark UK bank holidays - daylight saving combined with a bank holiday can create an even tighter week.
Adjust your sleep gradually: If you're sleep-sensitive, shift your bedtime 15 minutes earlier starting three days before the spring change. You'll still lose an hour, but the adjustment feels less jarring.
Communicate with your team: If you work across time zones, send a message the week before each change. "Clocks go forward on 28 March - our usual 9 AM GMT standup moves to 10 AM BST on Monday, and stays there until October." Clarity prevents scheduling errors and 15-minute zoom-call delays while people figure out who's late.
Plan projects with transition dates in mind: If you're calculating time differences for a multi-phase project, mark the daylight saving dates as inflection points. Check any hour-based deadlines or handovers that fall in those weeks, and you'll avoid surprises.
Frequently Asked Questions
Q: Do all countries observe daylight saving time? A: No. Most of Asia (China, Japan, India) doesn't. Most of Africa doesn't. Parts of Australia do, but on a Southern Hemisphere schedule, roughly the opposite half of the year to the UK. The USA does, but on different dates than the UK. This staggered approach is why international scheduling requires a tool, not a calculator.
Q: When will the UK stop doing daylight saving time? A: Maybe never, maybe soon - it's debated. The EU has discussed abolishing it multiple times. The UK hasn't committed to a change yet. There are arguments both ways (sleep, traffic safety, energy use, mood), but for now, plan on it continuing.
Q: What if I'm flying on a daylight saving date? A: Your flight time doesn't change, but local time at your destination may. If you're flying London to New York in a transition week, the time difference is four hours rather than five. Modern travel apps handle this automatically, but if you're coordinating arrival times with someone, be explicit about whether you mean local or UTC time.
Q: Does the hour I lose in spring come back in October? A: Literally, yes - you gain that hour when clocks fall back. But you don't necessarily "recover" it. If you're tired in March, it can take a few days to adjust. October's extra hour doesn't undo March's grogginess.
Q: How do I handle daylight saving time if I bill clients by the hour? A: Be transparent. A full day spanning the spring change is 23 hours long, and one spanning the autumn change is 25 hours. Most freelancers just bill based on the hours they actually worked, which is the simplest approach. If you track time electronically, check that your system adjusts to local time.
Q: Why does daylight saving happen on different dates in different countries? A: Each country sets its own rules. The UK uses the last Sunday of March and October. The USA uses the second Sunday of March and the first Sunday of November. Southern Hemisphere countries change clocks in the opposite seasons. There's no global coordination - it's decided locally, which is why scheduling internationally is complicated.
Q: What's the difference between daylight saving time, British Summer Time, and GMT? A: British Summer Time (BST) is the UK's daylight saving time: the period when clocks are one hour ahead, from late March to late October. GMT is Greenwich Mean Time, the UK's winter time (UTC+0), which applies after the clocks go back. Some countries call daylight saving "summer time" or "daylight time," but the principle is the same: shift an hour of daylight from morning to evening.
Tools That Make Scheduling Across Daylight Saving Easier
When clocks change, use these tools to avoid errors and confusion:
- Time zone converter: Handles daylight saving transitions automatically. Enter your time and it shows everyone's local time, even during transition weeks.
- Calculate time differences across countries: When you're unsure of your exact time offset, this does it for you.
- Schedule across multiple time zones: Find meeting times that work for global teams without manual calculation.
- Add or subtract days from a date: For deadlines that span daylight saving changes.
- Calculate days between two dates: Project planning with exact day counts.
There are two ways to think about daylight saving time: "I gained an extra hour of evening daylight" and "I lost an hour of sleep." Both are correct. Plan ahead, use the tools above, and you'll spend less time confused than the hour you'd lose otherwise.