Enforceability of Restrictive Covenants or Non-Compete Clauses for Offshore Teams Under Philippine Labor Law

Introduction: Why Non-Compete Clauses Matter for Offshore Teams in the Philippines

Foreign BPO clients and tech companies operating with Philippine-based offshore teams often worry about two risks: (1) employees moving to competitors and bringing client relationships with them, and (2) employees using sensitive processes, pricing, scripts, or go-to-market plans acquired during employment. These concerns commonly lead to non-compete and non-solicitation provisions in employment contracts.

Under Philippine law, restrictive covenants are not automatically void. However, courts will enforce them only if the restrictions are reasonable and aligned with legitimate business interests. Poorly drafted clauses—especially those that are overly broad in scope, duration, territory, or covered activities—are vulnerable to being struck down or ignored.

Governing Legal Sources for Non-Compete and Non-Solicitation Clauses

Philippine enforceability analysis is driven mainly by contract law principles, applied in an employment context where courts are mindful of the employee’s right to earn a living and the employer’s right to protect lawful business interests.

1) Supreme Court Standards: Non-Compete Clauses Are Enforceable If Reasonable

The Supreme Court recognizes that non-compete or “non-involvement” clauses in employment contracts are not per se void as restraints of trade. The test is whether the restraint is reasonable as to time, trade, and place, and whether it is not greater than necessary to protect the employer’s legitimate interests.

This standard is clearly articulated in Tiu v. Platinum Plans Phil., Inc., G.R. No. 163512, February 28, 2007, where the Court upheld a two-year post-employment restriction in the pre-need industry, emphasizing the employee’s access to confidential and sensitive marketing strategies as a legitimate justification.

2) Injunction Cases: The Court Will Not Enforce Beyond the Contract’s Stated Period

When employers seek court orders to stop a former employee from working for a competitor, Philippine courts examine whether the restriction is limited and reasonable. In Ticzon, et al. v. Video Post Manila, Inc., G.R. No. 136342, March 29, 2000, the Court noted that a clause limited to employment and two years after separation—and limited to competitive businesses—was considered reasonable. The Court also recognized that disputes become moot once the prohibition period has expired.

3) Proper Forum: Post-Employment Damages Claims Usually Belong in Regular Courts

If the employer sues a former employee for damages (including liquidated damages) based on breach of a post-employment non-compete, this may be treated as a civil law dispute arising from post-employment relations. In Esico v. Alphaland Corporation, et al., G.R. No. 216716, January 20, 2021, the Supreme Court explained that labor tribunals (Labor Arbiter/NLRC) generally do not have jurisdiction over employer damage claims based on breaches that arise after employment ends.

For foreign BPOs and tech companies, this means enforcement planning is not only about drafting—there is also a procedural reality: your remedy may require filing in the regular courts, which affects timing, evidence presentation, and litigation strategy.

4) Related Labor Regulations: Background Rules that Affect Drafting Choices

While non-compete clauses are primarily tested under jurisprudence and contract principles, companies using offshore teams should be mindful of general labor and contracting rules that influence worker classification and risk allocation.

For example, Department of Labor and Employment issuances governing legitimate contracting/subcontracting emphasize coverage where an employer-employee relationship exists and prohibit labor-only contracting (DOLE Department Order No. 174, s. 2017, issued March 16, 2017). DOLE also clarified that BPO/KPO and similar IT-enabled services are generally not the kind of trilateral contracting arrangements contemplated under D.O. 174 (DOLE Department Circular No. 01, s. 2017, issued March 17, 2017). These issuances can affect how an offshore arrangement is structured and, in turn, what contract forms are used.

What Philippine Courts Usually Look For: The “Reasonableness” Factors

Although decisions vary by facts, Philippine cases consistently emphasize that restrictive covenants must be proportionate to the employer’s protectable interest.

Reasonableness Checklist (Time, Activities, Place, and Interest Protected)

