Residuals clauses: the hidden IP leakage point

Tucked into the confidentiality section of many NDAs and services agreements is a short paragraph that most teams skim past. It's often labeled "Residuals" or nested inside the definition of Confidential Information. It rarely runs more than four sentences. And it can, under the right circumstances, gut the protections the rest of the agreement was drafted to provide.

A residuals clause says that information the Recipient retains in "unaided memory" after the engagement ends isn't subject to the confidentiality obligations. Read literally, it creates a carve-out: anything an employee remembers without notes, documents, or deliberate study walks out the door with them, free to be used on the next project, including for a competitor.

That sounds narrow. In practice, the reach of a residuals clause depends entirely on how it's drafted, and the range is wide. Some versions protect nothing beyond the truly incidental. Others functionally license the Recipient's employees to apply everything they learned on the engagement to future work for anyone. This is a walkthrough of what a residuals clause actually does, the drafting patterns that expand or contract its scope, and why it's a standard sticking point in serious confidentiality negotiations.

What a residuals clause says

A representative residuals clause reads:

"Notwithstanding anything to the contrary, Recipient's employees shall be free to use, for any purpose, any Residuals resulting from access to or exposure to Confidential Information. 'Residuals' means information in non-tangible form which may be retained in the unaided memory of persons who have had access to Confidential Information, provided such persons have not intentionally memorized such information for the purpose of retaining and subsequently using or disclosing it."

Three mechanisms are doing the work here:

1. The carve-out. The clause creates an exception to the otherwise-applicable confidentiality obligations.
2. The definition of Residuals. Information in "non-tangible form" held in "unaided memory." No notes, no documents, no copies.
3. The anti-memorization proviso. Deliberate memorization for the purpose of later use doesn't qualify.

In the version above, any employee who genuinely remembers something from the engagement, the architecture of a system, a customer's strategic direction, a pricing model, can use that memory on future work, provided they didn't set out to memorize it.

Where residuals language originates

Residuals clauses came out of the tech industry in the 1990s and early 2000s, primarily from large vendors and consultancies. The underlying concern was legitimate: engineers and consultants move between projects, and without some kind of carve-out, every confidential exchange would theoretically convert former clients into permanent liability zones. A consultant who had ever worked on a pricing engine couldn't take another pricing-engine client without risk of a confidentiality claim, even if the second engagement involved entirely different code.

The residuals clause was the drafting response. It tried to separate knowledge workers' general skill growth from deliberate use of specific confidential information. The framing assumed that employees can't un-learn what they've seen, so the practical options are either to accept that reality in the contract or to litigate it after the fact.

That origin story explains why residuals clauses are most common in vendor paper, consulting agreements, and evaluation NDAs pushed by large service providers. It also explains why they're rare in NDAs pushed by the customer side of a deal.

Why they leak value

The leak isn't in the concept, it's in the scope. A narrowly drafted residuals clause limits itself to the kind of general skill transfer the rationale actually supports. A broadly drafted one can cover nearly anything a person remembers.

Several drafting choices inflate the reach of the clause.

"For any purpose"

A residuals clause that says residual information can be used "for any purpose" permits the Recipient to apply it on future work for competitors of the Discloser. A narrower version limits use to "the Recipient's internal business operations" or "Recipient's general development of its products and services," both of which are meaningful but don't authorize direct competitive use.

Silence on the anti-memorization proviso

The provision that excludes deliberately memorized information is doing real work. Without it, a Recipient's employees can study the Confidential Information, internalize it, and claim residuals protection. The proviso attempts to distinguish incidental retention from strategic retention. Clauses that omit it are broader than they look.

The practical challenge is that the proviso is difficult to enforce. Proving someone intentionally memorized information is a high bar. But the proviso still has deterrent value and can support a claim when circumstantial evidence is strong.

Residuals that cover patents

Some residuals clauses are limited to copyright and trade secret obligations but are silent on patent rights. Others expressly disclaim any implied patent license but still permit use of residual information. This matters: a person can remember the architecture of an invention without remembering it's patented, and a poorly drafted residuals clause can create ambiguity about whether the carve-out reaches patent rights.

Cleanly drafted clauses are explicit: residuals cover confidentiality obligations only, and no patent license is granted by implication.

Residuals that cover all parties' information

