Skip to main content
Contracts

NDA and Contract Red Flags Freelancers Should Check Before Signing

Freelancer reviewing an NDA and client contract before signing
FG
FreelancerGuideHub Editorial Team Reviewed against current US government and Copyright Office sources
Educational information, not individualized legal advice. Contract law varies by location and facts. A local attorney can evaluate the actual agreement.

Short answer: An NDA deserves closer review when it defines nearly everything as confidential, omits ordinary exclusions, lasts forever without distinguishing trade secrets from routine information, hides IP assignment or noncompete terms, restricts lawful reporting, or gives only the client powerful remedies. These are prompts to ask questions or seek legal review, not proof that a contract is invalid.

Five-minute review

  • Identify exactly what information and project the NDA covers.
  • Look for exclusions covering prior knowledge, public information, independent development, and lawful third-party receipt.
  • Separate confidentiality from ownership: an NDA should not quietly transfer your tools, templates, or portfolio rights.
  • Confirm scope, acceptance, payment, revisions, termination, and liability in the main services agreement.
  • Read the governing-law, dispute, injunction, and indemnity sections before relying on a short summary.

A client asking for confidentiality is normal. The real question is whether the wording is connected to a legitimate project need and whether you can understand the obligations before accepting them. Review the NDA together with the statement of work and services agreement: important ownership, payment, or restrictive terms may appear outside the document labeled "NDA."

Nine NDA red flags to examine

Clause to examineWhy it mattersA useful clarification
Everything is confidentialA definition covering any information you see, hear, or create may be hard to follow in practice.Can the definition identify categories, the project, or information marked or reasonably understood as confidential?
No standard exclusionsYou may be asked to protect information already public, already known to you, independently developed, or lawfully received elsewhere.Can the agreement add these ordinary exclusions and explain how they are documented?
No permitted-use limitThe document states what you cannot disclose but not what you may use to complete the work.May confidential information be used solely to evaluate or perform the named project?
One duration for every kind of informationTrade secrets and routine launch plans do not necessarily need identical treatment.Can ordinary confidential information have a defined term while trade secrets remain protected as required by applicable law?
Hidden ownership transferConfidentiality language may also assign drafts, methods, templates, or pre-existing materials.Which deliverables transfer, when does transfer occur, and which background materials remain yours?
Disguised noncompete or no-hire restrictionA clause may limit clients, industries, employees, or future projects rather than merely protect information.Can it be narrowed to actual misuse of confidential information or conflicts tied to the project?
No lawful-disclosure processThe agreement may ignore subpoenas, government reporting, or legally protected disclosures.Can it allow disclosures required or protected by law, with notice only when legally permitted?
One-sided emergency remediesInjunction, legal-fee, venue, or indemnity terms can make a small project carry disproportionate risk.Are remedies, notice, cure rights, and dispute costs reasonably allocated to the risks each party controls?
Terms incorporated by an unseen linkPolicies can change or contain additional restrictions you have not reviewed.Can every incorporated document be attached, dated, and made subject to mutual written changes?

1. The definition is broader than the project

Start with the definition of "Confidential Information." It should be possible to connect the protected information to the client, project, or business purpose. A catch-all definition is not automatically unenforceable, but it creates operational uncertainty: you may not know what can be discussed with a subcontractor, shown in a portfolio, or retained for tax and recordkeeping purposes.

2. Common exclusions are missing

A practical NDA usually addresses information that was already known, becomes public without your breach, is independently developed without using the client's information, or is lawfully received from another source. The exact wording and burden of proof matter. Keep dated notes or repository history if independent development could later become important.

3. The NDA also claims your intellectual property

Confidentiality and ownership answer different questions. An NDA protects information; an assignment transfers rights. If the document contains "work made for hire," "hereby assigns," or similarly broad language, review it as an IP provision rather than treating it as routine secrecy language. Identify pre-existing code, templates, processes, fonts, stock assets, and reusable know-how in writing.

The US Copyright Office explains that a specially commissioned work qualifies as a work made for hire only in specified circumstances and categories. Do not assume the label alone resolves every ownership question. See our companion guide on what to include in an NDA and our freelance contract template guide.

4. Confidentiality is used as a broad work restriction

Watch for language that prevents work for an entire industry, contacting broad groups of people, or using general skills and experience. That goes beyond keeping specified information secret. The FTC's nationwide Noncompete Rule is currently not in effect, and state law varies, so do not rely on a headline that says all noncompetes are banned. Evaluate the location, worker status, wording, and facts.

5. Lawful reporting is not addressed

US federal law includes protections for certain confidential disclosures of trade secrets to a government official or attorney for reporting or investigating suspected legal violations, and for sealed court filings. The same statute requires notice of that immunity in certain agreements governing trade secrets or confidential information with employees, a term that includes contractors and consultants for this provision. Other laws may also apply. A contract should not be read as replacing rights that the law preserves.

How to tell if a freelance contract is fair

