Drafting Intellectual Property Clauses in Renewable Energy Joint Ventures and Protecting Tech Contributions (Philippines)

Introduction: why IP terms matter in Philippine renewable energy joint ventures

Renewable energy joint ventures (JVs) commonly involve a foreign technology provider partnering with a Philippine developer for project development, engineering, procurement, construction, and operations. The foreign party’s value usually lies in proprietary know-how, designs, control systems, software, and performance methods—assets that can be difficult to retrieve once shared.

In the Philippines, IP protections in RE JVs depend heavily on contract drafting: who owns improvements, how confidentiality is enforced, whether technology transfer terms comply with mandatory Philippine rules, and how disputes are handled. Poorly drafted clauses can result in loss of ownership, leakage to competitors, unenforceable restrictions, or tax and compliance complications.

Governing Philippine law affecting IP clauses in RE joint ventures

1) Technology transfer and licensing controls under the Intellectual Property Code (RA 8293, 1997)

Many JV IP provisions—especially those involving licensing of patents, know-how, software, designs, or manufacturing processes—are treated as technology transfer arrangements. Under the Intellectual Property Code, certain provisions are treated as prima facie anti-competitive and prohibited, while other provisions are mandatoryand must appear in voluntary license contracts.

For prohibited clauses (examples: restrictions that prevent use of competitive technologies; clauses barring the licensee from contesting validity; restrictions on R&D designed to absorb and adapt the technology; and clauses exempting the licensor from liability), see Section 87 of RA 8293 (1997).

For mandatory clauses, Section 88 requires, among others: Philippine law to govern interpretation and venue in the proper court where the licensee has its principal office; continued access to related improvements during the term; arbitration rules and venue limitations; and the rule that Philippine taxes on payments relating to the technology transfer arrangement shall be borne by the licensor. These mandatory requirements directly affect how foreign firms should draft governing law, dispute resolution, and tax gross-up provisions in RE JV licensing and IP-sharing documents.

2) State control principles where the project involves natural resources or state-regulated energy arrangements

RE projects can intersect with constitutional and regulatory concepts on state control over natural resources and energy development. Although this is not an IP statute, it shapes the overall JV relationship and operational control expectations, which in turn affects access to technology and project data.

The Supreme Court recognized that foreign participation may come with management-related protections, but the State must retain control where constitutionally required. The Court explained that foreign entities typically demand roles to protect their investment and ensure effective operations, but such arrangements are acceptable only if sovereignty and state control remain with the State in relevant sectors. (La Bugal-B’laan Tribal Association, Inc. v. Ramos, G.R. No. 127882, 2004.)

3) Renewable Energy IRR provisions relevant to project contracting

The DOE Implementing Rules and Regulations of the Renewable Energy Act (Department Circular DC2009-05-0008, 2009) reiterate that exploration, development, and utilization of certain energy resources remain under full control and supervision of the State, and that foreign RE developers may undertake RE development via RE service/operating contracts subject to constitutional limits. These constraints can influence JV structuring, work allocation, and access rights to project outputs (including drawings, data, and software) that are often mixed with proprietary technology.

Core contractual safeguards foreign technology contributors should demand

1) Clear classification of what is being contributed: background IP vs. project outputs vs. improvements

Start by defining three buckets of IP and data:

• Background IP: pre-existing patents, designs, software, source code (if any), manuals, know-how, and trade secrets owned by the foreign firm before the JV.
• Project outputs: drawings, models, specifications, test results, performance data, commissioning records, and operating procedures produced during the project.
• Improvements / developed technology: modifications, enhancements, derivative works, or new inventions arising from use of the foreign firm’s background IP.

Without precise definitions, local partners may later argue that deliverables or improvements are jointly owned or freely usable across other projects.

2) Ownership of improvements: allocate by rule, not by negotiation later

Foreign firms commonly seek a clause providing that improvements, derivative works, and work-in-progress related to the licensed technology are owned by the foreign firm (or licensed back to it). This is frequently litigated in technology collaborations and is best settled upfront.

However, drafters must check that improvement-ownership and assignment clauses do not fall into prohibited categories under RA 8293, particularly if they operate as a forced “transfer for free” or have anti-competitive effects. If the arrangement qualifies as a technology transfer arrangement, ensure compliance with Sections 87 and 88 of RA 8293 (1997).

3) License scope must be narrow: project-only, non-transferable, and time-bounded

A safer default is to grant the JV or local developer only a limited license that is:

• Purpose-limited (solely to design/build/operate the named RE facility);
• Site-limited (restricted to the specific project location and capacity);
• Non-transferable (no assignment or subcontractor pass-through without written consent); and
• Time-bounded (expires upon termination or after defined post-termination support periods).

Be careful with post-expiration restrictions: RA 8293 lists clauses that restrict use of the technology after the expiration of the arrangement as prima facie adverse to competition, subject to specified exceptions. (RA 8293, Section 87, 1997.)

4) Confidentiality and trade secret controls should be operational, not generic

A short NDA clause is often inadequate. Consider operational controls commonly needed in RE projects:

• Confidentiality perimeter: identify categories (control algorithms, source code, performance curves, equipment configurations, procurement pricing, vendor lists, predictive maintenance methods).
• Access controls: role-based access to data rooms and SCADA/EMS interfaces; audit trails; MFA requirements.
• Subcontractor flow-down: written confidentiality and IP assignment obligations for EPC contractors, O&M contractors, and consultants.
• Return/destruction: defined timelines, formats, and certifications for deletion, including backups.

In RE JVs, leakage usually happens through shared contractors and shared employees rather than direct “theft,” so the clause should address those channels.

5) Employee and contractor IP assignment: require proof, not promises

