As at: 22 June 2026

Software licences can unintentionally morph into de facto IP assignments when poorly drafted clauses grant licensees rights so broad that they strip licensors of meaningful ownership and control. This practice note highlights how “assignments by stealth” occur, the risks they pose, and safeguards to prevent them.

The Core Issue

• Licences vs. Assignments: A licence should grant limited rights of use (installation, execution, distribution) while ownership of the underlying IP remains with the licensor.
• Stealth Assignments: Overly broad licence terms can, in practice, transfer ownership or control of IP to the licensee without explicitly calling it an “assignment.”

How It Happens

• Broad Grant of Rights: Clauses giving “all rights” to use, modify, distribute, and create derivatives.
• Perpetual & Irrevocable Licences: Worldwide, royalty-free, irrevocable licences resemble outright transfers.
• Work-for-Hire Language: In development agreements, licence clauses tied to “work-for-hire” provisions convert licences into assignments.
• Exclusive Licences Without Safeguards: Prevent licensors from exploiting their own IP.
• Integration in Broader Contracts: Outsourcing or JV agreements may embed licence terms that effectively transfer IP.

Risks & Consequences

• Loss of Control: Licensors may lose the ability to exploit or develop their own software.
• Valuation Impact: Investors may view IP portfolios as compromised.
• Cross-Border Complications: Jurisdictions differ in interpreting licence vs. assignment.
• Regulatory & Tax Implications: Assignments may trigger tax events or require registration, unlike licences.

Safeguards for Drafting

• Define Scope Clearly: Limit licence to specific uses, territories, and durations.
• Avoid “All Rights” Language: Use precise terms that preserve ownership.
• Reserve Ownership Explicitly: State that all IP rights remain vested in the licensor.
• Distinguish Licence vs. Assignment: Ensure contract language reflects intent.
• Check Exclusivity Carefully: Carve out exceptions for licensor’s continued use.

Practical Checklist

• Is the licence time-bound or perpetual?
• Is it revocable or irrevocable?
• Does it grant exclusive rights without limitation?
• Does it allow derivative works without oversight?
• Does the contract explicitly reserve ownership for the licensor?

Practitioner Note

In today’s cloud-first, cross-border environment, stealth assignments are even riskier:

• Cloud & SaaS Models: Perpetual, irrevocable licences bundled with service agreements can resemble transfers.
• Open Source Integration: Broad sublicensing rights may unintentionally dilute ownership.
• Cross-Border Nuance: Some jurisdictions (e.g., EU vs. South Africa) treat exclusive licences as near-assignments, requiring careful drafting.
• Investor Due Diligence: Venture capital and M&A transactions scrutinize licence terms for stealth assignment risks.

In short: Drafting vigilance is essential. A licence should remain a licence – not an assignment in disguise.

Disclaimer: This practice note is for informational purposes only and does not constitute legal advice. Readers should consult qualified legal professionals for advice tailored to their specific circumstances.