What to Look for in an NDA Before You Sign

# What to Look for in an NDA Before You Sign

A client sends over an NDA and asks you to sign before the first call. Seems routine. You skim it, assume it's standard, and add your signature. But here's the thing — NDAs are not all created equal, and some of them contain clauses that could seriously limit what you can do, who you can work with, and what you can say for years after the project ends.

Non-disclosure agreements are one of the most commonly signed — and least carefully read — contracts in freelance work. They show up before discovery calls, at the start of projects, and sometimes mid-engagement when a client suddenly gets nervous about what you know. Most are reasonable. Some are not. Knowing the difference is entirely within your reach, even if you're not a lawyer.

Here's what actually matters when you're reviewing an NDA.

1. What Exactly Is Defined as "Confidential Information"

This is the single most important section in any NDA, and it's often where the problems hide.

Some agreements define confidential information narrowly — trade secrets, client lists, specific product specs. Others define it so broadly that virtually anything you learn during an engagement qualifies. One freelance developer described signing an NDA that defined confidential information as "any information, oral or written, disclosed during the relationship." That clause technically covered the fact that the company was hiring a developer at all.

Look for whether the definition includes a carve-out for information that: - Was already publicly known before you signed - You already knew before the engagement - You independently developed without using their information - You received from a third party without any confidentiality restriction

These exclusions are standard and protect you from being held liable for knowing things you legitimately already knew. If they're missing, ask for them to be added. Most reasonable clients won't push back.

Also check whether the confidential information needs to be marked as such. Some NDAs require the disclosing party to label documents "Confidential" — which gives you clarity. Others cover everything by default, which can feel unmanageable.

2. The Duration — and Whether It's Reasonable

Every NDA should have an end date. If yours doesn't, that's a problem worth raising.

A common structure is a one to three year confidentiality period from the date of signing or from the end of the project. That's generally fair. Perpetual NDAs — ones with no expiration — are harder to justify for most freelance engagements, especially for information that won't remain sensitive forever.

Imagine a UX designer brought in to work on a startup's app before launch. The product launches six months later. If the NDA has no time limit, the designer could technically be bound to secrecy about their involvement indefinitely — even after the work is public knowledge.

Trade secrets are the exception here. Genuinely proprietary formulas, algorithms, or processes can reasonably require ongoing confidentiality. But general business information, project scope, or internal team structures shouldn't tie your hands for life.

When you're reviewing NDA duration, also check whether the clock starts at signing or at the end of the relationship. The latter is more common and more protective for the client — just make sure you understand which applies.

3. Mutual vs. One-Sided: Who Is Actually Protected

There are two types of NDAs: unilateral (one-way) and mutual (two-way). Understanding which one you're signing matters.

A unilateral NDA protects only the client. You agree to keep their information confidential, but they have no equivalent obligation to protect yours. For most freelance relationships, this is standard — you're the one receiving sensitive business information, so it makes sense.

But consider this scenario: a brand strategist shares their proprietary workshop methodology, their pricing structure, and their client onboarding framework during a pitch to a potential client. If the NDA is one-sided, none of that is protected. The client could, in theory, take what they learned and use it however they like.

If you're sharing anything proprietary — your processes, your systems, your creative concepts — before a formal engagement begins, push for a mutual NDA. They're not unusual, and the ask is entirely legitimate.

One-sided agreements aren't automatically unfair, but you should know what you're agreeing to before you sign.

4. Obligations, Restrictions, and What You're Actually Agreeing to Do

Most people focus on what they can't disclose. Fewer read closely enough to notice what the NDA actually requires them to do.

Some NDAs include affirmative obligations — meaning active steps you must take to protect the information. These might include: - Limiting access to only those who need to know - Notifying the client immediately if you suspect a breach - Returning or destroying confidential materials at the end of the engagement

These aren't necessarily unreasonable, but you should know they exist. A content writer working from a client's shared Google Drive shouldn't be surprised to learn they're contractually required to delete all downloaded files upon project completion.

Also pay attention to restrictions on who you can share information with. Some NDAs prohibit you from discussing the work with subcontractors, collaborators, or even your accountant. If you regularly work with a virtual assistant or use third-party tools that process client data, make sure the NDA doesn't inadvertently put you in breach just by operating normally.

If in doubt, ask the client to clarify in writing. That email exchange can be valuable context if something ever becomes disputed.

5. Remedies and What Happens If Something Goes Wrong

This section tends to be buried near the end of an NDA, but it deserves careful attention.

Many NDAs include a clause stating that any breach — or even threatened breach — entitles the other party to seek an injunction without proving actual harm. That means they can go to court to stop you from doing something before any damage has even occurred. Combined with a clause that makes you liable for their legal fees if they prevail, the financial exposure can be significant.

Some agreements also include liquidated damages — a pre-agreed sum you owe if you breach, regardless of what the actual harm turns out to be. These clauses are common in high-stakes corporate contexts but occasionally turn up in freelance NDAs. If you see a fixed penalty clause, understand exactly what would trigger it.

None of this means you should refuse to sign. It means you should know what you're accepting. Most NDAs with robust remedy clauses are never enforced — but if the working relationship goes sideways, the contract you signed in a hurry becomes very relevant very quickly.

Before You Sign: A Practical Checklist

When an NDA lands in your inbox, run through these questions before adding your signature:

- Is confidential information defined clearly, with appropriate exclusions? - Is there a reasonable time limit on your confidentiality obligations? - Is this mutual, or one-sided — and is that appropriate given what you're sharing? - Are there any affirmative obligations that affect how you work day-to-day? - What are the consequences of a breach, and do they seem proportionate?

If you can answer all five with confidence, you're in good shape. If any of them leave you uncertain, that's your cue to ask questions or seek a second opinion before signing.

NDAs aren't documents to be feared. They're tools — and like any tool, they work better when you understand how they're built. Taking fifteen minutes to actually read one can save you from restrictions you never agreed to and obligations you didn't know you had.

If you want to move through contract review faster without missing the details that matter, JuriScans is worth bookmarking — it's built specifically to help freelancers and small businesses spot issues in agreements like NDAs before they become problems.