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)), and the definition of a work made for hire in 17 U.S.C. § 101 begins with “a work prepared by an employee within the scope of his or her employment.” 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.

Patents follow the same starting point. The Supreme Court has explained that “[s]ince 1790, the patent law has operated on the premise that rights in an invention belong to the inventor” (Board of Trustees of the Leland Stanford Junior University v. Roche Molecular Systems, Inc., 563 U.S. 776 (2011)). The work-made-for-hire doctrine is a copyright rule, so it never moves an invention to you. An employee’s or contractor’s patentable invention stays with the inventor until a written assignment transfers it, a point covered in the invention sections below.

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.

What does “scope of employment” mean when an employee creates work on the side?

The employee path covers only work made “within the scope of his or her employment,” and the Supreme Court has said that phrase is “a widely used term of art in agency law,” pointing to section 228 of the Restatement (Second) of Agency (Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989)). Applying that section to software an employee wrote, the Fourth Circuit quoted its three-part test: conduct is within the scope of employment “only if: (a) it is of the kind he is employed to perform; (b) it occurs substantially within the authorized time and space limits; [and] (c) it is actuated, at least in part, by a purpose to serve the master” (Avtec Systems, Inc. v. Peiffer, 21 F.3d 568 (4th Cir. 1994)).

In practice, the three questions are what you hired the person to do, when and where they did it, and whom they were trying to serve. A developer who writes code for your product at the office is inside the scope. The same developer writing an unrelated novel on weekends on a personal laptop is outside it, and owns the novel. The hard cases are the adjacent ones: an employee who builds a tool related to the job at home at night. The Avtec court observed that once the work is the kind the employee was hired to do, “courts have tended not to grant employees authorship rights solely on the basis that the work was done at home on off-hours.” So if you are an employee protecting IP created while moonlighting, keep the side project away from your employer’s subject matter, equipment, and time, and read your employment agreement’s assignment clause, which can reach further than the default rule. If you are the employer, a written agreement settles the edge cases that the three-part test leaves open.

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, not by who paid for the work. In Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989), the Supreme Court listed factors including the hiring party’s right to control the manner and means of the work, the skill required, the source of the tools, the location of the work, the duration of the relationship, the method of payment, the provision of employee benefits, and the tax treatment of the hired party, and held that “[n]o one of these factors is determinative.” 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 independent contractor intellectual property problem, and a bare work-for-hire label is only marginally better than no agreement at all.

Who owns intellectual property created by independent contractors with no written agreement?

The contractor does. With no signed writing, the work-for-hire path is closed (it requires a signed instrument) and no assignment exists, so the contractor keeps the copyright under section 201(a) and keeps any patent rights as the inventor. Your business is left with whatever permission to use the work the circumstances imply. That is usually enough to keep using the deliverable for the purpose you paid for, but not enough to stop the contractor from reusing or licensing the same work, and not enough to let you hire someone else to rebuild it freely. When the paperwork is missing, a court may find an implied license rather than full ownership.

Contractors are not entitled to royalties by default either. Nothing in the Copyright Act gives a creator an ongoing payment on work they were paid to make; ongoing compensation comes from a contract that provides for it. The difference is leverage. A contractor who never assigned the copyright still holds the exclusive rights and can charge you for uses the original arrangement did not cover. Fix a missing agreement by asking the contractor to sign a confirmatory assignment now, ideally while the relationship is still friendly and in exchange for a modest payment that serves as consideration.

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 writing requirement also reaches exclusive licenses: 17 U.S.C. § 101 defines a “transfer of copyright ownership” as “an assignment, mortgage, exclusive license, or any other conveyance, alienation, or hypothecation of a copyright or of any of the exclusive rights comprised in a copyright, whether or not it is limited in time or place of effect, but not including a nonexclusive license.” So an exclusive license you take from a contractor needs the same signed writing as an assignment. 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 under a services agreement.

