IP Assignment Clauses in Employment Contracts: What Indian Employees Should Know

Understanding IP Assignment in Indian Employment

Intellectual property (IP) created by employees at work is one of the most contentious issues in employment contracts. Many developers, designers, engineers, and innovators don't realize that overly broad IP assignment clauses in their employment contracts may transfer ownership of their personal projects, inventions, and creative work to their employer—even work done on personal time.

Under Indian law, the Patents Act, 1970 and Copyright Act, 1957 have specific provisions about IP ownership in employment relationships. Understanding these provisions helps protect your intellectual property rights.

How Indian Law Treats IP in Employment

Patents Act, 1970: Employee Inventions

Section 72 of the Patents Act addresses patent ownership in employment contexts.

Key principle: An invention belongs to the employee, not the employer, unless:

1. Invention is made in pursuit of employment duties: Work directly related to the job
2. Invention uses company resources or information: Developed using company materials, facilities, or confidential information
3. Invention belongs to category employer is engaged in: Work is in the field the employer operates

Even then, the employee has certain rights:

• Right to be named as inventor
• Right to receive compensation/royalty if employer commercializes
• However, compensation is often disputed and hard to enforce

Copyright Act, 1957: Original Works

Section 17 of the Copyright Act specifies copyright ownership.

Key rule: The author (creator) owns copyright, not the employer, unless:

1. Work is created in the course of employment: Created as part of job duties
2. Agreement states otherwise: Explicit contract transferring copyright

Critical difference from patents: For copyright, an explicit agreement is necessary for the employer to own copyright. Mere employment relationship doesn't automatically transfer copyright.

This is huge for developers: Code you write for side projects typically remains yours unless you have an explicit IP assignment clause covering it.

Types of IP Assignment Clauses

Type 1: Narrow Assignment (Work-Related Only)

Clause language: "Employee assigns all intellectual property created during the course of employment and related to the company's business to the company."

What this covers:

• Code written for company projects
• Inventions related to company's products/services
• Work created using company resources

What this does NOT cover:

• Side projects unrelated to company business
• Personal inventions created on personal time
• Hobby projects using personal resources

Assessment: This is reasonable and standard in most industries. Courts generally enforce such clauses.

Example: You work for a web development company and create a personal e-commerce app in your free time. Since this is unrelated to your company's business, you likely own it.

Type 2: Broad Assignment (Work-Related and Personal)

Clause language: "Employee assigns all intellectual property created during the term of employment, whether related to the company's business or not, to the company."

What this covers:

• Everything created during employment
• Side projects on personal time
• Inventions in personal capacity
• Code for personal portfolio

Assessment: Overly broad and problematic. Courts often limit such clauses.

Example: You develop a mobile app in your free time completely unrelated to your company. This clause would claim ownership of your app, your creative work, your potential startup idea.

Enforceability: Indian courts disfavor one-sided IP assignments and often reduce scope. However, litigation is expensive and uncertain.

Type 3: Automatic Assignment (Even Before Creation)

Clause language: "All intellectual property created by employee automatically vests in company, including pre-employment work and future work."

What this attempts to cover:

• Work created before employment (retroactive!)
• Personal projects before joining
• Future side projects indefinitely
• Even after employment termination

Assessment: Clearly unenforceable under Indian law. Courts have explicitly rejected such clauses as unconscionable and unreasonable.

Key case: Such clauses violate principles of fairness and contract law. Courts will likely:

• Enforce only the work-related portion
• Void the retroactive and perpetual portions
• Award damages if employer acted on the clause wrongfully

Type 4: The "Moonlighting" Clause

Clause language: "Employee shall not engage in any external activities, projects, or employment without company's written consent. All work created by employee, including personal projects, belong to company."

What this covers:

• Complete restriction on side projects
• Automatic ownership of anything you create
• Requires permission for any outside work

Assessment: Heavily depends on enforceability context. IT companies (Infosys, Wipro cases) have enforced such clauses, but courts increasingly question their reasonableness.

Indian Legal Precedent on IP Clauses

Important Cases

Case 1: Monsanto v. Nuziveedu Seeds (Supreme Court)

Though primarily about patent invalidity, the judgment clarified:

• Employees who develop inventions as part of their job assign patent rights to employer
• But this requires the invention to be made "in the course of employment"
• Personal inventions remain employee's property

Implication: Courts require clear nexus between employment and invention.

Case 2: Ericsson v. Microelectronics (Delhi High Court)

• Employee left company and started competing venture using knowledge from employment
• Court held: Confidential information cannot be used, but general industry knowledge belongs to employee
• IP created using company-specific knowledge can be restrained, but blanket IP assignment to company was limited

