For freelancers & contractors
Client NDAs hit freelancers differently: a broad definition can lock up your portfolio, a hidden non-solicit can cost you future clients, and residuals language can restrict the skills you sell. The NDA red flags freelancers should check, in plain English, with the fix for each.
Updated July 14, 2026 · 6 min read
Freelancers sign more NDAs than almost anyone: many clients send one before the first call. Most are harmless. But an NDA reads differently when you are independent, because the same clauses that mildly inconvenience an employee can quietly restrict your portfolio, your niche, and your future client list, the things your business actually runs on.
This guide covers the NDA red flags that matter specifically for freelancers and independent contractors: portfolio bans hiding in the confidentiality definition, non-solicit clauses that shrink your market, residuals language that claims the know-how you sell, and one-way agreements that bind you but not the client.
It is general information, not legal advice. Use it to read the NDA a client just sent you, push back where it overreaches, and sign the reasonable ones with confidence. If you want a second pair of eyes, ClauseShift reviews the actual document in minutes and quotes the exact clause behind every flag.
If 'confidential information' covers everything you learn or produce during the engagement, then showing the work in your portfolio, or even naming the client, can technically breach the NDA. For a freelancer, an invisible portfolio is a real business cost that an employee never pays.
Ask for: Ask for an explicit portfolio carve-out: the right to display the finished work and name the client once the project is public, or after a defined quiet period.
Buried non-solicit language can bar you from working with the client's customers, partners, or contacts, sometimes for years. Your next three clients may be people you met on this project. An employee gives up little by signing this; a freelancer gives up pipeline.
Ask for: Ask to strike non-solicit language from the NDA entirely, or narrow it to people you only know because of this engagement, with a short term.
You sell the same skills to every client. A clause that restricts 'residual knowledge', general techniques, processes, and experience you retain in your head, can claim the very expertise you charge for, and make your next similar project a breach risk.
Ask for: Ask for an explicit residuals clause: general skills, knowledge, and experience retained in unaided memory are excluded from confidentiality.
Client NDAs are usually drafted one-way: you are bound, they are not. But freelancers disclose too: your rates, your methods, your proposals, your tooling. If the NDA only protects them, your pitch and pricing can be shopped to a cheaper competitor with no recourse.
Ask for: If you will share proposals, methods, or pricing, ask to make the NDA mutual so the same duties run both ways.
An employee's NDA obligations fade into the background of a salary. A freelancer juggling many clients has to actively remember and police every live NDA. Indefinite or five-plus-year terms multiply across every client you have ever signed with.
Ask for: Ask for a two-to-three-year term from disclosure, with only true trade secrets lasting longer.
Watch for IP assignment, non-competes, exclusivity, or indemnities smuggled into a 'standard NDA' sent before you have even scoped the work. Those terms shape the whole engagement and deserve negotiation in the actual freelance contract, not a signature on day zero.
Ask for: Ask to keep the NDA confidentiality-only and move IP, exclusivity, and liability terms into the services agreement where they can be priced and negotiated.
An NDA is written once and signed by many, and it is usually drafted with employees in mind. An employee has one employer, a salary that continues while they comply, and an HR department that remembers the paperwork. A freelancer has many clients, gets paid per project, and personally carries every obligation they have ever signed.
That asymmetry is why the same clause lands differently. A broad confidentiality definition costs an employee nothing visible; it costs a freelancer their portfolio. A non-solicit means little inside a salaried job; it deletes future clients for an independent. Reading an NDA as a freelancer means asking one question of every clause: what does this cost my business after this project ends?
Most client NDAs are templates nobody at the client has read closely. Asking for a portfolio carve-out, a mutual duty, or a defined term is normal professional hygiene, not hostility, and clients who work with freelancers regularly expect it. A short, specific request ('can we add a portfolio carve-out once the project is public?') gets a yes far more often than a redlined document.
If a client refuses every reasonable change, that is information. The NDA is the first document in the relationship; how they negotiate it predicts how they will negotiate scope changes and invoices. Run the NDA through ClauseShift first so you know exactly which clauses to raise, each one quoted, and which are standard and safe to sign as-is.
Paste the text, upload a PDF or DOCX, record a voice note, or email the contract to review@clauseshift.com. You get a plain-English risk report: an overall score and the specific clauses that matter, each with the exact contract text quoted so you can verify it yourself. ClauseShift does not keep the document you upload, only the report is saved to your account, and it trains no AI of its own on your contracts.
Only if the NDA lets you. If the confidentiality definition covers the deliverables, displaying them or naming the client can be a breach. Ask for a portfolio carve-out before signing; many clients will agree to one once the project is public.
Sometimes. If only the client discloses anything sensitive, one-way is fine. If you will share proposals, pricing, or methods, ask to make it mutual so your side of the conversation is protected too.
A pure confidentiality clause should not, but non-solicit, non-compete, or exclusivity language hidden in an NDA can. That is a red flag: ask to strike it or negotiate it separately in the services contract where it can be priced.
Weigh the specific risk. A stubborn overbroad NDA on a small project may not be worth it, especially with portfolio bans or non-solicits. How a client negotiates the NDA also tends to predict how they will handle scope and payment later.
Yes. Paste or upload the NDA and you get a plain-English risk report in minutes, with every flag quoting the exact clause it came from, including portfolio, non-solicit, and residuals issues. Free to start, no card needed.
Last reviewed July 14, 2026. ClauseShift Review provides informational risk summaries and is not a substitute for legal advice.