IP Assignment Agreement

IP Assignment Agreement: moving ownership of software cleanly

Intellectual property is usually a technology company's single greatest asset. All the ideas, designs, inventions and know-how, made concrete.

An Intellectual Property Assignment Agreement (IPAA) transfers ownership of that asset from one party to another. Done properly it is quick, clean and complete — which is what the pace of the software industry demands. Done badly, it leaves the buyer holding something they do not fully own.

When you need one

Buying or selling software or a software business
Bringing contractor-built code in-house where the developer, not you, owns it by default
Restructuring, moving IP between group companies
Founder or co-founder transfers into a company vehicle
Investor or acquirer due diligence that finds a gap in your chain of title

It works for assignments by or to an individual or a company, in either direction.

The clauses that matter most

1. Identifying the software

You cannot assign what you have not described. There are two layers to this.

First, a short description in the interpretations section, for example, "the Acme scheduling app, designed to help Microsoft Partners manage engineer dispatch."

Second, real detail in the Software Specification (Schedule 1): published specifications, details of registered patents including number and class, and any registered designs.

The assignment should cover all updates, upgrades and versions, the software in both source and object code form, and the IP rights in the related documentation — operating manuals, training manuals and the like.

2. The assignment itself

The party giving up the rights is the assignor; the party receiving them is the assignee.

The assignor assigns all worldwide rights with full title guarantee. That guarantee carries three covenants:

The assignor has the right to sell the IP.
The assignor will do all it reasonably can, at its own expense, to ensure the IP transfers.
The IP is free from encumbrances, no attached licences, no charges left over from a previous owner.

If, after signing, the rights do not vest properly in the assignee for any reason, the assignor must use best endeavours to complete the transfer, which can mean registering patents or filing the relevant documentation.

3. Consideration

This agreement is signed as a deed, so money does not strictly need to change hands for it to be binding. That is useful for intra-group transfers and founder assignments.

Where payment is part of the deal, a consideration clause covers it. VAT is not included and should be invoiced separately.

4. Warranties

Like any transaction involving goods, the assignor gives warranties, here, promises about the state of the software itself rather than its age or condition.

Typical warranties: that the software is original and not copied from any other work; that the assignor is the legal owner; that it has not been licensed from a third party. Around ten warranties is a normal set.

Warranties give the assignee assurance they are getting what they are paying for. If one is breached, the injured party can seek damages where they can prove a quantifiable loss.

5. Confidentiality

The software and its documentation contain information the assignee will treat as confidential. The agreement binds the assignor to keep it secret from third parties, including after the transfer.

6. Power of attorney

The assignor grants the assignee a power of attorney. In practice: if a signature relating to the IP is needed after the transfer, the assignee can sign on the assignor's behalf. That saves the deal when the assignor is hard to reach months later. The assignor must ratify and confirm what the assignee does as attorney.

7. Moral rights

An author has inherent moral rights in their work, most commonly the right to be named, the right for the work not to suffer derogatory treatment, and a say over confidentiality.

Moral rights cannot be transferred, only waived. They rarely bite on computer programs themselves, but they may be enforceable in the software documentation. The agreement therefore includes a worldwide waiver of moral rights in the software and documentation.

8. Governing law

If the parties and the work are in England, English law and exclusive jurisdiction of the English courts is the preferred position, with non-exclusive available where genuinely necessary.

Frequently asked questions

Does my contractor's code belong to me automatically? Not necessarily. Absent a written assignment, the developer may retain ownership. This is the single most common gap acquirers find in due diligence.

What is the difference between assigning IP and licensing it? An assignment transfers ownership permanently. A licence grants permission to use it while ownership stays where it is.

Why sign as a deed? Because a deed does not require consideration to be binding — useful for group restructures and founder transfers where no money changes hands.

Can moral rights be assigned? No. They can only be waived, which is why the agreement includes an express worldwide waiver.

How Cloud Contracts 365 helps

Cloud Contracts 365 produces an IP Assignment Agreement from a guided questionnaire, prompting you for the software specification, warranties and consideration detail that make the transfer stick. Every executed assignment is stored in one place — so when an investor or acquirer asks you to prove your chain of title, you can, in a couple of clicks.