Signing example

Sign an IP assignment agreement online

To sign an IP assignment agreement online, upload the final PDF, put the assignor's initials on the schedule of works and the moral rights consent, and send it to the assignor first. This envelope carries the four page Tallow Labs agreement in which contract developer Sonia Ekwueme assigns six works, from the ledger core service to the developer documentation, while keeping her Quill logging library under a licence back, behind an access code.

Send a document for signing2 signers, an access code for the assignor, an email link for the company

The document itself is written out in full on its own page: read the wording there. This page is only about signing it.

Who signs what

Sonia Ekwueme, the Assignor, signs first
Initials on page 1, under the schedule of six assigned works · Initials on page 3, under clause 5, the moral rights consent · Signature, name and stamped date on the Assignor lines on page 4 · Verified by access code
For Tallow Labs Limited, the Assignee, countersigns
Signature block on page 4 over the printed Name, Position and Date lines · Email link

The signing journey

  1. Step 1

    Seven fields, order on

    The assignor gets initials under the schedule on page 1 and under the moral rights consent on page 3, then a signature, name and date on her lines on page 4. The company gets one signature block with Name, Title and Date over For Tallow Labs Limited. Sign in order is on, assignor first.

  2. Step 2

    An access code, read out on a call

    The assignor carries an access code of at least four characters, typed by the sender when she was added and never returned by the API. It was read out on the call where the schedule was agreed, so the emailed link alone does not open the agreement.

  3. Step 3

    One drawing, three marks

    Sonia enters the code, accepts consent and draws once. The portal fills both initials spots and the page 4 signature from that drawing, her name arrives prefilled from the recipient row, and the date stamps itself from the moment she submits, on the 12 January 2027 date the agreement is made.

  4. Step 4

    The company countersigns

    Only now is the Tallow Labs officer invited. The officer opens a copy already carrying her marks, types a position on the Title line and signs, and the certified PDF goes to both parties and the sender.

Every field, and who fills it

Seven fields across two parties. The assignor owns two initials spots, on page 1 under the schedule and on page 3 under clause 5, then a signature, a name and a date on page 4. The company owns one block with Name, Title and Date over the printed Name, Position and Date lines. Both names come from the recipient rows, both dates are stamped, and only the company officer's title is typed. The six works, the $6,401 consideration and the licence back are printed in the document and covered by its hash, because the sender cannot pre-type anything into a field.

What the signed file records

The certified PDF carries all four pages: the schedule, the assignment that takes effect on the date of the agreement, the $1 plus $6,400 final invoice consideration, the licence back of the Quill library, the list of open source components and the handover within 10 business days. The certificate shows the assignor verified by Email link + access code and the company by Email link, each with an IP address, consent time and signing time.

How to adapt this envelope

For an employee rather than a contractor, much of this is already the employer's under the default rule for work made in employment, so the document usually becomes a confirmation with a prior inventions schedule instead of a list of works. A company that executes through two officers adds a second recipient with a block of its own. A later short form assignment for one registration, which clause 7.3 promises, is always its own envelope.

What makes this signing flow work

The schedule is initialled, not described

Clause 1.2 keeps background IP with the assignor, which is why the agreement assigns a list rather than the whole project. The six rows, TL-01 to TL-06, name each repository or design file and when it was created. Initials directly under that table fix exactly what moved, in the assignor's own mark.

Initials on the consent that cannot be assigned

Moral rights cannot be assigned, only consented to. Clause 5.1 has Sonia consent to modifying, renaming or deleting the works and publishing them without her name. Her initials on page 3 put her mark on that consent itself, not only on the signature page a clause away.

The code fits a contractor who is finishing up

Sonia's engagement ends on 29 January 2027 and she works remotely. Reading the code out on a call ties her signature to the person on that call, and the certificate prints Email link + access code beside her name rather than a bare click on a forwarded email.

Questions people ask

Does the contractor keep the Quill logging library?

Yes. Clause 1.2 says background IP, anything she owned before 2 March 2026 or made outside the engagement, is not assigned, and names the Quill library. Clause 4.1 then licenses it to Tallow Labs forever and royalty free to the extent it is embedded in the works, so the company can keep shipping it without owning it.

Why does the assignor initial the schedule of works?

Because the schedule decides what moved. A later argument about whether the API client libraries or the design system tokens were included runs into her initials directly under rows TL-04 and TL-05, made from the same drawing as her signature and recorded in the same signing event on the certificate.

How is the access code shared with a remote contractor?

Out of band, never in the invitation email. The sender types a code of at least four characters when adding the recipient, the API stores only a salted hash and never returns it, and the sender reads it out by phone or video call. Five wrong attempts lock the recipient for fifteen minutes.

Does the company sign on the same day?

Not necessarily. The officer is invited as soon as the assignor's signature lands and can sign any time before the envelope expires, 30 days after it was created. Clause 2.1 makes the assignment take effect on the date of the agreement, 12 January 2027, rather than on whichever day the countersignature lands.

What if the contractor disagrees with the schedule?

She can press Decline and type a reason, for example that the reconciliation worker reused her own code. The envelope moves to declined, nothing further is stamped, the sender is emailed the reason, and the company is never invited. A corrected schedule goes out as a fresh envelope, since a sent one cannot be edited.

Is the moral rights consent valid when signed electronically?

Australian copyright law lets an author give a written consent to acts that would otherwise infringe moral rights, and the Electronic Transactions Act 1999 lets an electronic signature meet a signature requirement where the method identifies the person and is reliable. The envelope keeps the code check, consent record and hash chain. Advice on a specific consent belongs with a lawyer.

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 one like this

Other signing examples

Want the steps in the builder? Read Send a PDF for e-signature, then Add several signers to one envelope. For everything this generator can do, see the signing flow maker.

Sources

Written and checked by the OneCraft team. Last checked .