Define: Collaborator's Results

What Collaborator's Results Means in a Contract

Collaborator's Results is a defined term used in multi-party collaboration, research and joint development agreements to identify which portion of the overall project output belongs to a particular Collaborator rather than to the other party or to the parties jointly. It is a carve-out from the broader category of Results generated during the collaboration, isolating those outputs that are so closely tied to one Collaborator's own pre-existing know-how or property that fairness and practicality dictate they should remain with that party.

The term matters because collaboration agreements rarely treat all outputs the same way. Some outcomes are genuinely joint, some belong to the party that funded or led the work, and some, the Collaborator's Results, are properly attributed to the party whose underlying inputs made that particular discovery possible. This is common in Research and Development Agreements and similar arrangements where multiple contributors bring distinct assets to a shared project.

Understanding this term correctly is important for anyone reviewing or negotiating a collaboration, since it directly determines ownership and downstream commercial rights over specific deliverables.

How Collaborator's Results Is Defined or Measured

The standard formulation defines Collaborator's Results as those Results directly related to the composition, characteristics, manufacture, development, enhancement or use of the Collaborator's Background, the Collaborator's Materials, or the Collaborator's Confidential Information. In other words, if a Result cannot be properly understood or exploited without reference to something the Collaborator already owned or brought into the project, it falls into this category.

Many agreements supplement or replace this general test with a specific description of the kind of Result the Collaborator is meant to own, particularly where the parties want more certainty than a relatedness test can provide. This might reference a named field of use, a particular technology stream, or specific deliverables listed in a schedule.

• Directly related to Collaborator Background: Results that build on pre-existing know-how the Collaborator contributed.
• Directly related to Collaborator Materials: Results arising from the use, modification or analysis of physical or digital materials supplied by the Collaborator.
• Directly related to Collaborator Confidential Information: Results that could not have been generated without access to confidential information the Collaborator disclosed.

Where Collaborator's Results Appears in Agreements

This term appears most frequently in intellectual property and ownership clauses within collaboration, joint venture and research agreements, often alongside definitions of Background, Materials, Confidential Information and Foreground or Results generally. It is common in academic-industry partnerships, technology co-development arrangements, and manufacturing collaborations.

It also surfaces in agreements resembling a Development Agreement, a Materials Transfer Agreement, or a Community Development Agreement, wherever more than one party contributes distinct inputs and the parties need a mechanism to allocate resulting outputs fairly rather than defaulting to joint ownership.

Industries where this definition is particularly relevant include technology, manufacturing, healthcare and energy, where proprietary background technology or materials are frequently combined with a partner's contribution to produce new, commercially valuable results.

Why the Exact Wording Matters

The precise drafting of this definition determines who owns valuable outputs once the collaboration ends, which can have significant commercial consequences. A definition drawn too broadly may inadvertently give a Collaborator ownership of Results that should properly be shared or owned by the other party, while a definition drawn too narrowly may strip the Collaborator of results that legitimately depend on its contributions.

Ambiguity in terms like directly related can create disputes, particularly where a Result draws on inputs from multiple parties. Courts and tribunals applying the law governing the contract will generally look to the plain wording of the definition, so vague or circular drafting increases the risk of costly disagreement after the fact.

Drafting Considerations

Drafters should consider whether a general relatedness test is sufficient or whether the agreement would benefit from a specific, itemized description of the Results a Collaborator is to own, particularly in technically complex projects. Clear cross-references to the definitions of Background, Materials and Confidential Information are essential, since Collaborator's Results is entirely dependent on those upstream definitions being accurate and complete.

It is also worth addressing overlapping or hybrid Results that relate to more than one party's inputs, and specifying a resolution mechanism such as joint ownership, licensing back, or an escalation procedure. Parties negotiating a Software Development Agreement or comparable collaboration should ensure this definition is reviewed alongside licensing, confidentiality and publication clauses, since ownership of Collaborator's Results often triggers related rights and restrictions elsewhere in the agreement.