If your business pays people to create software, brand assets, video, or course content, you need to know who owns the copyright. Remote teams, marketplace contractors, and AI-assisted workflows blur the line between employee and contractor, and one wrong assumption can leave you without the right to use, license, or enforce work you paid for. The fix is simple: a signed agreement before work starts, a present assignment as a fallback, and a registration plan for the assets that matter.
The Legal Framework You Need to Know
United States: Work-for-Hire Is a Narrow Door
- Employees. Under 17 U.S.C. § 101 and § 201(b), if an employee creates a work within the scope of employment, the employer is the author for copyright purposes. Whether someone is an "employee" is decided by the common-law agency factors from the Supreme Court's decision in Community for Creative Non-Violence v. Reid: who controls the work, who provides the tools, whether there are benefits and payroll tax treatment, how long the relationship lasts, and similar facts.
- Independent contractors. A contractor's work is a "work made for hire" only if two things are true: there is a signed written agreement saying so, and the work falls within one of nine statutory categories (a contribution to a collective work, part of a motion picture or audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, or an atlas). If either is missing, the contractor owns the copyright unless they sign a separate assignment.
- Practical takeaway. Many common deliverables, such as a standalone logo, an app's source code, or product photography, do not fit the nine categories. Use both: work-made-for-hire language plus a present assignment of all rights as the fallback.
The Berne Convention sets international baselines like national treatment but does not override these domestic ownership rules. Ownership and transfers are still governed by each country's law and your contract.
Outside the United States: Author-First, Contract-Driven
| Country or region | Employee-created works | Contractor-created works |
|---|---|---|
| EU | The author (a natural person) owns first; many Member States presume employer ownership for software and some employee works | Written assignment under national law |
| UK | Employer owns works made in the course of employment (CDPA 1988 s. 9 and s. 11) | Written assignment |
| Canada | Employer owns works made in the ordinary course of employment (Copyright Act s. 13(3)) | Written assignment |
| Australia | Employer owns works made under a contract of service (Copyright Act s. 35(6)) | Written assignment |
| Japan | Employer is the author of works made by employees in the course of duties (Copyright Act Art. 15), subject to conditions | Explicit agreement |
The pattern is consistent: an employer usually owns what employees create on the job, and a contractor keeps the copyright until they assign it in writing. The United States is the outlier in adding the nine-category test on top of the signed writing. There is no unitary European Union copyright registration; the EUIPO runs a voluntary database that records claims but does not grant rights.
Procedure: From Agreement to Registration to Enforcement
1) Get the Right Agreement in Place, Before Work Starts
- Timing. Sign before creation. In the United States, a contractor work-for-hire statement must be in a signed writing made before the work is created. Otherwise you rely on assignment.
- Core clauses to include:
- Parties, scope of work, and deliverables.
- Classification: employee or independent contractor.
- Work-for-hire statement (United States only) if the deliverable fits a statutory category.
- Present assignment of all rights as a fallback.
- Moral rights waiver where permitted (especially for Canada, Australia, Japan, and the United Kingdom).
- Warranties of originality and non-infringement.
- Cooperation with registration and enforcement.
- Confidentiality and return of files and assets.
- Governing law, venue or arbitration, and injunctive relief.
- Formalities. Notarization is not required, but it helps as evidence. Keep signed counterparts and change orders together.
If you already have work in hand with no agreement, a standalone copyright assignment fixes the gap. It is far cheaper than arguing about ownership after the fact.
2) Record Ownership
- United States. Registration is not required for copyright to exist, but you generally need it to sue and to claim statutory damages and attorney's fees. File online with the U.S. Copyright Office; the fee is set by the Office and varies by application type. Many claims must be brought within three years of accrual (17 U.S.C. § 507(b)), so register the assets you may need to enforce before a dispute starts. Our copyright registration service handles the application and the deposit.
- Canada. Optional registration through CIPO gives you a certificate that is evidence of ownership in court. CIPO charges a fee per work.
- European Union, United Kingdom, Australia, Japan. No formal registration system. Keep signed agreements and time-stamped records of creation.
3) Enforce Your Rights
- Pre-litigation. Send a cease-and-desist letter with proof of ownership (contracts, registration certificates, work files). Use platform takedowns; a DMCA takedown asks sites and marketplaces hosted in the United States to remove infringing copies, and timing varies by platform.
- Copyright Claims Board (United States). For claims up to USD 30,000, the CCB offers a streamlined, online alternative to federal court. A filing fee applies, split between filing and the point at which the claim proceeds. The respondent can opt out, so it works best against parties who want a quick, cheap resolution too.
- Litigation. Federal courts in the United States apply a three-year limitation period. A registration is a prerequisite to filing suit for United States works.
Common Pitfalls We See
- Misclassifying creators. In the United States, calling someone a contractor does not make their work a work-for-hire if the Reid factors point to employment, and vice versa. Courts look at control, tools, benefits, tax treatment, and duration.
- Relying on a bare "work-for-hire" label for contractors. If the deliverable is outside the nine categories, the clause fails. Without a present assignment, the contractor owns the copyright.
- No signed writing. For United States contractors, a verbal deal or an email thread is not enough for work-for-hire, and it is a problem if you did not also capture an assignment.
- Ignoring termination rights. In the United States, creators can potentially recapture assigned rights after 35 years under 17 U.S.C. § 203. True works-for-hire are excluded. If you rely on assignments, plan for that horizon.
- Overlooking moral rights. Attribution and integrity rights can limit modifications or require credit in several countries. Use waivers or consents where permitted.
- Skipping registration. In the United States, registration is inexpensive and quick relative to the cost of a dispute, and you cannot sue without it.
- Fuzzy scope of employment. For distributed teams, define the job duties and the types of works covered. Side projects and out-of-scope work can flip ownership.
Strategic Recommendations
- Classify first, then contract. Map each creator to employee or contractor using the Reid factors for United States engagements, and use the matching template.
- Use dual protection in the United States. Include a work-made-for-hire clause only when the deliverable plausibly fits a statutory category, and always add a present assignment of all right, title, and interest. Add a further-assurances clause to fix gaps later.
- Localize for work outside the United States. In the European Union, the United Kingdom, Canada, Australia, and Japan, rely on a clear written assignment with moral rights waivers or consents where permitted. Confirm governing law, forum, and language.
- Lock timing and deliverables. State that the agreement is executed before work begins and covers all drafts, iterations, and derivatives. Require delivery of working files and code repositories.
- Register early and on a cadence (United States and Canada). Batch registrations as assets ship so you are never scrambling before a takedown or a lawsuit.
- Build a takedown and small-claims playbook. Standardize cease-and-desist templates and platform takedown checklists. Consider the CCB for smaller United States disputes.
- Anticipate AI-assisted outputs. Have contributors assign the human-authored portions and confirm they hold rights in any prompts and training data they supply. Keep records of human authorship, because purely AI-generated material is not registrable in the United States.
- Keep a clean evidence trail. Store signed agreements, statements of work, change orders, time logs, commit histories, and creation metadata.
- Plan for exit and recapture. If you rely on assignments, model termination-of-transfer timelines. Secure option rights, perpetual licenses, or buyouts as needed.
- Align governing law with enforceability. If most exploitation is in the United States, choose United States law and venue for contractor agreements. For teams in the European Union or the United Kingdom, localize so the assignment and moral rights waivers are valid.
Example Clauses to Consider (Plain-English Starters)
- Work-for-hire (United States): "To the extent the Deliverables qualify under 17 U.S.C. § 101, the parties agree the Deliverables are specially ordered or commissioned as a 'work made for hire.'"
- Present assignment: "To the extent any Deliverable does not qualify as a 'work made for hire,' Contractor hereby irrevocably assigns to Company all right, title, and interest in and to the Deliverables and all intellectual property rights therein, worldwide."
- Moral rights: "Where permitted by applicable law, Contractor waives and agrees not to assert any moral rights or similar rights (including rights of attribution and integrity) in the Deliverables."
- Further assurances: "Contractor will execute any documents and take actions reasonably requested to perfect, record, or enforce Company's rights."
- Cooperation with registration and enforcement: "Contractor will provide declarations and evidence reasonably needed for copyright registration and enforcement."
These must be tailored for each country. The above is not one-size-fits-all.
FAQs We Hear From Founders and Content Leads
- Do we own a logo we paid a freelancer to design in the United States? Not automatically. A logo rarely fits a statutory category, so a work-for-hire clause alone usually fails. You need a written assignment. Until then, the designer owns it.
- Our remote developer is a contractor for tax purposes. Do we own their code? It depends. Courts look at the Reid factors, not just tax forms. Use an assignment as backup even if you believe it is a work-for-hire.
- Is a European-style "work-for-hire" possible? Generally no. In the European Union, the author owns first and rights move by contract under national law.
- Do we need to register copyrights? In the United States, registration is needed to sue and to claim statutory damages. In Canada, it helps prove ownership. The United Kingdom, Australia, Japan, and most European Union countries have no formal registration.
Bottom Line
- In the United States, work-for-hire ownership of contractor work is the exception, not the rule. Always pair it with a present assignment.
- Outside the United States, ownership is contract-driven: get a written assignment and moral rights waivers where allowed.
- Register early in the United States and Canada, keep meticulous records, and use takedowns or the CCB for fast relief when budgets are tight.
How GTC Helps
GTC drafts and localizes work-for-hire and assignment agreements across the United States, the European Union, the United Kingdom, Canada, Australia, and Japan, aligning your classification, contracts, and enforcement plan with each country's rules. We also run copyright registration programs, DMCA takedowns, and cross-border enforcement so the work you pay for stays usable, licensable, and defensible.
