Intellectual property assignment, Tallow Labs

IP assignment agreement template with a schedule and moral rights

An IP assignment transfers ownership of work that already exists, which is why the schedule matters more than the wording around it. This one moves six named works from a departing contract developer to the startup that paid for them, licenses back her own library, and lists what gets handed over in the ten days after signing.

Create a document with OneCraft4 A4 pages, editable, then download as a PDF

The document, page by page

Every page as it renders and as it prints, with nothing summarised. Read the wording before you reuse it.

IP assignment agreement · Tallow Labs and S. Ekwueme · IPA-2027-01Page 1 of 4
IP assignment agreement · Tallow Labs and S. Ekwueme · IPA-2027-01Page 2 of 4
IP assignment agreement · Tallow Labs and S. Ekwueme · IPA-2027-01Page 3 of 4
IP assignment agreement · Tallow Labs and S. Ekwueme · IPA-2027-01Page 4 of 4
Intellectual property assignment agreement

Made on 12 January 2027 between Sonia Ekwueme of 18 Marsh Lane, Fairport, called the Assignor, and Tallow Labs Limited of Level 3, 90 Ashwood Street, Fairport, called the Assignee. The Assignor was engaged as a contract developer from 2 March 2026 and finishes on 29 January 2027.

6
Works assigned
$6,401
Consideration
12 Jan 2027
Effective
10 days
Handover window
1. What is being assigned
1.1
The assigned works
The assigned works are the six works in the schedule below and everything created as part of them, including source code, test suites, database schemas, build and deployment definitions, design files, written documentation and the commit history itself.
1.2
Background IP is not assigned
Background IP means anything the Assignor owned before 2 March 2026 or developed outside this engagement, including the Quill logging library. It stays hers and is dealt with by the licence in clause 4.1, which is why the schedule lists works rather than describing the whole project.
Ref
Work
Where it lives
Created
TL-01
Ledger core service
Repository ledger-core
Mar to Aug 2026
TL-02
Reconciliation worker
Repository recon-worker
Jun to Oct 2026
TL-03
Merchant dashboard
Repository merchant-web
Apr to Nov 2026
TL-04
API client libraries
Repository clients
Sep 2026
TL-05
Design system tokens
Design file TL-DS
Jul 2026
TL-06
Developer documentation
Repository docs
To Nov 2026
2. The assignment
2.1
Assigned now, not promised later
The Assignor assigns to the Assignee all right, title and interest in the assigned works, including copyright and every other intellectual property right in them. The assignment takes effect on the date of this agreement and does not depend on any further document being signed.
2.2
Rights that arise later
Any right in the assigned works that comes into existence after today, in any country, is assigned to the Assignee as soon as it arises. The assignment is worldwide and lasts for the full term of each right, including every renewal and extension, and it covers the right to sue for and keep the proceeds of an infringement that happened before today.
3. What the Assignor is paid
3.1
Consideration
The Assignee pays the Assignor $1 for this assignment, together with the final invoice of $6,400 under the consulting agreement dated 2 March 2026, making $6,401 in total, payable within seven days. The Assignor acknowledges that the fees already paid under that agreement were paid for work that was always intended to belong to the Assignee.
4. Background IP and third party code
4.1
Licence back for background IP
The Assignor grants the Assignee a perpetual, irrevocable, worldwide, royalty free and sublicensable licence to use, copy, modify and distribute her background IP to the extent it is embedded in the assigned works. The Assignee may keep using the Quill library in the platform without paying anything further.
4.2
Open source components
The assigned works include the open source components below, each under a permissive licence. None of them requires the Assignee to publish its own source code. The Assignor has not included any component under a copyleft licence without written approval, and there is no such component in the works.
Four Go libraries under the MIT licence, listed in ledger-core go.mod.
One Go library under the Apache 2.0 licence, with its notice file retained.
Twenty two front end packages under MIT, BSD and ISC licences.
One font under the SIL Open Font Licence, used in the design system only.
5. Moral rights
5.1
Consent to acts affecting moral rights
To the extent the law allows, the Assignor consents to the Assignee and anyone it authorises doing anything to the assigned works that would otherwise infringe her moral rights, including modifying, rewriting, renaming, relicensing or deleting them, and publishing them without naming her. No attribution is required. She may describe the project in general terms and name the Assignee in her portfolio, but may not publish code, screenshots of customer data or architecture documents.
6. What the Assignor warrants
6.1
The warranties
The Assignor warrants each of the following, and tells the Assignee promptly if anything later shows one of them to be wrong.
1.
The assigned works are her own original work, apart from the components named in clause 4.2.
2.
She is entitled to assign them, and nobody else has a claim to them.
3.
No employer, university or earlier client has any right to the works.
4.
The works are free of any security interest, charge or exclusive licence.
5.
She has not used any code covered by a confidentiality obligation to a third party.
7. Handover and further assurances
7.1
What is handed over, and when
Within 10 business days the Assignor transfers ownership of the repositories, the design file and the documentation site, hands over administrator access to the deployment and monitoring accounts, and moves every credential into the Assignee’s password vault.
7.2
No copies kept
After the handover the Assignor deletes local copies of the assigned works from her own machines and backups, apart from anything she is required to keep for tax records, and confirms that in writing.
7.3
Further assurances
The Assignor will sign anything reasonably needed to record or perfect this assignment in any country, at the Assignee’s cost, including registration forms and a short form assignment. This obligation continues after the engagement ends.
8. General
8.1
Whole agreement, variation and notices
This agreement is the whole arrangement between the parties about the assigned works and replaces any earlier understanding about ownership. It may be changed only in writing signed by both parties. Notices go to the email addresses beside the signatures.
Assignor, Sonia Ekwueme
Name
:
Date
:
For Tallow Labs Limited
Name
:
Position
:
Date
:

