Assignment of Rights in Computer Software With Reservation Template

In plain language: Identifies the assignor and assignee by legal name and entity type, and states the background context — what the software is, how it was created, and why the assignment is occurring.

Common mistake: Using trade names instead of registered legal entity names. If the assignor entity doesn't match copyright registration records, the chain of title becomes defective and may need costly correction later.

In plain language: Precisely identifies the software being assigned — including version numbers, repository locations, functional description, and any documentation — so there is no ambiguity about what is and is not transferred.

Common mistake: Describing the software only by product name without version or repository reference. This creates scope disputes when the codebase evolves post-signing or when multiple versions exist.

In plain language: States which intellectual property rights are transferred — copyright, patent rights, trade secrets, and related rights — and whether the assignment is worldwide and perpetual.

Common mistake: Omitting patent rights from the assignment scope. If the software is later found to embody a patentable invention the assignor holds, the assignee may have no right to that protection.

In plain language: Explicitly carves out rights the assignor retains after the transfer — for example, a perpetual, royalty-free license to use the software internally, or rights to pre-existing underlying libraries.

Common mistake: Drafting the reservation clause in vague terms such as 'for personal use.' Without specifying the exact scope — commercial vs. non-commercial, sublicensable or not, geographic limits — the reservation is unenforceable or triggers disputes at the first exercise.

In plain language: States the price or other value exchanged for the assignment, the payment schedule, and any conditions on payment such as escrow release or milestone delivery.

Common mistake: Stating consideration as '$1 and other good and valuable consideration' without specifying the real amount. This nominal-consideration formula is enforceable in most US states but creates problems in Canada and the EU, where courts scrutinize adequacy of consideration more closely.

In plain language: The assignor confirms they own the rights being transferred, the software does not infringe third-party IP, there are no outstanding licenses or encumbrances, and no open-source components are embedded that would void proprietary claims.

Common mistake: No open-source disclosure warranty. Undisclosed GPL or AGPL components embedded in assigned software can infect the entire codebase with copyleft obligations, fundamentally altering the value received by the assignee.

In plain language: Requires the assignor to compensate the assignee for losses arising from a breach of the warranties — particularly third-party IP infringement claims — and sets any cap on indemnification liability.

Common mistake: No liability cap on indemnification. An uncapped indemnity in a software assignment can expose an individual developer to liability far exceeding the assignment price if a significant infringement claim arises.

In plain language: The assignor waives any moral rights — rights of attribution and integrity — to the extent permitted by applicable law, so the assignee can modify, adapt, or publish the software without restriction.

Common mistake: Omitting a moral rights waiver for international transactions. In Canada, the UK, and the EU, moral rights exist separately from economic copyright and cannot be assigned — only waived — meaning an assignee without a waiver may face restrictions on modification or publication.

In plain language: Specifies which jurisdiction's law governs the agreement and the mechanism for resolving disputes — arbitration, mediation, or court — including the venue.

Common mistake: Choosing a governing law with no connection to either party's jurisdiction. Courts in several jurisdictions — including California and Ontario — apply local mandatory IP rules regardless of the contractual choice of law.

In plain language: Requires the assignor to execute any additional documents — copyright office registration forms, patent assignment recordals, domain transfer forms — needed to perfect the assignee's title in relevant registries.

Common mistake: No further-assurances clause. Without it, an assignor who later becomes uncooperative — or insolvent — may leave the assignee unable to record title in copyright or patent registries, weakening enforceability against third parties.

An assignment of rights in computer software with reservation is a legal agreement in which the owner of software intellectual property transfers ownership to another party while explicitly retaining defined rights — such as a personal-use license or rights to pre-existing underlying libraries. Unlike a full assignment, the reservation clause ensures the original developer can continue using specified elements of the software after the transfer takes effect. It is commonly used in developer-to-client transfers, startup IP sales, and technology M&A transactions.

A full assignment transfers all intellectual property rights in the software to the assignee with nothing retained by the assignor. An assignment with reservation achieves the same transfer of ownership but carves out specific, defined rights the assignor keeps — for example, a non-exclusive license to use the software in their own products, or ownership of pre-existing code libraries embedded in the deliverable. The reservation must be drafted precisely; a vague carve-out creates ongoing disputes about what the assignor may and may not do.

Yes. Under the copyright laws of the United States (17 U.S.C. § 204), Canada, the United Kingdom, and most EU member states, an assignment of copyright must be in writing and signed by the assignor to be legally effective. An oral agreement to assign software rights is generally unenforceable. The written agreement should also be specific enough to identify the software being transferred without ambiguity.

Most developers reserve the right to use pre-existing code libraries, frameworks, and tools they built before the engagement — these are typically listed as "pre-existing IP" excluded from the assignment scope. Many also negotiate a non-exclusive license to use the finished software as a portfolio reference or to re-use generic architectural patterns in future projects. Reserving rights to demonstrate the work to prospective clients is also common, subject to any confidentiality obligations.

Recording is not required for the assignment to be valid between the parties, but it is strongly advisable. Under US copyright law, a recorded assignment has priority over a later unrecorded assignment to a different party — meaning a fraudulent or mistaken second transfer to another buyer could defeat an unrecorded assignment. The filing fee is approximately $105 at the US Copyright Office as of 2026. In the UK and Canada, similar registration systems exist and provide comparable protection.

No. In most jurisdictions outside the United States, moral rights — the right of attribution and the right to object to derogatory treatment — cannot be assigned; they can only be waived. In the US, moral rights for software are not recognized under federal law, so this is less of a concern domestically. For agreements involving Canadian, UK, or EU parties, the assignment must include an explicit written waiver of moral rights to give the assignee full freedom to modify and publish the software.

Open-source components are subject to their own licenses — some permissive (MIT, Apache 2.0), some restrictive (GPL, AGPL). Copyleft licenses like the GPL can require the assignee to release the entire codebase as open source if the software is distributed, which may fundamentally undermine the value of the assignment. The assignor should disclose all open-source components before execution, and the assignee should conduct independent due diligence using a license-scanning tool before closing.

For straightforward assignments between a freelancer and a domestic client at low dollar values, a high-quality template is typically sufficient. Legal review is strongly recommended when the assignment involves material IP value (above roughly $25,000), cross-border parties, patent rights in addition to copyright, open-source compliance issues, or when the reserved rights are commercially significant. A 1–2 hour attorney review typically costs $300–$800 and can prevent disputes that cost multiples of that to litigate.

The assignment must be supported by consideration — something of value exchanged by both parties — to be enforceable as a contract in common-law jurisdictions. Payment is the most common form. In employment contexts, continued employment or a bonus may serve as consideration. In Canada, courts have scrutinized nominal consideration ($1) more carefully than US courts; a stated fair-market-value amount is more defensible. The consideration amount should always be specified in the agreement rather than left as a vague recital.

Generally, no — an executed assignment of IP rights is intended to be irrevocable and permanent. However, an assignment can be unwound by mutual written agreement, or may be voidable if one party can show fraud, misrepresentation, duress, or failure of consideration. Some jurisdictions also allow rescission if the assignee materially breaches a condition attached to the assignment. To minimize risk of inadvertent rescission, the agreement should include a clear statement that the assignment is irrevocable once the consideration has been paid.