Securing Preliminary Injunctions Against Departing Corporate Executives involving IP Theft

Introduction: Why preliminary injunctions matter in executive IP-theft disputes

Foreign subsidiaries in the Philippines sometimes discover—often only upon resignation or termination—that a departing director or senior executive has copied proprietary source code, algorithms, training data, process documentation, or internal system access credentials and is moving to a competitor. In these situations, damages after trial may be inadequate because trade secrets can be disseminated quickly, and once confidentiality is lost, it is difficult to restore.

Philippine law allows courts (and, in certain labor-dispute settings, labor tribunals) to issue temporary restraining orders (TROs) and preliminary injunctions to stop threatened or ongoing wrongful acts where there is a showing of a protectable right and a serious risk of irreparable injury if relief is withheld. The litigation challenge is to move quickly while building a record strong enough to survive opposition, avoid procedural pitfalls, and target enforceable relief.

Governing legal sources for injunctions and IP-related restraints

1) Intellectual property statutes and ownership rules. The Intellectual Property Code (R.A. No. 8293, approved June 6, 1997), as amended by R.A. No. 10372 (approved February 28, 2013), supplies statutory protection for copyrightable works (including computer programs) and other IP rights.

For government-funded R&D and technology-transfer arrangements, the Philippine Technology Transfer Act of 2009 (R.A. No. 10055, approved March 23, 2010) contains special rules, including a provision limiting the issuance of injunctive relief by courts other than the Supreme Court in disputes arising from its implementation (Section 17, Article VII, R.A. No. 10055, approved March 23, 2010). This is a specialized regime; many private-sector executive disputes will not fall under it, but subsidiaries working with state universities or government-funded projects should check early.

2) Supreme Court jurisprudence on restraints involving employees and confidential information. Courts have upheld injunctive relief to enforce reasonable post-employment restrictions intended to protect investments and trade secrets, subject to the contract’s time limits and other defenses. In Ticzon, et al. v. Video Post Manila, Inc., G.R. No. 136342, August 10, 2000, the Supreme Court recognized that injunctive relief in a non-compete setting is tied to the contractual prohibition period; once the agreed period expires, disputes over the injunction can become moot.

In labor-related confidentiality disputes, the Supreme Court has also cautioned against vague or overbroad confidentiality definitions being used to justify severe sanctions. In Yonzon v. Coca-Cola Bottlers Philippines, Inc., G.R. No. 226244, January 20, 2021, the Court emphasized that loss of trust and confidence requires a position of trust and a clearly established act justifying the loss; it also treated overly broad confidentiality rules with skepticism where disclosure was in good faith for a legitimate purpose.

3) NLRC rules on injunctions in labor disputes (when the controversy is within labor jurisdiction). If the dispute is framed as a labor dispute pending before the National Labor Relations Commission (NLRC), the NLRC may issue injunctions under its rules. The 2025 NLRC Rules of Procedure (NLRC En Banc Resolution No. 09-25, 2025) define injunctions and enumerate formal requisites, including sworn allegations, supporting evidence, verification, certification against forum shopping, and an undertaking relating to the bond. The earlier 2011 NLRC Rules of Procedure likewise recognized injunctions in ordinary labor disputes and required a certification of non-forum shopping and a cash bond before effectiveness.

What a Philippine court typically requires for a TRO or preliminary injunction

While the detailed standards are drawn from Philippine procedural doctrine on injunctive relief, executive IP-theft cases generally turn on four litigation essentials:

• A clear and unmistakable right (e.g., ownership of the copyrighted program, enforceable confidentiality and IP-assignment covenants, lawful possession/control of systems, and documented trade-secret measures).
• A material and substantial invasion (e.g., copying source code, mass downloads, external storage transfers, forwarding of repositories, credential misuse, or solicitation of engineers with confidential know-how).
• Urgency and irreparable injury (e.g., imminent disclosure to a rival firm, risk of losing secrecy, and competitive harm not readily measurable in damages).
• Need to preserve the status quo (e.g., stop use/disclosure pending trial, quarantine devices, preserve logs, and restrict access).

Philippine courts are generally more receptive to injunction requests that are specific, measurable, and tethered to identifiable property or information (named repositories, device serial numbers, accounts, and defined “Confidential Information” categories), rather than broad “do not compete” commands that resemble restraints of trade without proof.

Choosing the right forum and cause of action

Forum selection affects speed, remedies, and evidence handling. A foreign subsidiary should decide early whether the case is best treated as: (a) a civil action for injunction and damages involving IP and confidential information; (b) a labor controversy; or (c) an intra-corporate case (if the respondent is a director/officer and the controversy genuinely involves corporate rights and relationships).

