Explainer
Technical Data Rights, Explained
The Basics
Who Paid Decides
In Department of Defense contracts, rights in noncommercial technical data are set by DFARS 252.227-7013. What the government receives is a license, and its size follows the money. An item developed exclusively at private expense (paid entirely from indirect cost pools or costs not charged to a government contract) earns the contractor the most protection. An item developed exclusively with government funds earns the government unlimited rights. Anything in between is mixed funding.
The clause also says that private expense should be decided at the lowest practicable level, so one system can hold data in several categories: a government-funded assembly can contain a privately developed component, and the data for each follows its own funding.
The Categories
Seven Kinds of Rights
- Unlimited rights
- The government may use, modify, reproduce, release, or disclose the data in any manner and for any purpose, and let others do the same. It applies to data for items developed exclusively with government funds, and to several categories regardless of funding, including form, fit, and function data and data needed for installation, operation, maintenance, or training.
- Government purpose rights
- For items developed with mixed funding. The government may use the data inside the government without restriction and release it outside for U.S. government purposes, including competitive procurement, subject to nondisclosure conditions, but not for commercial purposes. The default period is five years, or whatever the parties negotiate, after which the government has unlimited rights.
- Limited rights
- For data on items developed exclusively at private expense. The government may use the data within the government, but may not release it outside or use it for manufacture without the contractor's written permission, with narrow exceptions such as emergency repair or overhaul.
- Restricted rights
- The software counterpart of limited rights, for noncommercial computer software developed exclusively at private expense (DFARS 252.227-7014): for example, use on one computer at a time.
- SBIR/STTR data rights
- Data generated under a Small Business Innovation Research or Small Business Technology Transfer contract (DFARS 252.227-7018). During the protection period the government has limited rights in the technical data and restricted rights in the software. The period ends 20 years after the contract award unless the parties negotiate another.
- Specifically negotiated license rights
- The standard categories can be modified by mutual agreement, recorded in a license agreement made part of the contract, but never to give the government less than limited rights.
- Commercial technical data
- For commercial products and services developed exclusively at private expense (DFARS 252.227-7015). The government may use the data within the government only and may not use it to manufacture additional quantities, except for categories it may use without restriction, such as form, fit, and function data and data needed for operation, maintenance, installation, or training.
Civilian agencies work under the FAR instead. Its Rights in Data clause, 52.227-14, uses unlimited rights, limited rights data, and restricted computer software, with no government purpose rights category. The FAR is being rewritten through rolling class deviations; our piece on the FAR rewrite and technical data tracks what that changes.
Technical Manuals
Where Manuals Land
For publications teams this is the part that matters most. DFARS 252.227-7013 gives the government unlimited rights in technical data necessary for installation, operation, maintenance, or training purposes (other than detailed manufacturing or process data), whoever funded the item. The commercial clause lets the government use the same category without restriction, the software clause gives unlimited rights in software documentation the contract requires to be delivered, and the FAR clause names manuals for installation, operation, and routine maintenance and repair outright.
So a delivered operator or maintenance manual is usually the data the government holds the broadest license in, even when the equipment it describes was privately developed. That is why a manual should not quietly carry engineering detail that the contractor means to protect: once it is in the manual, it is in the category the government may share.
Our reading, not a legal test: the carve-out is where the arguments start. Detailed manufacturing or process data is defined as the steps, sequences, and conditions used to produce an item or perform a process, and depot repair or overhaul procedures can sit close to that line. Decide which side each procedure falls on before you write it, not after the government challenges the marking. The same data usually flows from the technical data package, which MIL-STD-31000 keeps separate from manuals.
Assertions
Say It Before You Deliver It
Restrictions are not something a contractor can add at delivery. Under DFARS 252.227-7017, an offer must identify the data the offeror, its subcontractors, and its suppliers assert should be furnished with restrictions, in an attachment signed by an official authorized to bind the company. The contract then carries that list, and 252.227-7013 says the contractor shall not deliver any data with restrictive markings unless the data is on it.
Assertions can be added after award only when based on new information or inadvertent omissions, and not when the omission would have materially affected source selection. In practice, the assertion list is written during the proposal, by people pricing the bid, long before anyone drafts a work package. If the publications team is not in that conversation, it inherits whatever the list says. The clauses that govern when that data is delivered, ordered later, or withheld are in our guide to DFARS technical data delivery clauses.
Markings
Four Legends, Every Page
A contractor asserts restrictions only by marking the deliverable. Under 252.227-7013 the authorized legends are the government purpose rights legend, the limited rights legend, the special license rights legend, and a copyright notice. For printed material the legend goes on the transmittal document or storage container and on each page that contains restricted data, with restricted portions of a page identified by circling, underscoring, a note, or similar.
Two failure modes follow. A nonconforming marking (a legend not in the authorized format) can be ignored, removed, or corrected at the contractor's expense if it is not fixed within 60 days of the contracting officer's notice. An unjustified marking is challenged under DFARS 252.227-7037, which generally allows a challenge within six years of final payment or of delivery, whichever is later, and at any time for data that is publicly available or was furnished without restriction.
For a structured publication, the legend is data like anything else: it has to survive conversion, appear on every page that needs it in every output, and stay attached to content reused in another manual. Rights legends also sit alongside, and are different from, distribution statements, which say who may receive a document at all, and from export control, which governs export and access by foreign persons.
What Is Changing
A Default Under Debate
Both FY27 defense bills would add a new section to title 10 making government purpose rights the default for technical data, computer software, and computer software documentation delivered to the Department, unless the contractor proves by clear and convincing evidence that it is entitled to more restrictive rights. The House passed its bill on 22 July 2026; as of late October 2026 the full Senate has not passed its version and there is no conference agreement. Our briefing on right to repair in the FY27 NDAA follows it, and right to repair and technical data sets out the background.
Whatever passes, the practical work is the same: know what you delivered, under which category, with which markings. Our technical data audit checklist is a place to start, and programs taking ownership of their source data should read what a government-owned CSDB means.
This page is educational background, not legal advice. Rights determinations, assertions, and challenges belong with your contracts team and counsel.
FAQ
Questions We Hear
What are technical data rights?
Technical data rights are the license the government receives in technical data delivered under a contract. Under the DFARS, which governs Department of Defense contracts, the standard categories are unlimited rights, government purpose rights, and limited rights, with restricted rights for software, SBIR/STTR data rights for small business research contracts, and a separate scheme for commercial data. Which category applies depends mainly on who paid to develop the item the data describes. This page is educational background, not legal advice.
What is a technical data rights assertion?
It is a contractor's formal statement, before delivery, of which data it believes should go to the government with restrictions, on what basis, and with which rights category. DFARS 252.227-7017 requires offerors to attach these assertions to their proposals, signed by someone authorized to bind the company. After award, the contract only allows data with restrictive markings if it is listed in the contract's attachment, and new assertions are allowed only for new information or inadvertent omissions.
What rights does the government get in technical manuals?
Usually the broadest. DFARS 252.227-7013 gives the government unlimited rights in technical data necessary for installation, operation, maintenance, or training purposes, other than detailed manufacturing or process data, regardless of who funded development. The commercial clause, DFARS 252.227-7015, lets the government use that category without restriction too, and the civilian FAR clause, 52.227-14, names manuals and training material for installation, operation, and routine maintenance and repair outright.
How long do government purpose rights last?
Five years by default, or another period the parties negotiate. The period starts when the contract, modification, or option that required development of the item is executed, and when it ends the government has unlimited rights in the data.
What is the difference between DFARS and FAR technical data rights?
The DFARS clauses (the 252.227-70xx series) govern Department of Defense contracts and use the unlimited, government purpose, and limited rights structure. Civilian agencies use the FAR's Rights in Data clause, 52.227-14, which works with unlimited rights, limited rights data, and restricted computer software and has no government purpose rights category. The FAR is being rewritten through rolling class deviations, so check which clause text your solicitation actually cites.
Is a data rights legend the same as a distribution statement?
No. A rights legend states the license the government holds in the data. A distribution statement states who may receive the document at all. A technical manual can carry both, and each has its own rules for format and placement.
Get In Touch
Markings That Survive Every Output?
We build technical manuals whose rights legends and distribution statements stay correct through conversion, reuse, and delivery, and we keep protected engineering detail out of the data you deliver with broad rights.