Briefing
Right to Repair Returns in the FY27 NDAA: What It Means for Technical Data
Where It Stands
Back, and Further Along
Last December the FY26 NDAA became law without the right-to-repair provisions either chamber had proposed. What survived was section 805, a digital system to track the technical data behind weapon systems, which we covered in the military right-to-repair fight is really a technical data fight.
This year both bills carry it. The House passed H.R. 8800 on 22 July 2026, 216 to 212, with the provision as section 861. The Senate Armed Services Committee reported S. 4784 in June with a similar section 804, but the full Senate has not passed it: a procedural vote to take it up failed on 14 July, and the Senate has not returned to it since late July. As of mid-October there is no conference agreement and nothing has been signed. Status lines on this page will be updated as that changes.
What the Bills Do
Default Rights, and the Burden of Proof
- Government purpose rights by default
- Both bills add a new section, 10 U.S.C. 3776: technical data, computer software, and computer software documentation delivered under a DoD contract "shall be provided with government purpose rights unless the contractor establishes, through clear and convincing evidence, entitlement to more restrictive rights."
- The contractor carries the paperwork
- To claim more restrictive rights, a contractor needs a compliant assertions table identifying each specific item, documentation of private development funding, exclusions applied at the lowest practicable segregable level, and matching portion markings on the deliverables. A deliverable that does not comply is treated as delivered with government purpose rights.
- Different reach
- The House version covers any DoD contract, subcontract, or other agreement; its committee report says this includes commercial procurements. The Senate version applies only to agreements for noncommercial products or services.
- Different teeth
- The House deems mismarked data for noncommercial critical readiness items to carry government purpose rights, and orders a study of clawing back overpayments. The Senate goes further: an independent analysis sets a fair price, overpayment becomes a contract debt, and contractors that repeatedly mismark data or submit invalid assertions become ineligible for contracts requiring data delivery.
- Data for wartime repair
- Both bills allow detailed manufacturing or process data to be released for operation, maintenance, installation, or training in support of wartime or contingency operations, where the original supplier cannot meet readiness requirements.
For context, government purpose rights sit between unlimited and limited rights in the DFARS technical data clause: the government may use and share the data for government purposes, including competitive procurement, normally for five years before the rights become unlimited.
Our Read
What It Means for Manuals
Neither bill mentions technical manuals, and that is worth understanding. Under current law (10 U.S.C. 3771) and the DFARS clause, data necessary for installation, operation, maintenance, or training, other than detailed manufacturing or process data, already carries unlimited rights. Most of what a technical manual contains falls in that category. The default-rights change mainly reaches what sits around the manual: design and source data, detailed manufacturing and process data, and software and its documentation.
The bills do amend that same paragraph, and the Senate committee describes the change as government purpose rights for detailed manufacturing and process data under urgent conditions. Read literally, the amended text is less clear, so the final wording deserves a close look before anyone relies on it.
Where publications teams will feel it is the markings. Manuals and interactive technical manuals routinely embed supplier content and proprietary process detail. Under either bill, every restricted portion needs an assertion and a portion marking at the segregable level; whatever is not marked correctly defaults to government purpose rights. That is a publishing-pipeline question as much as a legal one: markings carried as metadata on each data module or topic survive every output, while markings typed onto a PDF page do not. It also means the distribution statement and the data rights legend, two different controls on the same page, both have to be right.
What to Do
Six Steps Before the Bill Is Final
- Inventory every restrictive legend on your current deliverables, and the assertion behind each one.
- Check that markings can be applied at the segregable level your publishing pipeline actually produces: per data module, per topic, per figure.
- Keep operation and maintenance content separate in the source from detailed manufacturing and process data, so each carries the rights it should.
- Keep the assertions table in step with what is delivered, revision by revision, not just at contract award.
- Don't confuse data rights legends with distribution statements: both sit on the same page and answer different questions.
- Watch the Senate floor and any conference: scope (commercial or not) and penalties are where the versions differ.
The same discipline answers the FY26 inventory: our technical data package audit and the MIL-STD-31000 reference page cover what a complete package contains. This is a summary of public bill text, not legal advice; data rights questions on a live contract belong with counsel.
FAQ
Questions We Hear
What is the FY27 NDAA right-to-repair provision?
Section 861 of the House bill (H.R. 8800) and section 804 of the Senate committee bill (S. 4784) would make government purpose rights the default for technical data, computer software, and computer software documentation delivered to DoD, unless a contractor proves by clear and convincing evidence that it is entitled to more restrictive rights.
Has the FY27 NDAA right-to-repair provision become law?
Not as of mid-October 2026. The House passed its bill on 22 July 2026. The Senate Armed Services Committee reported its version in June, but the full Senate has not passed it, so there is no conference agreement and nothing has been signed. The FY26 NDAA dropped similar provisions in conference.
What are government purpose rights?
One of the license categories in the DFARS technical data clause, between unlimited and limited rights. They let the government use and share the data for government purposes, including competitive procurement, but not for commercial purposes. They normally run for five years, or another negotiated period, and then become unlimited rights.
Do technical manuals get government purpose rights under the bills?
The bills don't mention technical manuals. Under current law and the DFARS clause, data necessary for installation, operation, maintenance, or training (other than detailed manufacturing or process data) already carries unlimited rights, which covers most manual content. The bigger change for manuals is the marking discipline: any restricted portion needs an assertion and a portion marking, or it defaults to government purpose rights.
What is an assertions table?
The list a contractor provides identifying the specific technical data or software it intends to deliver with restrictions, the basis for each restriction, and the rights claimed. Under both bills, a table that does not identify each specific item leaves the deliverable with government purpose rights.
Get In Touch
Deliverables That Carry the Right Markings
We build technical publications in S1000D and the MIL-STD formats with markings, distribution statements, and applicability carried as data, so every output gets them right.