Work-for-Hire and IP Assignment for MN Businesses

Who owns the work your employees and contractors create?

Copyright vests initially in the human author of a work. Federal law states that “[c]opyright in a work protected under this title vests initially in the author or authors of the work” (17 U.S.C. § 201(a)). The author is the person who created it, not the person who paid for it. That single rule explains most ownership disputes I see in software and creative businesses.

There is one large exception, and it is the reason the employee-versus-contractor distinction matters so much. When a work is a work made for hire, federal law treats “the employer or other person for whom the work was prepared” as the author, who “owns all of the rights comprised in the copyright” (17 U.S.C. § 201(b)). For an employee creating work inside the scope of the job, ownership lands with the company automatically. No transfer is needed because the company was the author from the start. For a contractor, that automatic result usually does not apply, which is why a contractor’s work needs an extra step that an employee’s work does not. The baseline rules on intellectual property ownership and the mechanics of how copyright ownership works sit underneath everything that follows.

What does “work made for hire” actually mean under the Copyright Act?

“Work made for hire” is a defined term, and it covers exactly two things. The first is “a work prepared by an employee within the scope of his or her employment” (17 U.S.C. § 101). That is the employee path, and it operates without a contract clause. The second is a work “specially ordered or commissioned” that falls into one of nine specific categories, “if the parties expressly agree in a written instrument signed by them that the work shall be considered a work made for hire” (17 U.S.C. § 101).

The nine categories in the commissioned-work path are narrow and listed by name: a contribution to a collective work, a part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, and an atlas. A commissioned work qualifies as a work made for hire only if it both fits one of those nine categories and is covered by a signed writing using the work-for-hire language. Miss either requirement and the doctrine does not apply. In my practice, the gap that catches business owners is the category list: they assume any paid deliverable can be a work for hire, when the statute allows it only for those nine work types.

Why isn’t a “work for hire” label enough for your contractor’s code?

A “work for hire” label fails for most contractor work because the deliverable is not on the statutory list. Custom software, source code, general graphic design, websites, and most marketing materials are not a contribution to a collective work, a translation, an instructional text, or any of the other nine commissioned-work categories. When the work does not fit a category, calling it a work made for hire in the contract is legally empty, the doctrine does not apply, and the contractor keeps the copyright.

Two things make this worse than a simple drafting miss. First, federal courts decide who counts as an employee for work-for-hire purposes using common-law agency factors, looking at the degree of control, the source of tools, the skill required, and similar considerations, not by who paid for the work. A worker your accountant treats as a contractor will almost always be a contractor for copyright purposes too, so the employee path is closed. Second, a “work for hire” clause that does not work often does nothing else either, because it is not also written as an assignment. The result is a company that paid full price for software it does not own. This is the most common version of the problem in work your contractor created with no written agreement, and a bare work-for-hire label is only marginally better than no agreement at all.

What makes a present-tense IP assignment the clause that actually works?

Because the work-for-hire label fails for most contractor output, the clause that actually transfers ownership is an assignment. Federal law allows it: ownership of a copyright “may be transferred in whole or in part by any means of conveyance” (17 U.S.C. § 201(d)). But the transfer has a strict form requirement. A transfer of copyright ownership “is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed” (17 U.S.C. § 204(a)).

Two things follow from that rule. The transfer must be in a writing, and the writing must be signed by the contractor, the party who owns the rights being conveyed. A verbal promise does not satisfy it. An unsigned statement of work does not satisfy it. A “work for hire” recital, even in a signed contract, does not by itself operate as an assignment, because it asserts a doctrine rather than conveying the copyright. The fix is a clean assignment clause in a contract the contractor signs, drafted so the copyright in the deliverables transfers to your company. The same discipline applies whether you are hiring an outside developer or a consultant who needs an IP assignment clause in a services agreement.

What three clauses belong alongside the assignment: moral-rights waiver, further assurances, and present-tense language?

A working IP-transfer provision has three moving parts beyond the word “assign.” Each one closes a gap that a bare assignment leaves open.

1. Present-tense assignment language. The clause should say the contractor “hereby assigns” the copyright, not that the contractor “agrees to assign” it later. Present-tense language transfers ownership on signing. A promise to assign in the future is only a promise, and if the contractor never signs the follow-up paperwork, you may hold a contract claim rather than the copyright itself. Drafting it in the present tense makes the assignment self-executing.
2. Waiver of moral rights. Moral rights are the creator’s personal rights to be credited as the author and to object to changes that harm their reputation. They are separate from the copyright and do not automatically transfer with it. A waiver of moral rights, to the extent the law allows, lets your company edit, rebrand, and reuse the work without the creator later objecting.
3. Further-assurances clause. This obligates the creator to sign confirmatory documents after the engagement ends, including the paperwork the U.S. Copyright Office needs to record the transfer or register the work in your company’s name. It is the clause you rely on years later when you need a clean signature and the contractor has moved on.

Together these three turn an assignment from a label into an instrument. They also matter for later builds: if you expect updates and new versions, the agreement should make clear it covers later versions and derivative builds, not just the first deliverable. A well-built copyright transfer agreement contains all of these parts.

How does Minnesota worker classification change who owns the work?

Worker classification matters here because employee status is the input that flips the federal ownership default, and Minnesota decides that status under its own law. Minnesota’s general misclassification statute provides that “the nature of an employment relationship is determined using the same tests and in the same manner as employee status is determined under the applicable workers’ compensation and unemployment insurance program laws and rules” (Minn. Stat. § 181.722, subd. 3). The unemployment insurance law, in turn, defines “employment” as service performed by “an individual who is an employee under the common law of employer-employee and not an independent contractor” (Minn. Stat. § 268.035, subd. 15). So Minnesota applies a common-law control test, and the same test the state uses for unemployment and workers’ compensation also governs whether you have misclassified a worker.