What belongs in an IP assignment clause for contractors and consultants?

A working IP-transfer provision has several 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. A definition of the assigned IP. Name what transfers: copyrights, inventions and patent rights, designs, software and documentation, methodologies, and trade secret rights in the deliverables. A clause that assigns only “the work” invites an argument about what the work was.
3. A defined scope. The assignment should cover every deliverable and all intellectual property the consultant creates in performing the engagement, including work created after signing, and it should state any exclusions expressly. It should also say the rights transfer worldwide and for their full duration, so no one later argues that a territorial or time limit was implied.
4. 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.
5. Originality and non-infringement representations. The contractor should represent that the work is original, does not infringe anyone else’s rights, and has not been assigned or licensed to anyone else. Pair the representation with an indemnity so a third-party claim lands on the party who created the problem.
6. 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.
7. Timely disclosure and delivery of development records. The consultant should promptly disclose in writing each invention, design, and piece of work product as it is created, not only at the end of the engagement. The clause should set the deadline (for example, within a set number of days after creation), the format, and the person who receives each disclosure. It should also require the consultant to hand over the development records behind the work, such as source code, invention notes, drafts, design files, and related correspondence, during the engagement on request and in full when it ends. You cannot register, file for, or defend rights in work you do not know exists, and these records are often the evidence of who created what and when.
8. Cooperation in enforcement. Signing documents is not the only help you may need. A cooperation clause obligates the consultant to provide technical information and records about the work, help identify infringement, and assist your counsel in a dispute, including giving testimony, at your expense for their time.

Together these turn an assignment from a label into an instrument. The belt-and-suspenders version also includes a work-for-hire designation, under the 17 U.S.C. § 101 definition, for any deliverable that fits one of the nine categories, with the assignment as the backstop for everything else. 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 should consultants protect pre-existing and background IP?

If you are the consultant, intellectual property protection starts with what you bring to the engagement. Most consultants reuse their own code libraries, templates, frameworks, and methods from client to client. A broad assignment of “all intellectual property used in or delivered with the work” can hand that toolkit to one client. The agreement should separate background IP (what you owned before the engagement or develop outside it) from the new work product.

The standard structure has three parts. List your background IP in an exhibit. Exclude it expressly from the assignment. Then grant the client a license to use the background IP as part of the deliverables, so the client gets everything it needs to run what it paid for without owning your toolkit. Decide in the drafting whether that license is perpetual, transferable with the business, and limited to the deliverables. If you are the client, the same exhibit protects you: it tells you exactly what you will not own, and the license makes sure that gap never stops you from using the work.

What confidentiality and data-security terms belong in a consultant agreement?

An assignment moves ownership, but a consultant also sees information you never intend to transfer: source code, customer lists, pricing, and product plans. A confidentiality clause protects that information, and it is also part of the “reasonable efforts” to keep a secret that Minnesota trade secret law requires (discussed below). I suggest the clause cover four points:

• A definition of confidential information. Name the categories (technical data, code, business and customer information, and the deliverables themselves), state that the definition covers information in any form, oral, written, or electronic, and list the usual exclusions, such as information that is already public or that the consultant already knew.
• Permitted use. The consultant may use the information only to perform the engagement, not for its own benefit or a third party’s, and may share it only with its own personnel who need it and who are bound by the same terms.
• Duration. Set a fixed period after the engagement ends for ordinary business information, and keep the duty running for trade secrets for as long as they remain secret.
• Return or destruction. At the end of the engagement, the consultant returns or destroys your materials and confirms in writing that it has done so.

Minnesota’s 2023 noncompete ban leaves these clauses intact, because Minn. Stat. § 181.988 excludes nondisclosure agreements and agreements protecting trade secrets from its definition of a covenant not to compete.

