Does my employment NDA cover information I already knew before I was hired?
Does your NDA cover prior knowledge? Generally, no. Learn how 'prior knowledge' exclusions protect you and how TermScore can audit your contract today.
Does my employment NDA cover information I already knew before I was hired?
No. Standard employment NDAs almost universally exclude information you possessed prior to your start date. If an agreement lacks an explicit 'prior knowledge' exclusion, it is considered overly broad and may be legally unenforceable in many jurisdictions, including California and New York.
The Anatomy of a Prior Knowledge Exclusion
A well-drafted Non-Disclosure Agreement (NDA) should contain an 'Exclusions' section. This section defines what does not constitute 'Confidential Information.' Without this, you could theoretically be sued for using your own professional expertise or pre-existing industry knowledge.
Standard Exclusions to Look For
- Prior Knowledge: Information known to the employee before the date of the agreement.
- Public Domain: Information that becomes generally known to the public through no fault of the employee.
- Independent Development: Information developed by the employee independently without using the employer's proprietary data.
- Third-Party Disclosure: Information rightfully received from a third party without a duty of confidentiality.
Key takeaway: If your NDA lacks a specific carve-out for pre-existing knowledge, you are at risk of being restricted from using your own professional skills. Always request an amendment to include this language before signing.
Action Item: Review your current NDA for a section titled 'Exclusions' or 'Exceptions.' If it is missing, draft a simple addendum stating: 'Confidential Information does not include information that was known to the Employee prior to the date of this Agreement.'
Why Courts Disfavor Overly Broad NDAs
Courts generally view employment contracts through the lens of 'reasonableness.' An NDA that attempts to claim ownership over your brain—specifically the knowledge you acquired before you ever met your employer—is often viewed as an illegal restraint on trade.
| Jurisdiction | Enforceability Stance |
|---|---|
| California | Strictly limits NDAs; broad restrictions are often void under BPC 16600. |
| New York | Requires 'reasonableness' in scope and duration; overbreadth leads to blue-penciling. |
| Texas | Enforces reasonable restrictions; requires a legitimate interest to be protected. |
The Risk of 'Blue-Penciling'
In many states, if a judge finds your NDA is too broad, they may 'blue-pencil' it—meaning they strike out the illegal parts. However, in some jurisdictions, an overly broad contract is thrown out entirely. Relying on a judge to fix your contract is a high-stakes gamble you should avoid by negotiating better terms upfront.
Action Item: If you are in a high-tech or competitive industry, ensure your NDA specifically defines 'Confidential Information' narrowly rather than using catch-all phrases like 'any and all information learned during employment.'
How to Protect Your Pre-Existing Knowledge
If you possess trade secrets or proprietary methodologies from a previous role, you must be proactive. You cannot simply rely on the NDA's text; you must create a record of your knowledge.
- Document Your Baseline: Create a summary of your existing expertise, methodologies, or non-proprietary tools you intend to use.
- Disclose Conflicts: If you have a specific, pre-existing invention or process, disclose it to your employer in writing before signing the NDA.
- Maintain a Paper Trail: Keep dated copies of your research, certifications, or previous work products that prove your knowledge predates your current employment.
Key takeaway: Documentation is your best defense. If a dispute arises, a dated email or a portfolio of your work from three years ago is more powerful than any legal argument.
Action Item: Create a 'Prior Knowledge Disclosure' document. Attach it as an exhibit to your employment contract to explicitly carve out your existing intellectual property.
The Role of Independent Development
Even if you didn't know something before you were hired, you might develop it independently while employed. A robust NDA must account for this. If you use your own time and resources—and no company equipment—to develop a new skill or process, you must ensure your NDA does not claim that as 'Company Property.'
Red Flags in NDA Language
- 'All-Encompassing' Clauses: Any language claiming 'all ideas, concepts, or knowledge acquired during employment' belongs to the company.
- Lack of Time Limits: NDAs that claim to protect information 'in perpetuity' are often viewed as unreasonable.
- Vague Definitions: If the definition of 'Confidential Information' is so broad it could include your general professional experience, it is a red flag.
Action Item: If you see an 'all-encompassing' clause, ask for a modification that limits the scope to 'Confidential Information specifically developed for the Company using Company resources.'
TermScore can automatically analyze your employment contracts to identify missing 'prior knowledge' exclusions and highlight overly broad clauses that could jeopardize your professional future. By uploading your document, you receive an instant, plain-English breakdown of your risks, allowing you to negotiate with confidence before you sign.
TermScore Research
Our legal AI analyzes thousands of contracts to surface market standards, common pitfalls, and actionable insights for anyone who signs agreements.