The interaction is the part business owners miss, and in my experience it surfaces at the worst time: a reclassification finding usually arrives during an unemployment claim, a workers’ compensation audit, or a tax review, long after the work was delivered and the assignment was signed. If the IRS or the Minnesota Department of Labor and Industry reviews the relationship and concludes your “contractor” is actually an employee, the relationship is treated as employment. The work-for-hire employee path may now apply, which can help your ownership position, but the contractor-style assignment paperwork you signed may not match the relationship the state recognizes. Minnesota also prohibits requiring a worker who is actually an employee to “enter into any agreement or complete any document that misclassifies, misrepresents, or treats the individual as an independent contractor” (Minn. Stat. § 181.722, subd. 1). A construction business has an even stricter rule: under Minnesota’s construction misclassification statute, a worker who performs building construction or improvement services in the course of your business “is an employee” unless a detailed multi-factor test is met (Minn. Stat. § 181.723, subd. 3). The practical lesson: classify correctly first, then draft the IP terms to fit the real relationship. When the paperwork and the relationship diverge, a court may instead find an implied license rather than full ownership.

How far can a Minnesota invention-assignment clause reach?

A Minnesota employer can require an invention-assignment clause, but Minnesota law caps how far it reaches. Under Minn. Stat. § 181.78, an invention-assignment provision “shall not apply to an invention for which no equipment, supplies, facility or trade secret information of the employer was used and which was developed entirely on the employee’s own time,” and which either does not relate to the employer’s business or anticipated research and development, or does not result from the employee’s work for the employer (Minn. Stat. § 181.78, subd. 1). A clause that purports to reach such an invention “is to that extent against the public policy of this state and is to that extent void and unenforceable.”

Two points for employers. First, the limit is narrow: it protects only the genuinely personal invention, made on the employee’s own time, with none of the employer’s equipment, supplies, facilities, or trade-secret information, and disconnected from the employer’s business and the employee’s job. An invention built on company time or with company resources, or that relates to the company’s work, is still assignable. Second, Minnesota imposes a notice obligation: an employer that uses an invention-assignment provision must give the employee written notice that the clause does not apply to inventions meeting the section’s criteria. A well-drafted employee agreement carves out the personal-invention category in its own language and includes that notice, so the clause stays enforceable for everything it can legitimately cover.

What protects your work product if the assignment paperwork has a gap?

When an assignment is missing or defective, two backstops do real work. The first is trade secret law. Source code, build processes, and proprietary methods you have kept confidential can qualify as trade secrets under the Minnesota Uniform Trade Secrets Act (“MUTSA”), which defines a trade secret as information that “derives independent economic value . . . from not being generally known” and “is the subject of efforts that are reasonable under the circumstances to maintain its secrecy” (Minn. Stat. § 325C.01, subd. 5). MUTSA lets a court issue an injunction: “[a]ctual or threatened misappropriation may be enjoined” (Minn. Stat. § 325C.02). The federal Defend Trade Secrets Act (“DTSA”) adds a parallel federal cause of action when the trade secret is “related to a product or service used in, or intended for use in, interstate or foreign commerce” (18 U.S.C. § 1836). So a departing developer who keeps proprietary code can be stopped under state or federal law, even if your assignment paperwork is imperfect, as long as you treated the material as a secret.

The trade secret backstop has a condition: it works only if you actually kept the material secret. The MUTSA definition requires reasonable secrecy efforts, so access controls, confidentiality agreements, and limited distribution are what make the protection available. The second backstop is copyright enforcement against copied output, where a registration plus a DMCA takedown notice gives you a fast route to remove infringing material. Neither backstop is a substitute for a clean assignment, but together they cover gaps while you fix the paperwork.

When should you register the copyright, and how does registration timing affect enforcement?

Registration is not required to own a copyright, but it is required to enforce one in court. Federal law states that “no civil action for infringement of the copyright in any United States work shall be instituted until preregistration or registration of the copyright claim has been made” (17 U.S.C. § 411(a)). A company can own valuable software for years without registering it, and that is fine until the day someone copies it. At that point, an unregistered owner has to register before filing suit, which adds delay at the worst possible moment.

Timing also affects the remedies available. Registering a work before an infringement begins, rather than after a dispute surfaces, is what preserves the strongest enforcement options, including statutory damages and the possibility of recovering attorney fees. An owner who registers only after the problem appears keeps the right to sue but loses the leverage those enhanced remedies provide. For a business whose core asset is code or creative work, the practical move is to register key works on a regular schedule, the same way you would renew a license or file an annual report. That is the argument for why registering a copyright matters before there is ever a dispute to litigate.

The bottom line for Minnesota business owners

Owning the work your business pays for is a chain of three decisions, and a break anywhere costs you the asset. Classify your workers correctly, because employee status changes the ownership default and Minnesota decides that status under its own law. Use a present-tense IP assignment, with a moral-rights waiver and a further-assurances clause, because a “work for hire” label fails for most contractor deliverables. Register the copyrights in your important works early, because registration is the gate to enforcement. Trade secret protection backstops the gaps, but only if you have kept the material secret. To see how these rules apply across the rest of your intellectual property, our Minnesota copyright practice covers the related questions. If you are putting new contractor or employee agreements in place, or you have discovered that an old agreement may not have transferred what you assumed, contact the firm to start an intake and conflict check before sending confidential documents. Email [email protected] with a brief description of the situation, and we can arrange a practical read on where your ownership stands.