Implication: Broad IP assignments are scrutinized; courts protect employee's ability to use general knowledge.

Case 3: Wipro's Moonlighting Litigation

Wipro (major IT company) has litigated against employees engaging in side projects:

• Wipro's position: Employment contract prohibits side work; employee violated it
• Employee's position: Side work doesn't harm Wipro; personal time and personal resources
• Court's inclination: Generally favor Wipro due to clear contract language, BUT with exceptions:
  • If side project competes with Wipro's business: Wipro wins
  • If side project doesn't compete: Courts increasingly favor employee
  • If side project uses Wipro's IP/tools: Wipro wins

Current trend: Courts are balancing employer interests with employee's right to freelance and side hustle in non-competing areas.

Red Flags in IP Clauses

Red Flag #1: All Personal IP Assigned to Company

Clause: "All intellectual property created by employee, whether during work hours or personal time, whether using company resources or personal resources, belongs to company."

Why it's problematic:

• Prevents personal projects and side hustles
• Violates Copyright Act principle that author owns copyright unless explicitly agreed otherwise
• Courts will likely enforce only work-related portion

What you should do:

• Request amendment: "IP assignment applies only to work created during employment and related to company's business"
• Document rejection: If company refuses, note this concern

Red Flag #2: Automatic Assignment Without Any Conditions

Clause: "All work created shall automatically vest in company."

Problem: "Automatic vesting" suggests ownership transfers immediately, even for personal work. This is questionable under Indian law.

Better clause: "Work created in the course of employment shall be assigned to company upon written notice."

Red Flag #3: Retroactive IP Assignment

Clause: "Employee assigns all intellectual property created during employment and three months before employment commencement."

Why it's problematic:

• Attempts to claim ownership of work done before employment
• Clearly unreasonable; violates fairness
• Courts will void this provision

Assessment: Completely unenforceable. If such a clause exists, demand its removal.

Red Flag #4: Perpetual Assignment After Employment

Clause: "IP assignment continues indefinitely after employment termination."

Why it's problematic:

• Prevents employee from leveraging personal skills post-employment
• Unreasonable restraint on employee's career
• May be challenged as restriction on trade

Reasonable version: "IP assignment applies during employment only; post-employment IP created by employee is employee's property."

Red Flag #5: Vague Definition of "Company Business"

Clause: "All IP related to 'company business or any business company may undertake in future' belongs to company."

Problem: "Any business company may undertake in future" is too vague and broad, allowing company to claim ownership retroactively of your side projects if company later enters that business.

Better definition: "Company business means the specific business the company is engaged in as of the date of this agreement, namely [specify exactly]."

Negotiating IP Clauses

Before Signing: Key Negotiation Points

Point 1: Define "Company Business" Narrowly

Request: Replace vague language with specific definition.

Original: "Work related to company business"

Revised: "Work related to the company's current business of [specify: software development, e-commerce, etc.], and only work created during work hours using company resources"

Point 2: Separate Work-Related IP from Personal IP

Request: Clear separation between assigned and non-assigned IP.

Add clause: "Employee shall own and retain all intellectual property created outside work hours and unrelated to company's business, using employee's personal resources."

Point 3: Limit Non-Compete Scope for Side Projects

Request: Clarify that non-compete doesn't prevent side projects in non-competing areas.

Add clause: "Non-compete clause applies only to work directly competing with company's business. Employee may engage in side projects in non-competing fields with advance notification to company."

Point 4: Require Explicit Assignment for Company IP

Request: Require written notice and assignment agreement, not automatic transfer.

Add clause: "Company-related IP shall be assigned to company upon written assignment agreement signed by both parties, with explicit description of the work being assigned."

Point 5: Define Compensation for Assigned IP

Request: If company gets IP ownership, you should get compensation.

Add clause: "For assigned IP commercialized by company with revenue exceeding ₹10 lakhs annually, employee shall receive [1-5%] of annual revenue as compensation."

Red Flags in "Standard" Clauses

Many companies say IP clauses are "standard and non-negotiable." This is rarely true:

• Junior roles: Sometimes truly non-negotiable
• Senior roles: Almost always negotiable
• Startup/scale-up roles: Usually negotiable in exchange for equity
• Large tech companies: Claim non-negotiable but may accept modifications

Strategy: Propose reasonable modifications; many companies will accept if you frame it professionally.

Side Projects and Moonlighting: Legal Position

Can You Have a Side Project While Employed?

Legally: Yes, unless:

1. Your employment contract explicitly prohibits it
2. Side project competes with your employer's business
3. You use company resources, time, or confidential information for side project
4. Side project conflicts with your employment duties