No single clause proves that a full agreement is fair. A useful test is whether both sides can answer the same operational questions from the written document:

  • Scope: What will be delivered, in which format, and what is explicitly excluded?
  • Acceptance: Who reviews the work, under what criteria, and within how many days?
  • Payment: What triggers an invoice, when is it due, and what happens to undisputed amounts?
  • Changes: How many revision rounds are included and how are new requests priced?
  • Termination: Can either party exit, what notice applies, and how is completed work paid?
  • Ownership: Which final deliverables transfer, when, and what licenses cover background materials?
  • Risk: Who controls each risk, what liability is excluded or capped, and who handles third-party claims?
  • Disputes: Which law and forum apply, and is the process realistic for the project's value?

Compare these terms with the proposal and emails. If the written contract contradicts the commercial deal, ask for a written amendment before work begins. Our guide to writing a freelance contract provides a section-by-section framework.

What is not automatically a red flag?

Some clauses deserve attention without being inherently unreasonable. A mutual NDA is not always better than a one-way NDA if only one party will disclose confidential information. An indefinite obligation may be relevant to genuine trade secrets. A client may reasonably require ownership of final paid deliverables. An injunction clause may reflect the fact that unauthorized disclosure cannot always be repaired with money alone.

The deciding questions are narrower: Is the term connected to a real risk? Is it clear enough to follow? Does it reach beyond what the project requires? Does the price reflect the rights being requested? Can you comply without giving up unrelated future work?

  • Noncompetes: The FTC says its nationwide Noncompete Rule is not in effect and not enforceable. State rules and case-specific enforcement remain important.
  • Trade-secret reporting: 18 U.S.C. Section 1833 describes immunity for specified confidential reports and sealed filings, plus notice requirements in certain agreements.
  • Copyright ownership: The Copyright Office explains that initial ownership, assignments, and works made for hire follow distinct statutory rules.

This is a US-oriented overview, not a substitute for checking the law that governs your contract. Cross-border projects can add tax, data-transfer, language, service-of-process, and enforcement issues.

Questions and negotiation scripts

Ask for a specific change rather than telling the client the whole contract is unfair. A short explanation tied to project delivery is easier to evaluate.

For an overbroad NDA: "Could we limit Confidential Information to information disclosed for this project and add exclusions for public, previously known, independently developed, and lawfully received information?"

For hidden IP assignment: "I can assign the final paid deliverables listed in the statement of work. Please exclude my pre-existing tools, templates, methods, and general know-how, with a license for any background material embedded in the final work."

For unclear acceptance: "Could we add objective acceptance criteria and a five-business-day review period, with one consolidated revision request?"

For disproportionate liability: "Can we limit each party's responsibility to losses caused by matters it controls and discuss a liability cap proportionate to the project fees and available insurance?"

If a proposed restriction could block important future clients, expose personal assets, or transfer valuable pre-existing IP, the practical next step is a lawyer licensed in the relevant jurisdiction. Avoid relying on a fixed dollar threshold; a small contract can contain a large restriction.

Pre-signing checklist

  1. Save a complete, dated copy of every document and linked policy.
  2. Match the legal entity and signer's authority to the party that will pay you.
  3. Highlight definitions, incorporated documents, governing law, and survival clauses.
  4. Write down the information, systems, and people you will actually need to access.
  5. List all pre-existing tools, templates, code, assets, and know-how you plan to use.
  6. Confirm deliverables, acceptance, invoice trigger, payment date, revisions, and termination payment.
  7. Check whether confidentiality language also restricts clients, hiring, competition, publicity, or portfolio use.
  8. Request edits in writing and keep the final signed version with its exhibits.

Frequently asked questions

Look closely at unlimited definitions, missing exclusions, unclear permitted use, one duration for every type of information, hidden IP or noncompete terms, restrictions on lawful reporting, and one-sided remedies. Context matters, so use these as review prompts rather than automatic conclusions.

Check whether scope, acceptance, payment, changes, termination, ownership, liability, and disputes are clear and workable for both parties. Read all incorporated documents and compare the agreement with the commercial terms discussed.

No. Genuine trade secrets may justify protection while the information remains a trade secret. Ordinary business information is often handled with a defined term. The correct approach depends on the information and applicable law.

No. The FTC states that its nationwide Noncompete Rule is not in effect and not enforceable. State law and case-specific facts still matter.

Consider local advice when the contract restricts future work, assigns pre-existing IP, creates uncapped or unfamiliar liability, applies foreign law, or creates a risk you could not comfortably absorb.

Primary sources and limits

Last source review: July 30, 2026. This page explains review questions and does not determine whether any particular clause is valid or enforceable.

FG

FreelancerGuideHub Editorial Team

We turn primary sources and practical freelance workflows into plain-language decision guides. Material legal claims on this page are linked to official sources.

Was this checklist useful?

EDITORIAL REVIEW

How this page was checked

This page was rebuilt around observed search questions, checked for character-encoding errors, and reviewed against current US government and Copyright Office sources.

  • Ownership: FreelancerGuideHub editorial desk.
  • Evidence standard: primary government sources for legal-status claims; clearly labeled practical interpretation.
  • Scope: educational contract-review questions, not individualized legal advice or a finding that a clause is enforceable.

Read our editorial policy