How to Draft an Ironclad Joint Venture Agreement in the Philippines: Why Protecting Your Intellectual Property is the Ultimate Priority

Introduction: why IP protection often decides whether a joint venture succeeds or fails

A joint venture (JV) can accelerate market entry, spread capital requirements, and combine technical know-how with local execution. But it also creates a predictable risk: once technology, brand assets, or confidential know-how are shared, the other side may use them beyond the agreed scope, including after the JV ends. That risk is not solved by good intentions; it is solved by a Joint Venture Agreement (JVA) that treats intellectual property (IP) as a first-order subject, with ownership rules, usage limits, recording steps, and a dispute mechanism designed for fast enforcement.

Philippine doctrine treats a JV as closely related to a partnership arrangement, with familiar features such as shared interests, shared returns (often including losses), and some measure of joint control. The label “JV” will not control if the substance shows a partnership-like arrangement, which matters for governance, tax posture, and allocation of risk—including IP risk (Valdes, et al. v. La Colina Development Corporation, et al., 2021; Philex Mining Corporation v. Commissioner of Internal Revenue, 2008; JG Summit Holdings, Inc. v. Court of Appeals, et al., 2000).

Governing law and controlling concepts you should reflect in the JVA

Joint ventures in Philippine jurisprudence. The Supreme Court describes a JV as an association formed for a limited objective, similar to a partnership, generally involving: (a) community of interest in the undertaking, (b) sharing of profits and losses, and (c) a mutual right of control (Valdes, et al. v. La Colina Development Corporation, et al., 2021; Philex Mining Corporation v. Commissioner of Internal Revenue, 2008; JG Summit Holdings, Inc. v. Court of Appeals, et al., 2000).

Contract terms control when clear. Where the contract language is clear, courts apply the literal meaning of its stipulations and do not search outside the contract for intent. This is a drafting warning: ambiguity is usually paid for later, in litigation (Valdes, et al. v. La Colina Development Corporation, et al., 2021).

Intellectual Property Code framework. The Intellectual Property Code of the Philippines (Republic Act No. 8293, 1997) supplies the legal infrastructure for ownership, transfer, and recording of IP-related instruments, and it reflects a policy of protecting exclusive rights while recognizing the social function of IP (Intellectual Property Code of the Philippines, 1997).

Why IP is the highest-risk asset in many JVs

In many JVs, one party contributes proprietary technology, software, methods, trade secrets, product designs, brands, or business systems, while the other party contributes distribution, regulatory access, local facilities, manpower, or capital. The imbalance is that the party receiving the know-how can often replicate or re-route it. Without tight drafting, the JV becomes a low-cost technology transfer that you cannot unwind.

Drafting approach: build the JVA as an integrated set of documents (and make arbitration cover them all)

Large projects often involve multiple documents: a JVA, amendments, a memorandum of agreement, IP licenses, and assignments. The Supreme Court has treated successive agreements executed to implement a single project as one integrated contract set, allowing an arbitration clause in the JVA to extend to later agreements and even to nominees or beneficiaries in appropriate circumstances (Bases Conversion Development Authority, et al. v. DMCI Project Developers, Inc., 2016).

Drafting implication: write the JVA so that (a) later project agreements are expressly “project documents,” (b) disputes under all project documents are routed to the same dispute forum, and (c) permitted assignees, nominees, and project vehicles are clearly within the dispute clause’s scope.

IP-first provisions to include in an “ironclad” JVA

1) Definitions that remove ambiguity

Define the subject matter early and consistently. Use definitions that a court or arbitrator can apply without guesswork, because clear terms are enforced as written (Valdes, et al. v. La Colina Development Corporation, et al., 2021).

Common definition blocks:

• Background IP: IP owned/controlled by a party before the JV, plus independent developments outside the JV.
• Foreground IP: IP created in the JV or in performing the project.
• Improvements: modifications to Background IP made during the JV.
• Confidential Information / Trade Secrets: include source code, technical data, non-public pricing, customer lists, supplier terms, and internal processes.

2) Ownership rules: decide “who owns what” before anyone shares anything

