Under federal copyright law, employers automatically own works created by employees within the scope of their employment—no written agreement required. Independent contractor work, however, belongs to the contractor unless a written agreement transfers the rights. Minnesota adds a layer of complexity with Minn. Stat. § 181.78, which limits what employers can require employees to assign, protecting inventions developed on the employee’s own time with the employee’s own resources. The result is a framework where federal copyright law, federal patent law, state statute, and contract terms all interact to determine who owns the work your business pays to create.
That is the short version. The rest of this guide explains how these rules interact, where the gaps appear, and what every Minnesota business owner should do to secure ownership of the intellectual property that drives the company’s value.
The Default Rule: Employers Own Employee Work Product
The federal Copyright Act establishes the baseline. Under 17 U.S.C. § 201(b), when an employee creates a work within the scope of employment, the employer is considered the author from the moment of creation. The employer holds all copyright rights automatically. No written agreement is needed, and no assignment is required.
This is the “work made for hire” doctrine, defined in 17 U.S.C. § 101. A work qualifies as made for hire if it is “prepared by an employee within the scope of his or her employment.”
What “Scope of Employment” Means Practically
The scope-of-employment inquiry asks whether the work was created as part of the employee’s job duties. Courts generally apply three factors drawn from the Restatement (Second) of Agency:
- The work is of the kind the employee was hired to perform
- The work was created substantially within authorized time and space limits
- The work was motivated, at least in part, by a purpose to serve the employer
A software developer who writes code at the office during business hours is creating work within the scope of employment. The same developer who writes an unrelated novel on weekends using a personal laptop is not. The line between these scenarios is not always clean—and the cases that generate disputes tend to involve employees who create work that is adjacent to, but not squarely within, their core job responsibilities.
The Employee-Versus-Contractor Threshold
Before the work-for-hire doctrine applies at all, the creator must be an “employee” rather than an independent contractor. The U.S. Supreme Court addressed this distinction in Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989) (available at Cornell LII), establishing a multi-factor test drawn from common-law agency principles. The factors include:
| Factor | Points Toward Employee | Points Toward Contractor |
|---|---|---|
| Control over how work is done | Employer directs manner and means | Worker controls methods |
| Skill required | Ordinary skill, employer trains | Specialized skill, self-directed |
| Source of tools and materials | Employer provides | Worker provides own |
| Location of work | Employer’s premises | Worker’s own location |
| Duration of relationship | Ongoing, indefinite | Project-based, finite |
| Right to assign additional projects | Employer can assign freely | Limited to contract scope |
| Method of payment | Salary or hourly | Per-project or invoice |
| Employee benefits | Provided (health, retirement) | Not provided |
| Tax treatment | Employer withholds taxes | Worker pays own taxes |
No single factor is dispositive. Courts weigh the totality of the relationship. A misclassified “contractor” who functions as an employee may still be treated as an employee for copyright purposes—which means the hiring party may own the work even without a written agreement. Conversely, a true independent contractor relationship means the work-for-hire doctrine does not apply automatically, and the hiring party needs a written agreement to acquire ownership. For a deeper analysis of classification issues, see Independent Contractor vs. Employee in Minnesota.
When the Default Fails: Contractor Work, Joint Works, and Gaps
Independent Contractors Own What They Create
When a business hires an independent contractor—a graphic designer, a freelance developer, a marketing consultant—the contractor owns the copyright in the resulting work by default. The business receives only an implied license to use the work for the purpose for which it was commissioned, not ownership of the underlying intellectual property.
This surprises many business owners. You paid for the work, you directed the project, and you may have spent months collaborating on revisions—but unless you have a written agreement transferring ownership, the contractor holds the copyright.
The Nine Categories: When Contractor Work Can Be “Work for Hire”
Federal copyright law provides a narrow exception. Under 17 U.S.C. § 101, a specially ordered or commissioned work qualifies as work for hire only if two conditions are met:
- The work falls within one of nine statutory categories: (1) a contribution to a collective work, (2) part of a motion picture or other audiovisual work, (3) a translation, (4) a supplementary work, (5) a compilation, (6) an instructional text, (7) a test, (8) answer material for a test, or (9) an atlas.
- Both parties sign a written agreement stating the work is a work made for hire.
Notice what is missing from the nine categories: standalone software, logos, website designs, marketing copy, photographs, and most of the creative work businesses commission every day. For those works, a work-for-hire agreement is legally insufficient to transfer ownership. The business must obtain a separate written assignment of copyright.
Joint Works and Shared Ownership
A third scenario arises when the hiring party and the contractor both contribute copyrightable expression with the intent to create a single, integrated work. Under 17 U.S.C. § 101, this creates a “joint work,” and each contributor becomes a co-owner of the entire copyright. Either co-owner can license the work without the other’s permission (subject to an accounting for profits), but neither can grant an exclusive license or transfer ownership without the other’s consent.
Joint authorship disputes are unpredictable and expensive. A well-drafted contractor agreement eliminates the issue entirely by assigning all rights to the hiring party upfront.
Invention Assignment Agreements and Minnesota’s Employee Protections
The Role of Invention Assignment Clauses
While copyright’s work-for-hire doctrine covers creative works, it does not address patents, trade secrets, or inventions. For those categories, employers rely on invention assignment agreements—contractual provisions in which the employee agrees to assign rights in work-related inventions to the employer.
These clauses are standard in employment agreements across technology, manufacturing, and professional services. They typically require the employee to:
- Disclose all inventions created during employment
- Assign ownership of work-related inventions to the employer
- Cooperate in filing patent applications
- Execute any documents necessary to perfect the employer’s rights
Minnesota’s Statutory Limitation: Minn. Stat. § 181.78
Minnesota is one of several states that limit how broadly an employer can draft invention assignment clauses. Minn. Stat. § 181.78 provides that 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” if the invention either:
- Does not relate directly to the employer’s business or the employer’s actual or demonstrably anticipated research or development, or
- Does not result from any work performed by the employee for the employer.
Any provision that purports to reach inventions meeting these criteria is “void and unenforceable” as against Minnesota public policy. Under subdivision 2, an employer cannot require such a void provision as a condition of employment or continued employment. And under subdivision 3, if the employment agreement requires any invention assignment, the employer must provide written notice to the employee at the time of signing, explaining these statutory limitations.
What This Means for Minnesota Employers
The statute does not prohibit invention assignment agreements. It draws a boundary. Employers can require assignment of inventions that relate to the business, that use employer resources, or that result from the employee’s work duties. Employers cannot reach inventions the employee develops independently, on personal time, with personal resources, on unrelated subjects.
In practice, compliant invention assignment clauses should:
- Track the statutory language closely, requiring assignment only for inventions within the permitted scope
- Include the required written notice (often attached as an exhibit to the employment agreement)
- Require the employee to disclose inventions so the employer can evaluate whether they fall within the assignment obligation
- Provide a mechanism for the employee to identify pre-existing inventions that are excluded from the agreement
Employers who use overbroad assignment language risk having the entire clause declared unenforceable—not just the offending provision. Hall PC regularly advises Minnesota businesses on drafting compliant invention assignment provisions that protect the company without overreaching.
Practical Steps to Secure IP Ownership
Knowing the rules is only useful if your agreements reflect them. The following framework addresses the most common ownership gaps.
Employment Agreement Provisions
Every employment agreement for a role that involves creative or inventive work should include:
| Provision | Purpose |
|---|---|
| Work-for-hire acknowledgment | Confirms that works created within scope of employment are owned by employer under federal copyright law |
| Invention assignment clause | Assigns patent and trade secret rights in work-related inventions, compliant with Minn. Stat. § 181.78 |
| Statutory notice exhibit | Satisfies the written-notice requirement under Minn. Stat. § 181.78, subd. 3 |
| Prior-inventions schedule | Allows the employee to exclude pre-existing inventions from the assignment obligation |
| Cooperation clause | Requires the employee to sign documents and assist with IP registrations |
| Confidentiality provision | Protects trade secrets and proprietary information during and after employment |
For guidance on protecting confidential information, see the Trade Secret Protection Policy Template.
Contractor Agreement Provisions
Contractor agreements require a different approach because the work-for-hire doctrine applies only within the nine statutory categories. A comprehensive contractor IP clause should include:
- Work-for-hire designation—For deliverables that fall within the nine categories, state that the work is a work made for hire under 17 U.S.C. § 101.
- Present-tense assignment—For all deliverables (including those outside the nine categories), include language such as “Contractor hereby assigns to Company all right, title, and interest in and to the Work.” Use present tense (“hereby assigns”), not future tense (“agrees to assign”), to effect an immediate transfer.
- Broad IP definition—Cover copyrights, patent rights, trade secret rights, moral rights, and any other intellectual property rights in the deliverables.
- Waiver of moral rights—Where applicable, include a waiver of any moral rights or rights of attribution the contractor may hold.
- Further-assurances clause—Require the contractor to execute additional documents necessary to perfect the company’s ownership.
- Representations—Require the contractor to represent that the work is original, does not infringe third-party rights, and has not been previously assigned or licensed.
The belt-and-suspenders approach—combining a work-for-hire designation with an assignment—ensures coverage regardless of whether the specific deliverable qualifies under the nine categories.
IP Audit Checklist
Even with strong agreements in place, ownership gaps accumulate over time. Conduct periodic IP audits to identify and resolve them:
- Review all active employment agreements—Confirm that each agreement includes a compliant invention assignment clause and statutory notice
- Review all contractor agreements—Verify that each includes both work-for-hire and assignment provisions
- Identify unassigned work—Look for older projects completed before current agreements were in place, particularly logos, website content, and software
- Record assignments with the USPTO—For patented inventions, record assignments with the United States Patent and Trademark Office to establish a public record of ownership
- Register key copyrights—Federal copyright registration is required before filing an infringement lawsuit and unlocks statutory damages
- Audit open-source usage—Confirm that any open-source components used in products comply with their license terms and do not create unintended obligations
Building IP ownership into the Legal Operating System™ for your business ensures these protections do not depend on any single person remembering to handle them. See the Legal Operating System framework for a structured approach to embedding legal protections into daily operations.
Protecting Against Reverse Engineering and Misappropriation
Ownership is only the first layer. Once you have secured IP rights, you need ongoing protections—confidentiality agreements, non-disclosure provisions, and in some cases, clauses restricting reverse engineering—to maintain the value of what you own. Minnesota employers should also consider whether copyright protections or trade secret designations provide the strongest enforcement options for specific assets.
Who owns intellectual property created by an employee?
Under federal copyright law, the employer automatically owns works created by an employee within the scope of employment. This is the work-for-hire doctrine under 17 U.S.C. § 201(b). The employer is treated as the legal author from the moment of creation, with no assignment or written agreement required.
Does an employer own intellectual property created by an independent contractor?
No. The contractor owns the IP by default. Copyright in contractor work transfers to the hiring party only if the work falls within one of nine statutory categories and a written work-for-hire agreement is signed before the work begins, or if the contractor assigns the rights in a separate written agreement.
What is Minnesota Statute 181.78?
Minnesota Statute 181.78 limits what employers can require employees to assign. An invention assignment clause cannot reach inventions the employee developed entirely on the employee’s own time, with the employee’s own resources, that do not relate to the employer’s business or result from the employee’s work for the employer. Any clause that attempts to reach those inventions is void under Minnesota law.
Can an employer require an employee to assign all inventions as a condition of employment?
Not in Minnesota. Under Minn. Stat. § 181.78, subd. 2, an employer cannot require a provision that would be void under the statute as a condition of employment or continued employment. The employer must also provide the employee with written notice of the statutory limitations at the time the agreement is signed.
What are the nine categories of work for hire for independent contractors?
Under 17 U.S.C. § 101, the nine categories are: contributions to collective works, parts of motion pictures or audiovisual works, translations, supplementary works, compilations, instructional texts, tests, answer material for tests, and atlases. Work outside these categories cannot qualify as work for hire even with a written agreement.
How should a business secure IP ownership from contractors?
Use a written agreement that includes both a work-for-hire designation (for eligible categories) and a present-tense assignment of all intellectual property rights. The agreement should cover copyrights, patent rights, trade secrets, and any other IP. Include a further-assurances clause requiring the contractor to sign additional documents to perfect the transfer if needed.