Time (Duration)

• Courts have upheld a two-year post-employment restriction in appropriate circumstances (Tiu v. Platinum Plans Phil., Inc., G.R. No. 163512, February 28, 2007; Ticzon, et al. v. Video Post Manila, Inc., G.R. No. 136342, March 29, 2000).
• Longer periods increase risk unless the role involves unusually sensitive information (e.g., high-level leadership, specialized strategy, long-cycle enterprise sales).

Trade/Scope (Prohibited Activities)

• Clauses are more defensible when they prohibit working for a competing business in a similar role, rather than “any employment” or “any business.”
• Non-competes are easier to justify for employees with access to confidential information, pricing, client lists, playbooks, product roadmaps, or marketing strategy (Tiu v. Platinum Plans Phil., Inc., G.R. No. 163512, February 28, 2007).

Place (Geographic Reach)

• Philippine jurisprudence speaks of “place” as a factor, but for offshore teams, geography can be tricky because the work is digital and global. A worldwide ban can look excessive unless narrowly tied to defined competitors, defined clients, or defined markets where the employee actually worked.

Legitimate Business Interest

• Courts are more receptive when the clause is tied to a real protectable interest such as trade secrets, confidential strategy, or customer relationships built on the employer’s investment.

Non-Compete vs. Non-Solicitation: Which Is More Defensible for BPO and Tech?

For many offshore roles, a carefully drafted non-solicitation clause is often more enforceable and business-friendly than a broad non-compete. It directly targets client and talent poaching without blocking the employee’s ability to earn a living.

Clause Type	What It Restricts	Typical Enforceability Risk	Better Use Case
Non-compete	Working for or engaging in a competing business after separation	Higher risk if broad in time/scope/place or blocks the employee’s livelihood	Senior roles, sales leaders, product/security roles, or those with deep access to sensitive strategy (Tiu v. Platinum Plans Phil., Inc., G.R. No. 163512, February 28, 2007)
Non-solicitation (clients)	Soliciting or dealing with defined customers/accounts the employee handled or learned through the employer	Lower risk if it targets specific accounts/time period and avoids blanket bans	Most BPO roles with direct client exposure
Non-solicitation (employees)	Poaching co-workers for a competitor or a new venture	Moderate risk; should be limited to active recruitment/inducement	Team leads, managers, and recruiters

Drafting Guidance for Foreign BPO and Tech Companies (Clauses Courts Are More Likely to Respect)

Below are drafting approaches that align with the Supreme Court’s emphasis on reasonableness and legitimate business interests.

1) Narrow the “Competitive Business” Definition

A common mistake is defining “competitor” as any company in the same broad industry (e.g., “technology,” “outsourcing,” “marketing”). Instead:

• Limit “competitor” to specific competing services the employee worked on (e.g., “outsourced customer support services for fintech clients in APAC”).
• Where possible, attach an indicative competitor list (non-exhaustive) and require employer notice when asserting a company is a competitor.

2) Tie the Restriction to the Employee’s Actual Role and Access

In Tiu v. Platinum Plans Phil., Inc., the Court highlighted the employee’s high rank and exposure to confidential strategies (G.R. No. 163512, February 28, 2007). Drafting should reflect that logic:

• Explain that the employee will have access to confidential information (client pricing, scripts, solution architecture, internal tools, KPIs, forecasting, security measures).
• Restrict only roles that would use or exploit that information (e.g., “sales, solutions, client success, account management for competing services”).

3) Keep the Duration Defensible

A two-year period has been upheld when justified (Tiu v. Platinum Plans Phil., Inc., G.R. No. 163512, February 28, 2007; Ticzon, et al. v. Video Post Manila, Inc., G.R. No. 136342, March 29, 2000). For many offshore roles:

• Consider 6 to 12 months for rank-and-file or mid-level roles.
• Reserve 12 to 24 months for senior leadership, enterprise sales, security, or roles with long-cycle client relationships.

