Joint Development Agreement
For Informational Purposes Only
A comprehensive R&D collaboration framework for two companies jointly developing technology, products, or processes — with detailed IP ownership, patent prosecution, inventorship workflows, and commercialization provisions designed to prevent the disputes that commonly derail joint development projects.
What This Document Does
A joint development agreement establishes the framework for two companies to collaborate on research, engineering, or product development. It defines the scope of the project, assigns responsibilities, allocates costs, and — most critically — determines who owns the intellectual property that results from the work. The agreement also governs patent prosecution, enforcement, publication rights, materials handling, and what happens when the project ends or one party wants to commercialize the results.
This template uses a modular exhibit structure. The master agreement sets the legal framework, while individual exhibits define the development plan, budget, background IP, ownership model, patent procedures, materials protocols, risk allocation, and exit provisions. This separation allows the parties to negotiate the business terms without reopening the legal architecture.
Why Startups Need This
Startups collaborate on R&D for many reasons: a hardware company partners with a software company to develop an integrated product, two biotech firms combine complementary capabilities to pursue a therapeutic target, a university spinout works with an industry partner to commercialize research, or two technology companies jointly develop a platform. These collaborations generate valuable IP — and without a written agreement, that IP becomes the subject of disputes that can be far more expensive than the development itself.
The most dangerous default rule in joint development is joint patent ownership. Under 35 U.S.C. Section 262, absent an agreement to the contrary, each joint owner of a U.S. patent may practice and license the invention without the other owner’s consent or any obligation to account for profits. This means your development partner could license your jointly owned patent to your direct competitor — legally and without your approval. This template defaults to single-owner models with defined licenses back, using joint ownership only when the parties make a deliberate, informed choice.
Key Provisions Explained
Claim-Level Inventorship Workflow
Inventorship is a legal determination, not a business decision. A steering committee or project manager cannot decide who invented something — that determination must follow applicable patent law and consider the contribution to each claim of the patent application. This template requires prompt invention disclosures with dates, contributors, and supporting records. Patent counsel then maps contributions to specific claims, confirms employee and contractor assignments, and corrects inventorship when claims change during prosecution. The workflow includes execution and recordation deadlines because inventors who leave the company or refuse to cooperate can block patent prosecution entirely.
Single-Owner IP Default
The template offers three ownership models — employer-of-inventors, subject-matter allocation, or lead-owner with license back — and requires the parties to select one in Exhibit D. Under any model, joint ownership applies only to items expressly designated after counsel review. Each model includes defined license-back terms so that the non-owning party retains the rights it needs for its business without the risks of joint ownership. The IP schedule also addresses improvements, data, trained models, software, materials, know-how, documentation, and negative results.
Patent Prosecution and Enforcement
For each invention, Exhibit E identifies the filing lead, consultation rights, countries, outside counsel, and cost allocation. Before abandoning a filing, the lead must give 30 days’ notice so the other party can assume prosecution and costs. The enforcement procedure addresses standing, compulsory joinder (required for joint patents in many jurisdictions), cost advances, settlement vetoes, recovery waterfall, and what happens when one party declines to participate in enforcement. Neither party may settle in a way that admits invalidity, licenses the other’s IP, or imposes obligations on the other without consent.
Background IP Protection
Each party’s pre-existing IP — patents, know-how, software, data, and materials — must be identified in Exhibit C before the project begins. The agreement grants a narrow, nonexclusive license to use background IP solely for performing assigned project work during the term. Commercial rights to background IP require separate licenses defined in Exhibit D. No implied licenses arise from collaboration or disclosure. If background IP is not identified upfront, disputes about what each party brought to the table become extremely difficult to resolve after the fact.
Publication and Confidentiality Balance
Research collaborations often involve parties with different publication incentives — a university partner may need to publish for academic credit, while an industry partner may want to protect trade secrets and file patents first. This template permits proposed publications after a review period, during which the reviewer may remove its confidential information and delay publication for a defined period to allow patent filing. The reviewer may not suppress publication indefinitely. Trade-secret duties survive as long as information qualifies, but the agreement recognizes that legitimate academic and regulatory obligations may require disclosure.
Emerging Provisions (2025–2026)
AI/ML Model and Data Provenance
Joint development increasingly involves training machine learning models on combined datasets, generating synthetic data, or building AI systems that incorporate both parties’ contributions. Traditional IP frameworks do not map cleanly onto trained models — the “invention” is the model weights, which are derived from training data, architecture, and hyperparameters contributed by different parties. This template requires classification of inputs, weights, outputs, derived data, code, documentation, and license restrictions separately, with provenance tracking and a prohibition on commercialization until incompatible terms (including open-source license obligations) are cleared.
Government and Grant Funding Controls
When either party uses government-funded resources, university facilities, or grant-supported personnel, additional IP obligations arise that can override the parties’ contractual arrangements. Federal funding may trigger march-in rights, government-use licenses, or manufacturing-location requirements under the Bayh-Dole Act. University policies may require technology transfer office approval, revenue sharing, or publication rights. This template requires each party to disclose sponsorship, funding source restrictions, and institutional policies before funded work begins, and blocks the use of restricted resources until the rights matrix is reconciled with the agreement’s IP architecture.
Commercialization as a Separate Module
The research license and the commercialization license serve different purposes and should be structured separately. The research license is narrow, nonexclusive, and limited to project performance. Commercialization rights — including field, territory, exclusivity, sublicensing, diligence obligations, milestone payments, royalties, audit rights, patent-cost allocation, stacking provisions, change-of-control effects, and termination triggers — require their own detailed schedule. Leaving commercialization terms for “later” creates the risk that completed research becomes commercially unusable because the parties cannot agree on post-development economics.
How to Use This Template
1. Define the project scope precisely. Exhibit A should specify the field, objectives, specifications, work packages, personnel, facilities, milestones, and acceptance criteria. Work outside the defined scope requires a written change order — this is critical because IP ownership follows the project boundary.
2. Complete the background IP schedule. Exhibit C must identify each party’s pre-existing patents, know-how, software, data, and materials with specificity. Anything not listed is at risk of being claimed as project IP.
3. Select and negotiate the ownership model. Choose employer-of-inventors, subject-matter allocation, or lead-owner with license back. Define the license-back terms, including field, territory, exclusivity, sublicensing, and royalties. Do not default to joint ownership without understanding the consequences under 35 U.S.C. Section 262.
4. Build the patent docket before filing. Establish decision deadlines, filing countries, cost allocation, and step-in rights before the first invention disclosure. Patent deadlines are unforgiving — a missed priority date cannot be recovered.
5. Disclose funding restrictions. If either party will use government-funded resources, university facilities, or grant-supported personnel, disclose the applicable restrictions and reconcile them with the IP architecture before work begins.
Related Forms
This template is provided by Montague Law for informational and educational purposes. It does not constitute legal advice and does not create an attorney-client relationship. Joint development involves patent law, trade-secret protection, inventorship determination, government-funding compliance, data governance, and commercialization economics that vary by jurisdiction, technology area, and funding source. Consult qualified patent and transactional counsel before using this template. Montague Law is a Florida-based law firm focused on corporate, M&A, venture capital, and technology transactions.