How to protect your work when a client claims ownership

The project is delivered. The client is happy. Six months later, they sell the company, and the new owner contacts you to confirm that all the work you produced is theirs to keep.

You say yes — because it seems obvious. They paid for it.

But in most jurisdictions, that’s not how copyright works.

Who actually owns the work

By default, the person who creates a work owns it. Not the person who paid for it.

This applies to code, copy, designs, illustrations, videos — anything covered by copyright. Paying for a service doesn’t transfer ownership. Only a written agreement does.

In practice, what a client buys when they hire a freelancer is a license: the right to use the work. Not ownership of it.

Most freelancers and clients go through entire projects without knowing this. Most of the time, it doesn’t matter. It matters the day the client tries to sublicense the work, modify it significantly, sell it, or include it in a company acquisition — and needs to prove clean title.

The clause that fixes it

You don’t need much. One sentence in the contract:

“Upon receipt of full payment, [Freelancer] assigns to [Client] all intellectual property rights in the deliverables produced under this agreement.”

That’s it. The key conditions:

• Full payment first — IP transfers when the invoice clears, not when you deliver the files
• “All intellectual property rights” — covers copyright and related rights
• “Deliverables produced under this agreement” — limits it to this project, not your past or future work

If you want to retain the right to show the work in your portfolio, add one sentence: “Client grants Freelancer a non-exclusive, royalty-free license to display the work for portfolio purposes.” Most clients have no problem with this.

What “work for hire” means

Sometimes a client sends you a contract that includes “work for hire” language. This is a specific legal concept — mainly US — where the work is treated as if the employer created it, removing the need for a separate assignment clause.

For most freelancers, this is fine. The practical effect is similar: the client ends up owning the work.

The thing to watch for is what else comes with it. Work-for-hire language sometimes appears in contracts that also include non-competes, exclusivity clauses, or rights to past and future work. Read the full clause, not just the three words.

If you’re outside the US or want cleaner terms, the assignment clause in your own contract is simpler.

Source files are a separate question

IP assignment and source files are related but not the same.

Assigning copyright doesn’t automatically mean handing over working files. A designer can transfer all rights to a logo and still, technically, keep the Figma source. The client can use the logo — but can’t modify it without coming back to you.

Whether to include source files in the standard deliverable, or price them separately, is a commercial decision. What matters is that it’s written down before delivery. “Deliverables include final files in [format]. Source files are available separately at [price]” — one line in the project brief or contract removes the post-delivery argument.

The scope of work is where you define what “deliverables” means. That’s also where the source files question gets settled.

When you’ve already delivered without a clause

It happens. The project ended, everything was fine, and two years later the client asks for written confirmation that the IP is theirs.

You can still assign it retroactively. A short written agreement — even an email exchange works in many jurisdictions — that explicitly transfers the rights for work produced under that project is sufficient. Date it, get a response confirming receipt, keep a copy.

If there’s a dispute and the client is claiming rights they don’t actually have in writing, consult a lawyer. The default in most places is that you still own it — which puts you in a stronger position than most people assume.

Make it a default, not a special request

IP clauses feel like advanced contract territory. They’re not.

They’re one paragraph in a contract you send to every client. Most clients read it, nod, and move on. The ones who push back on a standard IP assignment clause are worth questioning.

What every freelance contract should include covers the other clauses that tend to get skipped — payment terms, kill fees, revision limits. IP is one piece of a contract that protects you before the project starts, not after something goes wrong.

Timescanner reads your calendar to track hours by client and project. If a dispute arises over what was actually delivered, having a timestamped record of what you worked on — and when — is useful evidence. Works with any iCal-compatible calendar.