How to Review an NDA Before You Sign: A Freelancer's Complete Guide
Most freelancers sign NDAs without reading them. I understand why — you're excited about the project, the client seems legitimate, and the document looks like every other NDA you've seen. So you scroll to the signature line and sign.
Here's what that cost one developer I know: he signed a standard-looking NDA before a six-month contract. The IP assignment clause didn't have a carve-out for pre-existing code. When the project ended, the client claimed ownership of a logging library he'd built years earlier and used across dozens of other projects. Not the work product — his own tool. It took a $3,000 legal letter to resolve something that should have taken fifteen minutes to catch.
This is a guide on how to review an NDA before you sign: what to look for, what's genuinely dangerous, and what to do when you find something you don't like.
What Is an NDA and Why Should Freelancers Care?
A non-disclosure agreement (NDA) is a contract that restricts what you can say, share, or do with information you receive during a client engagement. They're standard before any serious project — tech work, creative engagements, consulting, advisory roles.
From the client's side, an NDA is paperwork. From yours, it's a legal document that can restrict your future earning potential, your portfolio rights, and your ability to use tools you built yourself.
The asymmetry is the problem. The client's legal team spent hours drafting this document to protect the client as broadly as possible. Nobody is looking out for your interests except you. And freelancers are particularly exposed because most don't have a retained lawyer, don't have time to wait three days for a legal review, and are in the uncomfortable position of "I'd rather just sign and get started."
That discomfort is exactly what these documents rely on.
If you want a deeper look at the specific risks by freelancer type, read NDA review for freelancers. This post is about the process of reviewing one.
Step 1 — Read the Entire Document First (No Shortcuts)
The most common mistake freelancers make is reading an NDA like a checklist — jumping to the non-compete clause, skimming everything else, and calling it done.
Don't do this.
NDAs are written as interconnected systems. The definition section at the front determines the scope of every obligation in the document. A non-compete clause that looks reasonable in isolation might cover your entire industry if the "competitive business" definition is written broadly enough. An indemnification clause that seems standard might be uncapped if the liability section three pages later doesn't apply to indemnity claims.
Read the whole document once, in order, before evaluating anything. On the first pass, don't try to assess every clause — just understand what you're looking at. Mark anything that feels unusual or unclear. Then go through the eight specific areas in Step 2.
Most freelance NDAs are 3–5 pages. This takes 10–15 minutes. That is the entire cost of not making a $3,000 mistake.
Step 2 — How to Review an NDA: Check These 8 Clauses
Not all clauses carry equal risk. These eight categories are the ones that consistently cause problems for freelancers — and the ones NDA Guard scores on every review.
1. Non-compete scope and duration
What it is: A restriction on working with competitors or in the same industry for a period after the engagement ends.
Risky version: "You may not work for any company in the same industry as Client for 24 months after termination, worldwide." That's your entire client base, gone for two years.
Market standard: 12 months, scoped to direct competitors (ideally named), limited to the geography where the client actually operates.
Watch for: Duration over 18 months. Industry scope broad enough to cover your entire practice area. Worldwide geography. Non-competes that apply during unpaid gaps in the engagement.
2. IP assignment and pre-existing IP carve-outs
What it is: Transfers ownership of work you create during the engagement to the client.
Risky version: "All work product, including any pre-existing materials incorporated into deliverables, shall be the sole property of Client." This can capture tools, frameworks, and templates you built long before this project.
Market standard: Assignment limited to deliverables created specifically for this engagement, with an explicit carve-out for "Contractor's pre-existing tools, libraries, and materials" — ideally listed in a schedule or exhibit.
Watch for: The phrase "including pre-existing materials." Any claim to tools you use across multiple clients. No carve-out language at all.
3. Duration of confidentiality
What it is: How long you're legally bound to keep information confidential.
Risky version: "In perpetuity," "indefinitely," or "for so long as the information remains a trade secret." This creates obligations that could theoretically never expire.
Market standard: 2–5 years from the end of the engagement. Up to 7 years is acceptable for sensitive technology. Indefinite duration is not.
Watch for: Any language that doesn't specify an end date. "For the life of the trade secret" sounds legitimate but is functionally indefinite. Clauses that survive termination "indefinitely."
4. Jurisdiction and governing law
What it is: Specifies which state or country's laws govern the contract, and where any disputes must be resolved.
Risky version: "This Agreement shall be governed by the laws of Delaware and any disputes shall be resolved exclusively in the courts of Delaware" — when you're a freelancer in London, Melbourne, or Berlin.
Market standard: Your jurisdiction, or a neutral location, or binding arbitration through an established body (AAA or JAMS).
Watch for: Courts in another country. Any language that waives your right to contest jurisdiction. No arbitration option for international parties.
5. Indemnification scope
What it is: You agree to cover the client's costs if they face legal claims related to your breach of the NDA.
Risky version: Unlimited indemnification — "Contractor shall defend, indemnify, and hold harmless Client from all claims, damages, and expenses arising from any breach." No dollar cap. No carve-outs.
Market standard: Indemnification capped at the total fees paid under the contract, limited to claims arising directly and provably from your breach.
Watch for: No cap anywhere in the document. "Arising from or related to" language (too broad). Indemnification that covers third-party claims not directly caused by your breach.
6. Liquidated damages
What it is: A pre-agreed financial penalty per breach, regardless of actual harm caused.
Risky version: "$10,000 per unauthorized disclosure." If you accidentally mention a project name to the wrong person, you owe $10,000 — whether or not anyone was actually harmed.
Market standard: Most standard freelance NDAs don't include liquidated damages at all. When they appear, they should be proportionate to realistic harm.
Watch for: Any fixed-dollar penalties per breach. These are unusual in standard freelance NDAs and worth flagging every time you see them.
7. Confidentiality scope breadth
What it is: The definition of what information is actually confidential.
Risky version: "All information disclosed by Client, whether oral, written, electronic, or implied, shall be Confidential Information." This covers publicly available information, things you already knew, and anything you could infer from context.
Market standard: Defined categories (technical specifications, customer lists, business strategy, financial data) with explicit carve-outs: publicly available information, information you already possessed before the engagement, and information you independently develop.
Watch for: No carve-outs at all. Oral disclosures with no written confirmation requirement. Definitions that don't expire even after information becomes public.
8. Return and destruction obligations
What it is: What you must do with confidential materials when the engagement ends.
Risky version: "Upon termination, Contractor shall immediately return or destroy all Confidential Information and provide written certification that no copies exist." If you've received information in email threads, this is impossible to comply with literally.
Market standard: "Commercially reasonable efforts" to return or destroy materials, with carve-outs for information stored in backup systems or inherently retained in professional records.
Watch for: Absolute destruction requirements with no exceptions. Certification obligations you can't honestly fulfill. Unreasonably short timelines (48 hours to destroy all materials is not standard).
NDA Guard reviews your NDA automatically — flags all 8 risk categories above in 60 seconds. Risk scored, plain English, with counter-language ready to paste. First review free →
Step 3 — Understand What You'd Actually Be Agreeing To
After reading through the document and flagging specific clauses, do a plain-English translation of the obligations you'd actually be taking on.
Write them out simply:
- "I can't work with any software company for two years after this ends."
- "I'm handing over ownership of any tools I use in this project."
- "If there's a dispute, I'd have to appear in Delaware."
- "If I accidentally mention this project, I owe them $10,000."
Seeing your obligations in plain sentences makes it much easier to evaluate whether they're reasonable. It also prepares you for the negotiation in Step 5, because you'll be negotiating specific obligations — not abstract legal language.
This exercise often surfaces problems that weren't obvious in the legal text. If you can't translate a clause into plain English after two attempts, that's a signal in itself. Vague obligations in contracts tend to be interpreted in favor of the party with more legal resources.
Step 4 — Decide: Sign, Negotiate, or Walk Away
After steps 1–3, you have a clear picture of what this NDA actually asks of you. Now you make a decision.
Sign as-is if: The obligations are reasonable, the duration is capped, the IP assignment has carve-outs for your existing work, and the jurisdiction is workable. Most NDAs from legitimate companies — especially for shorter engagements — fall here. Sign them.
Negotiate if: You found 1–3 specific issues that are material to your business. A non-compete that covers your entire client base. IP assignment with no pre-existing IP carve-out. Indefinite confidentiality duration. These are normal things to push back on, and most clients will engage professionally.
Walk away if: The NDA contains unlimited liability, punitive damages, requires you to surrender your existing portfolio or tools, or restricts your ability to earn a living in ways you can't negotiate out of — and the client refuses to modify anything. A client who won't budge on genuinely one-sided terms is telling you something useful before you start working together.
The vast majority of engagements fall in the first two categories. Most NDAs are fixable with targeted, professional pushback.
Step 5 — How to Request Changes Professionally
When you find something you want to change, don't reject the NDA — counter it. Most clients will engage if you approach this correctly.
The formula:
- Acknowledge the purpose of the clause ("I understand you want to protect competitive information")
- Identify the specific issue ("The current language would prevent me from working with any software company for two years, not just direct competitors")
- Propose specific replacement language ("I'd suggest limiting this to direct competitors in your product category, for 12 months from the engagement end date")
Specific, professional counter-proposals get accepted far more often than vague objections. Legal teams respond to tracked changes and redline comments — not emails that say "this seems unfair."
How to frame the email: keep it brief, stay professional, and frame it as making the agreement workable for both parties. Something like: "I've reviewed the NDA and have a couple of questions on clauses 4 and 7. I've marked up the document with suggested changes and I'm happy to discuss on a quick call."
When to Hire a Lawyer Instead
There are situations where a 60-second AI review isn't the right tool.
Get a lawyer when:
- The NDA involves equity, stock options, or a significant financial stake in the company
- Non-compete restrictions could realistically affect your ability to work in your field for years
- The indemnification is uncapped and the engagement involves meaningful financial exposure
- The client refuses to modify any terms and the contract is material to your income
- You've read the document twice and still don't understand what a clause is asking you to agree to
AI review is best used as a fast, reliable first pass. It tells you whether a lawyer is warranted — and if so, what specific questions to bring. Walking into a $200 legal consultation with the clauses already identified and your questions written down cuts the time (and the bill) significantly.
FAQ
How long should it take to review an NDA?
For a standard 3–5 page freelance NDA, plan for 15–20 minutes doing it yourself. With an AI tool like NDA Guard, the initial analysis takes 60 seconds and gives you a risk-scored summary across all 8 categories — you can then decide whether any individual clause needs deeper attention. Budget more time for longer documents (some enterprise NDAs run 8–10 pages) or agreements with terms you haven't seen before.
What if I don't understand a clause?
Ask. You can ask the client's contact directly: "Can you help me understand what clause 7.3 is trying to protect?" That's not a red flag — it's a reasonable question. You can also paste the clause into NDA Guard or any capable language model to get a plain-English explanation. If you still can't understand it after two attempts, that clause is worth a lawyer's attention. Vague obligations tend to be interpreted in favor of the party who drafted them.
Can I ask a client to change their NDA?
Yes — and you'll succeed more often than you expect. Clients send standard NDAs because their legal team drafted one years ago and nobody pushes back. When you make specific, professional counter-proposals rather than general complaints, most legitimate clients will engage. You're more likely to get a change accepted if you can briefly explain why the current language creates a disproportionate burden relative to what the client actually needs.
Is it bad to ask for changes to an NDA?
No. Asking for reasonable modifications to a one-sided NDA is professional. It signals that you read the document, understand your rights, and take your agreements seriously. Experienced clients expect this from serious contractors. The only time it causes friction is if you object to every clause without specific reasons — which reads as stalling rather than negotiating.
What's the most dangerous NDA clause for freelancers?
IP assignment without a pre-existing IP carve-out. This is the clause most likely to have long-term financial consequences — because it can transfer ownership of tools and assets you use across multiple clients, not just deliverables created for this one project. Non-compete clauses feel more immediately threatening, but they're also more often unenforceable. Broad IP assignment is enforceable, and it's nearly impossible to undo once signed and the project is complete.
Sign Informed, Not Blind
Reviewing an NDA doesn't require a law degree. It requires knowing what to look for and spending fifteen minutes actually looking. The eight clauses above cover the vast majority of risks freelancers face — and they take less time to check than most client onboarding forms.
Most NDAs are fine. Some need targeted changes. A few are worth walking away from. The only way to know which one you're holding is to read it.
If you want a faster path, NDA Guard reviews the full document automatically — scores all 8 categories, explains every flagged clause in plain English, and gives you counter-language ready to paste. First review is free.