Residuals Clause

A residuals clause (sometimes called a "residual knowledge" or "residual information" clause) permits the receiving party to use ideas, concepts, know-how, and techniques that remain in the unaided memories of their personnel after exposure to confidential information. In other words, if your employees remember general concepts from what they learned, they can apply that knowledge without violating the NDA.

The rationale behind this clause is practical: humans cannot selectively erase memories. When engineers, consultants, or businesspeople are exposed to new information, some of it inevitably becomes part of their general knowledge and expertise. A strict confidentiality obligation that prevents using anything learned would be impossible to follow.

However, residuals clauses are highly controversial because they can significantly undercut confidentiality protections. The line between "general concepts retained in memory" and "specific confidential information" is often blurry, making these clauses difficult to enforce or defend against.

• Freedom to Operate: For companies that frequently evaluate technologies and business opportunities, residuals clauses prevent them from being paralyzed by concerns about inadvertent misuse of remembered information.
• Employee Mobility: Without residuals protections, employees who worked on confidential projects might face career limitations since they can't "unknow" what they learned.
• Significant Risk for Disclosers: If you're sharing trade secrets or proprietary methods, a broad residuals clause could effectively allow the other party to replicate your innovations "from memory."
• Enforcement Challenges: It's extremely difficult to prove whether someone recreated information from documented sources versus "unaided memory."
• Industry-Specific Impact: In software, consulting, and R&D contexts where knowledge transfer is inevitable, these clauses are common but hotly negotiated.

• Scope of "Residuals": Does the clause cover only general skills and know-how, or does it extend to specific ideas, concepts, and techniques? Broader definitions favor receivers.
• Documentation Restrictions: A proper clause should prohibit intentional memorization or "brain dumping" after exposure - look for this protection.
• Personnel Limitations: Should only apply to employees who were properly exposed, not to any employee who might claim residual knowledge.
• Nature of Information Shared: The more specific and valuable your secrets (formulas, algorithms, methods), the more dangerous a residuals clause becomes.
• Competitive Context: Sharing with potential competitors under a residuals clause essentially gives them license to use learned insights.