Section by section

What each section is for, so you can keep the ones you need and drop the rest.

Parties and assignment summary
Assignor, assignee, the engagement dates and a stats strip of works, fee and handover.
1. What is being assigned
The definition of the assigned works, the background IP carve out, and the schedule table.
2. The assignment
A present assignment, rights that arise later, and the worldwide term.
3. What the Assignor is paid
One dollar plus the final invoice, and why the earlier fees already covered the work.
4. Background IP and third party code
The licence back for her own library, and the open source components with their licences.
5. Moral rights
Consent to acts that would otherwise infringe, and what she may say in a portfolio.
6. What the Assignor warrants
Five numbered warranties about originality, entitlement and encumbrances.
7. Handover and further assurances
Repositories, credentials, no copies kept, and signing whatever a registry later needs.

Clauses in this document

How to adapt this agreement

For an employee rather than a contractor, check the employment contract first: work made in the course of employment often vests in the employer already, and an assignment then only needs to cover the edges. For an assignment as part of a company sale, move the warranties into the sale agreement and keep this document short, because the buyer's protections belong where the price is. For a design or brand handover, swap the repository column for file locations and add a clause dealing with fonts and stock images, which are licensed to the creator and usually cannot be assigned at all.

What an assignment cannot move

An assignment transfers ownership, but three things do not travel with it. Moral rights cannot be assigned in Australia, which is why a separate consent sits alongside the transfer rather than inside it. Copyright that does not exist yet needs express words about future copyright, or the assignment captures only what existed on the day it was signed. And anything the creator brought to the job rather than made for it stays theirs unless it is named, which is what the background intellectual property carve out is for. Registered rights need one more step: a patent or a trademark also has to be recorded with the registry before the transfer is effective against third parties.

What makes this document work

Six named works beat one broad sentence

The schedule lists each work with its repository and the months it was built, from the ledger core service to the documentation site. An assignment that says everything created during the engagement invites an argument about what that included; a table does not.

The developer keeps her own library, and says so

Background IP is defined as anything owned before the start date or built outside the engagement, including the Quill logging library. It is not assigned. Instead it is licensed back perpetually, irrevocably and royalty free, so the platform keeps working and she keeps her tools.

The handover is a list with a deadline

Ten business days to transfer the repositories and the design file, hand over administrator access, and move every credential into the company vault. Then a written confirmation that local copies have been deleted. Assignments fail on access far more often than on wording.

Questions people ask

What is an IP assignment agreement?

A contract that transfers ownership of intellectual property from one party to another, rather than licensing its use. Once signed, the assignor keeps nothing in the assigned works except what the agreement carves out, and the assignee can modify, relicense or sell them without asking.

What is the difference between an assignment and a licence?

An assignment moves ownership permanently. A licence leaves ownership where it is and gives permission to use the work on stated terms. This document uses both: the six named works are assigned outright, while the developer's own library is licensed back so the assignee can keep using it.

Why does an IP assignment need consideration?

Because it is a contract, and a contract needs something given in exchange unless it is executed as a deed. Here the assignee pays $1 for the assignment plus the final invoice of $6,400, making $6,401 in total, which is enough to make the assignment binding without resorting to a deed.

What are moral rights and why consent to them?

Moral rights are the creator's personal rights to be named and to object to derogatory treatment of their work, and they cannot be assigned. The practical answer is a written consent, which this agreement gives: the assignee may modify, rename, relicense or publish the works without naming her.

Should the schedule list open source components?

It should say what licences are in the works, and this one does. Four MIT libraries, one Apache 2.0 with its notice retained, twenty two front end packages and one open font licence, with a statement that nothing copyleft is present. That single clause is what an acquirer checks first.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make my ip assignment agreement template with a schedule and moral rights

Other document examples

Want the steps in the builder? Read Create a document with AI, then Every document component and when to use it. For everything this generator can do, see the document maker.

Sources

Written and checked by the OneCraft team. Last checked .