When IP transfers before you’re paid: a freelance contract trap

Why ‘ownership upon delivery’ or ‘upon creation’ is risky for freelancers, what to ask for instead, and how IP timing interacts with Net terms and final file handover.

A sentence like this shows up constantly in client paper:

All right, title, and interest in the Deliverables shall vest in Client upon creation / upon delivery.

Payment might be Net-45 or Net-60. Final invoice clears weeks later — or not at all. Meanwhile the client already has ownership language on their side and, often, the files.

That timing mismatch is the trap. You still have a debt claim. You may no longer have ownership leverage.

This is general information, not legal advice. Copyright and assignment rules differ by country. “Work made for hire” has a specific meaning in U.S. law and does not always do what a template pretends. For valuable IP or a live dispute, talk to a lawyer.

Why the timing word matters more than the heading

Most freelancers skim for the heading “Intellectual Property” and stop at “client owns the work.” The commercial risk is usually in the trigger:

Trigger	Practical effect if the last invoice is unpaid
Upon creation / performance	Client may already own drafts as you make them
Upon delivery	Handing over files can complete the transfer before money clears
Upon full payment	Ownership waits on the fee; stronger leverage if AP stalls
License now, assign on payment	Client can review/use under a limited license; full assignment waits

Illustrative contrast (not recommended boilerplate — for reading practice only):

“Ownership vests in Client immediately upon creation.” vs. “Upon receipt of payment in full, Contractor assigns the Deliverables to Client. Until then, Contractor retains all rights and grants only a limited license to review the work.”

Same topic. Very different leverage.

Work-for-hire labels are not a shortcut

Client templates often stamp “work made for hire” on every SOW. In some jurisdictions that phrase has narrow statutory meaning. Outside those facts, parties usually rely on a backup assignment anyway.

Commercially, treat WFH language as a signal: the client wants broad ownership. Your job is still to negotiate when ownership moves and what is carved out (your tools, templates, prior code, third-party licenses).

For a broader primer, see freelance IP ownership and work-for-hire.

What to ask for instead

You do not need a hostile rewrite. Aim for four practical points:

Assignment (or exclusive license) effective only after full payment for that deliverable or milestone.
Until then, a limited license to review or test — not a free pass to ship to production and resell.
Background IP stays yours (frameworks, generators, house templates); client gets a license to use what is embedded in the deliverable.
Portfolio rights unless the work is truly confidential — or a delayed / anonymized case study if they are brand-sensitive.

If the client needs full buyout economics (exclusive ownership, right to modify, hire others to modify, keep you off portfolio), price that buyout. Do not hide it inside a discounted day rate.

Pair IP with how you deliver files

Even a good “assigns on payment” clause is weak if you already sent unwatermarked finals and editable source on day one.

Operational habits that match the clause:

Share previews or restricted environments until the relevant invoice clears.
Release editable source / repo access / raw files on the same trigger as ownership.
On milestone deals, assign per paid milestone, not the whole project after the first wire.

When payment terms are long, this pairing matters more. See negotiating Net-60 and the payment terms guide.

Red flags in ownership sections

“All IP created during the term,” including unrelated side projects
Assignment of rejected concepts and pitches with no extra fee
Perpetual rights to your pre-existing tools with no license limit
Moral-rights waivers broader than the project needs
Ownership on delivery plus Net-60 plus no late fee
A total portfolio ban with no time limit on ordinary marketing work

One aggressive line is a markup. A cluster is a reason to slow down.

A short reply you can send

Ownership of the deliverables can transfer to you on full payment for each milestone — that matches how we handle source files too. Until an invoice is paid I’ll keep a review license in place so your team can give feedback. My pre-existing tools and templates stay mine; you’ll get the rights you need to use what’s in the delivery. If you need a full buyout and portfolio restrictions, I can quote that as a separate line.

Calm, specific, commercial.

Where ClauseClear fits

IP, payment, and termination only make sense together. If you want a plain-English pass over those sections before you sign, paste the agreement into ClauseClear. It flags risky timing and ownership language; it does not replace counsel when the deal is large or already hostile.

After terms are set, invoice the same entity named in the signature block, with the due date the contract actually uses. A clean invoice PDF that matches those terms helps when AP asks for paperwork.

Bottom line

If ownership moves on creation or delivery while money moves on Net-45/60, you gave away the leverage that makes slow invoices painful for the client. Tie assignment to payment, keep background IP, and align final file handover with the same trigger.