What are the legal risks of an undefined scope in an NDA?

An undefined scope renders an NDA overly broad, making it legally unenforceable in most jurisdictions. It creates ambiguity that allows employees to argue that the information was not confidential, potentially leading to the loss of trade secret protections and failed litigation.

How can I properly define confidential information?

Use a combination of a general description, specific categories (e.g., customer lists, source code), and a 'marked as confidential' requirement for physical documents.

A TermScore is an AI-generated risk rating from 0 to 100 that evaluates the fairness and risk level of any legal document. A score of 86-100 means the contract is highly favorable, while 0-30 indicates dangerous terms you should walk away from.

What types of documents can TermScore analyze?

TermScore analyzes any legal document including freelance contracts, employment agreements, residential leases, NDAs, brand sponsorship deals, SaaS vendor agreements, and rental applications. Upload PDFs, Word documents, or images.

How much does TermScore cost?

TermScore offers a free plan with 3 scores per month. The Team plan is $15/month for 30 scores, and the Professional plan is $50/month for 500 scores with team collaboration features.

Is my document data secure?

Yes. Documents are processed in memory and analysis results are stored encrypted. TermScore never shares your document data with third parties and you can delete your data at any time from your dashboard.

What are the legal risks of having an undefined scope of confidential information in an employment NDA?

The Legal Risks of Undefined Confidential Information

An undefined scope in an employment NDA renders the agreement overly broad and legally unenforceable. Courts frequently strike down NDAs that fail to specify what constitutes 'confidential information,' as they impose an unreasonable burden on employees and fail to provide fair notice of restricted conduct.

Key takeaway: If your NDA does not clearly define what is protected, you risk losing trade secret status under the Defend Trade Secrets Act (DTSA) and state-level Uniform Trade Secrets Acts (UTSA).

Why Specificity Matters in Litigation

When an NDA is challenged, the burden of proof rests on the employer. If the definition of confidential information is vague—such as using catch-all phrases like 'all information learned during employment'—judges often rule that the clause is an unenforceable restraint on trade. In jurisdictions like California, where Business and Professions Code Section 16600 strictly limits non-competes and broad confidentiality, vague NDAs are frequently invalidated entirely.

The Risks of Over-Breadth

Unenforceability: Courts may refuse to blue-pencil (rewrite) an overly broad contract, leaving you with no protection at all.
Chilling Effect: Overly broad NDAs can trigger regulatory scrutiny from the FTC or NLRB, which view restrictive covenants as potential violations of Section 7 rights regarding employee communication.
Loss of Trade Secret Status: If you treat everything as confidential, you treat nothing as confidential. Courts require evidence of reasonable efforts to maintain secrecy.

Action Item: Review your current NDA templates. If the definition of 'Confidential Information' exceeds 100 words without specific examples, it is likely too vague.

Comparing Vague vs. Precise Definitions

Feature	Vague Definition	Precise Definition
Scope	"Any and all information"	"Proprietary technical data, source code, and customer lists"
Marking	Not required	"Must be marked 'Confidential' or identified in writing"
Exclusions	None	"Excludes public domain or independently developed data"
Enforceability	Low (High risk of dismissal)	High (Clear evidentiary standard)

Best Practices for Defining Confidentiality

To ensure your NDA holds up in court, you must balance breadth with specificity. A robust definition should include both a categorical description and a procedural requirement.

Categorize Assets: Explicitly list categories such as financial projections, marketing strategies, source code, and client databases.
Implement Marking Requirements: Require that physical or digital documents be labeled as 'Confidential' to provide clear notice to the employee.
Include Exclusions: Explicitly state that information already in the public domain or known to the employee prior to employment is not covered.
Define the 'Why': Briefly explain that the information derives independent economic value from not being generally known.

Key takeaway: Always include a 'carve-out' for information that is publicly available or independently developed to demonstrate that the NDA is reasonable and not designed to stifle legitimate competition.

The Role of Reasonable Efforts

Under the DTSA, you must prove you took 'reasonable measures' to keep information secret. An NDA is only one part of this. If your NDA is vague, it serves as evidence that you did not actually identify or protect your trade secrets with the necessary rigor. Courts look for a nexus between the NDA definition and your internal data classification policies.

Action Item: Align your NDA definitions with your internal data security policy. If your IT department classifies data as 'Internal,' 'Confidential,' or 'Restricted,' ensure your NDA references these specific classifications.

Automated Contract Analysis

Manually auditing every employment agreement for vague definitions is time-consuming and prone to human error. TermScore uses advanced AI to instantly scan your contracts, identifying overly broad clauses and suggesting precise, legally defensible language that aligns with current jurisdictional standards, ensuring your intellectual property remains fully protected.