NDA for Independent Consultants and Fractional Executives: What's Different
If you serve five clients at once, you face NDA exposure that a full-time employee never will. Every new engagement adds another confidentiality obligation layered on top of all the others — different clients, different industries, overlapping timelines, and often directly competing interests. The risk isn't that any single NDA is unreasonable. The risk is that five individually reasonable NDAs, signed by someone whose job is to bring the same expertise and methodology to each client, compound into something that quietly constrains your entire practice.
This post covers the clause types that matter most for independent consultants and fractional executives: multi-client conflicts, prior knowledge and methodology protection, non-solicitation reach, duration risk in long engagements, and the residuals clause you should be asking for. Each section includes counter-language you can use.
For the broader list of clause types dangerous across all freelance relationships, 8 NDA Red Flags Every Freelancer Should Know is the right starting point. This post focuses on what makes the consultant's situation specifically more complex.
The Multi-Client Conflict Problem
A full-time employee signs one NDA and works for one employer. You sign multiple NDAs and work for multiple clients simultaneously — some of whom may be direct competitors. The clause that creates the most risk here is the confidentiality scope combined with the definition of "Confidential Information."
Most NDAs define confidential information broadly:
"All information disclosed by Client, directly or indirectly, in writing, orally, or by inspection of tangible objects, including but not limited to business strategies, financial data, customer lists, product plans, technical data, trade secrets, and other business information."
That definition is standard and usually fine in isolation. The problem is what happens when you're simultaneously serving Client A and Client B in the same market, and something Client A tells you in a strategy session is information you've already encountered from Client B — or will encounter from Client C next month.
You did not technically disclose Client A's information. But your advice to Client B, shaped by your knowledge of Client A's strategic direction, may constitute an indirect disclosure. You used Client A's confidential information — even if only as background context — to inform work that benefits a competitor.
This is not a hypothetical edge case. It is the central operational risk for consultants who work across competitors. The clauses that make it worse:
- Broad "use" restrictions: Many NDAs prohibit not just disclosure but any "use" of confidential information for any purpose other than the engagement. If your expertise was shaped by what you learned at Client A, using that expertise for Client B could technically violate the restriction.
- Industry-wide confidentiality definitions: Some NDAs define confidential information to include any knowledge of "industry trends, competitive dynamics, or market conditions" disclosed during the engagement. This turns market knowledge — the thing clients are paying you for — into a restricted asset.
What to do: Before signing any NDA, map it against your existing client list. If two clients are direct competitors, consult an attorney about conflict waivers or recusal protocols before proceeding. When you do sign, push for an explicit carve-out for general industry knowledge and pre-existing expertise:
Counter-language: "Confidentiality obligations do not apply to general market knowledge, industry trends, or professional expertise that Consultant developed prior to or independently of this engagement, even if Client disclosed related information during the engagement. This Agreement does not prohibit Consultant from serving other clients, including those in Client's industry, provided Consultant does not directly disclose Client's Confidential Information."
Prior Knowledge and Existing Methodology
Your frameworks are your product. The diagnostic process you run in week one, the workshop structure you've used across forty clients, the operational model you've refined over a decade — these are what clients are actually buying when they hire you. And standard IP assignment clauses are written in a way that can capture all of it.
The clause to watch:
"All work product, inventions, improvements, discoveries, and other materials created, developed, conceived, or reduced to practice by Consultant in connection with the Services shall be the sole and exclusive property of Client."
"In connection with the Services" is the phrase that creates the problem. If you deploy your standard diagnostic framework during a client engagement, and the deliverable you hand over includes that framework or is built on it, the clause above could assign the framework itself to the client — not just the output.
This matters in a way it simply does not for most employees. An employee who uses a company methodology to do company work is not personally at risk. You are deploying your own methodology to do client work — and the IP assignment clause does not automatically distinguish between the two. Without an explicit carve-out, you may be signing away the tool you use to serve every other client.
Related but separate: the "feedback and improvements" problem. If a client engagement prompts you to refine a methodology — a better way to run a workshop, an improved diagnostic question — the refinement may be captured as IP belonging to the client. You brought the framework in; you improved it during the engagement; they now own the improved version.
The fix is a pre-existing IP carve-out combined with a background materials clause. For a full analysis of how these clauses are typically drafted and what to ask for, the IP clause breakdown covers this in detail.
Counter-language: "Client shall own deliverables created specifically for Client under this Agreement. The foregoing does not apply to Consultant's pre-existing frameworks, methodologies, tools, templates, processes, or other materials developed prior to or independently of this engagement ('Background Materials'). Consultant retains all rights in Background Materials. Where Background Materials are incorporated into deliverables, Client receives a non-exclusive license to use the Background Materials as incorporated, but not independently."
Non-Solicitation Clauses
Non-solicitation and non-compete clauses are often conflated, but they restrict different things. A non-compete prevents you from working in a market or for competitors. A non-solicitation prevents you from approaching specific people — typically the client's employees, customers, or contractors.
For consultants, non-solicitation is usually the more common restriction — and the more insidious one, because it sounds narrow but can operate as a de facto non-compete depending on how it's written.
Here is a clause that looks reasonable:
"For a period of twelve (12) months following termination of this Agreement, Consultant shall not directly or indirectly solicit, recruit, or engage any employee, contractor, or customer of Client."
Now apply it to a fractional executive role. You spend 18 months embedded in a company. You know every key hire, every significant customer, every major vendor. The "employees and contractors" this clause covers might include people you've worked with daily for a year and a half — people who, independently, reach out to you about future work. The "customers" this clause covers might be entire industry categories you've built expertise serving.
The practical effect: you cannot follow up when a senior hire at that company moves to a new role and wants to bring you in. You cannot respond to inbound interest from customers who encountered your work during the engagement. You cannot work with vendors you built relationships with on the client's behalf.
Non-solicitation clauses are generally more enforceable than non-competes, and they survive in jurisdictions where non-competes are heavily restricted. They deserve the same scrutiny. The key questions:
- Does "solicit" cover inbound contact, or only outreach you initiate?
- Does "customers" mean current customers only, or former customers and prospects too?
- Does "employees" include people who were employees when you started but have since left?
Counter-language: "Consultant shall not directly solicit Client's current employees or contractors for competing services during the term of this Agreement and for six (6) months thereafter. This section does not apply to general solicitation (job postings, advertisements), responses to inbound contact initiated by individuals independently, or any individual who has ceased to be employed or engaged by Client prior to such contact."
Duration Risk for Long-Term Engagements
Fractional executive roles — fractional CFO, CMO, COO, CTO — frequently run 12 to 24 months. That duration creates a specific compounding problem: long engagement plus indefinite confidentiality survival equals a significant long-term constraint.
The survival clause is the piece most people skip:
"The obligations of confidentiality set forth in this Agreement shall survive termination and continue indefinitely with respect to trade secrets, and for a period of five (5) years with respect to all other Confidential Information."
Five years is common. Indefinite for trade secrets is nearly universal. Now apply that to a 24-month fractional CFO engagement. You were embedded in every major financial decision, board conversation, and strategic initiative for two years. The "confidential information" you're carrying forward covers decisions, personnel, financial structure, and strategic direction that may define the company for another decade.
This is not unreasonable from the client's perspective. The problem is how "Confidential Information" was originally defined — often as any information you received, regardless of whether it was marked or treated as sensitive. After a long embedded role, almost everything you know about the company falls under that definition.
The risk surfaces when you take your next engagement. How much of what you know can you use? How much of your sector expertise, sharpened by this engagement, is technically covered by the survival clause? How do you give a reference call about the company without disclosing confidential information?
What market standard looks like: Confidentiality obligations should be time-bounded (3–5 years for general confidential information, indefinite only for information that actually meets the legal definition of a trade secret). The definition of confidential information should exclude information that becomes publicly available, information you receive independently from a third party, and information you can demonstrate you knew prior to the engagement.
Counter-language: "Confidentiality obligations shall survive for three (3) years following termination of this Agreement. Obligations survive indefinitely only for information that meets the legal definition of a trade secret under applicable law. Obligations do not apply to information that: (a) becomes publicly available through no breach of this Agreement; (b) Consultant can demonstrate was known prior to disclosure; or (c) is received from a third party without restriction."
Serving multiple clients means you're signing NDAs constantly — and each one affects the others. NDA Guard reviews your full agreement, flags multi-client conflicts, IP overreach, and non-solicitation scope, and gives you counter-language ready to paste. Try your first review free →
The "Residuals" Clause
The residuals clause is one of the few NDA provisions that works in your favor — and most consultants never think to ask for it.
Here is what it looks like:
"Notwithstanding the foregoing, Consultant shall not be restricted from using Residual Knowledge in the conduct of Consultant's business. 'Residual Knowledge' means any information that is retained in the unaided memory of Consultant's personnel who had access to Confidential Information, without intentional memorization for the purpose of retaining and subsequently using or disclosing such information."
In plain English: anything you learn that you remember naturally, without deliberately trying to memorize it, is not subject to the confidentiality obligations. You cannot take notes home and use them. You cannot retain documents. But knowledge that becomes part of your professional understanding through the course of working — the kind of expertise that accretes over a long engagement — is not captured.
This clause originated in tech industry NDAs, particularly in Silicon Valley, as a practical acknowledgment that knowledge workers cannot surgically excise what they've learned. It has since become more broadly used in professional services contexts.
Why it matters for consultants: without a residuals clause, a strict reading of most confidentiality agreements means that after a long fractional engagement, your professional judgment itself is technically restricted. Every recommendation you make to the next client was shaped by what you learned at the last one. The residuals clause is the legal acknowledgment that this is how expertise works — and that it's not a breach.
Not every client will agree to a residuals clause. Some legal teams treat it as a loophole. But it is a legitimate and well-established provision in professional services agreements, and asking for it is not unusual.
Counter-language: "Notwithstanding any other provision of this Agreement, Consultant shall not be restricted from using, in the conduct of Consultant's business, Residual Knowledge retained in the unaided memories of Consultant's personnel without intentional memorization. 'Residual Knowledge' excludes documents, notes, or other tangible records that constitute Confidential Information."
Counter-Language Consultants Should Ask For
Consolidated from the sections above — a checklist for any consulting NDA:
Multi-client carve-out: "This Agreement does not prohibit Consultant from serving other clients, including those in Client's industry, provided Consultant does not directly disclose Client's Confidential Information."
Pre-existing methodology: "Consultant retains all rights in Background Materials developed prior to or independently of this engagement. Client receives only a non-exclusive license to Background Materials as incorporated into deliverables."
Non-solicitation scope: "Non-solicitation applies to direct outreach to current employees and contractors only. It does not apply to general solicitation or inbound contact initiated independently by individuals no longer employed by Client."
Confidentiality duration: "General confidentiality obligations survive for 3 years. Indefinite survival applies only to information meeting the legal definition of a trade secret."
Residuals: "Consultant may use Residual Knowledge retained in unaided memory in the conduct of Consultant's business, provided Consultant does not retain tangible records of Confidential Information."
Definition limits: "Confidential Information excludes general industry knowledge, publicly available information, information known to Consultant prior to disclosure, and information received from third parties without restriction."
FAQ
Can I work for two competing clients at the same time?
In most cases, yes — unless one of your NDAs includes an explicit exclusivity clause or a sufficiently broad non-compete. What you generally cannot do is directly disclose one client's confidential information to the other. Whether your advice implicitly draws on what you've learned is a murkier question that depends on how broadly the NDA defines "use." If both clients are direct competitors in a narrow market, it is worth reviewing both NDAs together — or getting counsel — before proceeding. This is a conflict management problem as much as a legal one.
Is a non-solicitation clause the same as a non-compete?
No. A non-compete prevents you from working in a market or for a class of competitors. A non-solicitation prevents you from approaching specific individuals (employees, customers, contractors) associated with a client. Non-solicitation clauses are generally more enforceable and survive in jurisdictions where non-competes are restricted, including California for most service providers. Consultants frequently encounter non-solicitation clauses as a substitute when clients know a non-compete won't hold up — but the practical effect on your practice can be significant depending on how "solicit" and "customers" are defined.
What's the difference between a unilateral and mutual NDA for consulting engagements?
A unilateral NDA protects only the client's information. A mutual NDA protects both parties. For most consulting engagements, the client will present a unilateral NDA — they're sharing sensitive information with you and want it protected. If you're sharing proprietary methodology or tools as part of the engagement, a mutual NDA is appropriate to ask for. In practice, many clients will push back, but a mutual NDA is a reasonable request when you're bringing IP to the table, not just receiving it.
How do I handle an NDA clause that covers every conversation I'll have during a 12-month engagement?
By limiting the definition of confidential information and adding a residuals clause. After a long embedded role, almost everything you know about a company could technically qualify as "information received during the engagement." Without limits on the definition and a residuals carve-out for knowledge retained in memory, the confidentiality obligation could functionally cover your entire professional judgment in that sector for years. The counter-language in the Duration Risk and Residuals sections above directly addresses this.
Should I review each new client NDA against my existing agreements?
Yes, and this is one of the most systematically underperformed parts of consultant NDA management. You are looking for: direct conflict with existing clients, definitional overlap that could make general expertise a restricted asset, and cumulative non-solicitation scope that, across multiple agreements, starts to cover most of your industry contacts. If you take on new clients at volume, keeping a simple log of who each NDA protects, what the confidentiality duration is, and whether there are any competitor or exclusivity restrictions will save significant time when a new agreement comes in.
The Compounding Problem
A single consultant NDA is usually manageable. The challenge is that consultants sign them constantly, in sequence and in parallel, with clients who may have competing interests and overlapping markets. Each clause that seems reasonable in isolation — broad confidentiality, non-solicitation of customers, indefinite survival for trade secrets — becomes a real constraint when it stacks with four others signed in the same year.
The clauses worth the most attention are the ones that reach beyond the specific engagement: IP assignment that captures pre-existing methodology, confidentiality definitions that extend to general expertise, and non-solicitation clauses broad enough to cover most of your existing network. These are not unusual clauses — they appear in routine NDAs from legitimate clients. But for a consultant, the blast radius is different.
The counter-language above covers the most common overreach. For a review of the clause types that cut across all these risks, the full NDA red flags guide is worth reading before any new engagement. And if you want to audit an NDA you're currently looking at, NDA Guard reviews the full agreement and flags consultant-specific risk — prior IP, non-solicitation scope, confidentiality duration — automatically.