Research And Development Agreements: US IP Terms

Maya runs a small skincare brand and hires a product lab to develop a new serum formula. The lab uses its existing testing methods, Maya shares her customer research and brand plans, and together they land on a formula that could become her next hero product.

Then comes the awkward question: who actually owns the formula, the test data, the know how and any patentable improvement?

That question is exactly why the IP terms in a research and development agreement matter. A good R&D agreement doesn't just describe the project. It sets out who can use what, who owns new IP, what stays confidential and how the results can be commercialized.

If you're working with a lab, university, manufacturer, software developer under a software development agreement, engineer, consultant or another company on product development, it's worth getting these points clear before the work starts.

What Is An R&D Agreement And When Do You Need One?

An R&D agreement is a contract that sets the rules for a research or product development project, and you need one whenever your business is paying for or contributing to work that could create valuable IP.

R&D projects can be exciting because you're building something new. They're also easy to misunderstand because both sides often bring something valuable to the table.

Your business might contribute:

• Product ideas, customer insights or technical requirements
• Existing designs, software, formulas, data or brand materials
• Funding, equipment or access to your customers or systems
• Commercial plans, market research or pricing strategy

The other party might contribute:

• Scientific, engineering or technical expertise
• Existing tools, code libraries, lab methods or test processes
• Staff, facilities, equipment or specialist data
• Improvements or inventions created during the project

Your agreement should turn those contributions into clear legal rights. That usually means covering scope, milestones, payment, deliverables, confidentiality, IP ownership, licenses, publication rights, warranties, liability and termination.

For IP specifically, the most useful starting point is to separate background IP from foreground IP.

• Background IP is IP a party already had before the project, or develops outside the project.
• Foreground IP is IP created during or because of the project.

Once you separate those two buckets, the rest of the agreement becomes much easier to draft and negotiate.

Who Owns The IP Created During R&D?

It depends, but you should never assume that paying for R&D automatically gives your business ownership of the IP created.

Under US law, different types of IP have different default rules. A contract can usually change the commercial outcome, but only if it uses the right language.

Patent Rights

Patent rights usually start with the human inventors who actually conceived the invention. If you want your business to own patentable inventions created during the project, you need a written assignment from the inventors or from the company that has already secured those assignments.

For example, if a consultant working for a development firm invents a new sensor design during your project, your agreement with the firm should require the firm to:

• Secure invention assignments from its staff and contractors
• Assign the project inventions to your business, if that's the agreed deal
• Help with US Patent and Trademark Office filings
• Sign any further documents needed to record or confirm ownership

The US uses a first inventor to file patent system. Public disclosures can also create real problems, especially outside the US. The US has a limited one year grace period for some inventor disclosures, but many other countries don't. If patents may matter, keep the project confidential and get patent advice before pitching, publishing or launching.

Copyright

Copyright ownership usually starts with the person or company that creates the work, unless there's a valid work for hire agreement or a written assignment.

The Copyright Act has specific rules for work made for hire. For employees, works created within the scope of employment can belong to the employer. For independent contractors, work made for hire only applies to certain categories of work and generally needs written wording signed by both parties.

Because R&D often involves software, drawings, manuals, datasets, reports and technical documentation, it's safer to include a clear copyright assignment where ownership needs to transfer. You can also add a backup license in case any part of the assignment doesn't work as expected.

Trade Secrets And Know How

Trade secrets are protected when the information has economic value because it's secret and you take reasonable steps to keep it secret. The federal Defend Trade Secrets Act is a key law here, alongside state trade secret laws.

In an R&D agreement, trade secrets might include formulas, source code, testing methods, manufacturing settings, negative results and technical learnings that never get patented. These can be just as valuable as registered IP.

Your agreement should say who owns the know how created during the project, who can use it after the project ends and what security measures each party must follow.

How Should Background IP And Confidentiality Work?

Background IP should stay owned by the party that brought it to the project, with only the limited license needed to perform the R&D.

This is one of the most common pressure points in R&D negotiations. Your business may need to share existing technology, designs, product plans or data so the other party can do the work. That doesn't mean they should be free to use those materials for other clients or future products.

A practical background IP clause should cover:

• Ownership: each party keeps what it already owns.
• Project license: each party grants only the license needed to perform the project.
• No implied rights: nothing is licensed unless the agreement says so.
• Restrictions: no reverse engineering, copying, reuse or disclosure outside the project.
• Return or deletion: confidential materials should be returned or securely deleted when no longer needed.

Confidentiality Terms

Confidentiality terms should protect both the information you disclose and the information created through the project.

They should usually cover:

• What counts as confidential information
• How confidential information can be used
• Who can access it within each organization
• How long confidentiality lasts
• Security standards, especially for sensitive technical files or data
• What happens if there's an unauthorized disclosure

If the agreement covers employees or contractors and trade secrets, the Defend Trade Secrets Act has a whistleblower immunity notice rule. Missing that notice can affect your ability to recover certain enhanced remedies and attorney fees in a trade secret claim, so it's worth handling this carefully in your contract wording.

Personal Data And Testing Data

If your R&D project involves user testing, health information, customer data, device data or app analytics, your agreement should also cover data rights, any data license terms and privacy obligations.

The Federal Trade Commission Act gives the FTC authority to act against unfair or deceptive business practices, including misleading privacy and security practices. State privacy laws and industry rules may also apply depending on your business, your users and the data involved.