When the consultant will handle sensitive data, add data-security terms to the confidentiality clause. The agreement should require security measures suited to the data, such as encryption in storage and in transit and access limited to the people working on the engagement. It should require the consultant to report any breach or unauthorized disclosure to you promptly, within a set number of days. And it should state that the security duties last as long as the consultant holds the data, not only for the term of the engagement. Minnesota law already imposes part of this duty for personal information: a business “that maintains data that includes personal information that the person or business does not own shall notify the owner or licensee of the information of any breach of the security of the data immediately following discovery” (Minn. Stat. § 325E.61, subd. 1(b)). A contract term extends that reporting duty to your business data and to suspected incidents, not only the personal information the statute defines.

How should compensation for an IP assignment be structured?

The parties choose the payment model; copyright law does not set one. A lump-sum fee works when the deliverable’s value is predictable and the client wants clean ownership. A royalty or revenue share fits when the work’s value is uncertain and the creator is willing to share the risk. A hybrid (a smaller fee plus a royalty) splits the difference. Whatever the model, the agreement should say plainly that the stated payment is the full consideration for the assignment, when it is due, and whether any part of it depends on future sales. A creator who expects ongoing payment needs that term in writing, because no royalty arises by default.

One federal rule affects long-term value on both sides. For any work other than a work made for hire, an author who grants a transfer or license on or after January 1, 1978 can terminate it during a five-year window that generally begins thirty-five years after the grant was signed; for a grant that “covers the right of publication of the work,” such as a book deal, the window begins “at the end of thirty-five years from the date of publication of the work under the grant or at the end of forty years from the date of execution of the grant, whichever term ends earlier” (17 U.S.C. § 203(a)(3)). The author must serve advance written notice, and “[t]ermination of the grant may be effected notwithstanding any agreement to the contrary” (17 U.S.C. § 203(a)). An assigned work can therefore revert decades later, while a qualifying work made for hire cannot. For most business software that horizon is academic, but for a logo, a book, or a long-lived creative asset it is one more reason to use the work-for-hire designation where the category fits.

What happens when your team and a contractor create a work together?

Joint authorship is the third ownership outcome, and it is the one businesses rarely plan for. A “joint work” is “a work prepared by two or more authors with the intention that their contributions be merged into inseparable or interdependent parts of a unitary whole” (17 U.S.C. § 101), and “[t]he authors of a joint work are coowners of copyright in the work” (17 U.S.C. § 201(a)). If your employees and an outside contractor both contribute copyrightable expression to one integrated product without an agreement, the contractor may end up a co-owner of the whole thing.

Co-ownership is messy. Each co-owner can use the work, and the Ninth Circuit has applied the rule that “[a] co-owner of a copyright must account to other co-owners for any profits he earns from licensing or use of the copyright” (Corbello v. Valli, 777 F.3d 1058 (9th Cir. 2015)). Whether one co-owner can grant an exclusive license or transfer without the other’s consent is not settled the same way everywhere; even the Corbello panel divided on how its earlier precedent applied. You do not want your product’s ownership to turn on that question. A contractor agreement that assigns all rights in the contractor’s contribution to your company up front eliminates the co-ownership problem before it starts.

Who owns AI-generated work, and how should the contract handle it?

Copyright protects human authorship. In Thaler v. Perlmutter, the D.C. Circuit held that “the best reading of the Copyright Act is that human authorship is required for registration,” and it added that this rule “does not prohibit copyrighting work that was made by or with the assistance of artificial intelligence,” because it “requires only that the author of that work be a human being” (Thaler v. Perlmutter, No. 23-5233 (D.C. Cir. Mar. 18, 2025)). The practical result: material a contractor generates with an AI tool may carry little or no copyright for anyone to assign, while the human-authored parts (selection, arrangement, editing, and original code or text) can be owned and assigned in the usual way.

