How to evaluate if an employment NDA's definition of proprietary information is legally overbroad for career mobility?
Learn how to identify overbroad NDA definitions that restrict your career mobility. Use TermScore to analyze your employment contract for legal red flags.
How to identify overbroad NDA definitions
An NDA’s definition of proprietary information is legally overbroad if it encompasses your general skills, industry knowledge, or information that is not truly confidential. To protect your career mobility, ensure the definition is limited to specific, non-public trade secrets rather than broad categories of 'all information learned during employment.'
The Anatomy of an Overbroad Definition
Employers often use 'catch-all' language to expand the scope of protected information. If you see phrases like 'all information learned during the course of employment' or 'any information related to the company’s business,' the clause is likely unenforceable in many jurisdictions, including California, where Business and Professions Code Section 16600 strictly limits restraints on trade.
Red Flags in NDA Language
- Lack of Specificity: The definition fails to distinguish between trade secrets and general professional knowledge.
- No Time Limitation: The definition implies that information remains proprietary indefinitely, even after it becomes common knowledge.
- Subjective Inclusion: Phrases like 'anything the company deems confidential' allow the employer to unilaterally expand the scope of the NDA.
- Overlap with General Skills: The definition includes 'methods, processes, and techniques' that are standard in your industry.
Key takeaway: If an NDA definition prevents you from using the skills you brought to the job or the general experience you gained, it is likely an illegal restraint on your ability to earn a living.
Action Item: Review your contract for a 'carve-out' clause. A fair NDA should explicitly state that 'Proprietary Information' does not include information that is or becomes generally known to the public through no fault of the employee.
Comparing Reasonable vs. Overbroad Definitions
| Feature | Reasonable Definition | Overbroad Definition |
|---|---|---|
| Scope | Specific trade secrets (e.g., source code, client lists) | All information learned during employment |
| Public Domain | Explicitly excluded | Not mentioned or vaguely defined |
| General Skills | Excluded | Included as 'proprietary techniques' |
| Duration | Limited to the life of the secret | Perpetual |
Evaluating Enforceability by Jurisdiction
The enforceability of an NDA depends heavily on where you work. Courts apply a 'reasonableness' test, weighing the employer's need for protection against your right to work.
Jurisdictional Nuances
- California: Extremely protective of employees. Any NDA that acts as a de facto non-compete by restricting your ability to use your skills is generally void.
- New York: Courts focus on whether the information is a 'legitimate trade secret.' If the information is easily discoverable, the NDA is often unenforceable.
- Delaware: More employer-friendly, but still requires the definition to be narrowly tailored to protect actual business interests rather than just preventing competition.
Action Item: Research the 'blue-pencil' doctrine in your state. In some jurisdictions, courts will rewrite an overbroad contract to make it reasonable; in others, they will strike the entire clause down.
Steps to Protect Your Career Mobility
When you are presented with an NDA, you must evaluate the definition of proprietary information before signing. Follow this process to mitigate risk:
- Identify the 'General Knowledge' Trap: Look for language that claims ownership of 'methods' or 'processes' you used. If these are standard in your field, request they be excluded.
- Demand a 'Public Domain' Clause: Ensure the contract explicitly states that information known to the public or independently developed by you is not proprietary.
- Negotiate the Definition: If the definition is too broad, ask for a 'Schedule A' attachment that lists specific, limited categories of information that are actually considered confidential.
- Document Your Baseline: Keep a record of the skills and knowledge you possessed before starting the job to prove that certain information was not acquired from the employer.
Key takeaway: Never assume a contract is non-negotiable. Requesting a narrower definition of proprietary information is a standard practice for senior-level hires and protects your future employability.
Action Item: If you are unsure if your NDA is overbroad, use TermScore to automatically analyze your contract. Our AI identifies vague definitions and restrictive clauses, providing you with the insights needed to negotiate better terms for your career.
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 tell if an NDA's definition of confidential information is legally too vague to enforce?
Employment & NDA
Is listing proprietary software frameworks on my resume a breach of employment NDA?
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?