NDAs are normal—overreach is not
Clients have legitimate reasons to protect product roadmaps, customer lists, and unpublished launches. Freelancers have legitimate reasons not to sign away their entire professional future for a two-week sprint. A good NDA is narrow, mutual where appropriate, and time-bounded. A bad NDA reads like a non-compete and an IP assignment wearing a confidentiality costume.
You do not need to be combative. You need to spot clauses that create outsized risk relative to the fee, then propose specific edits.
Watch for perpetual and undefined confidential information
If “confidential information” includes anything you see or hear with no exclusions for public knowledge, your own pre-existing tools, or residual general skills, push back. Ask for standard exclusions and a fixed term—often two to five years for ordinary commercial secrets, sometimes longer for true trade secrets properly identified.
Perpetual silence about vaguely defined information is difficult to honor and easy to litigate aggressively. Precision protects both parties.
IP assignment clauses hidden inside NDAs
Some documents labeled “NDA” quietly assign all work product and related ideas to the client, including your pre-existing frameworks. Confidentiality and ownership are different issues. Keep them in separate sections or separate agreements. Preserve your pre-existing IP with a schedule of excluded tools and libraries you bring to every engagement.
If the client needs work-product ownership, use a clear work-for-hire or assignment clause tied to paid deliverables—not a blanket grab of everything you think during the term.
Non-compete and non-solicit creep
Language that forbids working for any competitor, contacting any customer, or using general industry knowledge can function as a non-compete even if that word never appears. Narrow non-solicits focused on the client’s specifically introduced customers for a limited time may be negotiable; worldwide bans on practicing your craft are not a fair price for a short contract.
Jurisdiction matters. Some places heavily restrict non-competes. Still, do not sign harsh terms because you assume they are unenforceable—avoid the fight if you can.
Mutuality, residuals, and injunctive relief
Prefer mutual confidentiality when you will also share pricing, methods, or subprocessors. Residuals clauses (allowing use of residual mental knowledge without using documents) can be reasonable if drafted carefully. One-sided injunctive relief language is common; still read fee-shifting and arbitration terms so you know the dispute venue.
A clean NDA builds trust. An overreaching one signals how the client handles power. Negotiate early, in writing, and keep the signed PDF with the SOW.
How to propose edits without killing the deal
Send a short note: you are happy to protect true confidential information, and you need standard exclusions, a defined term, and IP language limited to paid deliverables. Attach a redlined PDF or a bullet list of requested changes. Clients who refuse any edit on a one-sided perpetual NDA for a tiny project are telling you how disputes will feel later.
Offer fallback positions. If they will not go mutual, ask for clearer definitions. If they want a longer term, ask for a narrower definition of secrets. Negotiation is tradeoffs, not a single ultimatum.
Align the NDA with the statement of work
The SOW should state deliverables, payment, and reuse of your pre-existing tools. The NDA should not contradict the SOW by assigning those tools away. If marketing case studies matter to you, reserve the right to list the client name or describe the project at a high level once it is public. Silence about publicly shipped work is often unnecessary.
Keep versions. The NDA you signed in January may not match the SOW you signed in March unless you force consistency.
When to walk away
Walk if the document bans you from working in your entire industry, claims ownership of unrelated ideas, or imposes uncapped liability for confidentiality breaches on a small fixed-fee job. Your downside must stay proportional to the upside. Professional confidentiality is reasonable. Career handcuffs for a logo redesign are not.
Good clients understand that freelancers protect themselves. The NDA conversation is an early culture test—use it.
Security addenda and data handling
Modern NDAs sometimes bundle security requirements: encryption, subprocessors, breach notice windows. Those can be reasonable for sensitive work. Make sure they match the actual data you will touch. A copywriter drafting blog posts should not accept hospital-grade HIPAA schedules by accident. Scope the data, then accept controls proportional to that data.
If you use subcontractors, ensure you can flow down confidentiality obligations—or disclose that you work solo. Surprises about subcontracting destroy trust faster than most clause disputes.
Finally, store signed NDAs where you can find them. A searchable folder named by client and year prevents the awkward moment when a new SOW arrives and nobody remembers what you already promised.