The local partner should warrant that it has enforceable agreements with its employees and contractors ensuring the JV can comply with its confidentiality and IP obligations. In complex collaborations, disputes can arise when personnel who actually wrote code or designed components claim rights or reuse them elsewhere.

For an illustration of contract drafting that requires a party to have agreements in place with representatives to satisfy ownership and assignment obligations, see BiTMICRO Networks, Inc. v. Cunanan, G.R. No. 224189 (2021) (contract excerpt on ownership of developed technology and future rights).

6) “No reverse engineering” and “no competing technology” clauses: draft carefully to avoid invalidity

Foreign tech owners often want restrictions against reverse engineering and use of competing technologies. Philippine law flags some competition-restricting clauses as prima facie adverse to competition in technology transfer arrangements, such as prohibitions on using competitive technologies in a non-exclusive agreement and restrictions on R&D designed to absorb or adapt the transferred technology. (RA 8293, Section 87, 1997.)

Instead of broad prohibitions, consider narrower drafting tied to legitimate interests, such as protecting trade secrets, cybersecurity, and integrity of safety-critical systems. Where strict limits are necessary, obtain specialized review for RA 8293 compliance.

7) Dispute resolution, governing law, and venue: align with mandatory Philippine requirements

If the IP clause sits inside a technology transfer or licensing contract, Philippine law mandates that Philippine laws govern interpretation and that venue be in the proper court where the licensee has its principal office. (RA 8293, Section 88, 1997.)

If arbitration is used, the agreement must comply with the options described in Section 88 (e.g., UNCITRAL/ICC rules) and must set the arbitration venue in the Philippines or a neutral country. (RA 8293, Section 88, 1997.)

8) Tax allocation and gross-up: the “licensor bears Philippine taxes” rule may change economics

Philippine law requires that Philippine taxes on payments relating to the technology transfer arrangement shall be borne by the licensor. (RA 8293, Section 88, 1997.)

Foreign licensors often assume “withholding tax is for the payor’s account” or include a gross-up shifting tax to the licensee. In Philippine technology transfer arrangements, this can conflict with the statutory requirement. Pricing and royalty rates should be computed with this allocation in mind.

Typical RE JV scenarios and how the IP clauses should respond

Scenario A: foreign firm provides proprietary control software integrated into a plant

Risk: the local partner gains access to source code, configurations, and performance tuning methods, then uses them on other projects.

Contract responses: purpose-limited license, strict confidentiality perimeter for software artifacts, audit rights, access logs, and post-termination deactivation/credential revocation. Clarify ownership of modifications and patches.

Scenario B: joint engineering produces improved turbine settings or solar plant layouts

Risk: disagreements on who owns “improvements” created during joint work.

Contract responses: pre-agree improvement ownership, define inventorship and documentation procedures, and require prompt disclosure of improvements. Ensure improvement clauses comply with RA 8293 restrictions for technology transfer arrangements.

Scenario C: EPC contractors and consultants handle sensitive design data

Risk: leakage through contractors not bound by adequate IP and confidentiality terms.

Contract responses: flow-down clauses, required contractor NDAs, IP assignment provisions for contractor-generated outputs, and sanctions for unauthorized sharing.

Suggested clause checklist (summary table)

Clause area	What the foreign tech contributor should seek	Philippine-law drafting notes
Definitions	Background IP, project outputs, improvements, confidential information	Prevents accidental transfer of pre-existing tech
Ownership & improvements	Clear rule for ownership of improvements/derivatives and disclosure duties	Avoid prohibited/anti-competitive clauses; review under RA 8293 Sections 87–88 (1997)
License grant	Project-only, non-transferable, limited term, limited territory/site	Post-expiration restraints can be problematic under RA 8293 Section 87 (1997)
Confidentiality controls	Operational controls: access, audit logs, data room rules, subcontractor flow-down	Most leaks occur via contractors and shared personnel
Employee/contractor assignments	Proof of IP assignment and confidentiality agreements	Support enforceability; see approach reflected in BiTMICRO v. Cunanan (2021)
Dispute resolution	Arbitration/court provisions aligned with business needs	Technology transfer arrangements must follow RA 8293 Section 88 (1997) rules on governing law/venue/arbitration
Tax allocation	Royalty/pricing reflects licensor-bearing Philippine taxes	RA 8293 Section 88 (1997): Philippine taxes borne by licensor in TTA payments

Compliance reminders for foreign firms partnering with Philippine RE developers

First, confirm whether the IP provisions constitute a technology transfer arrangement subject to RA 8293 Sections 87 and 88 (1997). If yes, draft around prohibited clauses and include mandatory provisions.

Second, align the JV’s operational control expectations with sectoral rules: RE service/operating contract structures and constitutional limits can affect how much operational influence foreign participants may exercise, which may indirectly affect technology access and security. (DOE Department Circular DC2009-05-0008, 2009; La Bugal-B’laan Tribal Association, Inc. v. Ramos, G.R. No. 127882, 2004.)

Conclusion: drafting approach for protecting foreign RE technology in the Philippines

Foreign technology contributors can protect proprietary RE technology in Philippine JVs through precise categorization of IP, narrowly scoped licenses, enforceable improvement and disclosure rules, rigorous confidentiality operations, and verified employee/contractor assignments. These measures should be written with the Intellectual Property Code’s technology transfer restrictions and mandatory clauses in mind to avoid unenforceable or risky provisions. (RA 8293, 1997.)

Before signing, foreign firms should run a clause-by-clause legal review focused on (a) RA 8293 technology transfer compliance, (b) project contracting structure under energy regulations, and (c) real-world leakage points such as contractors, shared systems access, and turnover of personnel.

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.