State with precision:

• Each party retains ownership of its Background IP.
• Whether Foreground IP is (a) owned by the JV entity, (b) jointly owned by the parties, or (c) owned by one party with licenses to the other.
• Who owns Improvements and whether there is a mandatory license-back.

If patents are involved and you plan joint ownership, reflect statutory limits on what a joint owner can do unilaterally. Under the Intellectual Property Code, each joint owner may personally make, use, sell, or import the patented invention for their own profit, but cannot grant licenses or assign interests without consent (or without appropriately sharing proceeds, as the law provides) (Intellectual Property Code of the Philippines, 1997).

3) License scope: narrow, measurable, and time-bounded

Where one party’s IP is licensed to the JV or the other party, draft license scope in measurable terms:

• Field of use (for which products/services).
• Territory (Philippines only, ASEAN, global).
• Term (JV life only; post-termination transition license if needed).
• Sublicensing (allowed only with written consent; define approved sublicensees).
• Source code escrow (when software is essential and continuity risk exists).

4) Confidentiality and trade secret controls that can actually be enforced

Pair confidentiality obligations with operational controls. Typical clauses:

• Need-to-know access and named roles allowed to receive confidential material.
• Data room rules, document marking, and audit logs.
• Return or destruction of confidential information on termination, with certification.
• Non-use covenant surviving termination, not just non-disclosure.

5) Technology transfer and improvement access (avoid clauses that the IP Code discourages)

If the arrangement resembles a technology transfer agreement, draft it to be compatible with the Intellectual Property Code’s policy against provisions that hinder local adaptation and research activity. The IP Code identifies as problematic clauses that restrict R&D or prevent adaptation to local conditions or innovation (Intellectual Property Code of the Philippines, 1997).

Drafting approach: protect the licensor’s proprietary advantage without banning legitimate local adaptation inside the permitted scope, and specify quality standards and approval procedures instead.

6) Recording and “paper trail” for IP assignments and licenses

Do not treat IP documentation as purely private. Under the IP Code, assignments, licenses, and instruments transmitting rights in patents should be recorded with the Intellectual Property Office (IPO), otherwise they may be void against a subsequent purchaser or mortgagee for value without notice, unless recorded within the statutory period or before the subsequent transaction (Intellectual Property Code of the Philippines, 1997).

Drafting approach: add a covenant that parties will sign recordable forms, cooperate on IPO recording, and treat failure to cooperate as a material breach. Align conditions precedent (such as funding drawdowns or technology delivery) with proof of recording where appropriate.

7) Non-compete and non-circumvention, aligned with legitimate business interests

To prevent a partner from using the JV as a training ground and then competing, include non-compete and non-circumvention covenants that are limited by:

• Scope (only competing products/services derived from the JV IP or confidential know-how).
• Territory (where the JV operates).
• Time (JV term plus a defined tail period).

Draft them as protection for IP and confidential information, not as a blanket market ban.

8) Exit, termination, and IP “unwinding” provisions

Most JV disputes arise at exit. Your JVA should specify, in detail:

• Who keeps the brand, domain names, software, customer data, and project documentation.
• Whether the operating party gets a limited post-termination license to service existing customers.
• Who owns work-in-progress inventions, and who files/maintains registrations.
• Buyout mechanics when a party’s IP is embedded in the JV’s operations.

9) Dispute resolution designed for multi-document projects

Arbitration is often chosen for confidentiality and speed, especially for IP-heavy ventures. Philippine jurisprudence supports a liberal view of arbitration agreements, and an arbitration clause in a principal JV contract may extend to related agreements executed for the same purpose, as well as to nominees or beneficiaries in appropriate cases (Bases Conversion Development Authority, et al. v. DMCI Project Developers, Inc., 2016).

Drafting approach:

• State that arbitration covers disputes “arising out of or relating to” the JVA and all project documents.
• Identify the seat/venue, institution or rules, number of arbitrators, language, and interim relief.
• Provide for emergency measures where IP leakage is alleged (e.g., interim injunction-like relief within arbitral rules, confidentiality orders).