In practice:

• Non-compete companies (Infosys, Wipro, TCS): Moonlighting without permission is breach of contract
• Non-compete clauses: Legally enforceable for competing side work; less clear for non-competing work
• Trend: Younger tech companies increasingly allow non-competing side projects

What You Need to Know

If your contract allows side projects:

• Get written permission for each project
• Keep work separate: Use personal devices, personal time, personal resources
• Don't compete: Don't work on projects competing with employer's business
• Document ownership: If you create IP, have written agreement with client stating you own the code/work
• Don't use company tools: Never develop side projects using company servers, software, or infrastructure

If your contract prohibits side projects:

• Strictly follow the prohibition
• Any side work discovered can be grounds for termination
• Company can claim ownership of your side projects under contract terms
• Best approach: Seek written permission, or negotiate contract amendment

IP Ownership During Employment: Best Practices

1. Document Your Work

For every IP you create:

• Note the date, time, and resources used
• Document if work-related or personal
• Keep personal project code separate from company code
• Maintain personal repositories (GitHub, GitLab) for personal projects

2. Notify Company of Side Projects (If Required)

If contract requires notification:

• Send email to manager/HR describing the project
• Confirm it's non-competing and on personal time
• Get written acknowledgment
• Request explicit ownership confirmation

3. Use Separate Devices/Resources

For side projects:

• Use personal computer, not company laptop
• Use personal internet, not company network
• Use personal accounts, not company email
• Develop on personal time, not work hours

Why it matters: If you use personal resources only, company's claim to ownership is weaker.

4. Explicit Assignment Agreements

For client work or collaborative projects:

• Have written agreement stating you retain ownership
• If client needs to use your code, license it to them (don't transfer ownership)
• Get client to acknowledge you as author/creator
• Keep certificate of ownership

5. Pre-Employment Documentation

Before accepting job:

• Document IP created before employment
• Keep evidence (GitHub commits with timestamps, registrations)
• Ensure contract explicitly excludes pre-employment work

Post-Employment IP Considerations

What Happens to Your IP After You Leave?

Depends on contract:

Scenario 1: Company Assigned IP to You After Leaving

• You own the IP
• Company cannot claim it unless breach occurred

Scenario 2: Dispute About Who Owns IP

• If during employment: Company may claim ownership if work-related
• Burden: Company must prove work was created during employment and work-related
• Your evidence: GitHub commits, timestamps, witnesses can help prove personal project

Scenario 3: Non-Compete Restriction Applies

• You cannot work on competing projects for duration of non-compete (typically 6-12 months)
• Non-compete applies to competing work only; your personal projects in different fields are fine
• Key case law: Overly broad non-competes are limited or voided by courts

Templates: What Good IP Clauses Look Like

Reasonable Narrow Clause

"Employee assigns to Company all intellectual property, including inventions, software code, designs, and copyrightable works, created during the course of employment (a) during working hours, (b) using Company resources or facilities, or (c) related to Company's current business. Employee retains ownership of all intellectual property created (i) outside working hours, (ii) using personal resources, and (iii) unrelated to Company's business. For clarity, Company's 'current business' means specifically [describe exact business line]."

Reasonable Broad Clause with Carve-Out

"Employee assigns to Company all intellectual property created during employment. Notwithstanding the foregoing, Employee retains ownership of personal projects created on Employee's own time using personal resources, provided Employee provides written notice to Company of such projects and confirms they are non-competing. 'Non-competing' means the project does not directly compete with or harm Company's business."

Compensation Clause (If Assigning Valuable IP)

"Company shall compensate Employee for assigned intellectual property as follows: (a) For patents licensed and generating annual revenue exceeding ₹50 lakhs, Employee shall receive 2% of annual revenue; (b) For software code commercialized and generating revenue, Employee shall receive recognition as creator and [compensation terms]. This compensation shall be in addition to regular salary."

Conclusion

IP assignment clauses are crucial but often overlooked in employment contracts. While employers have legitimate interests in owning work-product created during employment, blanket assignment of all personal IP is neither fair nor fully enforceable under Indian law.

Key takeaways:

1. Negotiate before signing: Don't accept broad IP clauses without pushback
2. Understand the distinction: Work-related IP can be assigned; personal IP usually remains yours
3. Document everything: Keep records of when and how you created your work
4. Use separate resources: Personal projects on personal time with personal tools strengthen your ownership claims
5. Get written permission: For side projects, notify company and request written confirmation of non-interference

For detailed review of your employment contract's IP clauses against legal standards and negotiation suggestions, try our IP clause analysis tools to protect your intellectual property rights.