An AI-era IP contract should address this directly. Require the contractor to disclose which deliverables used AI tools and how. Where ownership matters most (core code, brand assets, content you will license), require human authorship or meaningful human modification. Assign whatever rights the contractor holds in prompts, outputs, and the human contributions, and have the contractor represent that its use of the tools complies with the tool’s terms and does not infringe. Where copyright may be thin, confidentiality and trade secret protection carry more of the load, which makes the confidentiality terms above and the trade-secret backstop below more important.

What changes when the contractor is overseas or a foreign entity?

International treaties set floors, not a single ownership rule. Under the Berne Convention, authors enjoy in other member countries “the rights which their respective laws do now or may hereafter grant to their nationals, as well as the rights specially granted by this Convention” (Berne Convention, art. 5(1)), and the TRIPS Agreement requires WTO members to “comply with Articles 1 through 21 of the Berne Convention (1971)” (TRIPS Agreement, art. 9(1)). Neither tells you who owns a work a foreign contractor creates for your company.

U.S. courts answer the ownership question by choice of law. In Itar-Tass Russian News Agency v. Russian Kurier, Inc., 153 F.3d 82 (2d Cir. 1998), a case involving Russian works, the Second Circuit applied the rule that the parties’ interests in property “are determined by the law of the state with ’the most significant relationship’ to the property and the parties,” and concluded that Russian law determined ownership while U.S. law governed infringement in this country. So when your developer is a company abroad, the country where the work was made may decide who owns it, and that country’s rules on employee works, assignment formalities, and moral rights may differ from ours. Berne also protects moral rights “[i]ndependently of the author’s economic rights, and even after the transfer of the said rights” (Berne Convention, art. 6bis(1)), which is why a moral-rights waiver may not be fully effective everywhere.

For a cross-border engagement, I suggest four steps: a present-tense assignment that also satisfies the formalities of the contractor’s country, a choice-of-law and forum clause, confirmation that the foreign company itself owns what its own employees and subcontractors created (ask for their assignments), and a moral-rights waiver or consent drafted to the extent local law allows.

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. For copyright purposes, the Supreme Court decides that status under federal law: it has “relied on the general common law of agency, rather than on the law of any particular State, to give meaning to these terms” (Community for Creative Non-Violence v. Reid, 490 U.S. 730, 740 (1989)). Minnesota runs a separate test for its own employment laws. 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 for those state and tax purposes. That finding does not settle copyright ownership, because a court re-weighs the same facts under the federal Reid factors, but the facts behind a reclassification (your control over the manner and means of the work) usually point the same way in both tests. Meanwhile, 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.

Why do employee inventions need an invention-assignment clause?

The work-made-for-hire doctrine is part of the Copyright Act. It gives you your employee’s in-scope code, documents, and designs, but it does nothing for patentable inventions, which begin with the inventor. Federal patent law provides that “[a]pplications for patent, patents, or any interest therein, shall be assignable in law by an instrument in writing” (35 U.S.C. § 261). An invention-assignment clause is that instrument for your workforce.

A useful clause does four things. It requires the employee to disclose inventions made during employment, so you can decide which fall within the clause. It assigns the employee’s rights in covered inventions to the company, in present-tense language. It obligates the employee to cooperate in preparing and prosecuting patent applications. And it obligates the employee to sign any documents needed to perfect and record the company’s rights, during and after employment. Minnesota then limits how far that clause can reach.

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.” The statute also bars an employer from requiring a provision made void by subdivision 1 “as a condition of employment or continuing employment” (subd. 2).

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 either unrelated to the employer’s business and its research or development, or not the result of any work the employee did for the employer. An invention built on company time or with company resources is still assignable, and so is one that both relates to the company’s business and grows out of the employee’s work for it. Second, Minnesota imposes a notice obligation: an employer that uses an invention-assignment provision must give the employee written notice, at the time the agreement is made, that the clause does not apply to inventions meeting the section’s criteria (subd. 3). 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 should a Minnesota employee IP agreement include?

For any employee whose job involves creating software, content, designs, or inventions, the employment agreement should include these provisions:

