Clear and precise recognition and treatment of intellectual property (IP) are critical in government contracting because the ownership and use of preexisting IP, so-called “Background IP,” turn on the timing of, and funding sources for, the development of the IP. Therefore, internal documentation and standardized procedures for tracking and marking IP are crucial in the event of a dispute regarding the development, use, or ownership of IP before, during, and after performance on a government contract.

Those involved in negotiating contracts to develop collaborative technology, whether with the government or other commercial operators in the supply chain, are aware that it is important to define the rights and responsibilities of the parties with respect to any new IP.

All too often, however, these contracts purport to exclude preexisting IP without much fanfare. But a blanket exclusion of Background IP without any itemization or acknowledgment of what existed before the collaboration is a recipe for disaster, especially if the contractor does not maintain proper internal documentation.

Contractor IP often underpins technical differentiation, pricing, and performance. Internal tracking and documentation of IP are essential to protect proprietary assets, meet contractual and regulatory obligations, and preserve competitive advantage.

Both FAR and DFARS define ownership and licensing rights with respect to IP in terms of when the IP was developed and with what resources. “Background IP” refers to IP, data, or materials that existed prior to, or were developed outside the scope of, the specific government contract but may nevertheless be used in performing that contract or otherwise disclosed during performance, whether such disclosure was planned or not. In the defense context, the key regulatory provisions governing these rights are found in DFARS 252.227-7013 (Rights in Technical Data—Noncommercial Items) and DFARS 252.227-7014 (Rights in Computer Software—Noncommercial Items). For commercial items, DFARS 252.227-7015 governs technical data rights. These clauses establish the framework that determines what rights the government receives based on how and when the IP was developed, making the identification and segregation of Background IP a regulatory imperative, not merely a best practice.

Common categories of IP that may be used or disclosed during a project include:

• Patents and patent applications or potentially patentable inventions
• Copyrighted works, software, and databases
• Trade secrets, proprietary technical data, and know-how
• Third-party IP licensed to the contractor

Under the DFARS framework, the government’s rights in each of these categories will generally fall into one of three tiers: unlimited rights, government purpose rights, or limited rights (for technical data) or restricted rights (for computer software). Which tier applies depends on the development history and funding source of the particular asset. Properly categorizing Background IP at the outset is therefore essential to ensure it receives the appropriate restrictive markings and is not inadvertently delivered with broader rights than the government is entitled to receive.

Patents and patent applications, copyrights, and trademarks are usually filed or registered with the government and so will eventually be public information; trade secrets, proprietary and confidential technology or processes, business records, and other unpublished written materials, however, are valuable in part because of their proprietary nature. Therefore, while publicly filed or registered patents, trademarks, and copyrights are easily dated (at least from the date of filing or registration), a trade secret or confidential business process may not be so easily tracked. Without specific documentation and dating of proprietary materials, it may be difficult to prove, years later, what was preexisting and what was developed during performance. Without disciplined internal documentation, contractors risk unintentionally granting broader rights to the government or third parties, losing trade secret protection, or compromising future commercialization.

Best Practices for Accurate IP Records

In collaborative agreements or contracts for research and development, Background IP tends to be considered conceptually but not given any concrete meaning. For example, if a contract defines Background IP as “all intellectual property rights owned by or licensed to a Party at the start of the Contract,” this definition is merely acknowledging a concept without giving it any metes or bounds. In the event of a dispute regarding what IP was preexisting versus developed during performance on the contract, the Parties could litigate this issue ad nauseam.

A savvy contractor, therefore, should maintain strict processes to accurately track, date, and mark all IP developed by the company, both before and during performance on any contract, but particularly contracts involving the government.

Some best practices for protecting Background IP:

• Establish a centralized IP register: Maintain a single source that captures each asset’s description, owner, contributors, funding source, development status, export classification, third-party content, applicable contract clauses, legends, and deliverable mapping.

This may seem overwhelming or even impossible at first, but once the processes are in place, stakeholders will quickly become accustomed to maintaining such detailed documentation.

• Tie records to life cycle gates: Embed IP checkpoints in R&D, proposal, contract kickoff, design review, release management, and closeout. Require confirmation of legends and rights assertions before deliverables are finalized.

