Wisconsin UI uses a gate, then a count

For general private employers under Wisconsin unemployment law, the analysis is not a single list. The first part asks whether the worker is free from the employer’s control or direction. If the worker is under control or direction, the worker is an employee and the analysis does not move forward to rescue the classification with business-independence factors.

Only after Part 1 is satisfied does Part 2 matter. The worker must meet at least six of nine listed conditions. That sequence should shape the workpaper. Put control evidence first, then a nine-condition schedule with a yes, no, or unresolved status supported by documents. Do not blend the two stages into an overall “contractor score.”

Part 1 should be reconstructed from assignments, not the worker’s title

Look at how work is assigned, scheduled, supervised, and corrected. Who chooses sequence? Can the worker accept or reject projects? Does the company provide detailed instructions or require company methods? Are there mandatory hours or a continuing duty to be available? A consultant label or business card has little value if the company retains operational control.

Quality requirements need nuance. A customer can define deliverables and reject work that fails contractual specifications without necessarily controlling the means. The risk grows when the company dictates step-by-step methods, trains the worker to perform the service its way, or manages the person like internal staff. Preserve the difference between result specifications and process control.

Condition 1 asks whether the worker affirmatively holds out as a business

Wisconsin’s first Part 2 condition looks for evidence that the individual advertises or otherwise affirmatively holds out to the public as being in business. A dormant LLC or a tax form does not by itself demonstrate that market-facing behavior. The file should show how prospective customers can find and engage the worker.

Examples include a business website, listings, proposals, business cards, professional profiles that offer services, or other genuine marketing. Capture dated evidence because a webpage created after an audit letter has much less historical value than records showing the worker was in the market during the period under review.

Several conditions are best proven from accounting records, not narratives

Wisconsin asks about main expenses, profit or loss, recurring business liabilities, and economic dependence. Those topics can be tested with numbers. Identify what expenses are required to perform the service, who pays them, what fixed obligations continue between projects, and whether pricing and cost management can materially change the worker’s profit.

Do not write “bears expenses” when the company reimburses nearly everything. Do not claim “risk of loss” if the worker is guaranteed a rate for every hour and has no meaningful costs. A simple project P&L, insurance invoice, software subscription history, equipment purchase, or office obligation can be more persuasive than three paragraphs of conclusions.

Multiple contracts and economic independence need separate evidence

One condition asks whether the individual operates under multiple contracts with one or more employing units to perform specific services. Another asks whether the individual is economically dependent on a particular employing unit. These concepts overlap but are not identical. A worker may have two contracts with one customer yet remain economically dependent on that payer; another may have only one active project during a short period but maintain a viable independent business and a pipeline of other customers.

Document the facts each condition actually asks about. Keep executed scopes and project orders for the multiple-contract condition. For economic dependence, preserve customer concentration, marketing, pipeline, prior clients, fixed business infrastructure, and what the business would do when the current project ends.

Create an unresolved category instead of stretching weak facts to reach six

Because six of nine is a numerical threshold, there is a natural temptation to turn borderline evidence into a “yes.” Resist it. Use three states: supported, not supported, and unresolved. If the business reaches only five supported conditions, that is a decision point—not an invitation to relabel an ambiguous sixth factor.

For an unresolved condition, identify the missing record and the person who can verify it. If the fact did not exist during the period, say so. A contemporaneous file that acknowledges a missing condition is more defensible than an after-the-fact checklist in which every row is green with no documentary support.

For borderline files, list the six conditions the company believes are actually satisfied and put the evidence citation beside each one. Conditions that are merely possible or depend on an unsigned future plan should stay in an unresolved column. This prevents a reviewer from unconsciously counting the same business fact twice just to reach six and makes a later re-review much faster when new evidence arrives.

Keep Wisconsin UI analysis separate from other worker-status tests

Wisconsin agencies administer more than one worker-classification framework for different laws. The unemployment page for general private employers expressly uses the two-part control plus six-of-nine test. A company should label the workpaper “Unemployment Insurance” and cite the UI source so no one later substitutes a checklist built for a different program or purpose.

This matters in multi-agency audits. A business can keep one factual evidence repository—contracts, invoices, control records, business-market evidence—but map those facts separately to each legal test. Shared facts are efficient; shared legal conclusions are not.

WISCONSIN THRESHOLD WORKSHEET

Control gate + six-of-nine evidence tracker

Stop at Part 1 if control is present. If Part 1 is satisfied, count only conditions supported by contemporaneous evidence.

StageIssueStatus choicesBest evidence
Part 1Free from control/directionSupported / No / UnresolvedSchedules, instructions, approvals
Part 2Held out as a businessSupported / No / UnresolvedMarketing, proposals, listings
Part 2Multiple contractsSupported / No / UnresolvedContracts, SOWs, purchase orders
Part 2Main expensesSupported / No / UnresolvedExpense ledger, reimbursements
Part 2Profit/lossSupported / No / UnresolvedProject P&L, pricing records
Part 2Recurring obligations/economic independenceSupported / No / UnresolvedInsurance, subscriptions, client mix

WORKED EXAMPLE

Example: five strong conditions are still not six

A Wisconsin company hires a field specialist who sets methods, rejects assignments, and works without day-to-day supervision. Part 1 is well supported. The specialist advertises publicly, pays main expenses, has recurring insurance, can make a project profit or loss, and works from a chosen location with personal equipment.

The company initially marks “multiple contracts” yes because the specialist signed three work orders—but all three are with the same company and the records do not clearly establish how the condition applies. Rather than force a conclusion, the reviewer marks it unresolved and checks the remaining statutory conditions. The file reaches only five clearly supported conditions.

That result is useful. It tells the company the contractor classification is not adequately supported under the UI test today, even though the relationship looks independent in ordinary business language.