What Does Work for Hire Actually Mean?

What Work for Hire Legally Means

Under U.S. copyright law (specifically Section 101 of the Copyright Act), a “work made for hire” is a work where the hiring party is considered the legal author. Not the person who actually created it. The employer or client is treated as though they wrote the code, designed the logo, or composed the copy themselves. The creator never owned it. Legally, they never existed as the author at all.

There are two categories. The first is work created by an employee within the scope of their employment. This is automatic. If you are a W-2 employee and you build something as part of your job, the company owns it. No separate agreement is required.

The second category is specially commissioned work from an independent contractor. This is where freelancers come in. For work for hire to apply here, two conditions must both be true: the work must fall into one of nine specific statutory categories (including contributions to collective works, translations, compilations, and instructional texts), and both parties must sign a written agreement stating the work is made for hire.

Here is the catch. Many types of freelance work do not fit neatly into those nine categories. Custom software, original graphic design, and standalone articles do not always qualify. So contracts often include both a work for hire clause and a separate IP assignment clause as a fallback. If work for hire does not apply, the assignment ensures the client still gets ownership. Either way, you lose it.

Why It Matters for Freelancers

The practical consequences are broader than most freelancers realize when they sign. Here is what work for hire actually means for your business:

You cannot reuse the code, designs, templates, or any component of the deliverable on other projects. That React component library you built for a client? If the contract includes work for hire language, you cannot use those components on your next project, even if you wrote them from scratch using patterns you have used for years.

You cannot put the work in your portfolio without the client’s explicit permission. This seems like a small thing until you realize that your portfolio is how you get your next client. Some contracts prohibit public display entirely. Others require written approval, which the client may never bother to give.

You cannot license the work to other clients, even non-competitors. If you designed a booking system for a yoga studio and a dentist’s office wants something similar, you cannot adapt your previous work. You have to start from zero.

The client can modify, resell, sublicense, or transfer your work to anyone, for any purpose, without credit or additional compensation to you. They can put their name on it. They can sell it to your competitor. They can alter it in ways that damage its quality and still associate it with the original. You have no say.

Red Flags in Contract Language

Not all work for hire clauses are equally aggressive. Some are narrow and reasonable. Others are written to capture everything you have ever created or will create during the engagement. Watch for these specific phrases:

“All work product” is the broadest possible framing. It does not limit ownership to the specific deliverable described in the statement of work. It covers sketches, drafts, notes, research, prototypes, and anything else you produced while working on the project.

“Including derivative works” extends the scope beyond the deliverable itself. If you adapt a template you already own for the project, the derivative work clause could give the client ownership of your template, not just the adaptation.

“In perpetuity throughout the universe” sounds absurd, but it is standard legal language. It means the assignment has no time limit and no geographic restriction. Forever, everywhere. This phrase is common and not inherently problematic, but combined with broad scope language, it amplifies the impact.

“Including but not limited to pre-existing materials” is the most dangerous phrase on this list. Pre-existing materials are things you created before the engagement started. Tools, libraries, frameworks, templates. This clause attempts to transfer ownership of assets that existed before the client was even in the picture. It is often unenforceable, but fighting it in court is expensive and uncertain.

How to Protect Yourself

The good news is that these clauses are negotiable. Clients include them because their lawyer drafted a template that maximizes protection for the client. Most clients do not actually need or intend to enforce the broadest interpretation. Asking for changes is professional and expected.

Carve out pre-existing IP. Attach a schedule (Schedule A, Exhibit B, whatever naming convention the contract uses) that explicitly lists every tool, library, framework, and template you are bringing to the project. The contract should state that these remain your property and are licensed to the client for use in the specific deliverable.

Negotiate portfolio rights. Add a clause that grants you the right to display the work in your portfolio, on your website, and in case studies. Specify a reasonable waiting period if the client needs a head start (30 to 90 days after launch is typical).

Add a license back for non-competing uses. Even if the client owns the deliverable, you can negotiate a license that lets you reuse the underlying methodology, structure, or approach for clients in non-competing industries. The client gets their exclusive product. You get to build on your own expertise.

Retain general skills and knowledge. This is a standard clause in well-drafted contracts, but it is often missing from templates. It states that nothing in the agreement prevents you from using the general skills, techniques, and knowledge you developed during the engagement. You learned something while working on this project. That learning belongs to you.