10) Foreign participation and constitutional limits (when the JV operates a regulated activity)

If the JV will operate a public utility or an activity subject to constitutional ownership limits, the equity and control structure must comply with the 60%-40% Filipino-foreign rule. The Supreme Court has invalidated structures and bidding rules that would allow foreign entities to obtain more than what the Constitution and the governing contracts allow (JG Summit Holdings, Inc. v. Court of Appeals, et al., 2000).

Drafting implication: ensure the cap table, voting rights, reserved matters, and management control align with nationality restrictions before signing, and mirror those limits in any options, rights of first refusal, or “top” rights.

Common JV scenarios (and how IP clauses should change)

Scenario A: Foreign technology + Philippine distributor forms a JV company. Use a narrow field-of-use license to the JV company; add source code escrow if software drives the business; require non-use/non-circumvention and post-termination transition obligations.

Scenario B: Two Philippine companies co-develop a product. Decide whether Foreground IP is jointly owned or owned by the JV entity. If jointly owned, spell out who can license to third parties and on what consent threshold, reflecting statutory restrictions for patents (Intellectual Property Code of the Philippines, 1997).

Scenario C: Landowner + developer arrangement called a “JV.” If the contract is actually a sale with profit-sharing mechanics, courts may treat it as a sale rather than a JV absent intent to contribute to a common fund and share profits and losses (Valdes, et al. v. La Colina Development Corporation, et al., 2021). If the parties truly intend a JV, draft explicit partnership-like elements: contributions, profit and loss sharing, and shared control.

Summary table: clauses that usually determine whether IP stays protected

Clause area	What to specify	Why it matters under PH law/doctrine
Ownership	Background vs Foreground vs Improvements; filing/maintenance duties	Clear stipulations are enforced as written (Valdes, 2021)
Joint patent ownership	Consent thresholds for licensing/assignment; proceeds sharing	Joint owners’ limits under the IP Code (RA 8293, 1997)
License scope	Field, territory, term, sublicensing, audits	Prevents “scope creep” and post-exit use
Confidentiality + non-use	Access controls, return/destruction, survival, remedies	Trade secret value depends on controllable dissemination
Technology transfer terms	Improvement access; R&D/adaptation allowances with quality controls	IP Code flags restrictive clauses that hinder R&D/adaptation (RA 8293, 1997)
Recording	IPO recordal covenants and timelines	Unrecorded instruments may be void vs later purchasers/mortgagees without notice (RA 8293, 1997)
Dispute resolution	Arbitration covering all project documents; interim relief	Arbitration clauses may extend to related agreements/nominees (BCDA v. DMCI-PDI, 2016)

Final observations and drafting recommendations

First, treat the JVA as an IP governance document, not only a business deal memo. Put ownership, licensing, confidentiality, improvement access, and exit rules in writing with measurable scope, because clear stipulations will usually control (Valdes, et al. v. La Colina Development Corporation, et al., 2021).

Second, structure documentation so IP transfers and licenses are recordable and recorded. Add a cooperation covenant for IPO recording where applicable, and link compliance to milestone obligations (Intellectual Property Code of the Philippines, 1997).

Third, draft dispute resolution to fit multi-document implementation. Ensure the arbitration clause captures all project documents and parties that will later appear in the structure (such as nominees or a project company), consistent with Supreme Court guidance (Bases Conversion Development Authority, et al. v. DMCI Project Developers, Inc., 2016).

Fourth, if foreign equity or regulated activities are involved, confirm constitutional and contractual limits early. Rights that change control or effectively bypass nationality limits can be void and destabilize the entire venture (JG Summit Holdings, Inc. v. Court of Appeals, et al., 2000).

About Nicolas and De Vega Law Offices

 Nicolas and de Vega Law Offices is a full-service law firm in the Philippines.  You may visit us at the 16th Flr., Suite 1607 AIC Burgundy Empire Tower, ADB Ave., Ortigas Center, 1605 Pasig City, Metro Manila, Philippines.  You may also call us at +632 84706126, +632 84706130, +632 84016392 or e-mail us at [email protected]. Visit our website https://ndvlaw.com.