Most business owners treat the independent contractor agreement as the thing that decides whether a worker is a contractor. It is not. In Minnesota, classification is decided by how the relationship actually works, measured against a common-law test, and a signed agreement that calls someone a contractor carries no weight if the facts say otherwise. A well-drafted agreement still matters, just for different reasons: it is how you confirm you own the work product, how you keep confidential information protected, and how you set clean payment and termination terms. This article walks through what an independent contractor agreement should cover and why, and where Minnesota law, federal copyright law, and your own drafting choices each control the outcome. It is part of how I advise clients in my business operations practice.

Does a written agreement make someone an independent contractor in Minnesota?

No. A written agreement does not make a worker an independent contractor in Minnesota. Classification turns on the substance of the working relationship, not the label in the contract, and Minnesota’s misclassification statute treats a misclassifying agreement as a problem rather than a defense. Under Minn. Stat. § 181.722, an employer may not “require or request an individual who is the person’s employee . . . to enter into any agreement or complete any document that misclassifies, misrepresents, or treats the individual as an independent contractor.” Each such agreement “constitutes a separate violation.”

The statute does not define the classification test inside itself. It borrows one: the nature of the 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.” So the agreement is evidence of intent, and intent matters, but it sits underneath the actual facts. In my practice, the recurring mistake is treating the signed contract as the finish line. The more useful way to think about it: the agreement records the deal you intend, and the way you run the engagement either confirms that deal or quietly undoes it.

What test decides independent contractor status in Minnesota?

Minnesota uses a common-law five-factor test for general worker classification. The unemployment-insurance statute, Minn. Stat. § 268.035, defines covered “employment” as service performed by “an individual who is an employee under the common law of employer-employee and not an independent contractor,” and points to the administrative rules for the factors. Minn. R. 3315.0555 lists the five: “the right or the lack of the right to control the means and manner of performance,” “the right to discharge the worker without incurring liability for damages,” “the mode of payment,” “furnishing of materials and tools,” and “control over the premises where the services are performed.” The rule is explicit that “the two most important factors are items A and B”: control, and the right to discharge.

This is the test your agreement is measured against. Control here means the right to direct how the work is done, not just what result you want. A company that hands a contractor a defined deliverable and a deadline, and leaves the method to them, looks like a buyer of services. A company that sets the contractor’s hours, supervises their daily steps, and can fire them at will for any reason starts to look like an employer, whatever the contract says. The same discipline that produces good operating procedures helps here: write down what you are buying as a result, and resist the urge to manage the contractor like staff.

Why is the classification test different for construction contractors?

Construction is the major exception. For the Minnesota statutes and purposes covered by Minn. Stat. § 181.723, building construction or improvement services are subject to that statute’s construction-specific test rather than the general five-factor discussion above. The statute states that the “section only applies to persons providing or performing building construction or improvement services.” Under that statute, a construction worker is an independent contractor “only if the individual is operating as a business entity that meets all of the following requirements,” and the statute then lists 14 of them. All 14 must be met.

The construction test is close to a checklist. Among the 14 requirements, the worker’s business entity must be separately established, own or lease its own equipment, serve multiple clients, hold the required tax identification numbers and licenses, and be “operating under a written contract” that is “signed and dated by both” parties, “fully executed no later than 30 days after the date work commences,” and that “identifies the specific services to be provided.” Trucking and messenger or courier work has its own separate statutory test as well. For a construction or trucking business, the agreement is a compliance document, and missing a single requirement can flip the worker to employee status. For every other industry, the five-factor common-law test is the one that governs.

How should the scope and deliverables section be written?

The scope section should describe a defined result, not a supervised activity. List the deliverables, state the standard the work has to meet to be accepted, and set the deadline. Then stop. Leave the means and manner to the contractor, because the right to control the method is the single most important factor in the classification test, and the scope section is where companies most often give that control away without noticing.

The administrative rules define “control” broadly: it is “the power to instruct, direct, or regulate the activities of an individual whether or not the power is exercised.” That last phrase matters. Even a power you never use counts against you. A scope section that reserves the right to assign the contractor new tasks at your discretion, dictate their working hours, or require them to follow your internal procedures step by step is reserving control, and a reviewer applying the five-factor test will read it that way. The cleaner draft ties payment to milestones and acceptance of deliverables, references a precisely defined scope of work, and leaves the contractor free to decide how and when to do it. If the engagement genuinely needs hour-by-hour direction, that is a sign the role may be an employee role, and the agreement cannot fix that.

