Data Rights in Government Contracts: Protecting Your IP

Data rights in government contracts refer to the government's license to use, modify, reproduce, and distribute technical data and software delivered under a contract.

Key concepts:

• Technical data — Documentation, drawings, specifications
• Computer software — Code, programs, databases
• License rights — What government can do with your data
• Intellectual property — Your underlying IP rights

Why data rights matter:

• Protects your competitive advantage
• Determines who can use your work
• Affects recompete dynamics
• Impacts commercialization opportunities

Governing regulations:

• FAR 27.4 — Rights in data (civilian)
• DFARS 227.71 — Technical data (DoD)
• DFARS 227.72 — Computer software (DoD)

Unlimited rights:

• Government can use, modify, reproduce, disclose
• Can share with anyone for any purpose
• Applies to data developed entirely at government expense
• No restrictions on government use

Limited rights (technical data):

• For data developed at private expense
• Government can use within government only
• Cannot release outside government without permission
• Protects your commercial advantage

Restricted rights (software):

• Commercial software equivalent of limited rights
• Government use only for specified purposes
• Cannot modify or reverse engineer (typically)
• Protects your software investment

Government purpose rights:

• DoD concept for mixed funding
• Government can use for government purposes
• Can share with other contractors for government work
• Converts to unlimited rights after 5 years (typically)

SBIR data rights:

• Special protection for SBIR/STTR-funded data
• Protection period of up to 20 years
• Encourages small business innovation

Funding source is key:

The primary factor determining data rights is who paid for development:

Government-funded development:

• Government typically gets unlimited rights
• Developed with contract funds
• Created specifically for the contract

Contractor-funded development:

• Contractor retains limited/restricted rights
• Developed with your own IR&D or commercial investment
• Pre-existing before the contract

Mixed funding:

• Government purpose rights (DoD)
• Negotiated allocation (civilian)
• Document funding sources carefully

Commercial items:

• Commercial technical data — license rights only
• Commercial software — license per commercial terms
• Preserved commercial value

Before the contract:

• Identify pre-existing IP you'll use
• Document development history
• Understand contract data rights clauses
• Negotiate favorable terms where possible

Marking requirements:

Proper marking is essential:

• Mark limited rights data appropriately
• Use required legends and notices
• Apply markings at delivery
• Maintain marking records

During performance:

• Track funding sources for all development
• Segregate government-funded from private-funded work
• Document your investments
• Apply appropriate markings to deliverables

Assertion process (DFARS):

• Identify and assert restrictions before award
• List items in contract schedule
• Justify the basis for restrictions

DFARS data rights framework:

DoD has detailed rules in DFARS 252.227-7013 (technical data) and 252.227-7014 (software).

Pre-award assertions:

• Must identify restrictions in proposal
• List specific items with restrictions
• Cite basis for restriction
• Failure to assert may forfeit rights

Challenge process:

• Government can challenge assertions
• Contractor must justify restrictions
• Burden on contractor to prove basis
• Potential loss of restrictions if unsupported

Deferred ordering:

• Government can order data later
• Must pay fair compensation
• Can require delivery of previously undelivered data

Validation:

• Government can validate markings
• 3-year window after delivery (typically)
• You must provide evidence of basis

Computer software documentation:

• Follows technical data rules
• Same unlimited/limited rights framework
• Documentation separate from code

Computer software:

• Code, programs, databases, documentation
• Restricted rights = limited rights equivalent
• Source code vs. object code considerations

Commercial software:

• License per commercial terms
• Government accepts standard license
• May negotiate government-specific terms

Open source considerations:

• Open source components retain their licenses
• May affect your ability to restrict
• Disclose open source usage

Source code escrow:

• Government may require escrow
• Released only under specific conditions
• Protects government access if contractor fails

Incumbency advantage:

Your data rights can provide competitive advantage:

• Competitors may need access to your data
• Limited rights data may not be shared
• Reduces competition in some cases

Government's response:

• May require unlimited rights
• May negotiate broader licenses
• May work around restricted data
• Leveling provisions in recompete

Technical data packages:

• Government may share TDPs with competitors
• Restricted data excluded
• Can affect competitive landscape

Protecting your position:

• Assert restrictions properly
• Mark data correctly
• Document your investments
• Understand what government can share

Areas for negotiation:

• Scope of government license
• Duration of restrictions
• Specific items covered
• Marking procedures

Leverage points:

• Pre-existing IP you're bringing
• Commercial items
• SBIR/STTR protections
• Your investment level

Common negotiated terms:

• Specific restricted items list
• Extended protection periods
• Narrower government purpose scope
• Clearer commercialization rights

Proposal strategy:

• Identify IP early
• Make assertions in proposal
• Be prepared to justify
• Know what you can't concede

Red flags:

• Broad unlimited rights requirements
• No recognition of pre-existing IP
• Unreasonable challenge provisions