Your agreement should make clear who can use testing data, whether it can be anonymized or aggregated, who must provide privacy notices and what happens if there's a data incident.

Can You Commercialize The R&D Results?

You can commercialize the results only if the agreement gives your business the ownership, license and practical rights needed to do so.

Ownership isn't the only issue. Your business may own the foreground IP but still need licenses to background IP, lab methods, embedded software, materials, datasets or manufacturing know how to actually sell the product.

Think about commercialization from day one. Ask yourself: if this project succeeds, what will we need to manufacture, market, sell, license or improve the product?

Your R&D agreement should address:

• Field of use: can you use the results in all industries, or only in a specific market?
• Territory: are rights worldwide or limited to certain countries?
• Exclusivity: are you the only party allowed to use the results?
• Sublicensing: can you allow manufacturers, distributors, affiliates or customers to use the IP?
• Royalties: will the other party receive a royalty, milestone payment or revenue share?
• Improvements: who owns improvements made after the initial project?
• Publication: can the other party publish research papers, case studies or marketing materials?
• Regulatory support: who keeps records and provides information needed for product approvals?

Say you pay an engineering consultant to help develop a new bike accessory. You might own the final design files, but if the consultant used a proprietary hinge mechanism they already owned, you may need a license to that mechanism and a product supply agreement before you can manufacture at scale.

This is where template documents often miss the mark. The right clause depends on what the project is creating, what each party is contributing and how you plan to make money from the results.

What Patent, Copyright And Trademark Terms Should You Include?

You should include IP terms that match the type of assets your project is likely to create, because patents, copyright and trademarks are protected and transferred in different ways.

Patent Terms

If the project could create inventions, your agreement should set out who decides whether to file patent applications, who pays, who controls prosecution and who owns the resulting patents.

You may also need clauses covering:

• Prompt disclosure of inventions
• Inventor cooperation and signatures
• Recordkeeping for lab notebooks, design files and invention dates
• Confidentiality before filing
• USPTO assignment recordation
• Responsibility for maintenance fees after a patent is granted

If you work with a university, hospital, government funded lab or research institution, their internal policies and funding obligations may limit what they can assign. US federal funding rules, including the Bayh-Dole Act, can affect ownership and government rights in some inventions. Don't assume a sponsor automatically receives full ownership.

Copyright Terms

If the project creates software, reports, diagrams, training materials, product copy, CAD files, videos or documentation, your agreement should include copyright terms.

These terms should say whether your business owns the work, receives an exclusive license or receives a nonexclusive license. If you need to modify, reproduce, distribute or sublicense the materials, say that clearly.

Copyright registration with the US Copyright Office can strengthen enforcement options. For many US works, registration is generally needed before filing a copyright lawsuit, and timely registration can help preserve statutory damages and attorney fee options.

Trademark Terms

Trademarks protect brand names, logos, slogans and other source identifiers. Under the Lanham Act, trademark rights are tied to use in commerce and goodwill, not just who thought of the name first.

If your R&D partner helps name the product, design a logo or prepare packaging, your agreement should make clear that your business owns the brand materials and can register marks with the USPTO. It should also prevent the other party from using confusingly similar names or presenting the product as their own.

Warranties And Third Party IP

Your agreement should also deal with third party IP risk. For example, if the lab uses a third party dataset, open source code, licensed material or patented component, you need to know whether that affects your ability to commercialize.

Depending on the deal, you might ask for warranties that the deliverables don't knowingly infringe third party rights, or an obligation to identify third party materials. State contract law and the Uniform Commercial Code may also affect warranties where the project involves goods, prototypes or manufactured items.

Frequently Asked Questions

Do We Need A Separate NDA Before The R&D Agreement?

Often, yes. If you need to share sensitive information before the full R&D agreement is signed, a separate NDA can protect early discussions. Once the R&D agreement is signed, it should include more detailed confidentiality terms.

Is Joint Ownership A Good Idea?

Sometimes, but it can be messy. Patent co owners may have rights to use or license the patent without accounting to the other co owner unless the contract says otherwise. Joint copyright ownership can also complicate exclusive licensing and commercialization. If you choose joint ownership, spell out exactly how decisions, costs, licenses and revenue will work.

Can The Other Party Use The Results For Other Clients?

It depends on the ownership, license, confidentiality and exclusivity clauses. If you need exclusive product development, the agreement should clearly restrict the other party from reusing your foreground IP, confidential information and project specific materials in competing work, while recognizing that general skills and nonconfidential know how may need separate treatment.

What If The Project Fails Or Gets Terminated?

Your agreement should say what happens to work in progress, unpaid fees, prototypes, test data, confidential information and IP created before termination. Failed R&D can still produce valuable know how, so don't leave those rights unclear.

Key Takeaways

• Don't assume paying for R&D means your business owns the IP. Put ownership and assignment terms in writing.
• Separate background IP from foreground IP so each party knows what they can use during and after the project.
• Confidentiality terms should protect trade secrets, test data, commercial plans and technical know how.
• Commercialization rights matter as much as ownership. Check exclusivity, sublicensing, territories, royalties and improvement rights.
• Patent, copyright and trademark terms need different wording because US law treats each type of IP differently.
• If your project involves universities, federal funding, personal data or regulated products, get tailored advice before signing.

If you'd like help with your R&D agreement, IP ownership terms, confidentiality protections or commercialization rights, you can reach our team at (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they're provided by licensed US lawyers at ElevateNext US, LLC, a trusted US law firm, through the Sprintlaw platform.