Work For Hire Agreement: What Freelancers Must Know Before Signing
Three words buried in a contract can permanently transfer everything you create to your client — including the work you've already delivered.
“Work for hire” is one of the most misunderstood terms in freelance contracts — and the most dangerous. Under US copyright law, when work qualifies as work-for-hire, the client is legally treated as the author. That means they own the copyright from the moment you create it. No license. No rights reversion. No royalties. The work is theirs, permanently, as if you never made it.
For employees, this makes sense — your employer owns the software you write on company time. But freelancers are independent contractors, and the rules are different. A work-for-hire clause in a freelance contract doesn't happen automatically; it has to be in writing. And that's exactly why clients put it there — because without it, you keep the copyright by default.
That said, work-for-hire clauses aren't always unreasonable. If you're building something that will live inside a client's product, they may have a legitimate need to own the output. The problem is how these clauses are written. Most go far beyond what's necessary, and three specific traps account for the vast majority of the damage freelancers suffer.
- ✗The right to use your own work — including in future projects
- ✗The right to show it in your portfolio without permission
- ✗Any claim to royalties or additional compensation
- ✗The ability to build on it, iterate on it, or license it
- ✗Credit for creating it — legally, the client is the "author"
None of this is buried in fine print — WFH clauses are often the first or second clause in a contract, placed there deliberately because clients know most freelancers don't understand what they're signing away. Here are the three versions that cause the most harm.
The Retroactive WFH Clause
"This agreement applies to all work performed by Contractor for Client, including work performed prior to the execution of this agreement."
This language doesn't just cover the project you're starting today — it reaches back and claims ownership of everything you've ever made for this client, including mockups, prototypes, or preliminary work you may have shared informally before signing anything. If you built a logo concept last month before the contract was finalized, this clause can transfer that IP retroactively.
"I'm happy to assign IP rights for work under this agreement going forward, but I can't agree to retroactive assignment. I'd like to revise this to read: 'This agreement applies only to work performed after the execution date of this agreement.'"
The Blanket Assignment
"Contractor assigns to Client all intellectual property rights in any work related to Client's business or industry, whether or not created under this agreement."
This clause isn't limited to your deliverables — it grabs anything "related" to their industry. If you're a web developer who works across multiple SaaS clients, a blanket assignment from one client could technically claim your code libraries, design systems, or process templates you built independently and use across dozens of projects. The word "related" is intentionally vague, and intentionally broad.
"The current language is broader than I can agree to — it would capture work I do for other clients in the same space. I'd like to narrow this to: 'Contractor assigns all IP rights in the final deliverables specifically listed in this agreement's scope of work.'"
Paste your contract into FreeCoat → we flag IP grabs instantly.
Work-for-hire clauses, retroactive assignments, blanket IP grabs — FreeCoat identifies them all and gives you the negotiation language to push back.
Scan your contract free →The No Credit / No Portfolio Rights Clause
"Contractor agrees to keep all work product confidential and shall not display, publish, or reference the work in any portfolio, case study, or promotional material without prior written approval."
You just handed over your IP and now you can't even show the work to future clients. This clause is especially damaging for designers, developers, copywriters, and photographers whose ability to win new clients depends entirely on showing past work. A client can use your designs indefinitely — on their website, their ads, their sales decks — while you're legally barred from including that same work in your portfolio.
"I understand you may need to keep some details confidential. I'd propose this revision: 'Contractor may display the work in their portfolio and reference the engagement in case studies, provided no confidential business information, unreleased products, or proprietary data is disclosed.'"
A work-for-hire clause isn't inherently predatory — sometimes it's a reasonable business requirement. What's predatory is the retroactive scope, the blanket grab, the portfolio silence clause. These don't protect the client's legitimate interests; they maximize extraction at your expense.
Most clients will negotiate when you push back professionally. The scripts above are designed to show you're informed, not combative — you're protecting both parties from ambiguity, not trying to hold anything back.
If you want a second set of eyes before you sign, FreeCoat will scan your full contract and flag every IP clause — including work-for-hire language you might otherwise miss.
Does your contract have a work-for-hire clause?
Paste it into FreeCoat and find out in 30 seconds. We'll flag every IP clause and generate a negotiation email you can send today.
Review your contract free →Free · No account needed · Takes 30 seconds