The TMF’s September Cliff: The Senate Bought Time the House Hasn’t Agreed To
Nobody Has Actually Extended Anything Yet
The coverage in early August read like a rescue: the Senate had stepped in and saved the Technology Modernization Fund from expiring. The reality is narrower and considerably less comfortable. One chamber passed a bill. The other has not agreed to it. The deadline that threatens the fund — September 30 — has not moved by a single day.
The distinction matters to anyone with a project in the TMF pipeline, because planning around a reprieve that does not yet legally exist is how agencies end up stranded in October.
Why the Date Has Teeth
The TMF was created by the Modernizing Government Technology Act of 2017 as a revolving fund rather than a conventional appropriation. Agencies pitch modernization projects — retiring mainframes, hardening identity systems, moving citizen-facing services onto something built this century — and successful bids draw from a central pot, repaying it over time out of the savings the work produces.
The structure exists because the normal one does not fit the problem. Appropriations run annually; replacing a benefits system runs for years. A revolving fund lets an agency start work without betting the whole effort on surviving each budget cycle intact.
Congress reauthorized the fund through the end of fiscal 2026 — September 30. On that date, absent further action, both the fund’s authority to finance new work and the TMF board itself lapse.
What the Senate Actually Passed
The Senate’s continuing resolution, H.R. 6500, would fund the government through December 11 and carry three expiring authorities along with it: the TMF, the Cybersecurity Information Sharing Act of 2015, and the Federal Cybersecurity Enhancement Act. Cloture cleared 89-4 on the night of August 3, and the chamber passed the measure 90-6 on August 8.
The provision that matters for modernization work is specific and easy to miss. The Senate version lets the TMF finance new projects through December 11. The House’s competing version does not. Under the House text the fund could keep administering commitments it has already made, but could approve nothing new after September 30.
The stakes are concrete rather than symbolic. The fund had roughly $200 million left to spend as of early July, while the fiscal 2027 bill carries just $5 million in new authorization. Whether that existing $200 million can actually be put to work over the next several months depends entirely on which version survives.
Jessie Posilkin, the TMF’s acting director, put the constraint plainly: “With more time, we could do even more — but we’ll meet as much of the agency need as we can, while we can.” Senator Susan Collins framed the bill as giving Congress “the time we need to continue our work on bipartisan appropriations bills.”
Where It Stands Now
The House returns August 31 having passed different text. Between that date and September 30, the two chambers have to converge or the Senate’s extension remains a document rather than a law. That is roughly five weeks, much of the legislative calendar still unscheduled, and a provision that amounts to a minor line item inside a much larger appropriations fight.
Small provisions attached to large bills are precisely the ones that vanish in reconciliation — not because anyone opposes them, but because nobody spends political capital defending them. The TMF has genuine bipartisan support and has had it for years. That has not previously been sufficient to get it durable funding.
The Cadence Is the Actual Problem
Notice that even the good outcome here is not good. December 11 is fifteen weeks out. A federal system replacement is measured in years. An extension that buys a single fiscal quarter does not let an agency commit to a three-year migration; it lets an agency commit to the part of a migration that fits before the next cliff, which is not the same thing and generally costs more per unit of progress.
This is the structural cost that rarely appears in the reporting. Agencies respond to funding uncertainty by decomposing programs into smaller, safer increments, sequencing the politically defensible work first and deferring the foundational work that would have produced the actual savings. The revolving fund was designed specifically to escape that trap. Running it on ninety-day extensions puts it back in.
For agency technology leaders, the practical reading is unsentimental. Do not plan against December 11 — plan against September 30, and get board approval before it if your proposal is close. And when the appropriations conversation resumes, the argument that will actually move it is not modernization rhetoric but repayment data: which TMF-funded projects returned money to the fund, how much, and how fast. The case for predictable funding is strongest when it is made in the language appropriators already use.
Status as of late August 2026: the House had not acted on the Senate text at publication.