The Federal Government Has One System for Tracking Federally Funded Inventions. It Has Problems.
The federal government’s push to consolidate invention reporting onto a single platform is the right instinct—but the platform has structural limitations that are creating new inefficiencies even as it eliminates old ones. A July 2023 executive order directed nine major agencies to transition to iEdison, NIST’s web-based invention reporting system, by the end of 2025. GAO’s April 2026 technology transfer report (GAO-26-107971) finds the transition unfinished and the system itself in need of improvement.
What iEdison Is Supposed to Solve
Before iEdison, funding recipients reporting inventions to multiple agencies had to navigate completely different processes—some agencies required email submissions, some maintained their own databases, some had agency-specific forms with different required fields. A university with inventions funded by NIH, DOE, and NSF simultaneously was managing three different reporting tracks. iEdison was designed to collapse that into one.
For the agencies already using iEdison—including NIH, DOE, and NSF—the consolidation has reduced some of this burden. And representatives of one small business stakeholder group told GAO that reporting requirements don’t represent a significant obstacle to bringing products to market. The bigger barrier for small businesses, they said, is the commercialization “valley of death”—the gap in funding support between early technology development and commercial viability.
The Two Largest Agencies Were Still Transitioning
DOD and NASA were the final two of the top five federal R&D funders to complete the iEdison transition. Their journeys illustrate why the shift is harder than it sounds.
NASA had used its own internally developed New Technology Reporting system (e-NTR) for years and completed its transition to iEdison in September 2025. But officials noted the agency still needs to run both systems: e-NTR for inventions developed internally, iEdison for external funding recipients. Running parallel systems adds cost and administrative complexity.
DOD’s situation is more complicated. As of June 2025, DOD had no centralized department-wide process for tracking federally funded inventions. Individual components used the DD-882 form, a paper-and-digital process embedded in DOD’s contracting closeout workflow. Some components had already adopted iEdison voluntarily—including the Army Research Laboratory, DARPA, and the Office of Naval Research—but adoption was far from uniform. DOD planned to achieve department-wide transition by March 2026. As of the report’s completion, they had executed a memorandum of understanding with NIST and completed a security review with no required changes, but the Defense Federal Acquisition Regulation Supplement update was still pending, delayed by higher acquisition reform priorities.
The Flexibility Problem
iEdison’s most significant structural flaw is that it doesn’t require a standardized disclosure form. Funding recipients can upload invention disclosures in whatever format they choose. The system’s designers made this choice deliberately—to reduce burden on recipients who already have established internal forms. But the downstream effect is that agencies receive submissions in inconsistent formats that are difficult to compare and review.
For agencies managing high volumes of disclosures, this is a material problem. NIH officials told GAO that reviewing disclosures is time-intensive when recipients use their own formats. NASA officials noted the inconsistency is particularly acute when multiple organizations co-develop an invention, which happens in roughly one-third of NASA-funded cases—making it difficult for reviewers to determine whether submissions are duplicates. The practical result is more back-and-forth between agencies and recipients, and slower processing times.
In response to a GAO draft recommendation, NIST published a sample disclosure form on its website in March 2026, along with checklists and additional guidance. The form is optional—institutions with established templates don’t need to change their practices—but it gives recipients who don’t have their own forms a clear template to follow. GAO concluded that NIST’s action met the intent of the recommendation and withdrew it from the final report.
The Null Reporting Gap
A more fundamental limitation is that iEdison has no mechanism for null reporting—the ability for a funding recipient to certify that a specific grant or contract produced no inventions. This matters because unreported inventions are a real concern: under Bayh-Dole, the government has a royalty-free license to use all inventions it funds, but it can only exercise that right if it knows the inventions exist.
Currently, agencies use workarounds to identify potentially unreported inventions. DOE audits patent databases and asks recipients to certify completeness during contract closeout. DOD plans to continue using its DD-882 form in parallel with iEdison specifically to preserve null-reporting capability. NASA officials said the absence of null reporting will likely result in fewer disclosures and reduced ability to identify inventions that should have been reported.
NIST’s position is that null reporting is technically infeasible without a significant system redesign: iEdison doesn’t maintain a record of every grant and contract across all participating agencies, so it can’t know when a null report would be due. NIST also noted that requiring every funding recipient to log in annually to submit null reports for every award would dramatically increase system traffic and NIST’s operating costs.
The resulting situation is a practical gap in federal oversight of its own IP interests—one that DOD is addressing through parallel paperwork, NASA is still working through, and NIST considers structurally beyond the system’s current capacity to fix.