A founder hires a designer, pays the invoice in full, and assumes the logo now belongs to the company. Under United States copyright law that assumption is often wrong. Payment buys the service; it does not, by itself, transfer the copyright. The question of who owns the work turns on a statute, not a receipt.
The phrase work made for hire sounds like it means whatever a business pays to have made. It does not. It is a defined term in the Copyright Act, and it reaches only two situations: works prepared by an employee within the scope of employment, and certain commissioned works that both fall into nine enumerated categories and are covered by a signed written agreement calling them work for hire. Most of what a small business buys from a freelancer — a logo, a website, photographs, marketing copy, source code — sits outside both paths. When work for hire does not apply, the contractor owns the copyright the moment the work is fixed, and the only way the copyright moves to the business is a written assignment.
This matters because the gap is invisible until it is expensive. A company can use a logo for years, build a brand on it, and discover during a financing, a sale, or a dispute that it never owned the underlying copyright at all. The designer does. The fix is not complicated, but it has to be in writing and it has to be drafted as an assignment, not assumed from the fact of payment. This note explains the two statutory work-for-hire paths, why independent-contractor work usually needs an assignment instead, the difference between a license and an assignment, and the contract language that closes the gap before it opens.
The two narrow paths the statute actually allows
The Copyright Act gives only two ways for a work to be made for hire. The first is a work prepared by an employee within the scope of employment. If a salaried employee creates the work as part of the job, the employer is treated as the author and owns the copyright from the start, with no separate assignment. The hard part is the word employee. Courts read it through agency-law factors — control over how the work is done, who supplies the tools, how the worker is paid and taxed — and a person a business casually calls a contractor may, or may not, be an employee for this purpose. The label on the invoice does not settle it.
The second path is narrower still. A commissioned work can be work for hire only if two conditions are both met. It must fall within one of nine enumerated statutory categories — among them contributions to a collective work, parts of an audiovisual work, translations, compilations, and a few others — and the parties must sign a written agreement expressly stating that the work is made for hire. Miss either condition and the path closes for that work. A great deal of ordinary commercial work — most standalone logos, much standalone software — does not fit any of the nine categories at all, which means the work-for-hire label cannot attach to it no matter what the contract says.
The practical consequence is that for the typical independent contractor, work for hire is the wrong tool. The relationship is usually not employment, and the deliverable usually does not fit the nine categories. So the copyright does not pass to the business automatically and cannot be forced into work-for-hire status by wording alone. Something else has to carry the ownership across, and that something is an assignment.
Work made for hire is a defined term, not a description of whatever a business pays to have made.
Why an assignment is the instrument that transfers ownership
When work for hire does not apply, the independent contractor is the author and owns the copyright from the moment the work is fixed in a tangible form. To move that ownership to the business, the contractor has to transfer it, and the Copyright Act requires a transfer of copyright ownership to be in a writing signed by the owner. A verbal understanding, an email saying the files are yours, or a paid invoice will not do the work the statute reserves for a signed assignment. This is where a license and an assignment part ways, and the difference decides who owns the work.
A license is permission to use a copyright the contractor still owns. It can be broad or narrow, exclusive or not, perpetual or limited, but the contractor keeps the copyright and the business holds only the rights the license grants. An assignment is a transfer of the copyright itself: after a valid assignment the business becomes the owner and can use, modify, license, and enforce the work as its own. A company that thinks it bought a logo outright but received, at most, an implied license to use it has far less than it believed — it may not be able to register the copyright, stop a competitor, or convey clean ownership to an acquirer.
This is also why I paid for it is not a statement of ownership. Payment is consideration for whatever the contract actually granted. If the contract granted a service and delivered files, the business owns the physical files and, often, an implied license to use them for the purpose they were made — but not the copyright. Ownership of the copyright is a separate thing, transferred in writing on purpose. The invoice proves the business paid; it does not prove the business owns.
The fix lives in the contract, before the work begins
The reliable fix is a written intellectual-property clause in every contractor, freelancer, and vendor agreement, signed before the work starts. Sound drafting does two things at once: it states that the deliverables are works made for hire to the extent they qualify, and it adds a present assignment of all copyright and other intellectual-property rights in the deliverables to the company as a backstop for everything that does not qualify. The belt-and-suspenders structure matters because the parties usually cannot know in advance which deliverables will fit the nine categories, and the assignment catches whatever the work-for-hire label cannot.
Two carve-outs keep that language honest. The first is moral rights — rights of attribution and integrity that, for certain works, do not transfer with the copyright and in some cases cannot be assigned; a well-drafted clause addresses them with a waiver or consent to the extent the law allows rather than pretending they moved automatically. The second is prior works: a contractor frequently builds on tools, libraries, templates, or stock the contractor already owns, and the agreement should separate those pre-existing materials from the new deliverables and license the prior works embedded in what the company receives, rather than purporting to assign things the contractor cannot give.
Software, design, logos, and creative agencies are where this is felt most. A logo and standalone code generally do not fit the work-for-hire categories, so they ride entirely on the assignment language. An agency may itself be using subcontractors, which means the chain of rights has to run from each subcontractor to the agency and from the agency to the client, or the client's title has a gap it cannot see. The lesson of this note is narrow and useful: decide who owns the work in writing before the work is made, draft it as an assignment rather than trusting the work-for-hire label or the invoice, and the question of ownership never has to be litigated after the brand is already built.
Decide who owns the work in writing before the work is made — an assignment drafted up front is cheaper than a dispute after the brand is built.