Do I own the work my contractor creates?

Not automatically. Under federal copyright law, “copyright in a work protected under this title vests initially in the author or authors of the work.” 17 U.S.C. § 201. When a contractor creates something, the contractor is the author, so the copyright starts with the contractor, not with the company that paid for it. Paying for the work does not move the copyright. This is the single most expensive surprise I see in contractor engagements: a company that commissioned its logo, its codebase, or its website discovers it never owned the copyright.

There are two ways ownership can sit with the company. One is the “work made for hire” doctrine. For an employee, work created within the scope of employment is a work made for hire and the employer is the author. For a contractor, 17 U.S.C. § 101 is far narrower: a commissioned work is a work made for hire only if it falls into one of nine listed categories, “a contribution to a collective work, as a part of a motion picture or other audiovisual work, as a translation, as a supplementary work, as a compilation, as an instructional text, as a test, as answer material for a test, or as an atlas,” and only “if the parties expressly agree in a written instrument signed by them.” Software, marketing copy, logos, and most business deliverables are not on that list. For those, the work-for-hire label does nothing. The company gets ownership only the second way: a written assignment.

What makes an IP assignment clause actually transfer ownership?

A copyright assignment is only effective if it is in writing and signed by the contractor. 17 U.S.C. § 204 states that 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.” An assignment buried in a verbal understanding, or in an unsigned statement of work, does not transfer the copyright. The clause has to be written, and the contractor has to sign it.

A sound intellectual property clause does three things. First, it includes a present-tense assignment: the contractor “assigns” the work to the company, not “agrees to assign” it later, so ownership passes on signing rather than depending on a future act. Second, it adds a backup license, so that if any part of the assignment fails, the company still has a broad license to use the deliverable. Third, where the work is fine art, it addresses moral rights. Federal law, 17 U.S.C. § 106A, gives the authors of a narrow class of visual art a right of attribution and integrity, and those rights “may not be transferred, but . . . may be waived if the author expressly agrees to such waiver in a written instrument signed by the author” that “specifically identif[ies] the work, and uses of that work.” For ordinary business deliverables this rarely applies, but for commissioned artwork or sculpture, a specific signed waiver belongs in the agreement. The mechanics of how an assignment clause should read reward precision: name the deliverables, name the rights, and have the contractor sign.

How does a confidentiality clause protect the company?

A confidentiality clause is a contract promise that defines what the contractor may not disclose or reuse, both during the engagement and after it ends. A contractor often sees customer lists, pricing, internal processes, and product plans. Without a confidentiality clause, the contractor’s obligations are limited and hard to enforce. With one, you have a defined, enforceable standard: a description of what counts as confidential information, a promise not to disclose or use it outside the engagement, and a return-or-destroy obligation when the work is done.

The confidentiality clause is also one of the restrictive terms Minnesota law leaves fully intact. The state’s 2023 noncompete statute, Minn. Stat. § 181.988, is explicit that a “covenant not to compete does not include a nondisclosure agreement, or agreement designed to protect trade secrets or confidential information.” So while Minnesota has sharply limited what you can do to restrain a former worker, a confidentiality clause is not affected. The noncompete statute does not void a properly drafted confidentiality clause, but the clause still must be enforceable under ordinary contract and trade-secret principles. That makes it one of the most important clauses in the agreement, and worth drafting with care rather than copying a generic paragraph. Confidentiality is part of the duties that come with bringing someone inside your business, and the clause is how you make those duties concrete.

How Minnesota’s noncompete ban applies to contractor agreements

For contractor agreements entered into on or after July 1, 2023, outside statutory exceptions such as sale-of-business or dissolution contexts, Minnesota generally makes noncompetes void and unenforceable, including for independent contractors. The 2023 statute makes a covenant not to compete “void and unenforceable,” and it defines “employee” to mean “any individual who performs services for an employer, including independent contractors.” So in ordinary service agreements entered into on or after July 1, 2023, outside the statute’s exceptions, you cannot bar a contractor from working for your competitors or in your industry after the engagement ends, and a clause that tries to is unenforceable.

