GPR

Government Purpose Rights (GPR) let the government use, modify and disclose technical data or computer software for any government purpose. A government purpose includes release to a competitor, but excludes commercial use. By default, GPR converts to unlimited rights five years after execution of the contract.

GPR is the standard outcome for items developed with mixed funding. DFARS 252.227-7013 defines it for technical data. DFARS 252.227-7014 defines it for computer software.

Note the current clause titles. DoW replaced "noncommercial" with "other than commercial" in this clause family. 252.227-7013 now reads "Rights in Technical Data—Other Than Commercial Products and Commercial Services." 252.227-7014 now reads "Rights in Other Than Commercial Computer Software and Other Than Commercial Computer Software Documentation." Older guidance keeps the previous wording.

The five-year clock is the part people miss

Under the standard clauses, the government purpose rights period runs five years from execution of the contract requiring delivery. The parties may negotiate a different period. When the period expires, the rights of the government become unlimited. That change happens automatically, without notice, and without any further action by either party. The government may then release the item to anyone for any purpose, including commercial purposes.

This is negotiable. The five-year period is a default, not a statute, and the clause explicitly contemplates a different negotiated period. Almost nobody negotiates it, because almost nobody reads the clause until year four.

The rights ladder

The DoW data rights framework runs roughly from most to least government access:

• Unlimited rights — the government funded the development exclusively. Some categories carry unlimited rights regardless of funding: form, fit and function data, operation and maintenance manuals, data necessary for installation and operation, and similar categories.
• Government purpose rights — mixed funding. The period applies, and unlimited rights follow.
• Limited rights — technical data developed exclusively at private expense. The government may use it internally only, and may not release it outside the government except in narrow circumstances.
• Restricted rights — the software analogue of limited rights, with its own use and copying constraints.
• SBIR data rights — a separate regime under DFARS 252.227-7018 for data generated under a Small Business Innovation Research (SBIR) or Small Business Technology Transfer (STTR) award. It carries its own protection period.
• Specifically negotiated license rights — anything the parties agree to that differs from the standard categories.

The determining question for the standard categories is who paid for the development. The answer does not depend on who wrote it, who owns the copyright, or what the contract calls it.

The assertion table — DFARS 252.227-7017

DFARS 252.227-7017 requires an offeror to identify, before award, every item of technical data or computer software it intends to deliver with restrictions. The offeror submits the assertion as a table with four columns:

1. The technical data or computer software that the offeror will furnish with restrictions.
2. The basis for the assertion — the funding basis.
3. The asserted rights category.
4. The name of the person who asserts the restriction.

The consequence of an omission is severe. An item you fail to assert can go to the government without the restriction you intended, and the omission is difficult to fix after award.

Two rules regularly trap people. Mixed funding produces GPR, not limited or restricted rights. An assertion of limited rights on mixed-funded data is a common and rejectable error.

Firmware needs decomposition. The hardware element and the embedded software element can carry different funding histories and therefore different rights categories. An assertion of a single category over the whole assembly is usually wrong.

The mistake that makes this term matter

A company builds something on a program with a mix of its own money and government money, asserts government purpose rights on it because that is what mixed funding produces, and then treats the matter as closed. The assertion was correct. The proposal cleared review. Everyone moved to the next contract.

Five years is a long time in a small business. The engineers who knew the funding history left, the program moved into sustainment, and the module quietly became the piece of the product the company competes on. Nobody watches a date, because there is no date to watch. The clause generates no reminder, the contracting officer sends no letter, and nothing in the contract file changes on the day the rights convert. The company finds out when the government releases the item to a competitor, entirely within its rights to do so.

What goes wrong in practice

Someone assembles the assertion table the week the proposal is due. A company should maintain it continuously as an IP inventory. The table depends on funding history that nobody can reconstruct under deadline pressure.

Nobody tracks expiration. GPR granted on a contract signed years ago quietly matures into unlimited rights while the company still believes the item carries protection. There is no notice, no reminder, and no reversal.

The company asserts the funding basis instead of documenting it. "Developed at private expense" is a factual claim about the source of the money, and a challenge can test it. Keep the independent research and development (IR&D) records that support it.

What to do

1. Maintain a standing inventory of deliverable technical data and software.
2. Record a documented funding basis for every item in that inventory.
3. Update the inventory as development happens, not at proposal time.
4. Track the expiration date of every GPR grant against the contract that created it.
5. Decide well before that date whether the expiration matters commercially.
6. Where an item is core to your business, negotiate the period or the category before award.
7. Decompose firmware into its hardware element and its embedded software element.

That negotiation is possible before award and effectively impossible after award.

Strategies that keep your rights

These are the levers contractors actually use. Every one of them works before award and most of them stop working after it.

Fund the core privately, and prove it. Rights follow the money. Development you pay for entirely yourself produces limited rights, not government purpose rights. That claim only survives a challenge if your accounting supports it, so keep the IR&D records that show which project paid for what.

Segregate the crown jewels from the deliverable. A module you develop under a contract carries the rights that contract creates. The same module developed separately, then used, does not. Decide which side of that line each piece of your product sits on before you write the proposal.

Deliver the level of detail the contract requires, and no more. Form, fit and function data carries unlimited rights whatever you do. Detailed manufacturing and process data is what you protect. A deliverable specified as "drawings" and satisfied with full design disclosure gives away more than the contract asked for.

Negotiate the period on the items that matter. The five-year term is a default. The clause contemplates a different period. Almost nobody asks, which means almost nobody is refused for asking.

Mark every deliverable correctly, at delivery. An unmarked deliverable can lose its restriction. A wrongly marked one invites a challenge. The legend text is prescribed. Use the prescribed text.

Decompose firmware and integrated assemblies. Hardware and embedded software can carry different funding histories and different rights categories. One category asserted over a whole assembly is usually wrong and is an easy challenge for the government to win.

Put the expiration dates somewhere a person will see them. Nothing in the contract reminds you. Five years passes, the staff who knew the funding history leave, and the conversion happens silently.

Consider a specifically negotiated license. The standard categories are defaults, not a menu you must choose from. Where an item is central to your commercial business, a bespoke license is available and is the mechanism built for exactly that case.

What GPR is not

Government purpose rights are not a transfer of ownership. They are also not a patent license. The Bayh-Dole framework and its implementing clauses govern patent rights separately.

During the government purpose period, GPR does not permit the government or its recipients to exploit the item commercially. The restriction on commercial use is the whole point of the category. It is also the thing that disappears when the period expires.

When you need an answer that binds

Data rights is one of the places where a good general answer and a correct specific one can differ. The category that applies to your item turns on funding history, on what was asserted and when, and on the exact clause in your contract. None of that is visible from a page like this one.

If you have a question in that territory, talk to us about who to solicit legal advice from. We would rather point you toward counsel who works in this area than guess at the answer ourselves.

Silas™ maintains the assertion inventory and tracks each government purpose rights expiration date against the contract that created it.