Design Joint Development Agreement

---
name: design-joint-development-agreement
description: Use when two parties have an unresolved dispute over an underlying claim, ownership, or title question — a disputed boundary, overlapping mineral rights, contested IP ownership — that is blocking cooperation, and resolving that claim in the near term is impractical; structure an agreement that explicitly shelves the disputed claim and jointly develops and shares the economic value at stake now, deferring resolution of the underlying dispute to later or separate proceedings.
source: United Nations Convention on the Law of the Sea (UNCLOS) Art. 74(3)/83(3) — requires states pending maritime boundary delimitation to "make every effort to enter into provisional arrangements of a practical nature"; Norway–Russia Barents Sea Delimitation and Cooperation Treaty (2010), Annex II unitization provisions; Nigeria–São Tomé and Príncipe Joint Development Authority Treaty (2001); Texas Natural Resources Code Ch. 101 and comparable U.S. state compulsory-unitization statutes; API/IOGCC model unitization agreement language for oil & gas reservoirs with overlapping or disputed claims
tags: [law, contracts, dispute-resolution, joint-development, unitization, deferred-resolution]
related: [design-joint-venture-governance-agreement, negotiate-lease]
---

# Design Joint Development Agreement

When an underlying claim, ownership, or title dispute is blocking cooperation and can't be resolved quickly, structure an agreement that explicitly shelves the disputed claim, jointly develops and shares the economic value both parties want now, and defers resolution of the underlying dispute to later or separate proceedings.

## Why This Is Best Practice

**Adopted by:** UNCLOS Articles 74(3) and 83(3) codify this exact mechanism at treaty level: pending final maritime boundary delimitation, states are required to make every effort to reach provisional arrangements of a practical nature rather than leaving the disputed area undeveloped. The Norway–Russia Barents Sea treaty (2010) and the Nigeria–São Tomé and Príncipe Joint Development Authority (2001) both apply this mechanism in practice. In the private sector, oil and gas unitization agreements — a standard, statute-recognized mechanism in Texas, Oklahoma, and most other U.S. producing states, with model language published by the American Petroleum Institute and the Interstate Oil and Gas Compact Commission — let operators whose claims to a single reservoir overlap or conflict pool the resource and split economics under an agreed formula, while the underlying title or boundary dispute is resolved separately or later.

**Impact:** Unitization agreements are the standard industry mechanism for developing a shared reservoir when competing lease claims would otherwise block extraction entirely or produce wasteful, uncoordinated competitive drilling — several U.S. states go so far as to make unitization compulsory once a defined majority of interest-holders agree, specifically because leaving overlapping claims unresolved was documented to produce inefficient, wasteful extraction. The Norway–Russia and Nigeria–São Tomé arrangements similarly allowed resource development to proceed on a multi-year basis in maritime zones where full boundary delimitation remained unresolved for far longer.

**Why best:** The alternative to this mechanism is leaving all cooperation blocked until the underlying dispute resolves — which, for a genuinely hard claim/title dispute, can mean years or decades of foregone value for both parties. This structure is different from `design-joint-venture-governance-agreement`, which governs disagreements *within* a venture both parties already agreed to form on settled ownership terms. Here, the disputed claim is the *reason* the structure exists in the first place — the agreement's core function is separating "who develops and shares the value now" from "who ultimately owns the underlying claim," so that unresolved title doesn't have to mean unrealized value.

Sources: UNCLOS Art. 74(3)/83(3); Norway–Russia Barents Sea Delimitation and Cooperation Treaty (2010); Nigeria–São Tomé and Príncipe JDA Treaty (2001); Texas Natural Resources Code Ch. 101; API/IOGCC model unitization language.

## Steps

1. **State the disputed claim explicitly and confirm it's genuinely not resolvable in the near term.** Name precisely what's disputed — boundary location, ownership percentage, IP validity or inventorship — and confirm that pursuing resolution now would take longer or cost more than the value being left on the table by waiting. If the dispute could reasonably resolve quickly, resolving it may be simpler than structuring around it.

2. **Draft an explicit non-prejudice clause.** State clearly that entering the joint development arrangement does not constitute a waiver, concession, or admission by either party regarding the underlying disputed claim — this is what makes the shelving genuine rather than a de facto resolution in one party's favor.

