R&D and IP counselling – Confidentiality and Joint-Development Agreements

Companies engaged in research and development activities frequently collaborate with external partners, including suppliers and consultants who possess specialised expertise and technologies. The need to formalise such relationships through appropriate contractual arrangements is generally well recognised, particularly through confidentiality agreements and/or co-development / joint development agreements. However, the use of these legal instruments without a full understanding of their respective functions may expose a company to significant risks in relation to the protection of its Intellectual Property, potentially including irreparable damage.

The effective protection of Intellectual Property often depends on a timely and informed decision: selecting the appropriate contractual instrument before innovation is created. From a legal perspective, confidentiality agreements and co-development agreements/joint development agreements serve distinct and clearly differentiated purposes. A confidentiality agreement is designed to protect pre-existing information and facilitate its exchange while maintaining control over it. Typically, such agreements cover technical information, financial data, know-how and trade secrets. A co-development agreement/joint development agreement governs, inter alia, the ownership and allocation of Intellectual Property rights arising from collaboration between parties, including rights of use and commercial exploitation. Accordingly, it represents the most appropriate legal framework for research and development activities, following a preliminary phase in which confidential information is exchanged to assess the feasibility of collaboration.

Proceeding with development activities under a confidentiality agreement alone gives rise to both legal and competitive risks. Ownership of innovation and knowledge generated during the collaboration remains undefined, and there is a tangible risk that the value created may fall outside the control of a company. The term “confidentiality agreement” is, in practice, very broad: it can refer to anything from half a page of a generic memorandum of understanding to several pages of a carefully negotiated, quasi co-development framework. A frequently overlooked risk is the failure to identify clear boundaries both in terms of communication area and affected technology, which results in know-how being disclosed in a way that can no longer be effectively controlled.

A confidentiality agreement performs both a passive function, preventing pre-disclosure which would impair a subsequent IP process, and an active function, allowing its holder to act against the unlawful acquisition and use of know-how. From an Italian law perspective, the effectiveness of a confidentiality agreement is enhanced where it clearly identifies the information to be protected and forms part of a broader framework of measures aimed at preserving confidentiality. Such measures may also be relevant in establishing whether the information qualifies for trade secret protection under Article 98 of the Italian Industrial Property Code. The indefiniteness of the boundaries of what is protected is among the most significant risks: a vague agreement is difficult to monitor and enforce, while an excessively narrow and rigid definition fails to capture know-how that evolves during the collaboration.

When confidentiality clauses are embedded in a co-development agreement, ownership of any resulting development should also be addressed expressly, particularly where bargaining positions are unequal. Several “operative” clauses are systematically absent from a standard confidentiality agreement: a clear definition of the field of application, or foreground, and the contribution of each party; the allocation of ownership of jointly developed outputs; rights of use and management of resulting patents; and the duration of confidentiality obligations and permitted use of know-how in future collaborations. Under Italian law, failure to allocate ownership contractually may cause jointly developed IP to fall within the statutory co-ownership regime, potentially restricting each party’s ability to exploit, license or transfer the relevant rights independently. Confidentiality obligations may survive termination for a defined period or for as long as the information retains its confidential character. What is also generally missing is an item-by-item inventory of the information to be kept confidential.

These complex and sometimes opposing requirements may result in paradoxical situations where a company finances its own research and development by involving an external partner, yet the resulting Intellectual Property remains with the party that has formally generated the innovation, often the partner itself; or where an innovation partner is not properly compensated for its contribution and suffers an undue leakage of resources.

The challenge is not only a legal one, but also, and above all, an organisational one. In structured companies, Research and Development focuses on speed and time-to-market, Procurement prioritises cost efficiency, and Marketing seeks to anticipate and outperform competitors. Sensitivity to Intellectual Property considerations is often insufficient, despite its nature as a cross-functional strategic asset requiring visibility at the highest levels of corporate governance. Basic training on key Intellectual Property principles across all functions and company IP policies are therefore essential. Where public funding is involved, a publicly funded body cooperating in the research may hold a statutory right over the resulting invention; in such cases, it becomes essential to negotiate a dedicated research and development agreement.

