What the Friday the 13th Copyright Case Means for Freelancers

Lock ownership and transfer mechanics before you sign#

Before you quote, scope, or sign, lock the ownership model and transfer mechanics in writing. That is one practical way to avoid the kind of rights dispute the Friday the 13th copyright case made visible, and it is usually much easier to address before signature than after delivery.

The legal fork in that case was simple even though the litigation was not. Victor Miller wrote the screenplay in 1979, the film was released in 1980, and in 2016 he served a termination notice under 17 U.S.C. § 203.

The key question was whether he wrote as an employee, which could support work-made-for-hire treatment, or as an independent contractor, which left room to terminate an earlier grant under the statute. The Second Circuit rejected the employee argument, concluded he was an independent contractor, and held that his § 203 notice was effective as to Manny and its successors. The practical takeaway is straightforward: when status, ownership language, and transfer paperwork do not line up, the dispute can surface years later.

Four terms to pin down early#

Use these terms precisely before anyone redlines price or scope:

• Work made for hire: a copyright status that applies only in two specific situations under U.S. Copyright Office guidance, and changes who is treated as author and initial owner.
• Assignment: a transfer of copyright ownership.
• License: a grant of copyright rights that can be exclusive or nonexclusive.
• Termination notice: the advance written notice used to effect termination under 17 U.S.C. § 203.

These are not academic labels. They determine day-one ownership, permitted use, and whether a past grant may later be terminated under Title 17. At signing, § 204 is the immediate control point. A transfer of copyright ownership is valid only if it is in writing and signed by the owner of the rights conveyed, outside operation of law.

If someone says rights transfer "when we pay," ask two questions: where is the signed writing, and what exact event triggers transfer? If either answer is unclear, ownership is unclear.

Section 203 creates the longer-tail risk. It applies to qualifying grants executed on or after January 1, 1978, with statutory timing rules that include a five-year window and advance notice of not less than two and not more than ten years before the effective date. You do not need to memorize every branch before each project, but you do need to understand the contract consequence. The ownership model you choose now can affect control long after the project ends.

A sharper pre-sign decision filter#

Before you sign, pressure-test the deal in this order:

• If the client wants full ownership, choose that model before pricing. If they want assignment language or work-made-for-hire language, scope and fee should reflect it. If they only need defined usage rights, a license may be the cleaner fit.
• If the draft calls you an independent contractor, make the IP section consistent with that status. The Miller dispute turned on employee versus independent contractor treatment. If your agreement labels you independent but drops in work-made-for-hire language without resolving the mismatch, stop and rewrite.
• If rights are transferring, define one trigger event. Signature, delivery, acceptance, and final payment are different events. Pick one and use it consistently across the main agreement, SOW, and any IP addendum.
• If you may need to prove intent later, preserve evidence now. Keep the final signed agreement, final SOW, IP rider, if any, redlines, approval emails, acceptance records, payment proof, and notice delivery records. Confirm you have one fully executed version and that its IP terms match what the parties performed.

A common failure point is doing the negotiation work, then keeping the wrong file. Later, the problem is not just what the parties meant, but what they can prove.

The rest of this article follows that same fork from case logic to definitions, clause drafting, cross-border choices, and evidence discipline. If you want a quick companion before your next markup, start with Work for Hire vs. Assignment of Rights: A Freelancer's Guide to Owning Your IP.

We covered this in detail in Negotiating the 'Intellectual Property' Section of an Enterprise Contract.

What happened in Horror, Inc. v. Miller and why freelancers should care#

How your role is treated under the Copyright Act can shape long-term copyright control, including whether a later termination right is available. In Horror, Inc. v. Miller, the core dispute was whether Victor Miller wrote as an employee or an independent contractor for Copyright Act purposes.

If the screenplay was a work made for hire, Manny would own it and Miller's Section 203 termination notice would not work. The Second Circuit held Miller was an independent contractor, affirmed summary judgment for him on September 30, 2021, and held his Section 203 notice was effective against Manny and its successors.

For your deal, keep these terms precise:

• Work made for hire: under Section 101, this includes work prepared by an employee within scope of employment, and certain commissioned works only when the parties expressly agree in a signed writing.
• Independent contractor status, copyright context: this analysis is governed by copyright-law agency principles under the Reid framework.
• Termination of prior grants (§ 203): applies to qualifying post-1977 author grants for works other than works made for hire.

The contract signals that help or hurt each position#

The practical lesson is simple: inconsistent drafting creates long-tail ownership risk.

What to decide before work starts#