Not every dispute involving corporate officers qualifies as an intra-corporate controversy. In BiTMICRO Networks, Inc., et al. v. Cunanan, et al., G.R. No. 224189, March 10, 2021, the Supreme Court held that a case is not intra-corporate unless it both involves parties with qualifying intra-corporate relationships and concerns enforcement of correlative rights and obligations under corporate law or internal corporate rules; tort-based claims may remain within regular RTC jurisdiction.

For IP-theft fact patterns, many subsidiaries pursue a regular court action focused on injunctive relief to stop use/disclosure, supported by forensic evidence, plus damages and other relief as appropriate. If there is an ongoing labor dispute before the NLRC and the injunctive relief is tied to that labor controversy, the NLRC injunctive route may be considered, subject to the NLRC’s procedural requisites (NLRC En Banc Resolution No. 09-25, 2025).

Pre-suit preparation: building an injunction-ready record in 48–72 hours

Courts grant immediate relief more readily when the applicant can present coherent, contemporaneous proof. A foreign subsidiary should prepare a package that can be verified and authenticated.

1) Containment and digital forensics

• Lock down credentials (admin accounts, repository access, cloud tenants) and document the exact time and personnel involved.
• Preserve logs (Git activity, CI/CD logs, VPN logs, endpoint monitoring alerts, DLP triggers, email forwarding rules).
• Image devices using a qualified forensic vendor and maintain chain-of-custody documentation.
• Identify the “crown jewels”: list specific algorithm modules, model weights, proprietary libraries, and internal documentation sets.

If the subsidiary cannot articulate what information was taken and how it is protected, injunction requests tend to look speculative.

2) Contract audit: employment, executive, director, and separation documents

Check for enforceable provisions on:

• Confidentiality with clear definitions and survivability after termination.
• IP assignment for code created within scope of employment, using company resources, or relating to company business.
• Return of property, device surrender, and certification of deletion.
• Non-solicitation and limited non-compete provisions (time-bound and role-justified).

In Ticzon, et al. v. Video Post Manila, Inc., G.R. No. 136342, August 10, 2000, the injunction’s relevance was linked to the contractual post-employment restraint period. This highlights a drafting and litigation point: if a non-compete is invoked to support an injunction, the requested order should be aligned with the written duration and scope.

3) Corporate authority and verification documents

Prepare board resolutions or secretary’s certificates authorizing the filing, verification, and certification against forum shopping. Courts scrutinize standing and authority, especially for foreign-owned subsidiaries where signatories may be expatriates or regional officers.

4) Demand letter and preservation notice

A well-drafted letter can support urgency and show good faith. It should demand: (a) cessation of use/disclosure; (b) return of devices and documents; (c) preservation of evidence; and (d) identification of recipients of any disclosures. Avoid threats that could be construed as harassment; keep it factual and specific.

Relief design: what to ask the court to order (and what to avoid)

Injunction requests are stronger when they are narrowly tailored. Below is a comparison of commonly requested remedies.

Requested relief	Why it helps	Drafting caution
Prohibit use, disclosure, or dissemination of identified confidential information	Directly targets trade-secret harm	Define “Confidential Information” by categories and examples; cite specific repositories/doc sets
Order return and/or forensic preservation of devices and storage media	Prevents spoliation and continued access	Specify device identifiers; propose neutral custodian or court-supervised imaging
Restrict access to company systems and accounts	Stops credential misuse quickly	Coordinate with IT so the order is technically implementable
Broad restraint from working for a competitor	May prevent immediate competitive use	Higher risk of denial if overbroad; if used, match contract limits and justify necessity (see Ticzon)

Typical scenarios and how they are argued

Scenario A: Executive downloads the algorithm repository before resigning

The subsidiary typically pleads that the repository contains proprietary code and internal documentation treated as confidential; the executive’s copying and threatened disclosure justify immediate restraint. Supporting proof often includes access logs, email forwarding rules, DLP alerts, and a forensic summary.

Scenario B: Director claims the code is personally owned

Ownership disputes can complicate enforcement. In Sillano v. JGC Philippines, Inc., et al., G.R. No. 273562, March 26, 2025, the Court considered a dispute over ownership of a computer program and noted that orders compelling surrender of source codes were not lawful or reasonable where ownership and duty-to-create were not established in the employee’s agreements. For subsidiaries, the lesson is to shore up written IP assignment clauses and scope-of-work documentation and to avoid overreaching orders that assume ownership without proof.

