How to determine if an employment NDA definition of confidential information is legally overbroad?
Learn how to identify overbroad NDA definitions of confidential information. Protect your rights with our expert guide on legal contract analysis.
How to Determine if an Employment NDA Definition is Overbroad
An employment NDA definition is legally overbroad if it fails to distinguish between an employer's proprietary trade secrets and an employee's general knowledge, skills, or experience. If the definition lacks specific exclusions for public information or common industry practices, it is likely unenforceable under most state laws.
The Core Criteria for Enforceability
Courts generally evaluate the reasonableness of an NDA based on the employer's legitimate business interest. If the definition of "Confidential Information" is so broad that it prevents an employee from working in their chosen field, it will be struck down.
Key Indicators of Overbreadth
- Lack of Specificity: The definition uses vague "catch-all" phrases like "any and all information learned during employment."
- Failure to Exclude Public Knowledge: The contract does not explicitly state that information already in the public domain is excluded.
- Inclusion of General Skills: The definition attempts to claim ownership over the employee's "know-how" or general professional expertise.
- No Economic Value Requirement: The definition fails to require that the information must provide an actual competitive advantage to the company.
Key takeaway: If an NDA prevents you from using skills you brought to the job or learned through general experience, the definition is almost certainly overbroad and legally suspect.
Comparison: Reasonable vs. Overbroad Definitions
| Feature | Reasonable Definition | Overbroad Definition |
|---|---|---|
| Scope | Limited to trade secrets/proprietary data | Includes all information learned |
| Exclusions | Public domain, general knowledge | None |
| Duration | Defined timeframe or "as long as secret" | Perpetual, regardless of status |
| Clarity | Specific examples provided | Vague, sweeping terminology |
Step-by-Step Analysis Process
- Identify the "Catch-All" Clauses: Scan for phrases like "all information of any kind" or "any data related to the business." These are immediate red flags.
- Check for Exclusions: Look for a section titled "Exclusions from Confidential Information." If this is missing, the NDA is likely too broad.
- Evaluate the "General Knowledge" Test: Ask yourself: "Does this definition prevent me from using my own professional experience?" If yes, it is likely unenforceable.
- Assess the Economic Value: Does the information actually provide a competitive advantage? If the information is common knowledge in the industry, it cannot be protected as confidential.
Jurisdictional Nuances
State laws vary significantly regarding the enforceability of restrictive covenants. For example, California (Business and Professions Code Section 16600) has a very strong public policy against non-competes and overbroad confidentiality agreements that function as de facto non-competes. In contrast, states like Delaware or New York may allow broader definitions, provided they are "reasonable" in scope and duration.
Actionable Checklist for Review
- Ensure the definition is limited to information that is not generally known to the public.
- Verify that the definition excludes information independently developed by the employee.
- Confirm that the definition does not restrict the use of "general skills, knowledge, and experience."
- Check if the definition requires the information to be marked as "Confidential" or "Proprietary" to trigger protection.
Practical Takeaway
When reviewing an NDA, always look for the "Exclusions" clause. If the definition of confidential information is a single, sweeping sentence without carve-outs for your own professional development or public data, you should request a narrowing of the language to protect your future career mobility.
TermScore can automatically analyze your employment contracts to identify overbroad definitions, missing exclusions, and clauses that may violate state-specific labor laws, providing you with an instant risk assessment before you sign.
Check a suspicious clause
Paste a sentence or clause from your employment & nda to get an immediate statutory risk audit.
TermScore Legal Intelligence Group
Audited for 2026 StandardsResearched and cross-referenced against statutory codes, judicial rulings, and TermScore's proprietary Corpus of 100,000+ analyzed contracts. Our intelligence unit continuously audits contract enforceability and predatory clause variance across all 50 US jurisdictions.
Get the contract red-flag checklist
Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.
Keep reading
Employment & NDA
How to evaluate if an employment NDA's definition of proprietary information is legally overbroad for career mobility?
Employment & NDA
Can an employment NDA legally restrict open-source contributions on personal time?
Employment & NDA
Can an employment NDA legally restrict me from mentioning specific software frameworks on my resume?
Employment & NDA
Can an employment NDA legally restrict discussing technical project methodologies in job interviews?
Employment & NDA
Can an employment NDA legally prohibit me from contributing to open source projects on my own time?
Employment & NDA
Can an employment NDA legally claim ownership of personal side projects built without company resources?