The House Armed Services Committee voted 44-12 on June 5 to advance the FY2027 National Defense Authorization Act, a defense policy bill that emerged from a 14-hour markup with more than 900 amendments considered. Buried inside the sprawling legislation is a provision that could reshape how defense contractors negotiate intellectual property rights for decades to come.
The bipartisan right-to-repair amendment, sponsored by Reps. Maggie Goodlander (D-NH) and Pat Harrigan (R-NC), would establish government-purpose rights as the default IP standard for technical data, software, and documentation on future DoD contracts. That is a significant departure from current practice, where contractors often assert limited rights over their proprietary data and the government must fight for broader access during source selection and contract negotiations.
To understand why this matters, it helps to know what government-purpose rights actually means. Under this licensing tier, the federal government can use, modify, and share covered technical data or software for any government purpose, including sharing it with other contractors working on the same program. What the government cannot do is release that information commercially or allow a third party to use it for their own commercial gain. Government-purpose rights sit between unlimited rights, where the government can do essentially anything with the data, and limited rights, where use is confined to very narrow purposes tied to the original contract. Pushing government-purpose rights to the default does not eliminate contractor IP protections. The measure does not seize patents, copyrights, or trade secrets. Private IP remains private. But it does move the starting line.
Under the amendment, contractors who want more restrictive protections must proactively justify them. They would be required to provide detailed lists identifying each piece of data or software needing protection, supply evidence that the technology was developed with private funding, and include specific unlimited-rights exclusions. If a contractor marks information as proprietary without proper justification, or fails to document exclusions correctly, the government automatically receives government-purpose rights. The Pentagon would also be empowered to claim government-purpose rights if the Defense Secretary determines markings are improper or documentation is incomplete.
Industry groups pushed back hard. Five trade groups opposed the provision: the Aerospace Industries Association, the National Defense Industrial Association, the U.S. Chamber of Commerce, the National Association of Manufacturers, and the Association of Equipment Manufacturers. Keith Webster of the Chamber of Commerce warned that expanded right-to-repair would cause reduced industry participation, diminished innovation, and erosion of the defense industrial base. Committee Chairman Mike Rogers (R-AL) argued the amendment could force companies to choose between protecting their IP and competing for Pentagon contracts.
This is not the first time Congress has attempted this shift. Identical right-to-repair language was stripped from the FY2026 NDAA last year after an industry lobbying campaign, despite broad support from the Trump administration, Congress, and senior DoD leadership. That history makes the amendment's passage out of committee significant, though the harder fight likely lies ahead in the Senate and in conference, where industry lobbying will intensify again.
Beyond the IP fight, the FY2027 NDAA contains several other notable provisions for defense contractors. The bill adds $500 million to fund a second Arleigh Burke-class DDG-51 destroyer. The Army Improved Turbine Engine Program receives a $50 million boost, bringing its total authorization to $100 million. The Air Force's A-10 Warthog is retained through 2030. The Army receives $62 million for autonomous resupply vessels. The bill also mandates quarterly munitions inventory reports, a transparency measure aimed at keeping Congress better informed on stockpile readiness.
The full House floor vote is expected before the July Fourth recess. The Senate Armed Services Committee is scheduled to begin its own markup the following week. Whatever version the Senate produces, the right-to-repair language will face another round of lobbying in conference, making the coming weeks critical for contractors on both sides of the debate.
What It Means for Contractors
If this provision survives into the final FY2027 NDAA, it will restructure IP negotiations on every future DoD contract. For small and mid-sized contractors who lack in-house government contracts counsel, the documentation burden alone represents a meaningful operational change.
Software developers and companies that license proprietary tools into defense programs face the sharpest impact. Currently, asserting limited rights is relatively straightforward. Under the new framework, that assertion requires documented evidence of private funding and clause-specific justification. Contractors who have relied on boilerplate IP markings without maintaining underlying funding records will be exposed.
Systems integrators face a different challenge. When a program involves dozens of subcontractors, the burden of tracking and justifying IP claims across the entire supply chain multiplies quickly. Integrators serving as prime contractors will need to ensure their subcontractors maintain compliant IP documentation, because a missing exclusion anywhere in the chain could result in the government obtaining government-purpose rights over data the prime believed was protected.
OEMs with proprietary repair manuals, diagnostic software, or maintenance data are the most directly targeted by the right-to-repair framing. The entire premise of the amendment is to ensure DoD can authorize independent maintenance providers to service equipment without going back to the original manufacturer for permission or paying premium rates for access to technical data.
If you are currently bidding on new contracts, assume this language may be in effect and build your IP documentation practices now. That means auditing which technical data and software in your portfolio was developed with exclusively private funds, creating or updating records to support that determination, and drafting clause-specific exclusion language for each item you intend to protect. Existing contracts are not affected retroactively, but follow-on options and re-competitions will be. Engage your government contracts counsel now to review your current IP markings and determine which assertions require additional documentation to survive a contracting officer challenge under the new standard. Waiting until the final bill is enacted leaves insufficient time to remediate gaps across active proposals and existing contract vehicles. Treat Senate floor action and conference as your planning trigger, not enactment.
