Copyright law defaults to protecting the creator. Under 17 U.S.C. § 101 and § 201, the author of an original work owns the copyright. That's the baseline. Work-for-hire is an exception to that baseline — and it's a limited exception with two distinct pathways.

If someone is your employee — not a contractor — and they create the work within the scope of their employment, it's automatically a work for hire. You own the copyright without any written agreement needed.

But here's the operative word: employee. Not contractor, not freelancer, not 1099 worker. The IRS and courts look at the economic reality of the relationship. Do you control how and when the work is done? Do you provide tools and equipment? Is this their primary income source from you? Is there an ongoing relationship? If the answers point to employment, the work-for-hire doctrine likely applies.

Most solopreneurs work with independent contractors, not employees. So this pathway often doesn't apply.

For independent contractors, a work-for-hire relationship can only be created through a written contract — and only for specific categories of work defined by the Copyright Act. This is where the surprise hits people.

Work-for-hire contracts are valid for independent contractor work only if the work falls into one of these nine statutory categories:

1. A contribution to a collective work 2. A part of a motion picture or other audiovisual work 3. A translation 4. A supplementary work (prefaces, introductions, editorial notes, bibliographies, appendixes, indexes) 5. A compilation 6. An instructional text 7. A test 8. Answer material for a test 9. An atlas That's it. Nine categories. If the work your contractor creates doesn't fall into one of these, a work-for-hire clause in your contract is not effective. The contractor legally owns the copyright — even if they never thought about it, even if you paid them in full, even if the contract says "work for hire."

This is not a loophole. It's the explicit structure of U.S. copyright law.

Here's where things get practical and frequently problematic. Many common types of freelance work are not in the nine statutory categories:

Website copy or blog articles written by a freelance writer A custom logo or brand identity designed by a graphic designer Custom software code written by a developer Photographs taken by a freelance photographer Illustrations created by a commissioned artist Social media content or marketing copy If you hire a freelancer for any of these, a work-for-hire clause doesn't automatically transfer ownership of the copyright to you. The freelancer retains it under default copyright rules.

This has real consequences. Technically, a freelance developer who built your custom web application owns the code unless they've assigned their copyright to you in writing. A designer who created your logo owns it until they sign an assignment agreement. In practice, most freelancers don't know this and wouldn't exercise those rights — but "most freelancers won't enforce it" is not a legal protection.

When work doesn't fall into the nine statutory categories, the correct mechanism is a copyright assignment — a written agreement in which the creator explicitly transfers ownership of the copyright to you.

A copyright assignment clause looks something like this:

"To the extent the Work does not qualify as a 'work made for hire' under applicable law, Contractor hereby irrevocably assigns to Client all right, title, and interest, including copyright and all related rights, in and to the Work and all deliverables produced hereunder."

This is the belt-and-suspenders approach: include both a work-for-hire clause (for work that qualifies) and an assignment clause (for work that doesn't). This way, regardless of how a court would classify the work, ownership transfers to you.

That one paragraph in your contract does more to protect your intellectual property in hired creative work than anything else.

Here's another nuance that trips up business owners: assignment covers new work created for you, but what about things the contractor already owned before your engagement?

If a developer incorporates a code library they built years ago into your project, or a designer uses a Photoshop template they created on their own time, those are "pre-existing works" or "background IP" — and an assignment clause doesn't automatically transfer ownership of them to you.

The practical solution: your contract should specify that any pre-existing IP incorporated into deliverables is either (a) excluded (the contractor retains it), (b) licensed to you on specified terms, or (c) identified upfront so you know what's actually in the deliverable.

Most small projects don't involve significant background IP concerns. But for complex software development or comprehensive brand design, this is worth discussing explicitly in the contract.

Most of this guide has been written from the perspective of someone hiring creative work. If you're the one creating work as a contractor, the same rules apply in your favor — and understanding them is just as important.

When a client's contract includes a work-for-hire clause for work that's not in the nine categories, it may not achieve what they think it does. But an assignment clause absolutely does. Read your contracts carefully. Once you sign an assignment clause, you've transferred ownership of your creative work.

Considerations if you're a freelancer:

Portfolio rights: Assignment transfers ownership, but you can negotiate to retain the right to display work in your portfolio. Include this in your contract. Attribution: Assignment doesn't automatically include attribution rights. If credit matters to you, negotiate that explicitly. Ongoing licenses vs. full assignment: For some work, a broad license (giving the client extensive rights to use the work) rather than full assignment may be appropriate. You retain ownership but grant them what they practically need.

Whether you're hiring or being hired, your contract needs to address ownership of deliverables explicitly. The two-clause approach — work-for-hire where applicable, assignment as a fallback — handles the full range of situations cleanly.

Beyond the ownership clause, your contract should also address:

Moral rights. Visual artists in the U.S. have limited "moral rights" under the Visual Artists Rights Act (VARA) — the right to claim authorship and prevent intentional destruction of certain works of recognized stature. For most commercial work, a written waiver of moral rights can be included.

Representations and warranties. The creator should warrant that the work is original, doesn't infringe any third-party rights, and is free of any liens or encumbrances. This protects you if the contractor used someone else's work without permission.

Indemnification. If the contractor infringes a third party's IP and you get sued as a result, the indemnification clause determines who bears that cost. It should be the contractor.

Sometimes clients ask freelancers to provide sample work or "spec" deliverables before a contract is signed. This is legally murky. Absent a contract, the freelancer owns whatever they create — and if they later walk away from the engagement, they take the spec work with them, and you have no rights to use it.

If you're requesting spec work as a client, have at minimum a brief written agreement (a letter of understanding) that covers IP in the spec deliverables. If you're the freelancer creating spec work, be clear in writing that you retain all rights unless and until a formal agreement is signed.

One indirect consequence of work-for-hire relationships: if your working arrangement with a contractor starts to look like an employment relationship (you're directing their work closely, they work exclusively for you, they're integrated into your business operations), the IRS may reclassify them as employees — with significant back-tax and penalty exposure for both parties. The IP ownership framework and the employment classification question are separate legal issues, but they're often tangled together in practice.

If you work regularly and closely with the same few contractors, review the IRS's worker classification guidance and consult a tax professional if there's any ambiguity.

The most dangerous IP situations for solopreneurs aren't the ones where someone actively steals their work — they're the ones where ownership was never clearly established, and an unexpected claim emerges years later. Don't let your IP protection hinge on what a freelancer "probably won't do." Write it into the contract, every time, for every project.

If you're a freelancer, know what you're signing. An assignment clause is a permanent transfer of ownership — understand exactly what you're giving up before you sign.

Download NoBossly's work-for-hire and IP assignment contract clauses — ready to add to your agreements today.

This clause belongs in every contractor engagement and connects to copyright fundamentals. On the flip side, when you're the freelancer, your client contract should price IP transfer deliberately.