Employee non-disclosure agreement: what it is and what to include

What an employee non-disclosure agreement is

An employee non-disclosure agreement (often called an employee NDA or a confidentiality agreement) is a legally binding contract between an employer and a person it hires. Its core function is straightforward: the employee agrees not to use or disclose the company’s confidential information except as needed to do the job. In return, the employee receives or keeps employment, which courts in most US states treat as adequate consideration to support the promise.

Unlike a mutual NDA signed between two businesses, an employee NDA is usually one-directional. The company is the party sharing sensitive information, and the employee is the party promising to protect it. The agreement protects trade secrets and proprietary material such as customer lists, pricing models, source code, product roadmaps, financial data, manufacturing processes, and unreleased marketing plans. It supplements, rather than replaces, the baseline protection that trade secret law already provides, and a well-drafted NDA strengthens an employer’s position if a dispute ever reaches litigation.

It is worth separating the NDA from two related documents it is often confused with. A non-compete restricts where and for whom an employee may work after leaving. A non-solicitation restricts an employee from poaching customers or coworkers. An NDA does none of that: it only governs the handling of confidential information. Many employers combine all three into a single confidentiality and restrictive covenant agreement, but the obligations are legally distinct and are judged under different standards.

Key terms and clauses to include

A strong employee non-disclosure agreement is precise about what is protected and reasonable about how far the restriction reaches. The following clauses form the backbone of a defensible agreement.

• Definition of confidential information. Spell out the categories of protected material with specific examples, then add a catch-all for information a reasonable person would understand to be confidential. Vague definitions invite disputes, and overly broad ones risk being struck down as unenforceable.
• Exclusions from confidential information. Standard carve-outs cover information that is already public, that the employee already lawfully knew, that a third party lawfully provides, or that the employee independently develops without using company data. Courts expect these exclusions, and omitting them can undercut the entire clause.
• Obligations of the employee. State clearly that the employee must not use or disclose confidential information outside the scope of their duties, must safeguard it, and must limit access to those with a need to know.
• Duration of the obligation. Define how long confidentiality survives after employment ends. A fixed term of two to five years is common for general confidential information, while genuine trade secrets are often protected for as long as they remain secret.
• Return of materials. Require the employee to return or destroy all confidential materials, including electronic copies, at the end of employment.
• Ownership of work product. Confirm that inventions, code, and other work created in the course of employment belong to the company, and coordinate this with any separate assignment-of-inventions agreement.
• Whistleblower immunity notice. The federal Defend Trade Secrets Act requires employers to include a notice of immunity for confidential disclosures made to the government or in a court filing. Omitting it can cost the employer certain remedies, such as exemplary damages and attorney fees, in a later trade secret case.
• Remedies and injunctive relief. State that a breach may cause irreparable harm and that the company may seek an injunction in addition to monetary damages.
• Governing law and dispute resolution. Identify which state’s law applies and how disputes are resolved, since enforceability standards vary significantly from state to state.

Because enforceability turns on wording as much as on intent, this is exactly where a review before signature pays off. Pactolane can store your approved NDA templates in one repository, route each version through an approval workflow, and keep an audit trail of every change, so legal and HR review the same language every time.

When you need one

You need an employee non-disclosure agreement whenever a role gives someone access to information the company would not want a competitor or the public to have. In practice, that covers far more roles than employers assume.

Present the NDA at the offer stage, before the employee starts, so the promise is supported by the offer of employment itself. Asking a current employee to sign a new NDA mid-employment is possible, but some states require fresh consideration, such as a raise, a bonus, or a promotion, for the agreement to hold. Timing matters, because an NDA signed after someone already has access to sensitive data is weaker than one signed on day one.

Typical triggers include hiring engineers or product staff who will see source code or designs, sales and account teams who handle customer and pricing data, finance and operations staff with access to financials, and anyone joining a company that is preparing for fundraising, a partnership, or an acquisition. Contractors, interns, and temporary workers should sign as well, since they often touch the same information as employees. If a role involves proprietary information, the default answer is that an NDA belongs in the onboarding package.

Common pitfalls

The most frequent mistake is overreach. An NDA that tries to classify everything as confidential, including the general skills and knowledge an employee is entitled to carry to their next job, can be read narrowly or thrown out entirely by a court. Protect what is genuinely proprietary and let the rest go.

A second pitfall is treating an NDA as a substitute for a non-compete. Confidentiality obligations do not stop an employee from working for a competitor, they only stop the misuse of protected information. Employers who need both should draft both, and should confirm that restrictive covenants are permitted and reasonable in the relevant state.

Other recurring errors include omitting the standard exclusions, leaving the duration undefined, forgetting the Defend Trade Secrets Act immunity notice, failing to collect a signed and dated copy, and letting templates drift so that different hires sign materially different terms. Perhaps the quietest failure is losing track of the signed agreement altogether, which leaves the company unable to prove what the employee actually agreed to.

Disciplined contract management closes those gaps. Keeping every executed NDA in a searchable repository, standardizing on reviewed templates, capturing electronic signatures, and preserving an audit trail turns a stack of paperwork into an asset the company can rely on when it matters. Pactolane centralizes signed agreements and version history so that, if a confidentiality question ever arises, the current and correct version is one search away.

This page provides general legal information, not legal advice. Confirm the specific terms and enforceability of any employee non-disclosure agreement with qualified counsel licensed in your jurisdiction before you use it.