NDA Mistakes That Make Them Unenforceable

Reviewing and signing a business agreement. Photo: Mikhail Nilov via Pexels.

A non-disclosure agreement is one of the most common contracts a business signs — before a partnership talk, a financing conversation, a vendor engagement, or a sale process. Because NDAs feel routine, they are often pulled from a template, signed quickly, and filed away. The problem surfaces later: when confidential information has already been misused and the business discovers that the agreement meant to protect it will not hold up. Many NDAs fail not because the idea behind them was wrong, but because of avoidable drafting mistakes. Below are the errors that most often render a non-disclosure agreement unenforceable in Arizona, California, and Texas — and what a properly drafted NDA does instead.

1. Defining “Confidential Information” Too Broadly

The single most common reason an NDA fails is a definition of confidential information so sweeping that a court declines to enforce it. When an agreement purports to cover “any and all information” exchanged between the parties — including information that is public, already known, or trivial — a court may find the restriction unreasonable and refuse to enforce it as written. An overbroad definition can also make the agreement difficult to apply in practice, because neither party can tell what is actually protected.

A well-drafted NDA defines confidential information with enough specificity to be meaningful, and it includes the standard carve-outs: information that is or becomes public through no fault of the receiving party, information the receiving party already lawfully possessed, information independently developed, and information rightfully obtained from a third party. These exclusions are not boilerplate to be deleted — they are part of what makes the core protection enforceable.

2. No Time Limit, or an Unreasonable One

An NDA that lasts “in perpetuity” invites a challenge. Courts in many contexts disfavor confidentiality obligations of indefinite duration, particularly where the information will lose its sensitivity over time. The reasonable term depends on the nature of the information: ordinary business information may warrant two to five years, while genuine trade secrets can be protected for as long as they remain secret.

The drafting fix is to match the duration to the information. A common and defensible approach is a fixed term for general confidential information, paired with a separate provision stating that trade secrets remain protected for as long as they qualify as trade secrets under applicable law. That structure protects the most sensitive material without overreaching on the rest.

3. Treating an NDA Like a Non-Compete

This is where state law matters most, and where a careless template can quietly cross a legal line. An NDA is meant to protect confidential information — not to prevent someone from competing or from working elsewhere. When confidentiality language is drafted so broadly that it operates as a de facto non-compete, it can run into serious enforceability problems, and the rules differ sharply by state.

California is the clearest example: the state broadly prohibits agreements that restrain a person from engaging in a lawful profession or business, and recent law has strengthened that prohibition. A confidentiality provision drafted to function as a non-compete is vulnerable in California in ways it may not be elsewhere. Arizona and Texas permit reasonable restrictive covenants under defined conditions, but even there, an NDA that overreaches into competition risks being narrowed or struck. The lesson is the same across all three states: keep the NDA focused on confidentiality, and handle any legitimate non-compete or non-solicit need in a separate, properly scoped agreement that accounts for the governing state’s rules.

4. Missing or Mismatched Governing Law and Venue

An NDA signed by parties in different states — increasingly common with remote teams and out-of-state counterparties — needs to say which state’s law applies and where a dispute will be heard. When those provisions are missing, the parties can end up litigating the threshold question of where and under what law before they ever reach the actual breach. Because confidentiality and restrictive-covenant rules differ meaningfully between Arizona, California, and Texas, the choice is not a formality; it can determine whether the agreement is enforceable at all.

A properly drafted NDA states the governing law and venue deliberately, with an eye to where enforcement is likely to be sought and which state’s rules best support the protection the business actually needs.

5. No Real Remedy for a Breach

Even a well-defined NDA is of limited use if it gives the disclosing party no practical way to stop a breach in progress. Money damages for the misuse of confidential information are notoriously hard to prove, and by the time a dispute reaches a damages calculation, the harm may already be irreversible. An NDA that omits any reference to injunctive relief leaves the wronged party to chase compensation for a loss that cannot easily be measured.

Strong NDAs acknowledge that breaches may cause irreparable harm and provide that the disclosing party may seek injunctive relief in addition to other remedies. Depending on the relationship, the agreement may also address the return or destruction of confidential materials and the recovery of legal fees. These provisions give the agreement teeth and signal to both sides that confidentiality will be enforced.

6. The Wrong Parties — or No Real Signatures

An NDA only binds the parties who actually agree to it. Two recurring mistakes undercut otherwise solid agreements: signing in an individual’s name when the obligation should run to the company (or vice versa), and failing to bind the people who will actually handle the information — employees, contractors, and affiliates. If a company’s contractor leaks information and the NDA never reached that contractor, the protection may not extend to the actual breach.

Careful drafting names the correct legal entities, confirms the signatory has authority to bind that entity, and includes language requiring the receiving party to ensure its personnel and agents are bound to the same obligations. Mutual NDAs — where both sides may exchange sensitive information — should be genuinely reciprocal rather than one-sided language relabeled as mutual.

The Bottom Line

An NDA is easy to download and hard to get right. The agreements that fail tend to share the same flaws: a definition that is too broad, a term that is too long or absent, confidentiality language that strays into non-compete territory, missing governing-law provisions, no meaningful remedy, and the wrong parties on the signature line. Each of these is avoidable. For any confidential conversation that genuinely matters — a financing round, an acquisition discussion, a key vendor relationship — a short review of the NDA before signing is one of the least expensive forms of protection a business can buy, and it is far cheaper than discovering the agreement’s weaknesses after the information is already out.

This article is general information from Accord & Shield Legal, PLLC and is not legal advice. Reading it does not create an attorney-client relationship. For guidance on your specific situation, please consult a qualified attorney.