18f.org

18F worked on a broad set of federal, state, and local government technology projects before it was dismantled on March 1, 2025. Its public project list includes modernizing Weather.gov for NOAA, IRS Direct File for the Internal Revenue Service, and application modernization for the Treasury's Alcohol and Tobacco Tax and Trade Bureau (TTB), among others. The site also lists a separate set of "Interrupted projects"—work that was underway or planned when 18F was shut down—each with a "Read more" link for details.

What 18F did

According to 18F's own summary, its work fell into three categories:

• Modernized software development processes — helping agency IT teams and business owners adopt agile development. Alex Palmer, Chief Information Officer at the Federal Election Commission, is quoted saying 18F "was a game-changer for us" and "changed our whole methodology."
• Improved public-facing services such as websites and applications.
• Digitized and streamlined internal systems.

Interrupted projects listed by 18F

The site names the following interrupted projects, each with a link to read more:

The agencies represented span NOAA, IRS, Treasury, the Department of State, and the Election Assistance Commission, along with state and judicial bodies.

Status and context

18F states that it was dismantled by DOGE on March 1, 2025, and that it is taking legal action, with a latest statement available on the site. The organization describes more than 11 years of non-partisan civil service. For the current legal status, the statement linked from the site is the authoritative source; this page does not detail the outcome of that action.

Where the guides and resources are

18F says its work "belongs to the public" and that it has saved resources including its de-risking guide and engineering guide. These are available through a "Get the guides" link on the site, which is the place to start if you want the practical material rather than the project list.

18F changed government technology development by embedding agile, user-centered practices directly into agency teams rather than delivering one-off products. According to 18F's own account, its work centered on modernizing software development processes, improving public-facing services like websites and applications, and digitizing internal systems. The clearest evidence of a methodology shift comes from the Federal Election Commission: CIO Alex Palmer said 18F "helped the IT team and business owners get involved in the agile development process. It changed our whole methodology." That outcome—business owners and IT staff working together in agile cycles—is the mechanism to look for when assessing whether 18F-style work took hold at an agency.

What 18F actually did

18F described three categories of work:

• Modernized software development processes — moving agencies toward iterative, agile delivery instead of long specification-then-build cycles.
• Improved public-facing services — websites and applications that citizens interact with directly.
• Digitized and streamlined internal systems — back-office workflows converted from paper or legacy processes.

The FEC quote is the most concrete description of the first category: the change was not a tool or a product but a working method in which business owners participate in agile development alongside IT.

Why the approach changed agency methodology

The FEC example shows the pattern. 18F engaged with the agency, brought IT and business owners into the same agile process, and the agency reported that its "whole methodology" changed. The distinguishing feature is involvement of non-technical business owners in development cycles—when that happens, requirements come from the people who run the programs, and delivery happens in short iterations rather than a single handoff.

For a practical test of whether this pattern applies to a given project: ask whether program staff attend sprint reviews, whether work ships in increments shorter than a year, and whether the IT team and business owners share one backlog. If the answer is no on all three, the 18F-style method likely did not take root.

Projects 18F worked on

18F's page lists the following engagements, several of which it labels as interrupted:

The page presents these under "Interrupted projects," meaning work that stopped when 18F was dismantled. If you are tracing the status of any of these services, treat the 18F involvement as ended and check the agency's own site for current ownership.

Current status and where the resources are

18F states it was dismantled by DOGE on March 1, 2025, and that it is taking legal action. The team's public materials remain available: 18F says its work belongs to the public and that it has saved its de-risking guide, engineering guide, and other guides, accessible through the "Get the guides" link on 18f.org.

If you need the methodology rather than the projects, those guides are the practical starting point—they encode the de-risking and engineering practices behind the agile shift described above.

18F's guides and resources are still available through 18f.org, which states that "our work belongs to the public" and that it has saved materials including the de-risking guide and engineering guide. The site presents these as public property, so you can access them even though 18F itself was dismantled by DOGE on March 1, 2025. Use this route if you want the original 18F methodology and documentation rather than a third-party summary.

What 18F Was and What It Left Behind

18F was a team of non-partisan civil servants that, for over 11 years, worked to make government technology work better. Its stated work fell into three areas:

• Modernizing software development processes
• Improving public-facing services such as websites and applications
• Digitizing and streamlining internal systems

That work generated practical documentation — the de-risking guide and engineering guide are the two the site explicitly names as saved. The site frames all of it as belonging to the public, which is why the materials remain accessible after the team's dissolution.

How to Access the Guides

The site's "Resources from 18F" section is the entry point. The page describes the saved materials and provides a "Get the guides" path. The general flow:

1. Go to 18f.org.
2. Find the "Resources from 18F" section.
3. Follow the "Get the guides" link to reach the saved de-risking guide, engineering guide, and other materials.

The expected result is access to the original 18F documentation. The page does not specify file formats, hosting locations, or whether any materials require registration, so treat those details as unconfirmed until you reach the guides themselves.

What Else the Site Documents

Beyond the guides, the site is a record of what 18F did and where its work was interrupted. The "Interrupted projects" section lists engagements that stopped when the team was dismantled, including:

Each entry has a "Read more" link, so the site functions as a project index as well as a guide repository. If you are looking for documentation tied to a specific agency engagement, start from the matching project entry.

Current Status and Context

18F was dismantled by DOGE on March 1, 2025, and the site states that the team is taking legal action, with a "latest statement" available on the page. This matters for anyone citing 18F's work: the organization no longer operates, so the site is a static archive rather than an active support channel. The site also includes a testimonial from Alex Palmer, the FEC's Chief Information Officer, describing how 18F helped the IT team and business owners engage in agile development and changed the agency's methodology — useful context if you want to understand the intended use of the guides.