Scenario C: Company wants to suspend access while investigating

Although distinct from court injunctions, internal protective measures can matter. In Sillano v. JGC Philippines, Inc., et al., G.R. No. 273562, March 26, 2025, the Court recognized that preventive suspension can be valid when the employee’s continued employment poses a serious and imminent threat to the employer’s property pending investigation, subject to the statutory 30-day limit. This may support the narrative of urgency and risk management, but it does not replace the need for judicial relief against a former executive who has already departed.

Labor angle: when the dispute is brought to the NLRC

If the case is intertwined with a labor dispute within NLRC jurisdiction, the NLRC may issue injunctions under its rules. Under the 2025 NLRC Rules of Procedure (NLRC En Banc Resolution No. 09-25, 2025), the application must comply with formal requisites including sworn allegations, supporting evidence, verification and certification against forum shopping, proof of payment of fees, and an affidavit of undertaking relating to the bond. Under the 2011 NLRC Rules of Procedure, injunction petitions likewise required a certification of non-forum shopping and posting of a cash bond before effectiveness.

Subsidiaries should also be cautious about relying on vague confidentiality rules as a basis for severe action. In Yonzon v. Coca-Cola Bottlers Philippines, Inc., G.R. No. 226244, January 20, 2021, the Supreme Court criticized overly broad confidentiality definitions being used to justify dismissal where disclosure was made in good faith for a legitimate purpose. This is relevant when a departing executive claims whistleblowing or disclosure for a legal claim; pleadings should distinguish protected legal disclosures from competitive misappropriation.

Procedure management: how to move fast without creating dismissal risks

Speed is important, but procedural errors can defeat urgent relief. Consider these steps:

• File a verified complaint and a verified application for TRO/preliminary injunction supported by affidavits and exhibits (forensic reports, logs, contracts, policies, board authority documents).
• Target enforceable, specific orders that a sheriff can implement (device turnover, prohibition of dissemination, restricted use of named repositories).
• Prepare for bond requirements because injunctions generally require posting a bond to answer for damages if issuance is later found improper (bond requirements are explicit in NLRC rules and commonly required in courts).
• Avoid forum-shopping issues by mapping all contemplated filings (civil, criminal, labor, administrative) and ensuring disclosures are accurate in the certification against forum shopping.

Also observe the hierarchy of courts for extraordinary remedies. In Microsoft Corporation v. Best Deal Computer Center Corporation, et al., G.R. No. 148029, September 24, 2002, the Supreme Court reiterated that a Rule 65 petition is meant to correct jurisdictional errors (not mere errors of judgment) and emphasized adherence to the hierarchy of courts absent exceptional reasons.

Evidence tips that often decide injunction hearings

• Show reasonable secrecy measures: access controls, NDAs, role-based permissions, security policies, and training records.
• Prove threatened misuse: competitor role similarity, solicitation emails, repository cloning, or suspicious uploads.
• Use clear “before/after” timelines: when access occurred, when resignation was tendered, when downloads happened, and when competitor engagement began.
• Prepare credible affiants: IT security head, custodian of records, and direct supervisor who can explain business impact.

Recommended contract and compliance measures to reduce injunction friction

Courts grant emergency relief more predictably when internal documents are coherent. Foreign subsidiaries should consider:

• Executive IP assignment clauses that cover code, models, and documentation created within role scope, using company resources, or related to company business.
• Defined confidential information schedules with examples (repositories, model weights, roadmaps, customer datasets).
• Exit protocols: immediate credential revocation, device audit, signed deletion certificate, and reminder of ongoing confidentiality duties.
• Board-level handling for directors: ensure fiduciary duties, access rights, and post-separation obligations are documented in board resolutions and policies.

Final observations and recommended next steps

A successful preliminary injunction application in an executive IP-theft case usually depends on combining tight relief drafting with forensic-ready evidence and enforceable contractual foundations. Subsidiaries should act immediately to preserve evidence, define the protected information with specificity, and select a forum aligned with the real cause of action and requested remedies.

Before filing, ensure authority documents are complete, the certification against forum shopping is accurate, and the injunction request is not broader than necessary. Cases such as Ticzon, et al. v. Video Post Manila, Inc., G.R. No. 136342, August 10, 2000, and Sillano v. JGC Philippines, Inc., et al., G.R. No. 273562, March 26, 2025, highlight recurring win-or-lose issues: aligning injunctive relief with contractual limits and avoiding overreaching assumptions on ownership of computer programs.

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.