IP & Data RightsClause — contract · AUG 2025Flows Down to Subs

DFARS 252.227-7013Rights in Technical Data—Noncommercial Items

Looking for the official text? Read DFARS 252.227-7013 (AUG 2025) at acquisition.gov. It is a contract clause, so it binds the Contractor during performance. Everything below is checked against that text.

Overview

This clause governs the government's rights in technical data for noncommercial items. The government receives unlimited rights in data developed exclusively at government expense, limited rights in data developed exclusively at private expense, and government purpose rights in data developed with mixed funding. Proper data rights marking is essential to protect contractor IP.

This is a clause, not a provision

Clauses go into contracts and bind the Contractor during performance; provisions go into solicitations and bind the Offeror before award. DFARS 252.227-7013 is prescribed with the words “use the following clause”, so it governs how you perform, not how you bid.

When Does This Apply?

All DoD contracts for noncommercial items that involve the creation or delivery of technical data.

Key Requirements

  • 1Mark all technical data with the appropriate rights legend
  • 2Unlimited rights for government-funded data
  • 3Limited rights for contractor-funded data
  • 4Government Purpose Rights for mixed-funded data (5-year restriction)
  • 5Challenge procedures for unmarked or improperly marked data

Flowdown to Subcontractors

Yes — DFARS 252.227-7013 carries its own subcontract flowdown.

Paragraph (l), Subcontractors or suppliers: where technical data will be obtained from a subcontractor or supplier for delivery to the Government, “the Contractor shall use the following clause(s) in the subcontract or other contractual instrument … and require its subcontractors or suppliers to do so, without alteration, except to identify the parties.”

Checked against the clause text at acquisition.gov, read 27 July 2026.

Real-World Example

A mid-size defense electronics manufacturer, Quantum Systems Inc., received a $12M Navy contract to develop a new radar processing unit. During the design phase, they developed proprietary algorithms using $800K of internal R&D funds, while the remaining technical specifications were government-funded. When delivering the technical data package, Quantum initially marked all documentation with 'Limited Rights' legends, claiming full contractor funding. The Navy's contracting officer challenged the markings during the 90-day review period, demanding proof of funding sources. After a costly 6-month documentation review involving $150K in legal fees, Quantum had to re-mark 70% of the technical data with 'Unlimited Rights' legends, effectively giving the government perpetual rights to commercialize their core algorithms. The lesson learned: maintain detailed contemporaneous records of all funding sources during development, and engage intellectual property counsel before marking any technical data deliverables.

Why This Matters for Your Business

This clause fundamentally determines who owns the intellectual property created under DoD contracts, directly impacting a contractor's competitive advantage and future revenue streams. It affects both primes and subcontractors delivering any technical data under noncommercial item contracts. Improper marking can trigger False Claims Act liability, with penalties up to $23,607 per violation plus treble damages. The government can also terminate contracts for cause if contractors refuse to provide properly marked technical data. With CMMC third-party assessment suspended in 2026 and self-attestation now the operative gate, contractors face increased scrutiny of their data handling practices, making proper technical data rights management critical for maintaining security clearances and contract eligibility. The growing emphasis on domestic manufacturing and technology transfer restrictions under ITAR and EAR makes understanding these rights essential for long-term business sustainability.

Compliance Checklist for DFARS 252.227-7013

  1. 1Contracts team must insert appropriate technical data rights clauses into all subcontracts exceeding $25K that involve technical data deliverables.
  2. 2Legal counsel shall establish written procedures for determining funding sources and assigning appropriate rights categories for all technical data.
  3. 3Program managers must maintain contemporaneous funding records linking each technical data element to its government or contractor funding source.
  4. 4IP attorney shall review and approve all technical data markings before delivery to ensure compliance with DFARS 252.227-7013 requirements.
  5. 5Contracts administrator must validate that all delivered technical data contains proper rights legends as specified in paragraph (f) of the clause.
  6. 6Legal team shall implement challenge response procedures to address government disputes over technical data markings within required timeframes.
  7. 7Quality assurance personnel must audit technical data deliverables quarterly to verify proper marking compliance and identify correction needs.
  8. 8Training coordinator shall provide annual DFARS technical data rights training to all program managers and contracts personnel handling noncommercial item contracts.