Checkpoints ensure that no novel development goes undocumented, and legends are crucial because failure to accurately mark deliverables can result in the government obtaining unlimited rights in a contractor’s Background IP.

• Track funding and cost records: Attribute development activities to specific funding sources, with contemporaneous timekeeping and cost records to support rights assertions.

Because FAR and DFARS define certain IP rights in terms of funding sources, accurately tracking funding is key to asserting rights in Background IP. Specifically, DFARS recognizes three development funding categories: items developed exclusively at private expense, items developed exclusively at government expense, and items developed with mixed funding. Each category triggers a different level of government rights. Maintaining clear, contemporaneous cost-accounting records that map development activities to these funding buckets is the single most important evidentiary foundation for any rights assertion or challenge.

• Standardize markings and templates: Adopt approved legends and implement document controls that prevent alteration or removal. Use standardized rights assertion forms with substantiation attachments.

As with the IP register, once processes are in place, using standardized marking should become second nature, particularly in light of DFARS 252.227-7037, where the government has the right to challenge nonconforming or unjustified markings and the contractor bears the burden of substantiating its asserted restrictions. If a contractor cannot justify its markings within the prescribed response period, the contracting officer may strike the restrictive legend entirely, potentially converting proprietary Background IP to data in which the government holds unlimited rights.

• Implement invention disclosure workflows: Provide accessible disclosure portals, prompt evaluation, and calendaring for reporting and election deadlines. Maintain links to patent filings and government communications.

Most companies with sophisticated engineers and developers have processes for invention disclosures and internal IP counsel; best practices would require disclosure workflows even if the company utilizes outside IP counsel for actual filings because they require developers to consistently be thinking of their work in terms of novelty and what may be a proprietary development. This sort of tracking is key to asserting rights in Background IP even if no patent application is ultimately filed. Federal contractors should also be aware of their obligations under FAR 52.227-11 (Patent Rights—Ownership by the Contractor) or  its DFARS counterpart, which impose specific timelines for disclosing subject inventions, electing title, and filing patent applications. Missing these deadlines can result in the government obtaining title to an invention that the contractor might otherwise have retained. Integrating these regulatory deadlines into the invention disclosure workflow ensures that contractual obligations and internal IP strategy remain aligned.

• Monitor subcontractor IP: Require early assertions, approved legends, and development histories. Maintain supplier IP summaries that are aligned to the prime contract.

Requiring a subcontractor to maintain the same best practices as the prime contractor ensures another layer of protection from rights disputes.

• Integrate security and access controls: Restrict access to proprietary materials to those with a demonstrated need, log access, and align it with cybersecurity and export regimes. Preserve incident and remediation records.

Because wide swaths of IP are only valuable if maintained as confidential, such as trade secrets, to assert those rights you will have to prove that you took all reasonable steps to maintain the secrecy of the information. Again, while these procedures may seem onerous, they are key to maintaining the value of Background IP.

• Train and audit: Conduct periodic training for engineering, contracts, and program teams. Perform internal audits of deliverables, legends, and registers; remediate gaps and document corrective actions.

As discussed above, once processes are in place, stakeholders need to be trained on them and audited to ensure compliance. Consistent training and auditing are what turn these processes from esoteric thought exercises into value creation for the company.

• Govern with policy: Adopt an executive-approved IP management policy assigning roles, responsibilities, escalation paths, and documentation standards. Review annually and upon major contract or regulatory changes.

While engineers may be at the forefront of invention, it is key that IP value is recognized on a company-wide basis. IP policies should be developed and maintained from the top down.

Ambiguity with respect to Background IP can lead to unintended rights transfers, impediments to performance, data-rights disputes, and barriers to future commercialization. Without a clear itemization of preexisting IP and contemporaneous documentation of new IP, any subsequent dispute over who owns or otherwise can use or share IP following a collaborative contract can become an expensive game of they-said/they-said.

These disputes are adjudicated before the Armed Services Board of Contract Appeals or the Court of Federal Claims, and contracting officers and DCMA personnel may raise data-rights challenges during performance, at delivery, or even years later, during contract closeout. The applicable case law serves to demonstrate that contractors with disciplined, contemporaneous documentation are going to fare better than those attempting to reconstruct development histories after the fact. Implementing best practices for internal documentation will help ensure that Background IP retains its value and that development timing and funding sources are easily substantiated in the event of a dispute.