In sectors such as consumer goods, recurrent risk scenarios include situations of de facto co-development with suppliers and commercial partners, where the distinction between confidentiality and co-development arrangements is frequently underestimated. Indicators include product modifications, the emergence of new technical solutions during preliminary discussions and the joint development of prototypes or product variants. Where development involves external partners or small suppliers, the answer to who owns incremental improvements is not always straightforward and may depend on the applicable legal framework, the scope of the parties’ respective contributions and the nature of their relationship. The absence of clear contractual provisions may create uncertainty as to whether ownership vests in the commissioning party or remains with the supplier that contributed to the development, giving rise to disputes regarding exploitation and reuse of the resulting technology or know-how.

Identifying the right moment to move from a simple exchange of confidential information to a genuine co-development arrangement is itself a recurring challenge. No particular issue arises as long as the parties do not slip into a hybrid situation combining information exchange with substantive technical contribution. Remedying the situation after the fact is always more difficult, since by then the parties are, in effect, playing with their cards already on the table.

A particularly common source of disputes arises when, to obtain better pricing, an entity shares an existing supplier’s technical drawings or sheets with a new prospective supplier. Even where a confidentiality agreement is in place with the new supplier, technical drawings are generally protected both by copyright, as works of engineering design, and by Article 98 of the Italian IP Code, on account of their economic value. Where a product results from an unregulated co-development, moving production to a second supplier may expose the entity to claims concerning patents or the original supplier’s know-how. Immediate cost savings can be offset by litigation for patent or trade secret infringement, including customs seizures or injunctions, as well as reputational risk.

By contrast, where a supplier proposes an improved variant of a company’s design, ownership of that improvement lies with the supplier, subject to any subsequent transfer agreed between the parties. The most effective way to manage this risk is to accelerate the co-development process itself, by disclosing the company’s own foreground clearly and promptly, together with well-defined objectives. For Procurement, a simple protocol can help determine whether a project requires only a confidentiality agreement or a full co-development agreement. A pure supply arrangement involving specifications for standard catalogue components will typically be adequately covered by a confidentiality agreement alone; in every other case, the arrangement should be treated as co-development and regulated accordingly.

Similar considerations arise during user testing, trade-partner focus groups and Marketing presentations. Spontaneous suggestions that improve the product are frequently offered without any co-development agreement; such unsolicited ideas are generally treated as disclosed, and therefore available to all. Marketing and communication agencies raise a further question: where an agency proposes an innovative technical or design solution during a brainstorming session, ownership depends entirely on how the underlying engagement contract is drafted. Retroactive confidentiality agreements may mitigate further exposure, but cannot undo disclosures that have already occurred, and some resulting damage may be irreparable.

A recurring tension exists between Marketing, which seeks to communicate as much as possible, and the protection of trade secrets, which depends on disclosing as little as possible. Anything already visible on the market and reasonably susceptible to reverse engineering is generally better narrated openly, with clearly established dates, while genuine know-how and trade secrets are usually best kept outside Marketing’s remit altogether.

Formalising confidentiality and co-development agreements/joint development agreements need not delay research and development, procurement or marketing initiatives. Core elements, such as decision-making authority and ownership of Intellectual Property rights, should be negotiated at an early stage, while more detailed legal provisions can be refined subsequently. Generic contractual language should be avoided through precise definitions and clear delineation of both confidential information and co-development; standardised contractual templates are highly recommended.

A well-structured internal IP policy should cover information flows, authorised personnel and visitor access, and the safeguarding of laboratory notebooks and technical drawings through physical partitioning of production areas and robust IT confidentiality policies. Master agreements may be preferred over project-specific contracts, as they facilitate multiple initiatives with the same partners without repeated negotiation of fundamental terms, provided they are employed flexibly and properly embed specific cooperation environments and technology peculiarities. A concise reference checklist can also support different functions in distinguishing between confidentiality matters and co-development scenarios.

In conclusion, a confidentiality agreement marks the beginning of a dialogue, whereas a co-development agreement/joint development agreement establishes the framework governing collaboration. Innovation must not only be created, but it must also be effectively managed. This process begins prior to development, with the selection of the appropriate contractual instrument.