Decide the ownership story before work starts, then make every signed document tell the same story. If you are a contractor, the IP section should match that structure. If control terms and ownership terms point in different directions, resolve that before signature.

If rights are transferring, choose one trigger and repeat it everywhere. If the client wants more control, price for that outcome instead of treating it like a narrow use-rights deal.

Then keep one enforceability file in one place: the final signed agreement set and core project records. If ownership is challenged later, what you can prove will matter more than what either side remembers.

Related: Copyright Considerations for Freelance Photographers in the Age of AI.

The terms you must define early before any negotiation#

Define ownership before you discuss price. If you quote first, you risk selling one rights package while the client expects another.

Horror, Inc. v. Miller and CCNV v. Reid point to the same operational rule: ownership outcomes follow legal status and valid transfer language, not labels alone.

Four terms to lock before price talks#

• Work made for hire

Plain meaning: this status only works through specific statutory paths. Courts first determine employee vs. independent contractor status under common-law agency principles, and commissioned works must fit statutory categories and be covered by signed writing. Under 17 U.S.C. § 201(b), the hiring party is treated as the author if this status applies. In your deal: if you are a contractor, do not assume the phrase works just because it appears in a draft.

• Assignment

Plain meaning: a transfer of copyright ownership. Under 17 U.S.C. § 204(a), the transfer is not valid unless it is in a signed writing. In your deal: ownership leaves you, so the transfer trigger and signed records need to be clear.

• License

Plain meaning: permission to use the work under defined limits. An exclusive license is treated as a transfer of ownership interests. A nonexclusive license is not. In your deal: you can grant usage rights without giving up copyright, but only if scope is clear.

• Termination notice

Plain meaning: a formal statutory notice served on the grantee or successor under Section 203. For qualifying author grants executed on or after January 1, 1978, the window generally opens at 35 years and lasts five years, and notice must be served 2 to 10 years before the effective date. The as-served notice must also be recorded with the Copyright Office. In your deal: a transfer that looks final now can still be challenged later if the work was not truly work made for hire.

Fast comparison before you quote#

Run a consistency check across every deal document#

Read the master agreement, SOW, and IP addendum as one package. If one document calls you an independent contractor but another uses control-heavy terms about how, when, or by what means the work is done, stop and fix it. Under the Reid framework, that conflict matters.

Then check the rights language across all documents. If one file points to assignment and another points to license, you do not have a minor drafting issue. You have an ownership-risk issue.

Unless your contract expressly sets document priority, do not assume the master agreement automatically controls the SOW or IP addendum. Make hierarchy explicit in the signed set.

Use a pre-quote gate#

Before you send a price, confirm all four:

If any one of these is unclear, pause and clean up the documents before you price the work.

If you want a deeper dive, read Understanding the CCNV v. Reid Supreme Court Case.

Choose your ownership position before you quote price#

Choose the ownership path first, then price to match it. If you quote before deciding between assignment, scoped license, or work made for hire, your proposal, SOW, and IP terms can drift out of sync.

That sequence is not cosmetic. In the case, the ownership outcome turned on legal status, and the Second Circuit held Victor Miller was an independent contractor, with Section 203 termination effective as to Manny and successors. Your quote should follow the rights model you can support consistently in signed documents.

Use a three-path decision rule#

Start with scoped license when the client needs permission to use the work and you need to keep copyright. A nonexclusive license is not a transfer of copyright ownership, and rights can be split by scope.

Choose assignment when the client needs ownership, not just broad usage rights. A transfer of copyright ownership must be in a signed writing, so your pricing should reflect a true transfer, and any rights you retain should be stated clearly.

Use work made for hire only when the facts and drafting support it. If it applies, the hiring or commissioning party is treated as the author and owner. For certain commissioned works, that requires an express signed written instrument.

Match the asset and client use to the rights model#

The tradeoff is usually direct: more client control means a broader rights transfer and fewer reuse options for you.

Run four pre-quote checks before you send numbers#

Before you send numbers, review the documents the way a future dispute will: side by side. First, state which document controls if the proposal, master agreement, SOW, order form, and IP addendum conflict. Next, review annexes and order forms for immediate-transfer language that may conflict with a narrower grant.

Then pick one transfer event, signature, delivery, acceptance, or final payment, and repeat it everywhere. If transfer is tied to acceptance, make sure the acceptance clause uses the same deliverable definition and approval process as the SOW. Also keep one baseline in mind: handing over files or physical copies does not, by itself, transfer copyright.

