Technology Assignment Agreement Template

In plain language: Sets out the background context — who the parties are, why the agreement exists — and defines every capitalized term used throughout the document.

Common mistake: Leaving 'Assigned Technology' undefined in the recitals and relying on a vague Schedule. Courts have found assignment clauses unenforceable when the transferred assets cannot be identified with reasonable specificity.

In plain language: An attached exhibit itemizing every discrete piece of technology being transferred — source code repositories, patent applications, trade secrets, documentation, and data sets — by name, version, and location.

Common mistake: Using a broad catch-all description like 'all technology related to the Product' without an itemized list. Ambiguous schedules are the single most common source of post-closing IP ownership disputes.

In plain language: The operative clause that transfers all IP rights — copyright, patent, trade secret, and trademark rights — in the Assigned Technology from Assignor to Assignee, effective on the execution date.

Common mistake: Using 'agrees to assign' instead of 'hereby assigns.' Courts in the US and UK have treated 'agrees to assign' as a promise of future transfer rather than an immediate present-tense assignment, requiring a separate subsequent act.

In plain language: The Assignor waives any moral rights (right of attribution, right of integrity) they hold in the technology under applicable copyright law, to the extent permitted by law.

Common mistake: Omitting a moral rights waiver entirely. In Canada, the UK, and EU member states, moral rights survive a copyright assignment unless explicitly waived — leaving the Assignor with residual rights to object to modifications.

In plain language: States what the Assignee pays the Assignor in exchange for the transfer — a cash lump sum, equity, or a nominal amount — and confirms receipt, making the agreement binding.

Common mistake: Omitting consideration entirely in a standalone assignment document. Without it, the agreement may be treated as a gratuitous transfer and challenged as unenforceable in jurisdictions that require mutual exchange.

In plain language: The Assignor makes binding factual statements that they own the technology outright, have the right to assign it, have not previously licensed or encumbered it, and that it does not infringe any third party's IP rights.

Common mistake: No warranty that the technology is free of open-source license obligations. A single GPL-licensed dependency can restrict the Assignee's ability to commercialize the software, and discovering it post-closing is expensive.

In plain language: Lists technology developed by the Assignor before the assignment date that is explicitly excluded from transfer, preventing the Assignee from claiming ownership of work the Assignor created independently.

Common mistake: Skipping the Prior Inventions schedule when the Assignor has a body of pre-existing work. Without it, the assignment clause's broad language may inadvertently capture older projects — leading to disputes over assets the Assignee never intended to acquire.

In plain language: Obliges both parties to keep the terms of the agreement and any technical information exchanged during the transfer process confidential for a defined period.

Common mistake: No confidentiality obligation on the Assignee. Once the Assignee receives the technology, they may have strategic reasons to disclose its existence — a mutual confidentiality clause preserves the Assignor's privacy interests during and after the transfer.

In plain language: Requires the Assignor to defend and compensate the Assignee if a third party claims that the Assigned Technology infringes their IP rights — and vice versa for breaches of the Assignee's obligations.

Common mistake: Uncapped indemnification with no limitation of liability clause. An Assignor transferring a startup's entire codebase for nominal consideration should not bear unlimited indemnification exposure — negotiate a cap tied to the consideration amount.

In plain language: Specifies which jurisdiction's law governs the agreement and the mechanism for resolving disputes — typically arbitration or the courts of a named jurisdiction.

Common mistake: Choosing a governing law with no connection to either party's location or the technology's development. In cross-border assignments, a neutral jurisdiction can be appropriate — but courts may still apply local IP law regardless of the contractual choice.

A technology assignment agreement is a legally binding contract that permanently transfers ownership of intellectual property — software, source code, patents, trade secrets, and related documentation — from the creator or current owner (the Assignor) to another party (the Assignee). Unlike a license, which grants usage rights while the Assignor retains ownership, an assignment transfers title outright and irrevocably. It is the document that makes a company the legal owner of the technology it operates and builds upon.

An assignment is a permanent transfer of ownership — after execution, the Assignor has no remaining rights in the technology unless a retained license is explicitly carved out. A license is a permission to use the technology while the licensor retains ownership and can terminate or restrict use under defined conditions. Most investors and acquirers require outright assignment rather than a license because a license can be revoked, expire, or be voided by the licensor's bankruptcy.

Any time technology critical to the business was created before incorporation, by a contractor without a work-made-for-hire clause, or by a founder on personal equipment. These are the three most common clean-IP issues raised in Series A and M&A due diligence. Executing assignments early — before the first investor conversation — is far cheaper than negotiating them under time pressure at closing. Most investor term sheets include a representation that the company owns all its IP free and clear.

Yes. Both the Assignor and Assignee must sign for the agreement to be binding and to satisfy formal requirements for patent assignments in most jurisdictions. For US patent assignments, the USPTO additionally requires the assignment to be recorded within 3 months of execution to be enforceable against subsequent purchasers. Some jurisdictions also require the signature to be witnessed or notarized for the recordal to be accepted.

In most common-law jurisdictions, some form of consideration is required for a contract to be enforceable. Consideration can be a cash payment, equity grant, employment compensation, or a nominal sum — even $1 is typically sufficient if both parties acknowledge receipt. For assignments from employees, the employment contract and salary often constitute sufficient consideration, provided the assignment clause was included before or on the start date.

In the US, an unrecorded patent assignment is generally unenforceable against a subsequent bona fide purchaser who acquires the patent for value without notice of the prior transfer. This means a founder who assigns a patent to their company but fails to record it could theoretically re-assign it to a third party, who would then hold superior title. Similar principles apply in Canada, the UK, and EU member states. Recordal is not optional for patent assignments.

In the US, moral rights for software do not exist under federal copyright law, so this is rarely an issue. In Canada, the UK, and most EU countries, moral rights — including the right of attribution and the right to object to derogatory treatment — automatically vest in the creator and survive a copyright assignment unless explicitly waived. A developer who retains moral rights can, in theory, object to modifications that distort or mutilate their work. Always include a moral rights waiver for non-US assignments.

Before executing, request a software bill of materials (SBOM) listing every third-party library or component embedded in the codebase, along with its license. Copyleft licenses — GPL, AGPL, LGPL — impose conditions on downstream distribution and can require the Assignee to release their product under the same open-source terms. Permissive licenses — MIT, Apache 2.0, BSD — are generally safe. A single undisclosed copyleft dependency discovered post-assignment can create significant commercial and legal exposure.

For straightforward domestic assignments — a freelancer transferring a single application to their client, or a founder assigning pre-incorporation code — a high-quality template reviewed by the parties is often sufficient. Engage a lawyer when the assignment involves patents pending in multiple countries, when the consideration exceeds $50,000, when the assignment is part of an M&A transaction, or when the Assignor is a foreign national and cross-border IP rules apply. A 1–2 hour attorney review typically costs $400–$800 and is worthwhile for any assignment material to the business.