Provision	What it does
Work-for-hire acknowledgment	Confirms that copyrightable work created within the scope of employment belongs to the company
Invention assignment	Assigns the employee’s rights in covered inventions, drafted within the limits of Minn. Stat. § 181.78
Statutory notice exhibit	Gives the written notice that Minn. Stat. § 181.78, subd. 3 requires, at signing
Prior-inventions schedule	Lets the employee list inventions made before employment, which stay outside the assignment
Cooperation clause	Requires the employee to sign documents and help with patent and copyright filings, including after departure
Confidentiality provision	Protects trade secrets and proprietary information during and after employment

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.

How do you protect against reverse engineering and misappropriation?

Owning the IP is the first layer; keeping its value takes ongoing protection. Trade secret law stops misappropriation, but it does not stop reverse engineering. The federal Defend Trade Secrets Act states that “improper means” “does not include reverse engineering, independent derivation, or any other lawful means of acquisition” (18 U.S.C. § 1839(6)(B)). Minnesota’s list of improper means names “theft, bribery, misrepresentation, breach or inducement of a breach of a duty to maintain secrecy, or espionage through electronic or other means” (Minn. Stat. § 325C.01, subd. 2), and reverse engineering is not on it. So a competitor who lawfully buys your product and takes it apart has not misappropriated anything by trade secret law alone.

A contract closes that gap for anyone who signs it. When you give a customer, licensee, contractor, or prospective partner access to software, a prototype, or technical documents, the license or nondisclosure agreement should state that the recipient will not reverse engineer, decompile, disassemble, or attempt to derive the source code or design of what you provided, except as the agreement allows. Breaking that promise is a breach of contract you can sue on, even where trade secret law would not reach the conduct. For each asset, also weigh which protection fits best: copyright for code and content you will publish or distribute, trade secret status for formulas, processes, and source code you can keep out of sight.

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 generally loses those enhanced remedies. The main exception is a published work registered “within three months after the first publication of the work,” which keeps them for copying that began in that window (17 U.S.C. § 412). The statute also has narrower exceptions, including one for a work preregistered before the copying began and then registered on time. 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.

An IP audit checklist for Minnesota businesses

Ownership gaps accumulate quietly, usually from work done before your current agreements existed. A periodic audit finds them while the people who can fix them are still reachable:

• Review employee agreements. Confirm each creative or technical employee signed an agreement with a compliant invention assignment and the Minn. Stat. § 181.78 notice.
• Review contractor and consultant agreements. Confirm each has a present-tense assignment, not only a work-for-hire label, and a background-IP exhibit where the consultant reused their own tools.
• Find unassigned older work. Logos, website content, and software built before your current templates are the usual gaps; get confirmatory assignments signed.
• Record patent assignments. An unrecorded patent assignment “shall be void as against any subsequent purchaser or mortgagee for a valuable consideration, without notice, unless it is recorded in the Patent and Trademark Office within three months from its date or prior to the date of such subsequent purchase or mortgage” (35 U.S.C. § 261).
• Register key copyrights. Registration is the gate to an infringement suit for U.S. works under section 411(a).
• Audit open-source use. Confirm the open-source components in your products are used within their license terms, since some licenses impose obligations on software you distribute.

The bottom line for Minnesota business owners

Owning the work your business pays for is a chain of decisions, and a break anywhere costs you the asset. Classify your workers correctly, because employee status changes the ownership default, and the facts behind a state reclassification also weigh in the federal copyright test. Use a present-tense IP assignment, with a defined scope, a moral-rights waiver, originality representations, and further-assurances and cooperation clauses, because a “work for hire” label fails for most contractor deliverables. Cover inventions with a Minnesota-compliant invention assignment, because the work-for-hire doctrine never reaches patents. 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, my 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, email aaron@aaronhall.com with a brief description of the situation, and I can give you a practical read on where your ownership stands. Please hold confidential documents until I have opened an intake and run a conflict check.