The statute does leave you real tools. Critically, a void noncompete does not poison the rest of the agreement: the law says “nothing in this subdivision shall be construed to render void or unenforceable any other provisions” in the same contract. So the practical drafting move is to drop the noncompete entirely and rely on the restrictions that survive. Two of them carry most of the weight. A nondisclosure clause, as covered above, protects your confidential information. A nonsolicitation clause, which the statute also expressly carves out of the ban, can restrict the contractor from soliciting your customers or using your client and contact lists. Between those two, a well-drafted agreement protects the company’s actual interests, the information and the customer relationships, without relying on a clause that Minnesota courts will not enforce.

What should the tax, insurance, and termination terms cover?

The tax, insurance, and termination terms should reinforce that this is an arm’s-length engagement, not employment. On taxes, the agreement should require the contractor to furnish a Form W-9 and represent that they are responsible for their own income and self-employment taxes. The company reports payments to the contractor on a Form 1099-NEC under the federal reporting rules, and a tax-representation clause, paired with an indemnity, gives the company a contractual remedy if the contractor’s status representation turns out to be wrong. On insurance, the agreement can require the contractor to carry their own commercial liability coverage and provide certificates of insurance.

On termination, the agreement controls. A contractor is paid contract fees under the agreement, not wages, so Minnesota’s wage-payment statutes, which govern final paychecks for employees, do not set the timing of a contractor’s final payment. The agreement does. A clean termination section states the notice each side must give, what happens to work in progress and to fees already earned, and confirms that the confidentiality and intellectual property clauses survive termination. It should also address offboarding: cutting off access to systems and files when an engagement ends is a routine gap. One more practical point on execution: confirm who on your side has authority to sign the agreement, so the contract you rely on was signed by someone who could bind the company.

Can I reclassify an existing employee as an independent contractor?

Rarely safely. If the worker still fails Minnesota’s five-factor test, changing their label does not change their status. Requiring an actual employee to sign an independent contractor agreement is a separate violation under Minn. Stat. § 181.722, on top of any back taxes and benefits owed.

What happens if the state reclassifies my contractor as an employee?

The company can face compensatory damages, such as unpaid wages or benefits, penalties under Minn. Stat. § 181.722, and separate tax, unemployment, or insurance liabilities under applicable law. The penalty under Minn. Stat. § 181.722 can run up to $10,000 for each misclassified individual and up to $10,000 for each violation. Owners and officers who knowingly or repeatedly misclassify can be held individually liable.

Do I need a written agreement to engage a contractor in Minnesota?

Outside construction, Minnesota law does not require one. A written agreement is still the practical foundation for owning the work product and enforcing confidentiality. In building construction, a signed, dated, scope-specific written contract is one of 14 requirements under Minn. Stat. § 181.723 for contractor status.

Is a 'work for hire' clause enough to give my company the copyright?

Usually not on its own. Under 17 U.S.C. § 101, a contractor’s work qualifies as a work made for hire only in nine narrow categories, and software and most marketing deliverables are not among them. A sound agreement pairs the work-for-hire language with a present written assignment of everything else.

Can I require my contractor to carry their own insurance?

Yes. An independent contractor agreement can require the contractor to maintain their own commercial liability coverage and provide certificates of insurance. Requiring the contractor to carry their own coverage is also one of the terms that reinforces an arm’s-length, contractor relationship rather than an employment one.

Drafting an independent contractor agreement is two jobs at once. The agreement cannot decide classification: that is set by how the relationship actually runs, measured against Minnesota’s five-factor test, and no contract language overrides the facts. What the agreement does decide is whether you own the work product, whether your confidential information is protected, and whether your payment and termination terms are clean. Get the second job right, and run the engagement consistently with the first, and the agreement does real work. If you are putting a contractor relationship in place, or you are not sure an existing one would survive a closer look, getting a legal read before a dispute or an audit is far cheaper than after. You can find more in my Minnesota business operations counsel materials, or contact the firm to start an intake and conflict check before sending a copy of the agreement.