Residuals clauses in consulting NDAs: what you can reuse

What is a residuals clause?#

A residuals clause is a provision in a nondisclosure agreement or services contract that lets the recipient use residual information: ideas, concepts, know-how and techniques retained in the unaided memory of people who had authorized access to the other side's confidential information. Using residuals is declared not to be a breach, even though the underlying information was confidential.

Residuals language usually appears in mutual NDAs and master services agreements drafted by the party that expects to learn the most. Consulting firms, technology vendors and staffing firms ask for it because their people carry experience from one client to the next.

The clause does not change who owns the confidential information. It is a limited permission to use what stays in someone's head, and its value depends entirely on its wording.

• 1Unaided memory: information recalled without reference to documents, notes or files.
• 2Authorized access: only people who saw the information in the normal course of the engagement.
• 3No intentional memorization: many drafts exclude information someone studied in order to retain it.
• 4No IP license: no rights under patents, copyrights or other registered rights.
• 5No attribution: the recipient may not reveal the client as the source of what it uses.

Why consulting and staffing firms care about residuals#

Consulting firms care about residuals because their product is accumulated judgment. A partner who has run many pricing redesigns, or an operations team that has reset several distribution networks, brings pattern recognition to every new engagement, and clients pay for exactly that.

Without residuals language, a client's confidentiality clause usually defines confidential information broadly and restricts its use to the engagement. Read strictly, that could reach lessons learned on the client's problem. Most firms never test that reading, but it matters when the firm writes playbooks, trains new staff, builds a knowledge base or considers licensing internal records.

Staffing and recruiting firms face a related question. Recruiters learn client hiring practices, interview structures and compensation approaches; residuals language clarifies that general market knowledge can travel, while a client's pay data, org charts and job order details cannot.

What usually counts as residuals, and what stays confidential?#

Residuals usually cover general skills and patterns, while anything specific, recorded or attributable to a client usually stays confidential. The table reflects common drafting; your own agreements control, and courts read the exact text.

Unaided memory excludes drives, notes and AI tools#

Unaided memory means information a person can recall without looking anything up, so any stored copy falls outside the clause. A shared drive of past engagement folders, a personal notebook, a SharePoint library or a searchable knowledge base is a record, not a memory.

This matters more as firms adopt AI search and drafting tools. Indexing client deliverables into an internal assistant, or fine-tuning a model on engagement files, retains the material itself. Residuals language is unlikely to reach that use; whether it is allowed generally depends on the confidentiality, use and return-or-destroy clauses in each client contract.

The practical rule separates two kinds of reuse. What a consultant brings to the next client from experience may be covered by residuals. What the firm stores, indexes, trains on or licenses needs a contractual right of its own, or must be material the firm authored without client confidential information.

Clauses to read alongside the residuals clause#

A residuals clause never operates alone, so a contract review should read it with the clauses that define, limit and end confidentiality. The most common conflict is a broad definition of confidential information paired with a narrow residuals carve-out.

• 1Definition of confidential information: only marked material, or everything disclosed, including oral information.
• 2Use restriction: whether information may be used solely to perform the services.
• 3Return or destruction: what must be deleted at the end and whether archival or backup copies are allowed.
• 4Background and foreground IP: who owns pre-existing methods, tools and templates, and who owns deliverables.
• 5Aggregated data: whether anonymized insights may be used across clients.
• 6Survival: how long confidentiality lasts after the engagement ends.

Illustrative: an operations consultancy sorts its playbooks#

Illustrative: a fictional operations consulting firm with years of warehouse and network redesign work wants to build an internal playbook library, and asks whether it could also license its internal project reviews. Its general counsel pulls the master services agreements for the firm's largest clients.

Some agreements include mutual residuals clauses; the rest are client paper with broad confidentiality and strict return-or-destroy terms. Counsel concludes that residuals support consultants writing playbooks from experience, but not copying client layouts, throughput data or slotting files into them.

The decision: senior consultants rewrite each playbook from scratch, client names and figures are removed, and a reviewer checks each one against the source engagements. Client deliverables stay out of the library entirely. For new work, the firm adds a clear background IP clause and a narrow aggregated data clause to its own paper.

How to negotiate a residuals clause clients will accept#

A residuals clause clients will accept is narrow, mutual and paired with clear limits. Disclosing parties often resist broad language because, under the Defend Trade Secrets Act definition, information stays a trade secret only if its owner takes reasonable measures to keep it secret, and a loose clause can look like a gap in those measures.

How SourceX treats residuals in a rights review#

SourceX treats a residuals clause as context, not as a license. In the Rights step of the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery), client contracts are reviewed to separate firm-authored material, such as internal playbooks, project reviews and training content, from client confidential information, which is excluded by default.

Whatever proceeds is documented in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization. The firm keeps ownership, approves each step, and shares nothing during the initial assessment.