top of page
2e83dc_9d8120c2d41240f194f5a1eb7bc28386~mv2.png

Employee Leaves for a Competitor: The NDA Was Signed, But Was the Company Prepared?

Updated: Jul 31

VKC 2026 | Vol.1 | TN | Issue 01 | 28 Jul 2026 | Author: Adv. Amey Karmudi, Reviewer: Adv. Rakesh Umarani


SITUATION


A senior employee resigns and joins a competing business. Concerned about possible disclosure and misuse of sensitive information, the Managing Director approaches legal counsel to evaluate the company’s position under the Non-Disclosure Agreement (NDA) executed during employment.


Upon reviewing the documents and internal records of company, a more fundamental concern emerges.

The counsel observes that while an NDA exists, the agreement broadly defines confidential information without identifying the company’s specific proprietary information, trade secrets, or the categories of sensitive data actually accessible to the employee during his employment. The review highlights gaps in the supporting documentation, including the absence of records demonstrating:


  1. The specific confidential and sensitive information accessed by the employee;

  2. Whether access permissions were monitored and revoked;

  3. Whether company assets and information repositories were returned; and

  4. Whether continuing confidentiality obligations were reinforced during the exit process.


As a result of this review, the concern is no longer limited to whether an NDA was signed. The larger question becomes whether the company has created the necessary contractual and operational framework to identify, control and protect its confidential information throughout the employment.


THE MISTAKE COMPANIES USUALLY MAKE


Many companies, particularly growing businesses with expanding teams, assume that executing an NDA sufficiently protects their confidential information. The document is often treated as a complete confidentiality strategy rather than one part of a larger protection framework.


However, confidentiality concerns rarely arise because an NDA is missing. They arise when a company is unable to demonstrate how confidential information was identified, protected and controlled during the employment lifecycle. In several employment exits involving commercially sensitive roles, organizations discover that while contractual obligations exist, the supporting records required to establish those obligations are incomplete.


An effective confidentiality framework is therefore built through connected documentation. An Employment Agreement defines the employee’s role and obligations; a well-drafted NDA identifies the specific categories of confidential and proprietary information requiring protection; access control records demonstrate who was permitted to use sensitive information; asset and data registers establish possession and return of company property; and exit acknowledgments reinforce continuing confidentiality obligations after employment ends.


LEGAL LEARNING


Protection of confidential and sensitive information is not determined merely by the existence of an NDA but by the organization’s ability to establish that the information was confidential in nature and was treated accordingly.


This approach finds support in various judicial precedents. The Hon’ble Supreme Court in Niranjan Shankar Golikari v. Century Spinning & Manufacturing Co. Ltd1 recognized the protection of trade secrets and confidential information acquired during employment.


Similarly, the Hon’ble Delhi High Court in American Express Bank Ltd. v. Priya Puri distinguished between an employee’s general knowledge and experience and information capable of being protected as confidential/proprietary information.


Accordingly, organizations must not only identify the confidential information sought to be protected but also demonstrate the measures taken to safeguard such information.

Documentation, therefore, is not merely an internal administrative process; it creates the foundation required to identify, protect and enforce confidentiality obligations.


BUILDING A CONFIDENTIALITY DOCUMENTATION ECOSYSTEM


A confidentiality framework is strengthened when every document serves a clear purpose and creates a reliable record throughout the employment lifecycle.


Recruitment and Onboarding

Employment Agreement & NDA

Define employee obligations and identify the

confidential/proprietary information intended to be

protected.

IP Assignment & Policy

Acknowledgements

Clarify ownership rights and record acceptance of internal

confidentiality practices.


During Employment

Access Logs & Role-Based Permissions

Establish what information was accessible and whether

access was appropriately controlled.

Asset Registers & Data Records

Track possession and use of company devices, information

and resources.


Exit Management

Exit Records & Asset Handover

Confirm return of company property and closure of employee

access.

Confidentiality Acknowledgements

Reinforce continuing obligations after employment.


Mini Checklist -


Before confidentiality concerns arise, organizations should periodically evaluate whether their records answer the following questions:


✅ Was the confidential information clearly defined in the NDA?

✅ What information was confidential?

✅ Who had access to such information?

✅ Whether access was monitored and revoked?

✅ Whether company assets/data were returned?

✅ Whether confidentiality obligations were communicated?

✅ Whether evidence was preserved for future action?


VIDYAM OBSERVATION


One recurring pattern observed across growing organizations is that confidentiality protection is often viewed as a document-driven exercise limited to the execution of an NDA.

However, effective protection requires a structured framework where agreements, internal processes and employee records work together. A documentation ecosystem created from recruitment to exit strengthens internal governance and ensures that organizations are better prepared to protect their confidential and proprietary information.


Reviewer

Practice Lead / Partner

Last Reviewed

July 2026


Disclaimer:

This Team Note is intended solely for educational and informational purposes. It is based on general practice observations and does not refer to any client or confidential matter. It should not be construed as legal advice for any specific factual situation.


bottom of page