4) Use Non-Solicitation to Protect Client Relationships (Often More Workable)

For BPO and tech services, the most damaging risk is frequently client poaching, not the mere act of employment elsewhere. Draft a client non-solicit that:

• Lists covered clients/accounts by category (e.g., “accounts serviced in the last 12 months of employment” or “accounts assigned to the employee”).
• Defines solicitation as direct or indirect attempts to divert business, including using intermediaries.
• Allows the employee to accept work that is not connected to those clients.

5) Add Confidentiality and Trade Secret Protections (Better Foundation for Enforcement)

Even when a non-compete is disputed, a well-written confidentiality clause can support injunctive relief and damages theories. Make sure confidentiality provisions:

• Define confidential information with examples relevant to offshore delivery.
• Require return/deletion of data upon separation.
• Include obligations about company devices, passwords, and cloud access termination.

6) Be Careful with Liquidated Damages Clauses

Many employment templates impose fixed liquidated damages for any breach. Under Philippine litigation realities, an overly punitive amount can trigger disputes and may not be sympathetic to courts. Also note that employer damages claims for post-employment breaches are commonly treated as civil claims to be brought before regular courts (Esico v. Alphaland Corporation, et al., G.R. No. 216716, January 20, 2021).

• Set a sum that can be defended as a reasonable pre-estimate of loss (e.g., cost of replacement, transition costs, client churn risk), rather than a penalty.
• Consider tiered remedies (injunction + proven damages; or liquidated damages for specific, measurable breach types like client diversion).

Typical Offshore Scenarios and How to Draft for Them

Scenario A: Customer Support Agent Moves to a Rival BPO

A broad “no BPO work anywhere for two years” ban is likely vulnerable. A more defensible approach is a client non-solicitation plus confidentiality, and (if needed) a narrow non-compete limited to the same client vertical and the same account type the agent supported.

Scenario B: Sales Executive With Access to Pricing and Pipeline Joins a Direct Competitor

This is closer to the fact pattern that courts tend to respect, especially when the employee was exposed to sensitive strategy (Tiu v. Platinum Plans Phil., Inc., G.R. No. 163512, February 28, 2007). Draft a role-based restriction covering sales and account management for competing services for a reasonable time period, and pair it with client non-solicitation.

Scenario C: Team Lead Solicits Former Teammates to Join a Startup

Use an employee non-solicitation clause focused on active recruitment/inducement for a defined period (often 6–12 months), rather than prohibiting mere employment in the same industry.

Enforcement Options and Reality Checks (Philippine Setting)

Enforcement depends on facts, evidence, and timing. If seeking to stop a breach while the restricted period is running, employers sometimes pursue court action for injunctive relief, but the clause must be clearly limited because courts will not extend enforcement beyond the contractual period (Ticzon, et al. v. Video Post Manila, Inc., G.R. No. 136342, March 29, 2000).

If the claim is for damages based on post-employment breach, the dispute may fall outside labor tribunals and into regular courts (Esico v. Alphaland Corporation, et al., G.R. No. 216716, January 20, 2021). That affects how employers should preserve evidence (emails, access logs, client communications, documented account assignments, and offboarding checklists).

Conclusion: Draft Restrictions That Courts Can Defend as Fair

Philippine courts will uphold non-compete clauses when they are reasonable in time, scope, and place, and when they protect a legitimate business interest rather than simply blocking competition (Tiu v. Platinum Plans Phil., Inc., G.R. No. 163512, February 28, 2007). For many offshore team roles, a carefully defined non-solicitation clause combined with strong confidentiality provisions can provide better protection with lower enforceability risk.

For foreign BPO clients and tech companies, the drafting goal is not the widest restriction; it is a restriction that a judge can comfortably enforce: narrow, role-linked, supported by real confidentiality concerns, and limited to a reasonable period.

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.