Technical Data Rights: How to Keep the Government From Giving Your Designs to a Competitor

Published 2026 | TIKC NewsWire

You design something clever, win a contract, and deliver the drawings and technical data the government asked for. Months later you lose the follow-on work because the government took your data, handed it to a competitor, and let them build from it. You feel robbed. But in many cases the government was within its rights, because of how the data was marked when you delivered it. On government work, the markings on your technical data decide who gets to use it, and most contractors never think about them until it is too late.

Why data rights exist at all

The government buys the right to use technical data for a reason: it does not want to be locked into one contractor forever. If only you can read or build from your drawings, it cannot recompete the work or fix the item without you. So the rules set default rights depending on who paid to develop the data. If the government funded the development, it generally gets broad rights. If you developed it entirely at private expense, you can keep much more control, but only if you say so correctly.

The marking is the whole game

This is where contractors lose their edge. To restrict the government’s rights, you have to mark the data with the right legend at delivery. No marking, or a vague one, often defaults to the government getting unlimited rights. There is no do-over for forgetting. The marking is not a formality stamped at the end; it is the legal statement that tells the government what it can and cannot do with your work. Get it right and your private investment stays protected. Leave it off and you may have handed over your crown jewels.

The honesty rule cuts both ways

You cannot just stamp “proprietary” on everything either. Over-marking data, claiming restrictions you are not entitled to, is its own violation and can be challenged and stripped. The rule rewards contractors who know exactly what they developed with their own money and mark only that, accurately. This is the same discipline that keeps you out of trouble on a commercial item determination: claim what is true, prove it, and do not overreach.

What to do now

• Track who paid for development. Know which data you built at private expense and which the government funded, because that sets your rights.
• Mark at delivery, every time. Apply the correct restrictive legend before data leaves your hands; there is no fix after the fact.
• Use the right legend. Match the marking to the rights you actually have instead of a generic “proprietary” stamp.
• Do not over-mark. Claiming restrictions you cannot support can get all your markings challenged.
• Keep development records. Save proof of private funding so you can defend a restrictive marking if the government questions it.

Your technical data is often the most valuable thing you deliver, and the markings are how you keep it yours. The contractors who get burned are not the ones who lacked rights; they are the ones who had the rights and failed to claim them correctly. Track your funding, mark accurately at delivery, and keep your proof, and your designs stay your advantage instead of a competitor’s head start. Brick by brick.

FAQ

What are technical data rights?

They are the government’s rights to use, reproduce, and share the technical data and software you deliver. The scope of those rights depends largely on who funded the development and how the data is marked.

What happens if I forget to mark my data?

Unmarked or improperly marked data often defaults to the government receiving unlimited rights, meaning it can share your work freely, including with competitors. There is generally no way to add restrictions after delivery.

Can I just mark everything as proprietary?

No. Over-marking, or claiming restrictions you are not entitled to, can be challenged. If your markings are found unjustified, you can lose them, so mark only what you can support.

How do I know what rights I have?

It comes down to funding. Data developed exclusively at private expense generally carries the most protection, while government-funded development usually gives the government broad rights. Keep records that show which is which.

Sources

Defense Federal Acquisition Regulation Supplement. (2026). 252.227-7013, Rights in Technical Data.

U.S. Department of Defense. (2026). Guidance on intellectual property and data rights in acquisition.

This article is general information, not legal advice.