If ownership language is inconsistent across the proposal, SOW, and IP clauses, pause the quote and fix the package before work starts.

For a step-by-step walkthrough, see A Guide to the 'Safe Creative' Registry for Copyright Protection.

Contract clauses that prevent the same ownership fight later#

Once you pick the rights model, carry it through the entire contract set. The MSA, SOW, and any IP addendum should tell one ownership story with no conflicting language. In Horror, Inc. v. Miller - the Friday the 13th dispute - authorship status for Copyright Act purposes determined whether Section 203 termination was effective, so your documents need that same consistency from definitions through the operative transfer clause.

Put definitions in one controlling location, usually the MSA definitions or the IP addendum, and make each SOW incorporate them by reference. Keep them plain and consistent:

• work made for hire: the hiring party is treated as author only when statutory conditions are actually met
• assignment: a transfer of copyright ownership
• license: permission to use the work, and a nonexclusive license is not a transfer of ownership
• rights-transfer trigger: the specific event your contract uses for the operative clause, though ownership transfer still requires a signed writing

Use this sync check before signature: the same defined terms, the same trigger, and the same ownership sentence in every signed document.

Treat Indemnification and Limitation of Liability as core ownership-risk terms, not boilerplate. Escalate negotiation when infringement indemnity is drafted to cover client-side modifications, third-party combinations, or client-provided materials you did not create.

Pause signature if liability terms are so broad that enforceability is uncertain or if they conflict with your ownership structure. If you need deeper clause wording examples, see The Ironclad International Freelance Contract: 10 Clauses You Cannot Ignore.

Use a notice checklist inside the contract file, especially for ownership-transfer and Section 203 notices:

• named recipient and role
• permitted delivery method
• what counts as receipt
• timing standard for when notice is effective
• proof to retain, for example, delivery confirmation, email transmission record, or signed acknowledgment
• whether a copy of an as-served termination notice must be recorded when applicable
• where executed agreements, redlines, and notices are stored
• a placeholder to verify jurisdiction-specific formality requirements before execution

If you plan to record a transfer, align the process early because recordation timing can affect priority when competing transfers exist. You might also find this useful: What is the 'Berne Convention' for International Copyright?.

Before you send a draft, run your terms through a structured template so ownership, assignment, and license language stays consistent across documents: Freelance Contract Generator.

Governing Law Jurisdiction and Dispute Resolution in cross-border client work#

In cross-border work, these clauses are not just labels. Treat them as a verification step before kickoff, and make sure the contract set is internally consistent.

Governing Law, Jurisdiction, and Dispute Resolution are core contract-control terms in this section, but the materials here do not provide formal definitions or jurisdiction-specific drafting rules for them. What they do support is the risk context: the cited report reviews domestic and foreign legal developments, notes that courts are still resolving disputes in this area, and indicates policy guidance could change over time. It also does not predict future fact patterns.

Pause and resolve gaps if you see:

• key terms used without clear definitions in your contract set
• conflicting law, forum, or process language across versions
• reliance on public materials without official-domain cues (for federal sources, .gov) and secure https

Before kickoff, keep a clear record of final signed documents and approvals. When you rely on public legal materials during review, confirm source authenticity signals first, including the official domain and secure https.

Related reading: A deep dive into the 'choice of law' and 'jurisdiction' clauses for international freelance contracts.

Build a deal evidence pack before work starts#

Before kickoff, create one fully executed control file you can rely on if documents conflict. Control file is not a statutory term. It is simply your label for the single signed contract bundle that governs the deal.

Use these terms deliberately in that signed set:

• Entire agreement (integration) clause: says the written contract is the complete and final agreement, which helps block conflicting prior proposals or side promises. Put this in the main signed agreement.
• Order of precedence: sets the document hierarchy when terms conflict across the MSA, SOW, and IP addendum. Put this in the main signed agreement, or in a clearly governing amendment for the full signed set.

This matters because ownership disputes often turn on what the executed papers actually say. In the Friday the 13th dispute, the agreement was silent on screenplay authorship, and the work-for-hire question controlled ownership and whether termination could succeed. Copyright transfer validity also depends on writing and signature.

Stop and pause work if any of these are true:

• signature blocks are incomplete
• appendix labels do not match
• key IP terms differ across the MSA and SOW
• final redlines are missing and you expect to rely on drafting history

Go only when the executed bundle is complete, internally consistent, and archived as one control file.

Keep drafts and emails as support, not as the control file. For ownership-structure detail behind these choices, see Work for Hire vs. Assignment of Rights: A Freelancer's Guide to Owning Your IP. For a related workflow, see The Best Software for Creating Case Studies.

