How to Read a Freelance NDA in 5 Minutes

NDAs arrive as a formality — "just sign this before we get started." Most freelancers sign without reading. But a badly drafted NDA can block your portfolio, prevent you from working in your field, and expose you to liability that outlasts the project by years.

Here's what to check in five minutes before you sign.

1. Is it mutual or one-sided?

A mutual NDA protects both parties. A one-sided NDA only protects the client — you agree to keep their information confidential, but they make no corresponding promise about yours.

One-sided NDAs are common and not automatically a dealbreaker. But you should know which one you're signing. Look at the first paragraph for language like "Recipient agrees..." (one-sided) vs. "Each party agrees as a Recipient..." (mutual).

If you're sharing your own proprietary methodology, processes, or pricing with the client, push for mutual language.

2. How long does it last?

Look for the duration clause. Reasonable NDA terms:

1–3 years — standard for most freelance work. Long enough to protect genuinely sensitive business information, short enough to not haunt you forever.

5+ years or "indefinitely" — overreaching for most engagements. Perpetual NDAs are appropriate for trade secrets (a Coca-Cola recipe), not for a brand guidelines document or a software feature you built.

Redline: "The obligations of confidentiality in this Agreement shall survive for two years following termination of the engagement, after which this Agreement shall have no further effect."

3. What counts as "confidential information"?

The definition of confidential information is where most NDAs become overreaching. Red flag language:

"All information disclosed by Disclosing Party, whether oral, written, or electronic, whether or not marked as confidential."

This means a casual Slack message is now covered. A hallway conversation is covered. "What's your availability next quarter?" is confidential information. That's not what NDAs are for.

Better language: "Information that is: (a) marked as confidential at the time of disclosure, or (b) identified as confidential orally and confirmed in writing within 5 business days."

4. Does it cover your portfolio?

Many NDAs inadvertently — or deliberately — prevent you from using the work in your portfolio. The confidentiality clause sweeps up all deliverables, which means showing a client your past work violates the NDA from three engagements ago.

Always add an explicit carveout: "Notwithstanding the foregoing, Contractor may include Client's name and a general description of the services performed in Contractor's portfolio, website, and marketing materials, provided no Confidential Information is disclosed."

5. What are the exceptions?

A well-drafted NDA always includes standard exceptions for information that's already public, that you knew before the engagement, or that you develop independently. If these exceptions are missing, push to add them — they protect you from impossible situations.

Standard exceptions: "Confidential Information does not include information that: (a) is or becomes publicly available through no fault of Recipient; (b) was already known to Recipient before disclosure; (c) is received from a third party not bound by confidentiality; or (d) is independently developed by Recipient without use of Disclosing Party's Confidential Information."

6. What's the remedy for breach?

Check what happens if you accidentally share something. Some NDAs specify "injunctive relief" — meaning the client can get a court order immediately, without proving damages. That's aggressive language for a freelance engagement. More reasonable: a cure period before legal action.

"In the event of a breach or threatened breach, Disclosing Party shall provide Recipient written notice and a 5-day opportunity to cure before seeking any remedy."

The five-minute checklist

Before signing any NDA, check:

☐ Mutual or one-sided?
☐ Duration — 2 years or less?
☐ Definition of confidential information — specific or sweeping?
☐ Portfolio carveout present?
☐ Standard exceptions (public info, prior knowledge) present?
☐ Reasonable breach remedy — not automatic injunction?