Always Get IP Assignment in Writing From Contractors
The Ownership Gap Most Small Businesses Don’t Know Exists
You paid for the work, so you own it — that assumption feels obvious, but under US copyright law it is wrong, and discovering the gap at the wrong moment can cost you far more than the original project ever did.
This is not an edge case or a theoretical risk. It is one of the most routine legal surprises that surfaces when small businesses try to raise a funding round, go through acquisition due diligence, or simply part ways with a contractor who turns difficult. The underlying rule is straightforward once you know it, and the fix is genuinely simple. The problem is that most business owners never learn the rule until they are already in trouble.
What the Law Actually Says About Contractor Work
Under the US Copyright Act, copyright in a creative work vests automatically in the person who created it — the moment the work is fixed in a tangible form. There is one major exception: the work made for hire doctrine. If a work qualifies as work made for hire, the employer or commissioning party is treated as the legal author and owns the copyright from the start.
Here is where businesses get tripped up. Work made for hire applies automatically to work created by a W-2 employee within the scope of their employment. For independent contractors, the rules are much narrower. A contractor’s work qualifies as work made for hire only if two conditions are both satisfied:
- The work falls into one of nine specific categories defined by statute (things like contributions to a collective work, parts of a motion picture, translations, supplementary works, compilations, instructional texts, tests, answer material for tests, or atlases).
- There is a written agreement signed by both parties explicitly designating the work as made for hire.
Notice what is missing from that list: websites, software, logos, marketing copy, custom illustrations, podcast editing, and most of the other things small businesses routinely commission from freelancers. A custom software application built by an independent contractor almost certainly does not fit any of the nine statutory categories. Neither does a logo, a brand guide, or a social media content library. Without a written assignment clause, ownership of all of that work stays with the contractor — regardless of how much you paid, regardless of how specific your creative brief was, and regardless of whether the contractor ever mentioned ownership at all.
When This Actually Becomes a Problem
The ownership gap tends to be invisible during the normal course of business. You commission work, you receive deliverables, you use them, and everything feels fine. The gap becomes visible — and expensive — in a handful of specific situations.
Acquisition due diligence. When a buyer or their counsel reviews your IP portfolio, they will ask for written documentation of ownership for every significant asset: your software codebase, your brand assets, your website, your proprietary content. If you cannot produce assignment agreements, the buyer’s attorney will flag those assets as encumbered. At best, you spend time and legal fees tracking down former contractors to sign retroactive agreements. At worst, the contractor cannot be found, refuses to sign, or demands payment, and the deal is delayed, repriced, or falls apart.
Investment rounds. Investors and their counsel run the same IP review as acquirers. A venture firm or angel investor writing a meaningful check wants confidence that the product they are funding is actually owned by the company they are funding. Missing assignment agreements are a standard reason for deals to slow down or for founders to receive reduced valuations.
Disputes with former contractors. Most contractors are reasonable people and would never think to claim ownership of work you clearly commissioned and paid for. But relationships turn. If a contractor becomes unhappy — over a payment dispute, a non-renewal, a negative review — ownership of unassigned work can become a leverage point. A contractor who can credibly claim copyright in your logo, your codebase, or your core content library has meaningful leverage over your business even if their claim is primarily nuisance value.
Enforcement actions. If you ever need to enforce your IP — sending a cease-and-desist to someone copying your software, for instance — you typically need to demonstrate that you hold the copyright. Missing documentation weakens your position before you start.
The Two-Part Solution: Assignment and Work Made for Hire Together
A well-drafted contractor agreement handles IP ownership in two steps, and both steps belong in every contract you sign with an independent contractor doing creative or technical work.
Step one: Work made for hire designation. Include language stating that all work created under the agreement is work made for hire to the maximum extent permitted by applicable law. This language costs nothing and captures any work that does happen to qualify under the statutory categories.
Step two: Assignment as a fallback. Immediately after the work-made-for-hire clause, add an assignment clause stating that to the extent any work does not qualify as work made for hire, the contractor hereby assigns all right, title, and interest in and to that work — including all copyright, patent rights, and other intellectual property rights — to the company, effective as of the moment of creation. This is the clause that actually does the heavy lifting for most contractor work.
Together, these two provisions close the gap completely. You do not have to determine in advance whether a specific deliverable meets the statutory criteria; the contract covers both possibilities. The assignment clause should also cover moral rights waivers if you are working with contractors internationally, since some jurisdictions recognize rights that cannot be transferred by assignment alone.
A few additional provisions are worth including alongside the core assignment language:
- Pre-existing IP carve-out. If the contractor is bringing tools, libraries, or prior work into the project, identify those specifically and confirm that you receive a license to use them in the deliverable, even if ownership stays with the contractor. This protects both parties and avoids ambiguity.
- Moral rights and attribution. Confirm the contractor waives any right to attribution or integrity claims to the extent permitted by law.
- Further assurances. Include a clause requiring the contractor to execute any additional documents necessary to record or perfect the assignment. This gives you a contractual basis to get signatures later if a third party — a patent office, a domain registrar, a software registry — needs formal documentation.
- Subcontractor flow-down. If the contractor is permitted to use subcontractors, require that they obtain equivalent assignment agreements from those subcontractors and that rights flow up to you. A freelance developer who subcontracts part of the build creates the same ownership gap one level down.
How to Handle Existing Agreements That Are Missing This Language
If you have already worked with contractors and your agreements did not include assignment clauses, you are not necessarily without recourse — but you do need to act deliberately.
Start by auditing which assets matter most. Your production codebase, your primary brand assets, and any proprietary content that is central to your product or go-to-market are the highest priority. Work your way down from there.
For each significant asset, identify the contractor who created it and whether you have a current relationship with them. If the relationship is intact, reaching out for a retroactive IP assignment agreement is usually straightforward. Most contractors are cooperative when the request is framed professionally — you are not asking them to give up something they are actively using; you are asking them to confirm in writing the arrangement both parties understood to be in place.
If a contractor is difficult to locate or unresponsive, document your outreach efforts. In some cases, where the contractor cannot be found and there is no indication of an ownership dispute, you may be able to proceed with reasonable confidence — but this is a judgment call that warrants a conversation with an attorney familiar with IP law, not a unilateral decision.
Do not let the size of the task stop you from starting. Prioritize the assets that would surface first in due diligence or that carry the most operational risk, and work through the list methodically.
Practical Notes on Getting Contractors to Sign
In practice, most professional contractors are accustomed to IP assignment clauses and will sign without objection. It is a standard feature of commercial freelance work, and experienced contractors expect it. Pushback, when it happens, usually comes from two situations: a contractor who is unfamiliar with commercial contracting norms, or a contractor who specifically wants to retain rights for portfolio or reuse purposes.
For the second case, a reasonable accommodation is to allow the contractor to display the work in their portfolio while confirming that all IP rights belong to your company. That is a straightforward carve-out that addresses a legitimate professional interest without compromising your ownership position. What you want to avoid is agreeing to language that gives the contractor a license to reuse or resell the actual work product — a custom software component built for your product, for instance, should not end up in a competitor’s product because the original contract was vague.
The Bottom Line
IP assignment language is not boilerplate you include to look professional. It is the mechanism by which the work you paid for actually becomes yours in the eyes of the law. Adding it to every contractor agreement is a one-time habit that eliminates an entire category of expensive, avoidable problems — the kind that tend to surface at exactly the moment when your business can least afford a distraction. Build the clause into your standard contract, use it consistently, and you will never have to explain a missing signature during due diligence.