3. **Define the scope of joint development independent of the claim's eventual resolution.** Specify exactly what activity, resource, or asset is being jointly developed, and design the arrangement so it functions the same way regardless of which party is eventually confirmed to hold the disputed claim.

4. **Agree an economic-sharing formula that doesn't depend on resolving the dispute.** Specify how costs and revenues, royalties, or output are split — often based on relative contribution, working interest, or an agreed proxy — rather than a split that implicitly requires knowing who's "right" about the underlying claim.

5. **Establish joint or coordinated operational control for the development activity itself.** Define who operates, how major operational decisions are made, and how disputes about *operations* (as opposed to the underlying claim) get resolved — this is a narrower governance question than the claim dispute itself.

6. **Specify how and when the underlying claim will eventually be resolved, if ever.** State whether the parties will pursue separate resolution (litigation, arbitration, further negotiation) on a defined timeline, or leave it permanently deferred as long as the joint development arrangement continues to function — and what happens to the joint development structure if the claim is eventually resolved.

## Rules

- Always include an explicit non-prejudice clause — without it, participating in joint development can be read as conceding the disputed claim, which defeats the purpose of shelving it.
- The economic-sharing formula must not depend on resolving who's right about the underlying claim — if it does, the parties haven't actually shelved the dispute, they've just delayed litigating it under a different name.
- Scope the joint development narrowly to the specific shared value at stake — don't let the arrangement implicitly expand into ceding broader rights beyond what's actually being jointly developed.
- Decide explicitly whether and when the underlying dispute will be pursued to resolution — an arrangement that's silent on this can drift into permanent ambiguity that neither party actually intended.

## Examples

**Trigger:** Two oil and gas lessees hold overlapping claims to portions of the same underground reservoir, and litigating the boundary would take years while the reservoir's value depreciates from delayed or uncoordinated extraction.
→ Draft a unitization agreement: state the boundary dispute explicitly, include a non-prejudice clause, pool the reservoir under joint operation, and split output using an agreed formula (e.g., proportional to each party's estimated recoverable reserves under their respective claims) that doesn't require first resolving whose boundary claim is correct.

**Trigger:** Two companies both claim inventorship rights over a patent central to a product both want to bring to market, and resolving inventorship would require lengthy, expensive litigation.
→ Structure a joint development and cross-licensing arrangement: both parties commercialize the technology under an agreed revenue split, explicitly without either party conceding the inventorship dispute, while separately pursuing (or explicitly deferring) the underlying inventorship question through litigation or arbitration on its own timeline.

## Common Mistakes

- **Omitting the non-prejudice clause.** Without it, cooperating on joint development can later be construed as an implicit concession on the underlying claim, undermining the party's position if the dispute is eventually litigated.
- **Tying the economic split to resolution of the claim.** If the revenue-sharing formula requires knowing who's right about the disputed boundary or ownership, the parties have not actually shelved the dispute — they've just built a formula that can't be executed until it's resolved.
- **Leaving the timeline for eventual resolution completely undefined.** Silence on whether and when the underlying dispute will be pursued can leave both parties uncertain about the arrangement's long-term status, especially if one party's circumstances change.
- **Scoping the arrangement too broadly.** Letting the joint development structure implicitly extend beyond the specific disputed asset or activity can create new disputes about what exactly was shelved versus jointly conceded.

## When NOT to Use

- When the underlying dispute could be resolved quickly and cheaply relative to the value at stake — in that case, resolving the claim directly is simpler than structuring around it.
- When no genuine, real dispute exists and one party is using a "disputed claim" framing as a pretext to extract concessions from a party with a clearly weaker position — this mechanism assumes a genuine, good-faith dispute on both sides, not a manufactured one.
- When the parties cannot agree on even a claim-independent economic-sharing formula — if the sharing terms themselves require resolving who's right, this structure won't function as intended.

> **Legal disclaimer:** This skill encodes professional best practices for educational purposes. It is not legal advice. Joint development and unitization agreements carry significant jurisdiction-specific contract, property, and regulatory implications — consult licensed transactional counsel before structuring an agreement of this kind.