Estimated Compliance Cost

Initial compliance setup ranges from $25K-$150K depending on company size and existing IP management systems. Mid-size contractors typically spend $75K implementing proper marking procedures, legal review processes, and staff training. Annual ongoing costs average $40K-$80K for maintaining compliance, including IP attorney reviews and marking validation procedures. Non-compliance remediation costs can exceed $500K when including legal fees, re-work, and potential government claims. Implementation timeline spans 4-6 months for most contractors. Cost drivers include: existing contract portfolio size, complexity of technical data deliverables, current IP management maturity, and whether the company has dedicated contracts or legal staff. Companies with robust existing IP processes can achieve compliance for 60% less than those starting from scratch.

Cross-References & Related Requirements

This clause interconnects with DFARS 252.227-7014 (Rights in Noncommercial Computer Software) for integrated software-hardware deliverables, requiring coordinated marking strategies. It flows down through 252.244-7000 (Subcontracts for Commercial Items) to ensure consistent rights allocation throughout the supply chain. The technical data security requirements align with NIST 800-171 control families SC (System and Communications Protection) and MP (Media Protection), particularly SC-28 (Protection of Information at Rest) when storing marked technical data. Under CMMC 2.0, this clause supports Level 2 requirements by establishing data categorization protocols essential for implementing appropriate security controls. Proper implementation satisfies foundational requirements for 252.204-7012 (Safeguarding Covered Defense Information) by ensuring technical data is properly identified and categorized before applying security measures.

How This Clause Affects Your Proposal

This clause appears automatically in all DoD solicitations for noncommercial items requiring technical data deliverables, typically in Section I (Contract Clauses) without modification rights. During source selection, evaluate technical data rights implications early in your bid decision process, as unlimited rights requirements can significantly impact pricing strategy and intellectual property protection. Prepare a Technical Data Management Plan identifying all deliverable technical data, funding sources, and proposed markings as part of your technical proposal. Address potential rights conflicts proactively by proposing alternative technical approaches that minimize contractor-funded intellectual property exposure. Include detailed funding source documentation and marking matrices in your proposal to demonstrate compliance understanding and reduce post-award disputes. For competitive advantages, consider offering broader rights than required to enhance your technical evaluation scores while protecting core proprietary technologies through careful technical data scope definition.

Frequently Asked Questions

What is DFARS 252.227-7013?

DFARS 252.227-7013 (Rights in Technical Data—Noncommercial Items) This clause governs the government's rights in technical data for noncommercial items. The government receives unlimited rights in data developed exclusively at government expense, limited rights in data developed exclusively at private expense, and government purpose rights in data developed with mixed funding. Proper data rights marking is essential to protect contractor IP.

Does DFARS 252.227-7013 flow down to subcontractors?

Yes. DFARS 252.227-7013 carries its own subcontract flowdown. Paragraph (l), Subcontractors or suppliers: where technical data will be obtained from a subcontractor or supplier for delivery to the Government, “the Contractor shall use the following clause(s) in the subcontract or other contractual instrument … and require its subcontractors or suppliers to do so, without alteration, except to identify the parties.”

When does DFARS 252.227-7013 apply?

All DoD contracts for noncommercial items that involve the creation or delivery of technical data.

Is your tech stack DFARS 252.227-7013 compliant?

Run our free CUI Auditor to check if your tools meet this clause's requirements.

Audit Your Tech Stack Free

Turn this gap analysis into a remediation plan

This DFARS 252.227-7013 breakdown is the start, not the answer. Book a 25-minute compliance assessment — you leave with a prioritized roadmap and a fixed-fee implementation quote.

Book a 25-min assessment

Related: how much CMMC certification costs — DoD’s own priced figures

Discussion

Share your experience implementing this in your organization.

Join the Club to unlock joining discussions

Free membership — access intelligence, save your work, and more.

Create free account
Want this clause as structured data?
The full record for DFARS 252.227-7013 — applicability, requirements, NIST 800-171 mappings, FAQs — is in our open dataset on GitHub: clauses/252-227-7013.json. Free under CC-BY-4.0.