contracts

The Key Clauses in an Employee NDA, Explained

Adira EditorialLegal AI desk5 min read

What are the key clauses in an employee NDA? An employee NDA (a staff confidentiality agreement) is built from about ten clauses. Most protect the company's confidential information, and a few exist to keep the agreement lawful under employment law, which limits how far an employer can restrict a worker. An employee NDA is one-way: the employee is the receiving party and carries the obligations. Understanding each clause in plain English helps both employers who draft these and employees who are asked to sign them. This is general information, not legal advice. Employment rules vary widely, so consult a qualified lawyer in your jurisdiction for a specific agreement. ## Parties Names the company and the employee, and should be signed before or on the first day of work, and always before the employee gets access to confidential information. Signing after access has started weakens the protection. ## Definition of Confidential Information The core clause. It sets what the employee must protect: non-public company information such as business plans, finances, pricing, customer and supplier lists, source code, designs, and processes, plus anything marked or reasonably understood to be confidential. A good definition is specific to the business and the role. The trap is a definition so broad it tries to capture the employee's own general skills and knowledge, which the law in many places lets a worker carry to a new job. ## Exclusions Carves out information that is not really secret: information that is or becomes public without the employee's fault, that the employee lawfully knew before joining, or that they lawfully receive from a third party free to share it. Even an employee NDA should include these. Their absence is a common unfair term. ## Obligations of the employee Sets out the duties: use confidential information only to do the job, keep it secret and secure, do not disclose it outside the company without authorisation, and do not use it for personal gain or for a third party. These should be clear and realistic. A duty the employee cannot actually meet is both unfair and hard to enforce. ## Return of materials On leaving, or on request, the employee returns or deletes all confidential information and company property, including documents, devices, and copies. A clean exit process protects the company and gives the employee certainty about what to hand back. ## Duration An employee NDA usually applies during employment and continues for a set period after, often two to three years for ordinary information. Genuine trade secrets may be protected for as long as they stay secret. This split matters: a reasonable, time-limited duty on ordinary information is far more likely to be enforced than a perpetual one on everything. ## Permitted disclosure A crucial fairness clause. It confirms that nothing in the NDA stops the employee from making a disclosure required by law, reporting wrongdoing to a competent authority, or exercising a right that cannot lawfully be waived. In many jurisdictions this protection exists whether or not the NDA mentions it, and an agreement that appears to gag lawful reporting can be unenforceable or unlawful. A well-drafted employee NDA states the carve-out plainly. ## Intellectual property Often included to confirm that work the employee creates in the course of employment belongs to the company, to the extent local law allows. IP ownership rules for employee-created work differ by country, so this clause should fit the local position rather than grab everything, including unrelated personal projects. ## Restrictive covenants (if any) Some employee agreements add a non-compete or non-solicit clause. These are separate, significant commitments, not part of the confidentiality duty, and their enforceability varies sharply by country and region. Best practice keeps them in a separate clause or document so the confidentiality obligations are not dragged down if a court refuses to enforce a restriction. An employee should always read for one. ## Governing law Sets which law applies. For an employee NDA, the protections of the place where the employee works usually apply regardless, so a choice-of-law clause cannot be used to dodge local employment rights. ## A quick map of what each clause is for | Clause | Purpose | Who it mainly protects |

|--------|---------|------------------------| | Confidential Information | Defines the secrets | Company | | Exclusions | Keeps scope fair | Employee | | Obligations | Sets the duties | Company | | Return of materials | Clean exit | Company | | Duration | Time-limits the duty | Both | | Permitted disclosure | Preserves legal rights | Employee | | Intellectual property | Allocates ownership | Company (within law) | | Restrictive covenants | Limits competition | Company (if lawful) | ## Employer and employee read it differently An employer wants the confidential-information definition specific enough to enforce, a sensible duration, and a lawful permitted-disclosure carve-out so a court will uphold the rest. An employee wants exclusions, a time limit, protection for general skills and lawful reporting, and no hidden non-compete. A good employee NDA satisfies both, because an overreaching one often protects the employer less, not more. ## Where a contract workspace helps Understanding these clauses is one thing; drafting a fair NDA for every hire, keeping each signed copy straight, and remembering which post-employment duties are still running is another. That ongoing work is what an AI contract workspace can carry. Instead of re-reading each agreement to check the carve-out and the duration, you see every clause modelled in a structured clause tree with its position marked favourable, neutral, or unfavourable to your company, overreaching terms flagged, and the key dates tracked across the team. Adira is one workspace built around that idea, keeping drafting, per-clause risk, e-signing, version history, and compliance tracking together and tuned to how your company contracts. The clauses above stay the same; a workspace just makes drafting and tracking employee NDAs far less manual. Learn what each clause is for, keep the lawful-disclosure carve-out, and fit the duration and IP terms to your local law.

Frequently asked questions

Which clause keeps an employee NDA lawful?
The permitted-disclosure clause. It confirms the NDA does not stop the employee from reporting wrongdoing, cooperating with authorities, or exercising rights that cannot be waived. In many jurisdictions these protections apply regardless, and an NDA that appears to override them can be unenforceable.
Can an employee NDA claim the skills and knowledge I build at work?
Usually not. The law in many places distinguishes the employer's specific trade secrets, which an NDA can protect, from the general skills and knowledge a worker develops, which they can carry elsewhere. A definition that tries to capture ordinary know-how is often unfair and hard to enforce.
Should a non-compete be part of the employee NDA?
It is better kept separate. Non-compete and non-solicit clauses are distinct, heavily regulated commitments whose enforceability varies by country and region. Keeping them apart means a court refusing a restriction does not drag down the confidentiality duty. This is general information, not legal advice.
Was this useful?

See how Adira drafts in your voice and reads contracts from your side.

Explore the showroom

Working through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.

Try Weave — free