Joint Development Agreement Attorney — Austin, Texas
When two or more parties collaborate on developing new technology, a joint development agreement establishes upfront who owns the resulting intellectual property, how costs and revenues are shared, and what each party can do with jointly developed innovations — preventing ownership disputes before they arise.
Home → Practice Areas → Joint Development Agreements
Background IP, Foreground IP, and Sideground IP — Defining the Categories
Sophisticated joint development agreements distinguish among at least three categories of intellectual property that are relevant to the collaboration — and the treatment of each category is separately negotiated based on each party's interests and contributions.
Background IP refers to intellectual property that each party brings to the collaboration — innovations developed independently before the collaboration began that are contributed to or used in the collaborative work. Background IP typically remains owned by the contributing party, with each party granting the other a license to use its background IP for the purposes of the collaboration. The scope of that background license — whether it is limited to collaboration purposes, whether it extends to commercialization of collaboration results, whether sublicensing is permitted, and whether the license survives termination of the collaboration — is one of the most heavily negotiated provisions in joint development agreements.
Foreground IP refers to intellectual property developed in the course of the collaboration — the new innovations that the collaboration is designed to produce. How foreground IP is owned and licensed is the central IP question in any JDA negotiation. Options range from all foreground IP owned by one party with a license to the other, to foreground IP divided by technical field or application area, to joint ownership of all foreground IP with specified licensing rights, to a collaborative ownership entity that holds the IP for both parties' benefit. The right structure depends on each party's intended commercial use of the collaboration results, the relative contributions of the parties, and the anticipated licensing and enforcement strategy for the resulting IP.
Sideground IP — sometimes called feedforward IP — refers to innovations developed by one party during the collaboration period that relate to the collaboration subject matter but were not developed as part of the collaboration work itself. Whether sideground IP is captured by the JDA's foreground IP provisions or treated as the developing party's independent background IP is a definitional question with significant practical consequences — and one that generates disputes in collaborations that did not address it clearly upfront.
University-Industry Joint Development Arrangements
University-industry research collaborations are among the most productive sources of genuinely novel technology innovation — and also among the most complex IP ownership arrangements to negotiate, because university IP policies, federal funding obligations, and academic publication norms all intersect with the industry sponsor's commercial IP interests in ways that require careful structural navigation.
Most major research universities — including UT Austin — have IP policies that vest ownership of inventions made using university resources or in the course of university research employment in the university, with the university's technology transfer office managing licensing. When a company sponsors university research, the standard expectation is that the sponsoring company can negotiate a license to any IP that results from the sponsored research — but ownership typically remains with the university unless specifically negotiated otherwise.
The specific IP provisions available in university-industry sponsored research agreements vary significantly by institution, research program, and negotiating context. Key provisions that industry sponsors should negotiate include the scope of the company's license rights to research results — whether exclusive or non-exclusive, the field of use, the territory, and the royalty terms; the company's option rights to negotiate a license to inventions before the university begins licensing to others; the publication delay provisions that give the company time to file patent applications before the university's researchers publish; the treatment of inventions made jointly by university and company employees; and the interaction with federal funding obligations if any of the research is supported by government grants. I advise industry clients on university JDA negotiations with knowledge of UT Austin's specific IP policies and standard negotiating positions — information that gives company negotiators a practical advantage in reaching favorable terms efficiently.
International Joint Development — Cross-Border IP Complications
Joint development arrangements between US and foreign companies create IP ownership and licensing complications that purely domestic arrangements do not involve — including the interaction of different national IP laws governing inventorship and ownership, export control regulations that may restrict sharing of technology and IP with foreign parties, and the enforcement implications of joint ownership across jurisdictions where joint ownership rules differ significantly from US law.
In many foreign jurisdictions — including Germany, Japan, and China — joint ownership of patents carries different legal implications than US joint ownership. In some jurisdictions, a joint owner cannot independently license the jointly owned patent without the other joint owner's consent — which is the opposite of US law and creates significant complications when US and foreign partners try to apply the JDA's IP provisions across both jurisdictions. A JDA that establishes IP ownership rules based on US law without addressing the implications of those rules in the relevant foreign jurisdictions can produce unintended and commercially damaging results when the parties try to commercialize the collaboration results internationally.
Export control regulations — including the Export Administration Regulations and International Traffic in Arms Regulations — impose restrictions on sharing controlled technology with foreign nationals and foreign companies, including in the context of joint development collaborations. Technology in semiconductor manufacturing, certain software with encryption capabilities, optical systems with defense applications, and medical devices with dual-use potential can be subject to export control requirements that affect what can be shared with foreign collaboration partners, how jointly developed IP can be licensed internationally, and what documentation and compliance procedures the collaboration must maintain. I advise clients on the intersection of export control compliance and international joint development IP strategy — ensuring that collaboration arrangements achieve their commercial objectives within the applicable regulatory framework.
When Joint Development Arrangements Go Wrong — And How to Prevent It
Joint development collaborations fail — sometimes technically, sometimes commercially, and sometimes because the parties' interests diverge after the collaboration produces valuable results. The IP provisions of the JDA determine who controls the resulting IP in each of these failure modes, which in turn determines the practical consequences of collaboration termination for each party.
Technical failure — the collaboration does not produce the intended innovations — is the simplest case from an IP perspective. Each party retains its background IP, and if the JDA was well drafted, the question of who owns the minimal foreground IP actually generated is addressed clearly. The more consequential failure modes from an IP perspective are commercial disagreement — the collaboration succeeds technically but the parties cannot agree on how to commercialize the results — and interest divergence — one party is acquired, pivots its business strategy, or changes management in ways that alter its approach to the collaboration and the resulting IP.
Well-drafted JDA provisions address these failure modes specifically. Deadlock resolution mechanisms for commercialization disputes — including forced buyout provisions, independent licensing decisions after a specified period of deadlock, and arbitration of licensing strategy disputes — prevent commercially valuable IP from being locked up by parties who cannot agree on how to use it. Change of control provisions that determine the fate of collaboration IP and licensing rights when one party is acquired — including whether the surviving party has the right to terminate the collaboration, buy out the other party's IP rights, or require the acquirer to assume the collaboration obligations — protect both parties from the IP implications of their partner's corporate transactions. These provisions require legal sophistication and transactional experience to draft effectively, and they are precisely the provisions that standard form JDA templates handle inadequately.
Contact me at (512) 293-0710 or sconnolly@austin-patent-attorney.com to discuss your specific joint development situation.
[ Joint Development Agreement FAQs — Austin, Texas ]
Question: What happens to IP ownership if we develop technology together without a JDA?
Answer: Without a written agreement, jointly developed IP may be owned jointly by all contributing parties under US patent law — meaning each joint owner can independently practice or license the invention without the other's consent and without accounting for profits. This can be commercially devastating. A properly drafted JDA establishes clear IP ownership upfront, preventing the disputes that regularly arise from undocumented collaborations.
Question: What should a joint development agreement cover regarding IP ownership?
Answer: A well-drafted JDA addresses who owns IP developed solely by each party before the collaboration (background IP), who owns IP developed solely by one party during the collaboration, who owns IP developed jointly by both parties, what each party can do with jointly owned IP including licensing rights and sublicense rights, and how improvements to each party's background IP are handled. Getting these provisions right from the beginning is far less expensive than litigating them later.
Question: Can we negotiate JDA terms even if the other party presents their standard form?
Answer: Absolutely — and you should. Standard form JDAs are almost always drafted to favor the party presenting them. Before signing any JDA covering technology you are contributing to a collaborative project, have it reviewed by a patent attorney who understands the technical substance of what is being developed. I regularly review and negotiate JDAs presented to my clients by corporate partners, universities, and government agencies.
Question: What is a joint development agreement's licensing scope for background IP versus foreground IP and why does the distinction matter commercially?
Answer: Background IP is intellectual property that each party owned before the joint development began or developed independently during the collaboration outside its scope — the existing technology each party brings to the collaboration. Foreground IP is intellectual property created during the collaboration as a result of the joint development work — the new innovations the collaboration produces. The licensing scope for each is typically different: background IP is typically licensed to the other party only to the extent necessary for the collaboration itself — a development license — rather than a full commercial license. Foreground IP's ownership and licensing rights are the subject of the JDA's most important commercial negotiation — who owns what was created jointly, who can commercially exploit it, and under what terms each party can use the other's portion of jointly developed innovations. The commercial significance of getting this distinction right is that background IP that was licensed only for development purposes cannot be used by the other party for commercial exploitation without a separate license — which becomes a commercial issue if the other party's background IP is essential to commercializing the jointly developed foreground innovations.
Question: How does a joint development agreement address the situation where one party contributes significantly more resources or team size than the other during the collaboration?
Answer: Resource or team-size asymmetry — one party contributing more engineering hours, more capital, more equipment, or more technical expertise than was originally planned — creates IP ownership disputes when the JDA's ownership provisions assumed equal or different contributions than what actually occurred. When one party's team is significantly larger and its contributions predominate, a JDA that establishes equal ownership of all foreground IP regardless of contribution gives the smaller contributor disproportionate rights relative to what it actually put in. JDAs can address this prospectively through several mechanisms: contribution-tracking or contribution-weighted ownership — periodic assessments of each party's actual contributions relative to the planned allocation, with IP ownership adjusting based on documented contributions rather than estimates; a tiered ownership structure where one party owns innovations in certain categories and the other owns innovations in other categories; or milestone-based ownership that adjusts based on each party's actual contributions to specific deliverables. Alternatively, the JDA can simply establish that IP ownership is fixed regardless of actual contribution levels — eliminating tracking complexity in exchange for potentially less precise allocation. I calibrate these provisions to the collaboration's specific nature — research-intensive collaborations where engineering hour tracking is feasible use different mechanisms than product development collaborations where the relative value of contributions is harder to quantify.
Question: What is a joint development agreement's treatment of trade secrets when the collaboration involves sharing each party's proprietary manufacturing know-how?
Answer: Manufacturing know-how shared between parties in a joint development collaboration — process parameters, equipment configurations, material specifications, quality control approaches — presents specific confidentiality challenges because the shared know-how may be more valuable as a trade secret than any patent rights arising from the collaboration. JDA provisions for shared manufacturing know-how must address: the specific categories of know-how each party is required to disclose for the collaboration to succeed; the confidentiality obligations applicable to received know-how; whether disclosed know-how can be used in the recipient's own manufacturing operations outside the collaboration scope; how disclosed know-how interacts with the recipient's existing confidential information to create new insights that may not be clearly attributable to either party alone; and what happens to disclosed know-how in the receiving party's institutional memory when the collaboration ends — a problem that no JDA can fully address because confidentiality obligations do not erase knowledge from engineers who have genuinely absorbed technical information during the collaboration.
Question: What is an exclusivity provision in a joint development agreement and when should Austin companies accept or reject it?
Answer: Exclusivity provisions in JDAs restrict one or both parties from developing or commercializing technology in the collaboration's subject matter area outside of or in competition with the collaboration during the term and for a specified post-term period. An exclusivity commitment accepted by an Austin startup in exchange for a large company's collaboration resources can create a commercially devastating outcome: the startup is restricted from pursuing its core technology independently during the exclusivity period, and if the collaboration fails to produce commercial results, the startup has lost both the collaboration outcome and its independent development time. I advise Austin startups to critically evaluate exclusivity provisions in JDAs proposed by larger partners — specifically examining the exclusivity scope, the duration, the termination triggers, and whether adequate commercial compensation justifies the restriction. Exclusivity that covers the startup's entire core technology area during a multi-year collaboration is rarely justified by the collaboration's potential benefits; exclusivity limited to the specific collaboration outcomes during the collaboration term is more commercially reasonable.
Question: What happens to a joint development agreement when one collaboration party is subsequently acquired by a competitor of the other party?
Answer: Acquisition of one JDA party by a competitor of the remaining party is one of the most commercially problematic events that can occur during a collaboration — transforming a cooperative technology development relationship into a situation where a direct competitor has access to the other party's background IP, confidential information, and collaborative technology developments. JDAs that do not address this scenario leave the unacquired party in a legally uncertain position: the acquirer steps into the acquired party's shoes under the JDA, potentially giving a competitor contractual rights to continue the collaboration, access to background IP licensed for development purposes, and rights in the foreground IP that the collaboration produced. Well-drafted JDA change of control provisions give the unacquired party specific rights: the right to terminate the collaboration on short notice; the right to buy out the acquired party's foreground IP rights at a predetermined or fair market value price; and the option to convert the collaboration to a license-only relationship if the acquirer is a competitor. The change of control definition itself requires careful drafting — specifying whether it covers only outright acquisitions, or also significant minority investments, licensing transactions, and management changes that effectively transfer control without a formal acquisition. I negotiate these provisions specifically for Austin technology companies entering collaborations where acquisition risk in a competitive landscape is a realistic concern.
Question: What is a best efforts obligation in a joint development agreement and how is it different from reasonable efforts?
Answer: The difference between "best efforts" and "reasonable efforts" in a JDA's development obligation provisions is significant and has generated substantial litigation over its precise meaning in commercial contracts. "Best efforts" has been interpreted by some courts to require a party to take all possible steps to achieve the contractual objective regardless of cost or commercial reasonability — an extremely demanding standard that can require parties to take uneconomical actions to avoid breach. "Reasonable efforts" requires efforts consistent with what a reasonable commercial entity would take given its overall commercial context — a more balanced standard that allows cost-benefit judgment in performing the obligation. For Austin technology companies entering JDAs with development obligations, I recommend specifically negotiating for "commercially reasonable efforts" language — which incorporates the explicit commercial context that most parties actually intend — rather than accepting "best efforts" language that creates potentially unlimited development obligations. Courts in different jurisdictions interpret these terms differently, and the governing law provision in the JDA affects which interpretation applies.
Question: What is the difference between a joint development agreement and a collaboration agreement?
Answer: The terms are often used interchangeably but can have different meanings in practice. A joint development agreement specifically addresses the development of new technology — establishing IP ownership rules, cost sharing, and governance for a technology development program. A collaboration agreement is broader and may encompass commercial collaborations that do not involve joint technology development — co-marketing arrangements, distribution partnerships, or joint sales efforts that may touch on IP issues but are not primarily focused on creating new technology. For arrangements that involve genuine collaborative technology development — where both parties are contributing technical expertise and resources to create something new — a dedicated joint development agreement is the appropriate instrument, with IP provisions specifically tailored to the technology development context.
Question: How should a JDA address IP created by subcontractors hired by one of the collaboration parties?
Answer: Work product created by subcontractors — consultants, independent contractors, research organizations, or specialized vendors hired by one party to the JDA — creates specific IP ownership questions if the subcontractor's work relates to the collaboration subject matter. The JDA should address whether subcontractor-developed IP that feeds into the collaboration is treated as background IP of the hiring party or is subject to the collaboration's foreground IP provisions, and it should require that all subcontractors working on collaboration-related matters execute IP assignment agreements ensuring that all collaboration-relevant work product is properly owned by the party that hired them. It should also address the hiring party's disclosure obligations to the other collaboration party regarding the engagement of subcontractors who will work on collaboration-related matters — since the other party has a legitimate interest in knowing who else has access to or is contributing to the collaboration's subject matter. I advise JDA parties on subcontractor IP provisions and ensure that IP assignments are obtained from all subcontractors involved in collaboration-related work.
Question: What happens to existing IP licenses during a joint development collaboration?
Answer: Pre-existing licenses — agreements under which one party previously licensed its technology from a third party — can create complications in joint development arrangements if the licensed technology is contributed to or used in the collaboration. The original license may restrict sublicensing or use of the licensed technology in certain contexts — including use in a joint development collaboration with a third party. Before entering a joint development arrangement where licensed technology will be contributed, the existing license should be reviewed to confirm that the collaboration use is permitted. If the existing license restricts collaboration use, it may need to be amended to permit the specific joint development context, or the contribution of that licensed technology to the collaboration may need to be restructured to avoid license violations.
Question: How should a JDA address situations where one party has significantly more resources than the other?
Answer: Resource asymmetry — a common dynamic in corporate-startup and industry-university collaborations — creates specific JDA structuring challenges. The better-resourced party often has greater negotiating leverage and may seek JDA terms that disproportionately favor its IP interests. The less-resourced party needs JDA protections that prevent the collaboration from effectively becoming a technology transfer to the larger party without adequate compensation. Specific provisions that address resource asymmetry include: budget and cost-sharing provisions that ensure each party's contribution is recognized fairly; IP ownership provisions that are not simply assigned to the larger party because it is funding the collaboration; field-of-use and exclusivity restrictions that protect the smaller party's ability to commercialize innovations in its core market; and anti-assignment provisions that prevent the larger party from transferring its JDA rights to a competitor of the smaller party.
Question: What is a standstill provision in a joint development agreement?
Answer: A standstill provision in a JDA is a clause that restricts the parties from independently developing, patenting, or commercializing technology in the collaboration's subject matter area during the term of the collaboration and for a specified period afterward. Standstill provisions are sometimes requested by one party to ensure that the other party is genuinely committed to the collaborative development rather than using the collaboration as a source of intelligence for independent competing development. However, standstill provisions can significantly restrict the parties' business flexibility — particularly for companies that have multiple development programs in overlapping technology areas — and require careful scope definition to avoid inadvertently restricting legitimate independent activities outside the collaboration's core focus.
Question: What is a no-challenge provision in a JDA and is it enforceable?
Answer: A no-challenge provision in a JDA — also called a covenant not to challenge — is a contractual commitment by one or both parties not to challenge the validity of the other party's patents during the collaboration term and possibly for a specified period afterward. The enforceability of patent no-challenge provisions has been significantly limited by the Supreme Court's Lear v. Adkins decision and its progeny — courts have found that patent licensees cannot be contractually prohibited from challenging the validity of licensed patents because of the public interest in clearing invalid patents from the marketplace. While the enforceability of no-challenge provisions in collaborative development contexts versus pure licensing contexts has some nuance, I advise clients to approach no-challenge provisions cautiously and to understand their limited enforceability before accepting them.
Question: What is a technology roadmap provision in a JDA?
Answer: A technology roadmap provision establishes the specific technical objectives, milestones, and deliverables for the joint development collaboration — defining what both parties have agreed to develop, the timeline for development, the resources each party will commit, and the criteria for assessing whether the development is progressing appropriately. Technology roadmap provisions are important for managing the collaboration practically — ensuring both parties are aligned on what is being developed and when — and legally — providing the factual basis for assessing whether a party has fulfilled its development obligations if a dispute arises about performance. I advise JDA clients to be specific about technical milestones rather than accepting vague development objectives that create ambiguity about whether the collaboration's obligations have been satisfied.
Question: Can a joint development agreement be amended after it is signed?
Answer: Yes — like any contract, a JDA can be amended by mutual agreement of the parties. Amendments to JDAs are common as collaborative relationships evolve — the scope of collaboration may expand to cover additional technology areas, the resource commitments of each party may change, timeline adjustments may be needed, or the IP ownership provisions may need to be revised as the nature of the collaboration's results becomes clearer. JDAs typically include provisions specifying the form required for amendments — typically written amendments signed by authorized representatives of both parties. Oral amendments to JDAs are generally unenforceable, and informal understandings about how JDA provisions should be interpreted or applied are not legally effective substitutes for properly executed written amendments.
Question: What is a joint steering committee in a JDA and why is it important?
Answer: A joint steering committee (JSC) is a governance body established in a JDA comprising representatives of each collaboration party who oversee the development program — making decisions about technical direction, resource allocation, milestone assessment, and IP filing strategy. JSC governance provisions in a JDA address the composition of the committee, how it makes decisions including voting rights and quorum requirements, what matters require JSC approval versus what can be decided unilaterally by each party's technical team, and how JSC deadlocks are resolved. Effective JSC governance is particularly important for IP decisions during the collaboration — including decisions about whether to file patent applications on collaboration results and how to allocate ownership of specific innovations — because these decisions have long-term consequences that both parties need to participate in making.
Question: What is a development license in a JDA and why is it needed?
Answer: A development license is a grant of rights that allows each collaboration party to access and use the other party's background IP as needed to perform the collaborative development work. Without explicit development licenses in the JDA, each party technically infringes the other's background IP if they use it in the course of the collaboration. Development licenses are typically limited in scope — specifically covering use for collaboration purposes rather than granting broad commercial licenses to the background IP — and are typically royalty-free given that both parties are contributing their background IP to enable the collaboration. The scope of the development license needs to be carefully defined to avoid inadvertently granting commercial rights beyond the collaboration context.
Question: What is the difference between a joint development agreement and a sponsored research agreement?
Answer: A joint development agreement involves two or more parties each contributing technical expertise, resources, and effort to a collaborative development program — with IP ownership negotiated based on each party's contributions. A sponsored research agreement is fundamentally asymmetric — one party funds research conducted primarily by the other party, typically a university or research institution, with the sponsor receiving negotiated IP rights to the results rather than sharing ownership based on co-development. The distinction matters for IP ownership structuring because JDAs typically involve more complex ownership allocations reflecting multiple contributing parties, while sponsored research agreements typically involve a cleaner sponsor-licensee relationship where the research institution owns the IP and the sponsor negotiates access rights. For Austin technology companies working with UT Austin, the appropriate agreement structure depends on whether the company is genuinely co-developing alongside university researchers or funding university-conducted research — and the IP ownership consequences differ significantly.
Question: What is a joint development agreement's relationship to existing employee IP assignment obligations?
Answer: Every employee who works on a joint development program remains bound by their existing IP assignment agreement with their employer — meaning that inventions they make during the collaboration automatically belong to their employer through the employment IP assignment, regardless of what the JDA says about the collaboration's IP ownership. The JDA operates at the company level — establishing what each company owns of the collaboration's results — while the employment IP assignment operates at the individual level — ensuring that each company actually holds the rights its employees create. For this reason, JDAs should be consistent with the participating companies' employee IP assignment frameworks rather than creating obligations that conflict with them. If a JDA provision would require an employee to assign IP to the collaboration entity in a way that conflicts with their employment IP assignment, the conflict needs to be resolved before the collaboration begins.
Question: How does a JDA handle inventions made by a party's consultant or advisor who participates in collaboration meetings?
Answer: Consultants and advisors who participate in joint development collaboration activities — attending technical meetings, providing input on development direction, reviewing interim results — may inadvertently become contributors to inventions made during the collaboration. Without proper documentation, a consultant's inventive contribution could create an ownership claim that neither collaborating company anticipated or controls. JDAs should specifically address consultant and advisor participation by requiring that all consultants and advisors who participate in collaboration activities sign IP assignment agreements with their engaging company before participating, limiting collaboration-related information shared with consultants and advisors to those who have signed appropriate agreements, and establishing a clear policy that no consultant or advisor participation in collaboration activities occurs without prior IP agreement execution. I draft JDA provisions specifically addressing third-party participant IP management as a standard component of collaboration agreement preparation.
Question: What is a technology escrow provision in a JDA and when is it appropriate?
Answer: A technology escrow provision in a JDA establishes that each party deposits copies of their background IP technical documentation — source code, process specifications, manufacturing know-how — with a neutral third-party escrow agent, with release conditions triggered by specific events such as a party's failure to meet collaboration obligations, insolvency, or change of control. Technology escrow provisions are most appropriate in JDAs where each party's access to the other's background IP is critical to the collaboration's continuity — where a party's failure or departure would leave the remaining party unable to continue the joint development program without access to the departing party's technical materials. They are less common in shorter-term or less technically interdependent collaborations where each party retains sufficient independent capability to continue relevant development without the other's background IP. The escrow conditions — what triggers release and what the released materials can be used for — require careful negotiation to protect each party's legitimate interests.
Question: What is a field reservation provision in a JDA and why does it matter?
Answer: A field reservation provision is a JDA clause that specifically reserves to each party exclusive rights in defined technology areas or application fields outside the collaboration's scope — preventing the JDA's IP ownership provisions from inadvertently capturing innovations in areas the parties did not intend to share. Without field reservation provisions, broadly drafted foreground IP definitions can sweep in technical developments that one party made in adjacent areas during the collaboration period but that were not truly the product of the collaborative work. For example, if a semiconductor company and a software company collaborate on an AI-enabled inspection system, the software company might want to reserve its rights to AI algorithms it develops during the collaboration period for entirely different applications — reserving those developments as solely owned background or post-collaboration IP rather than allowing them to be characterized as collaboration foreground IP. I draft field reservation provisions that clearly define the collaboration's subject matter boundary and protect each party's independent development in adjacent areas.
Question: What is a non-solicitation provision in a JDA and how does it protect collaboration parties?
Answer: A non-solicitation provision in a JDA restricts the collaboration parties from soliciting each other's employees who participate in the joint development program during and for a specified period after the collaboration. These provisions protect each party's investment in building the technical team that makes the collaboration effective — preventing the situation where one party uses the collaboration to identify and recruit the other party's most valuable technical contributors. Non-solicitation provisions must comply with applicable law — Texas courts enforce reasonable non-solicitation provisions but scrutinize their scope and duration. For JDAs between Austin technology companies where engineering talent is a scarce competitive resource, non-solicitation provisions are particularly important because the technical team members who participate in the collaboration inevitably develop deeper relationships with the other company's technical leadership that could facilitate targeted recruiting.
Question: What is a collaboration's effect on each party's ability to file patents independently?
Answer: During a joint development collaboration, each party's ability to independently file patent applications on collaboration-related innovations is typically restricted by the JDA's IP provisions — specifically the provisions establishing that foreground IP is owned jointly or by a specific party rather than unilaterally by either collaborator. Filing an independent patent application on subject matter that qualifies as collaboration foreground IP without the other party's consent or in violation of the JDA's ownership provisions could constitute a breach of the JDA and potentially create ownership disputes about the filed application. JDAs should specifically address the patent filing process for collaboration innovations — establishing a joint IP committee or other governance mechanism for making patent filing decisions, allocating responsibility for prosecution costs, and defining the process for each party to propose patent applications on collaboration innovations and for the other party to review and consent. Without clear patent filing governance, collaboration patent opportunities can be missed while parties wait for consensus that the JDA structure does not provide.
Question: What is a publication restriction provision in a joint development agreement, and why does it matter for university and Austin technology company partnerships?
Answer: A publication restriction provision — sometimes called a publication approval provision — restricts the collaboration parties from publishing, presenting, or publicly disclosing collaboration results without prior review and approval, typically with a specified review period before publication is permitted. These provisions matter for two critical reasons. First, any public disclosure of collaboration results before a patent application is filed permanently destroys international patent rights in absolute novelty jurisdictions — including Europe, Japan, South Korea, and China — regardless of whether a US patent application is filed within the one-year US grace period. Second, publishing confidential technical results that constitute the other party's background IP or proprietary information could constitute both a JDA breach and trade secret misappropriation. University research partners present a specific version of this tension: faculty researchers' professional advancement and grant renewal depend on publishing, and universities generally cannot agree to permanent publication suppression. JDAs with university partners typically address this through a publication review period — commonly 60 to 90 days — during which the company reviews proposed publications for patentable content; company rights to request that specific patentable content be redacted or that publication be delayed to allow a patent application to be filed; university rights to publish the remaining non-patentable content without further delay; and the company's patent filing obligations once patentable content is identified during review.
[ Schedule a Free Consultation ]
Joint Development Agreement Services
Collaboration produces innovation — but collaboration without a properly drafted joint development agreement can produce IP ownership disputes that are expensive, damaging, and entirely avoidable.
I offer a free 30-minute consultation to discuss your collaborative development situation, identify the key IP ownership and licensing issues that need to be addressed, and explain what a well-drafted JDA would cover for your specific relationship. I draft joint development agreements with particular attention to patent ownership and licensing provisions — ensuring that your IP rights in jointly developed technology are clearly defined and protected from the very beginning of the collaboration.
My engineering background helps me understand the technical substance of what is being developed and structure IP provisions that accurately reflect what each party is contributing.
Call or text (512) 293-0710, email sconnolly@austin-patent-attorney.com, or fill out the form.
Phone: 512-293-0710
Email: sconnolly@austin-patent-attorney.com
Location: Austin, Texas
Serving Austin, Round Rock, Cedar Park, Georgetown, and all of Central Texas.
USPTO matters are federal — I work with clients throughout Texas and nationwide.
[ Related Services ]
Clients structuring joint development often also work with me on:
[IP Assignment Agreements] · [Non-Disclosure Agreements] · [IP Agreements & Contracts] · [Patent Portfolio Management] · [University & Research Institution IP]
Corporate-Startup Joint Development — Protecting the Startup's Position
Corporate-startup joint development collaborations create a specific IP ownership dynamic that startups frequently underestimate until they are already contractually committed. A large corporate partner with sophisticated IP counsel typically presents a standard form JDA that has been developed over years of corporate collaboration experience and that, not surprisingly, tends to favor the corporate party's IP interests — often capturing broad rights to jointly developed IP, requiring broad licenses to the startup's background IP, and imposing field-of-use or exclusivity restrictions that limit the startup's ability to commercialize its own technology independently.
I advise startup clients entering corporate collaboration arrangements on the specific JDA provisions that most significantly affect their long-term IP position — and negotiate those provisions to protect the startup's ability to commercialize its own technology, raise subsequent investment on the basis of its IP assets, and exit through acquisition without the corporate partner's IP rights creating complications for the transaction.
The provisions I focus on most carefully in corporate-startup JDA negotiations include the definition of background IP to ensure the startup's pre-existing technology is clearly excluded from corporate access, the scope of background IP licenses to limit corporate access to the startup's background IP to the specific collaboration purposes rather than broader commercial use, the ownership structure for foreground IP to ensure the startup receives ownership of or meaningful commercialization rights in innovations it contributes to, any exclusivity provisions that might limit the startup's ability to work with other partners or in adjacent markets, and change of control provisions that determine what happens to the collaboration and the IP rights if the startup is acquired. These provisions collectively determine whether the collaboration enhances or constrains the startup's long-term value — and they deserve careful attention before signature.
The IP Ownership Problem in Collaborative Innovation
Technology innovation increasingly happens across organizational boundaries — between startups and corporate partners, between university research groups and industry sponsors, between companies with complementary technologies that need integration to create market-ready products, and between original equipment manufacturers and their tier-one suppliers. Each of these collaborative arrangements generates intellectual property — and without written agreement establishing upfront who owns what, that IP falls into a legal default that almost always serves no one's interests well.
Under US patent law, an invention jointly made by employees of two collaborating organizations is jointly owned by both organizations — which means each joint owner can independently practice the invention and grant non-exclusive licenses to third parties without the other joint owner's consent and without accounting for any portion of the resulting revenue. For companies that collaborate on developing a core technology, joint ownership under the default rule means your collaborator can license your jointly developed technology to your direct competitor without asking your permission and without sharing the licensing revenue with you. This outcome is almost never what either party intended, and it is entirely avoidable with a properly drafted joint development agreement executed before the collaboration begins.
The stakes of getting IP ownership right in collaborative development arrangements are highest for precisely the collaborations that produce the most valuable innovations — between well-funded companies with significant technical resources who are creating genuinely novel technology together. A joint development agreement executed at the outset of a collaboration involving meaningful investment by both parties is not a formality to be delegated to junior counsel using a standard form. It is a foundational document that determines who owns the valuable innovations the collaboration produces and that deserves the same attention and negotiating sophistication that the collaboration itself receives.