Red flags that predict expensive disputes#

Use your control file to catch contradictions before you sign. In the Friday the 13th dispute, the expensive fight was not about one label in isolation. It was about how classification, ownership language, and transfer mechanics worked together over time.

Spot the clause conflicts early#

Start with classification. In Miller's appeal, the court treated him as an independent contractor for copyright purposes, applied the Reid control test, and said copyright law, not labor law, controls the work-for-hire analysis. For your contract, watch for this red flag: you are labeled independent contractor, but the client controls your methods, hours, tools, or step-by-step process. Approval of deliverables is normal. Control over how you create them is the conflict to fix.

Next, test rights scope. Your clause should clearly state whether rights are assignment or license, exclusive or nonexclusive, and whether derivative use or sublicensing is allowed, plus any purpose, term, or territory limits. If the client asks for broad, lasting rights while the fee and scope still read like a narrow services deal, pause and renegotiate before signature.

Then confirm the transfer trigger. State exactly when rights move: signature, delivery, acceptance, or final payment. Under 17 U.S.C. § 204, transfer validity depends on signed writing, and Section 203 termination mechanics can matter years later. Miller wrote in 1979, served termination notice in 2016, and the court treated that notice as effective as to Manny and its successors. That is why vague transfer language remains risky.

Finally, check document hierarchy. You need one order of precedence across the MSA, SOW, IP addendum, and PO. If forum or ownership terms drift into conflicting PO fine print, costs rise because you may end up fighting first about where and how the dispute is heard.

Where you should pause and renegotiate#

Pause the deal immediately in these situations:

1. Rights language is broad, but scope or transfer timing is unclear.
2. PO terms quietly change forum or dispute mechanics.
3. Transfer is immediate, but payment or acceptance terms are unclear.

If multiple transfer documents exist, verify execution timing and recordation strategy, because priority between conflicting transfers can turn on timing and recordation rules under 17 U.S.C. § 205.

Draft risk allocation like you expect to enforce it#

Treat Indemnification and Limitation of Liability as operational terms, not placeholders. Before signature, confirm the clause text states:

Do not leave these points implied.

Pre-sign go or no-go#

Go only if all checks pass:

• classification language matches actual control rights
• forum, governing-law, and dispute terms are aligned across the signed set, and the PO is subordinate
• rights scope is explicit and commercially aligned
• transfer timing is clear and supported by signed writing that satisfies § 204
• indemnity, defense duty, liability cap, carve-outs, and fee-shifting intent are explicit, not implied

Conclusion#

Do not draft or sign on assumptions about ownership. The Friday the 13th copyright dispute shows that outcomes can turn on relationship facts, exact contract text, and whether your records still support those facts years later.

Use the case as a process warning, not a headline rule. In Horror, Inc. v. Miller, the Second Circuit held on September 30, 2021 that Victor Miller was an independent contractor for copyright purposes and that his Section 203 termination notice was effective as to Manny and its successors.

For any procedural point after that appellate decision, verify the current case status before you rely on it.

Before you sign, run this sequence:

1. Align classification with reality. Make sure your status language matches how the work relationship actually operates.
2. Choose the ownership model deliberately. State whether the deal is a license, an assignment, or work-for-hire language, and keep the documents consistent with that choice.
3. Set the transfer trigger in signed writing. Under 17 U.S.C. § 204, transfer language must be in a signed writing. Define exactly when rights move.
4. Define notice mechanics early. If termination could matter, account for Section 203 timing, including the 35-year point, the 5-year window, and notice served 2 to 10 years before the effective date.
5. Lock document hierarchy. Keep the MSA, SOW, addenda, and related approvals synchronized, with a clear order of precedence.

Use a strict internal go/no-go gate: pause signing when core IP terms conflict across the MSA, SOW, and addenda, or when your evidence file is incomplete. Keep the executed agreement, IP exhibits, final redlines, approvals, delivery and acceptance records, payment proof, and any notice-service proof together.

Do not draft from headlines or recycled snippets. Default to explicit definitions, synchronized clauses, and retained proof trails. If recordation issues may arise, remember that recordation can affect priority and constructive notice, and consult a knowledgeable attorney when legal interpretation is uncertain.

If you want jurisdiction-specific interpretation or a pre-signature enforceability check, contact Gruv.

Need the full breakdown? Read Battle of the Forms Under the UCC for Freelancers. If you want to apply this checklist faster on future deals, keep a practical toolkit handy: Explore all tools.