Practical Notes

• The de-risking guide and engineering guide are the named saved resources; other documentation "and more" is referenced but not itemized on the page.
• No pricing or login requirements are stated on the page, so do not assume the guides are free of access conditions until you reach them.
• For project-specific material, use the "Interrupted projects" list and its "Read more" links rather than searching the site broadly.

18F was a team of non-partisan civil servants inside the U.S. government that worked for more than 11 years to make government technology work better. Its work covered three broad areas: modernizing software development processes, improving public-facing services like websites and applications, and digitizing and streamlining internal government systems. According to the organization's own site, 18F was dismantled by DOGE on March 1, 2025, and the team says it is taking legal action.

What 18F actually worked on

The site describes 18F's contribution in three plain categories:

• Modernized software development processes — helping agencies change how they build software, including bringing IT teams and business owners into agile development.
• Improved public-facing services — websites and applications that citizens interact with directly.
• Digitized and streamlined internal systems — back-office workflows that agencies use to do their work.

A quote on the site from Alex Palmer, the FEC's Chief Information Officer, describes the effect of that engagement: 18F "came in and helped the IT team and business owners get involved in the agile development process. It changed our whole methodology."

Projects that were interrupted

The site lists a set of projects under the heading "Interrupted projects," which is the clearest picture of the range of 18F's work. The list includes:

The spread matters: 18F's work was not confined to one agency or one type of task. It ranged from a weather site used by the general public to an internal case-management system for unaccompanied children, and from federal agencies to a state labor department.

What happened to 18F

The site states plainly that 18F was dismantled by DOGE on March 1, 2025, and that the team is taking legal action, with a link to its latest statement. If you are trying to understand 18F's current status, that statement is the primary source to read rather than secondhand summaries.

Where the resources went

The site notes that 18F's work "belongs to the public" and that it has saved its de-risking guide, engineering guide, and other materials, which are available through a "Get the guides" link. For anyone who wants to apply 18F's methods — such as de-risking a large software procurement or setting up an engineering practice in a public-sector team — those guides are the practical starting point.

How to use this if you are researching 18F

• If you want to know what 18F was: use the three-category description above and the project table as the summary.
• If you want to know its status: read the site's statement on the March 1, 2025 dismantling and the legal action.
• If you want to reuse its methods: start with the saved de-risking and engineering guides rather than trying to reconstruct them from news coverage.
• If you are looking for a specific project: check the interrupted-projects list first; it names the agency and project for each entry, and each has a "Read more" link on the site.

18F was dismantled by DOGE on March 1, 2025, according to the organization's own site. The same page states that 18F is "taking legal action" and directs readers to its latest statement for updates. So as of the site's current content, 18F is not operating as the government unit it was, and its status is tied to an ongoing legal challenge rather than a published restoration or replacement plan.

What the site confirms

The 18F homepage is explicit about the shutdown and about what remains available:

• Shutdown date and actor: "18F was dismantled by DOGE on March 1, 2025."
• Response: "We're taking legal action."
• Where to follow it: the site points to "our latest statement" for the newest position.
• What survives: "Our work belongs to the public. We've saved the de-risking guide, engineering guide, and more."

That last point matters for anyone who used 18F's methods or documentation. The guides are presented as preserved public resources, not as discontinued products, so they can still be consulted even though the organization is not active.

What 18F did before the shutdown

The site summarizes 18F's work in three categories:

A quoted customer, Alex Palmer, CIO of the Federal Election Commission, describes 18F as "a game-changer" that brought the IT team and business owners into the agile process and "changed our whole methodology." That quote is useful context for why the shutdown drew attention: 18F's role was process change inside agencies, not just building websites.

Projects that were interrupted

The site lists work that stopped mid-stream. These are the clearest evidence of what the shutdown cut off:

• NOAA — Weather.gov
• IRS — Direct File
• Treasury, Alcohol and Tobacco Tax and Trade Bureau — TTB application modernization
• FVAP.gov — Federal Voting Assistance Program
• Office of Refugee Resettlement — In Care Case Management System for Unaccompanied Children
• Maryland Department of Labor — Maryland Family Leave and Medical Insurance
• U.S. Court of Appeals for the Ninth Circuit — website redesign
• U.S. Department of State, Bureau of Consular Affairs
• Election Assistance Commission — web strategy
• Council on Environmental Quality
• Permitting Council

Each entry links to a "Read more" page on 18f.org. If you need the detail on a specific project — scope, stage reached, or what happens to the underlying service — that linked page is the place to check, since the homepage only names the projects.

How to check the current status yourself

Because the legal action is ongoing, the accurate answer can change. To verify rather than rely on a snapshot:

1. Go to 18f.org and open the "latest statement" link referenced on the homepage.
2. Check the date on that statement; treat anything older than the most recent post as superseded.
3. For a specific interrupted project, follow its "Read more" link and look for any note on handover or continuation.
4. For the preserved guides, use the "Get the guides" link under "Resources from 18F."

Expected result: you will either find a newer statement describing the legal outcome, or confirm that the March 1, 2025 shutdown notice is still the current position.

Common snag: third-party summaries often repeat the shutdown date without noting the legal action, which makes 18F look permanently closed with no pending challenge. The site's own statement is the better source for status.

What this means in practice

• If you want 18F's methods: the de-risking and engineering guides are described as saved and public, so they remain usable references.
• If you are tracking a specific project: the interrupted-projects list tells you whether your project was affected; the linked page gives the detail.
• If you need a definitive status: the legal action is unresolved on the page, so check the latest statement before relying on any "closed" or "restored" claim.