In a mutual NDA, a residuals clause typically applies to both parties. That's structurally fair but creates asymmetric risk where one party is sharing substantially more detailed or more valuable information. The party with the larger or more complex disclosure set is giving up more to the residuals exception.

Residuals in a services agreement vs. an NDA

Residuals clauses in standalone NDAs are often negotiated. Residuals clauses in services agreements, embedded in the MSA, often in a subsection of the confidentiality article, are negotiated less often, because the surrounding agreement has larger commercial terms competing for attention. This is where residuals language most commonly slips through without pushback.

The customer's side of the argument

When the customer is the party disclosing sensitive information, residuals clauses are usually unwelcome. The customer's position is typically:

• The agreement already includes standard exceptions (public domain, independent development, third-party receipt) that protect the Recipient from unreasonable liability.
• Residuals functionally permit the Recipient's employees to walk confidential information out the door under a memory-based loophole.
• The carve-out's scope is difficult to police, which means the customer's remedy for misuse is weak in practice.
• The legitimate concern about general skill growth is better addressed with a narrow carve-out for general knowledge, not a blanket "unaided memory" exception.

Common customer redlines:

• Delete the residuals clause entirely.
• Limit residuals to general skills and experience, excluding any specific customer information.
• Limit the purposes for which residuals may be used (e.g., "for Recipient's internal purposes only").
• Preserve the anti-memorization proviso and strengthen it.
• Carve out trade secrets, residuals protection does not apply to information that qualifies as a trade secret.
• Exclude personally identifiable information, customer data, and regulated information categories.

The provider's side of the argument

From the provider's or consultant's side, residuals clauses reflect operational reality. Key points:

• Knowledge workers can't partition their memory. After an engagement, they carry some amount of what they learned into future work, and pretending otherwise sets up a conflict that nobody can comply with.
• Without some form of residuals exception, the provider accepts a permanent liability overhang on every engagement, the kind that can't be managed with document destruction or access controls.
• The commercial alternative is for the provider to decline engagements in any adjacent area, which the customer usually doesn't actually want (the customer wants a provider with domain experience, which by definition comes from prior work).
• A well-drafted residuals clause isn't a license to exfiltrate, it's a recognition that the scope of enforceable confidentiality has outer limits.

Providers typically resist deletion of the clause but will often negotiate scope: limiting "for any purpose" language, excluding specific customer data, and strengthening the anti-memorization proviso.

What a balanced clause tends to look like

A negotiated residuals clause in a sophisticated agreement usually lands somewhere like this:

"Recipient's personnel shall be free to use for any lawful purpose any general knowledge, skills, and experience retained in the unaided memory of personnel who have had access to Confidential Information, provided that (a) such use does not involve disclosure of any Confidential Information in a form identifiable with the Discloser or its customers, (b) such personnel have not intentionally memorized Confidential Information for the purpose of later use, and (c) this Section does not apply to any information that constitutes a Trade Secret or to any personal data."

Not pretty, but it captures the workable middle ground: general skills pass through, specific information doesn't, trade secrets and personal data are excluded, and the anti-memorization proviso remains.

Operational controls that actually matter

Regardless of how the clause is drafted, the real protection against residuals leakage tends to sit outside the NDA:

• Scoped access. Fewer people see sensitive information. Residuals can't apply to something an employee never saw.
• Document control. If documents leave with the Recipient and then resurface, the residuals carve-out doesn't apply, it only protects unaided memory.
• Post-engagement destruction certification. The standard return-or-destroy obligation limits the footprint of information that could be "residual" later.
• Tenure tracking. Knowing which provider personnel worked on which engagement creates a baseline for evaluating later claims of independent development.

The bottom line

A residuals clause isn't a rogue provision, it reflects a real tension between the enforceability of confidentiality obligations and the way knowledge workers actually operate. But the scope of a residuals clause varies dramatically based on a handful of drafting choices: "for any purpose" or limited-use, with or without an anti-memorization proviso, trade secrets carved out or swept in, patent rights disclaimed or ambiguous.

The agreements that cause problems later are usually the ones where the residuals clause was taken at face value, a short paragraph, assumed to be innocuous, never read closely. Reading it closely at signature, and deciding explicitly what belongs in the carve-out and what doesn't, is the point where the leak can be closed.

Of all the places confidentiality obligations can quietly lose value, the residuals clause is near the top of the list. Knowing it's there is half the battle.