The Residuals Clause: How the Other Side Keeps Your Ideas

What the clause says

The typical formulation provides that nothing in the agreement restricts the receiving party from using residuals, defined as information in intangible form retained in the unaided memory of persons who have had access to confidential information, provided they have not intentionally memorised it.

Read alone, it sounds like an acknowledgement that people cannot unlearn things. Read against the rest of the agreement, it is an exception permitting use of what the other side remembers, which for a conversation about ideas is a large part of what you disclosed.

Why it matters most to the smaller party

Consider who is sharing what. A startup pitching a product concept to a large potential partner is disclosing an idea, an approach, and the reasoning behind it. There is no document at the centre of that; the value is in what the other side now understands.

A residuals clause permits their engineers to use exactly that. The disclosing party has protected its documents and left its know-how available. That asymmetry is why the clause is worth identifying before a pitch rather than after one.

Why counterparties insist on it

It is worth understanding the other side position, because it is not always unreasonable. A large company that reviews hundreds of proposals a year cannot realistically quarantine every idea it has heard, and an engineer who saw a pitch in March cannot be prevented from working on an adjacent problem in September.

Without a residuals clause, that company faces a claim every time it ships something resembling something it was once shown. So the clause exists to manage a genuine problem. That does not make it acceptable to you, but it explains why removal is sometimes genuinely not on offer.

What to do about it

• Ask for it to be struck. In many agreements it is template language rather than a negotiated position.
• If it stays, narrow it: exclude anything reduced to writing, and exclude specific categories such as technical architecture or customer information.
• Ask for it to apply only to individuals who have not had substantial access, rather than to everyone.
• Where it cannot be removed, calibrate what you disclose. Share enough to have the conversation, not enough to be rebuilt from memory.
• Consider staging disclosure, with the sensitive detail held back until the relationship progresses.

The honest position

If you are a small company signing a large company standard NDA with a residuals clause you cannot change, the realistic protection is behavioural rather than contractual. Decide in advance what you will and will not say in that meeting.

That is not a satisfying answer, but it is the accurate one, and it is considerably better than assuming the NDA covers you and discovering later that the clause you skimmed was the one that mattered.