Direct File’s quiet exit made retirement part of service design
The first filing deadline without IRS Direct File showed that ending a public digital service carries obligations of its own: to returning users, to the states that integrated with it, and to the public record.
Looking Back revisits one week at a time, from January 2020 to today, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
The week
April 15, 2026 was the federal individual income tax filing deadline, and the first since 2023 without IRS Direct File, the free tool that let eligible taxpayers file directly with the IRS. Direct File was piloted in 12 states in the 2024 filing season and offered in 25 states in 2025, when the IRS reported accepting about 296,500 returns through it, more than double the pilot year. In early November 2025, the IRS told participating states that Direct File would not be available in the 2026 filing season and that no future launch date had been set. Treasury Secretary Scott Bessent, also serving as acting IRS commissioner, said private-sector alternatives could do a better job. Taxpayers were pointed to options including IRS Free File, the long-standing program run with private software companies.
The policy argument over a government filing tool has been made at length on both sides, and we will not repeat it. The operational question is narrower and applies to any public service. Agencies launch digital services with roadmaps, user research and launch plans. They rarely plan for the end. Direct File was unusual: a service with returning users, state partners and a hard annual deadline, ended between seasons by a policy decision. That makes it a clear case study in what a retiring service still owes.
We see three obligations, each owed to a different group and each with a different owner. They run to the users, to the partners whose systems connect to the service, and to the public record of what the service cost and taught.
To the users: a route, not just a notice
A service with returning users creates an expectation that it will be there next year. When it is not, the agency owns the question of where those users go. A press statement and a closed web page meet the legal minimum. They do not reach a user who files once a year and remembers only the address they used last time.
A better pattern has four elements. Notify users through the channel they registered with, such as their account or email, before the season starts. Match alternatives to the situations the old service handled, so a user with a simple return knows which option fits and what its income limits are. Give users their own prior-year data in a portable form, because last year’s figures help with this year’s return. And keep the old address alive as a signpost, with plain guidance, because many users will arrive there at the deadline.
Each element has a cost and an owner. Notice requires that contact data was collected with consent to use it for this purpose. Portable data requires an export built while the service still runs. Signposting requires a contact center briefed on the alternatives and a web team that keeps the page current through the season.
To the partners: integrations that outlive the service
Direct File did not work alone. Participating states connected their own filing processes to it so that users could move from a federal return to a state return. Each integration represented work by a state revenue agency: interfaces, testing, user guidance and budget. When the federal service ended, those states had to decide whether to retire their side, repurpose it, or find another route for the same users.
The timing matters more than the decision. A notice in November leaves a state revenue department a few weeks before its own season begins, at a point when most system changes are frozen. The principle applies to any shared service, from a federal identity platform to a state benefits hub used by counties. A retirement plan should name the partners, give them a timeline that fits their cycles, and say what support continues during the transition.
Contracts and agreements are where this is enforced. Interagency agreements and data-sharing arrangements should include notice periods for termination and a description of what each party must do at the end. Few do. Adding them at launch costs little, because no one is yet arguing about the end.
To the record: what the public paid for
A retired service still holds data and still carries knowledge. Returns submitted through it remain subject to federal tax confidentiality rules and records schedules, whatever happens to the front end. Disposal and retention should follow those schedules deliberately, with a named records officer, not by default when infrastructure is switched off.
The knowledge matters too. User research, accessibility findings, performance data and code represent public investment. The IRS had published much of Direct File’s source code in 2025, which preserved part of that record. Research findings and operating lessons are easier to lose, because they live in team documents and in people who move on. An agency ending a service should publish or archive what it learned in a form others can find, whether the next attempt is by the same agency, another agency or a state.
Architecture affects how cleanly this can be done. Services built on shared platforms for identity, payments and data exchange leave those components running for other uses when they retire. Services built as self-contained systems take their components with them. That is a reason to prefer shared platforms at launch, regardless of how long a service is expected to last.
Finally, an agency should decide in advance what it will measure after a retirement. Calls and searches for the retired service, uptake of the recommended alternatives and complaints all show whether users found their way. Without those signals, the effect of ending a service is a matter of opinion on both sides of the policy argument.
With hindsight
The 2026 filing season ran without Direct File. IRS Free File, which is limited by income, Free File Fillable Forms and commercial software carried returns the tool might otherwise have handled. We have not seen reliable figures on how former Direct File users filed in 2026, and we would be cautious about any claim of precision on that question. The IRS said no future launch date had been set.
What the episode settled is that a public digital service with an established user base can be ended quickly by a policy decision. That argues for treating retirement as a designed event from the start: notice channels and data export for users, termination terms in partner agreements, and a plan for records and knowledge. Those provisions are cheap at launch and expensive to improvise when a decision has already been made.