Non-Disclosure Agreement (NDA): What Employers Need to Know

A non-disclosure agreement is a contract obligating someone to keep specified information confidential. In an employment context it appears in several forms — a standalone agreement at hire, a confidentiality clause inside an offer letter or handbook acknowledgment, a provision in a contractor agreement, or terms within a separation agreement.

It is one of the most routinely used and least carefully drafted documents in HR, and the consequences of getting it wrong have grown considerably as restrictions on what employers may require have expanded.

What an NDA can legitimately protect

The defensible core is genuine business information: trade secrets, proprietary methods, customer and pricing data, product plans, financial information not publicly disclosed, and — relevant to employers specifically — the personal data of other employees.

That last category is often omitted and is worth including explicitly. An HR or payroll employee handles compensation, medical information, and identifiers for the entire workforce. A confidentiality obligation covering employee data gives the employer a basis to act if that information is misused, and signals to the employee that it is not casually shareable.

What an NDA cannot restrict

This is where employers create exposure, frequently through boilerplate drafted years ago.

Discussion of wages and working conditions. Employees generally hold protected rights to discuss pay, hours, and conditions with one another. An agreement prohibiting employees from discussing their own compensation can be unlawful, and the presence of such a clause can itself create liability regardless of whether it is enforced.

Reporting to government agencies. Employees may report suspected violations to regulators and participate in investigations. Agreements must not purport to prevent this, and many jurisdictions require an explicit carve-out stating the right remains intact.

Disclosure of unlawful acts. A growing number of jurisdictions restrict agreements that prevent discussion of harassment, discrimination, or other unlawful conduct. California has been particularly active here, limiting provisions that would silence employees about workplace conduct they believe unlawful — including in separation agreements, where such clauses were once routine.

The practical effect is that a broadly drafted confidentiality clause can be unenforceable in part, unenforceable in whole, or affirmatively unlawful. Employers relying on templates predating these developments should treat review as overdue rather than optional.

The overbreadth trap

There is a persistent instinct to draft confidentiality obligations as broadly as possible on the theory that more protection is better. It generally produces the opposite.

An agreement defining confidential information as essentially everything the employee encounters is difficult to enforce, because a court asked to restrain someone must be able to identify what was actually protected. Overbreadth also increases the chance the agreement collides with the protected categories above.

A narrower, specific definition — naming the categories that genuinely warrant protection — is both more enforceable and less likely to create problems. Precision is the protective strategy, not scope.

Timing and consideration

Presenting an NDA after employment has begun raises questions about whether it is supported by adequate consideration, and rules vary by jurisdiction. The cleaner practice is presenting it with the offer, before the employee resigns from a previous position, and having it signed as part of onboarding.

Presenting confidentiality terms for the first time on day one, buried in a stack of paperwork, is common and weaker on both fronts — the employee has already accepted and relocated, and the circumstances make later claims about understanding less credible.

Enforcement realities

An NDA's practical value is often deterrent rather than remedial. Litigation is expensive, proving what information a former employee actually took and used is difficult, and damages are hard to quantify.

That argues for pairing the agreement with controls that reduce the need to enforce it: limiting access to what a role requires, restricting bulk exports, reviewing access logs before anticipated departures, and reconfirming obligations at exit while documenting that conversation.

The exit reminder is worth doing specifically. An employee reminded of what they agreed to, and asked to confirm they have retained no company data, is both less likely to take material and harder pressed to claim ignorance later.

Practical review points

• Define confidential information by category rather than sweepingly
• Include employee personal data explicitly among protected categories
• Carve out protected rights — wages and conditions, agency reporting, disclosure of unlawful conduct
• Confirm separation agreements comply with current restrictions on confidentiality terms
• Present at offer rather than after start where possible
• Ensure obligations survive the end of employment and state the duration
• Apply consistently across similarly situated employees
• Review templates against current law rather than assuming continued validity

Employer's Guardian helps employers align confidentiality terms with handbook policies and current requirements through employee handbook compliance.

This article provides general educational information, not legal advice. Restrictions on confidentiality agreements vary significantly by jurisdiction and change frequently. Consult qualified counsel before using or revising any agreement.