The daylight saving bill: will it pass, what it costs, and what to do

On 14 July 2026 the House passed H.R. 139, the Sunshine Protection Act, by 308 to 117. It would make daylight saving time permanent, so the clocks that spring forward in March would simply never fall back. President Trump is backing it, the coverage has been loud, and if you run anything that depends on the clock, the practical questions are what it costs, what to do, and whether it passes at all.

What would it cost, or save?

The original case for daylight saving was energy. The Department of Transportation found about a one percent reduction in the 1970s; a later natural experiment in Indiana found residential electricity use going slightly up, because the air-conditioning and heating added in the evening cancel the lighting saved. The other arguments are about evening light. More of it lifts evening retail spending, and studies find evening robberies and some traffic deaths falling after the spring change. Those studies measure the twice-a-year transition, not a year of permanent daylight time, and permanent daylight time produces the brighter evening by making winter mornings darker, which moves the same darkness onto the morning commute and the school run. The one saving no one disputes is ending the switch itself, which one economist puts at roughly $1.7 billion a year in lost productivity around the changeovers.

What organizations should be paying attention to is the cost. Changing the clock rules is a software migration, and this particular change is a hard one. The last time Congress touched daylight saving, in 2005, the patching cost somewhere between $350 million and a billion dollars, and that was the easy kind of change, because it only moved the dates the switch happens on. This bill does something harder. It redefines what the time zones mean, turning Eastern Standard Time from five hours behind London into four. Every system that stored a clock offset as a fixed fact, rather than looking it up, is now wrong until someone fixes it. In shape it is closer to Y2K, which cost the United States around $100 billion, than to a routine patch, with one important difference. Y2K had years of runway and failed loudly, while this change has little lead time and mostly fails silently, producing data that is an hour wrong but still looks valid. Airlines have asked for up to two years to adjust their systems, which is a fair proxy for how big the job is.

What should your organization do?

Your preparation does not need to depend on whether the bill passes, because the same work protects you either way.

This is not hypothetical, and it is not waiting on Congress. Yukon made daylight time permanent in 2020, British Columbia did the same in March, and Alberta is next. Turkey froze itself onto permanent summer time back in 2016. On top of those one-off moves, IANA revises the rules several times a year, so the data under every system already shifts without any single country making the news. Anything that touches Canadian or cross-border time is exposed today. A permanent United States switch would be the biggest version of a change the rest of the world already treats as routine, and it needs the same work that routine already demands. That alone is reason to start now instead of waiting on a Senate vote.

The checklist:

• Store the universal time and the location, never a fixed offset. Save timestamps in UTC together with a named zone like America/New_York, and never store the letters EST or a hardcoded number of hours. This is the single change that makes every future rule change a non-event.
• Keep the time zone data current everywhere. The rules live in a package called tzdata, and there is a separate copy inside your operating systems, your programming-language runtimes, your container images, and often inside individual applications. Updating one does not update the others. Find them all and put them on a patch schedule.
• Inventory the devices that cannot easily be patched. Thermostats, badge readers, security recorders, industrial controllers, and hardware security modules often have the clock rules burned into firmware with no update path. These are the ones that will quietly be an hour off, so list them now.
• Audit anything anchored to New York time. A great deal of financial and compliance timekeeping is keyed to the Eastern trading day on purpose. Find those records, confirm they use a real zone rather than a fixed offset, and check what happens to them across a rule change.
• Test the boundary before it arrives. Pick the date a change would take effect and run your scheduling, billing, and reporting against it in a test system. An hour-off error that surfaces in a test is a task; the same error in production payroll is an incident.

None of this work hinges on the bill. Storing an offset instead of a real time zone is technical debt you owe regardless. British Columbia already called part of it due, Alberta is next, and IANA rewrites the rules several times a year. The Sunshine Protection Act is only the biggest of the events that come to collect. Pay the debt down now and the bill is a non-event. Carry it, and something else hands you the same bad month on a date you did not pick.

Will it actually pass?

Probably not in this Congress, and the reason is structural, not partisan.

The House is the easy chamber. The bill now goes to the Senate, which is exactly where every previous version has died. In 2022 the Sunshine Protection Act passed the Senate unanimously and then died in the House; the chambers keep killing it in opposite directions. This time the block is already named. Senator Tom Cotton, a Trump ally, stopped the bill by objection in 2025 and has said he will ask the majority leader not to bring it to the floor. Roughly a dozen Commerce Committee members of both parties have voted against permanent daylight time before, and Majority Leader John Thune has called it an issue that people are "willing to really slow things down over". A messaging vote in the House is not sixty votes in the Senate.

There is also a respectable off-ramp for opponents. The American Medical Association, the American Academy of Sleep Medicine, and the National Sleep Foundation all want to end the clock change too, but they favour the opposite fix, permanent standard time rather than permanent daylight time, because morning light is what keeps the body clock aligned. That means a senator can vote against this bill without voting to keep changing the clocks, which is the politically comfortable place to stand. Congress has been here before. It put the country on permanent daylight time in 1974, and repealed it within ten months once people spent the winter waking up in the dark.

So there is real momentum and low odds of enactment soon, at least for this bill. The longer arc runs the other way. Ending the clock change is broadly popular, states keep queuing up trigger laws, and a permanent-time regime almost certainly arrives eventually. What is unsettled is not whether the switch ends but which time the country keeps when it does, permanent daylight or permanent standard. This particular bill is one to watch, not to bet on. The end of clock-changing is closer to a when than an if.