Colorado UI Worker Classification: How the Two-Part Test, Contract Presumption, and Advisory Opinion Fit Together

Start with Colorado’s two substantive conditions, not the contract language

Colorado’s unemployment framework is broader than the federal common-law shorthand many businesses know from IRS materials. For state UI purposes, services performed by an individual are generally treated as employment unless the business can establish that the individual is free from control and direction in performing the service and is customarily engaged in an independent trade, occupation, profession, or business related to that service. Those are the two core conditions. A 1099, LLC, or contractor label does not answer either one.

The practical consequence is that a Colorado review should begin with operations. Who decides how the work is done? What happens when the worker is unavailable? Does the person market the same service to a real market? Can the business continue if this client disappears? If the evidence does not support both freedom from control and an independently established business, a polished agreement will not repair the underlying relationship.

The nine written-document factors are an evidentiary route, not nine independent legal votes

Colorado law allows the parties to use a written document that addresses factors such as exclusivity, quality standards, method of payment, termination during the contract term, training, tools or benefits, timing, payment to a trade or business name, and separation of business operations. When the document contains the applicable factors and the required disclosure, it can create a rebuttable presumption of independent-contractor status.

That presumption is useful, but “rebuttable” matters. The Division’s worker-classification regulation says the real relationship can still establish covered employment even when an agreement exists. In other words, the document can affect who must prove what; it does not license the parties to write facts that are untrue. Before relying on the presumption, test every operative clause against invoices, manager instructions, schedules, training records, tools, and the worker’s outside business activity.

Separate the control file from the independent-business file

A common drafting error is to blend all favorable facts into one narrative. A stronger Colorado file uses two evidence folders because the statute asks two different questions. The control folder should contain scope documents, instructions, approval boundaries, schedules, quality specifications, training materials, and communications showing whether the business controls the means and methods or only the desired result.

The independent-business folder should look outward. Preserve the date the worker’s business began, public marketing, other customers, business insurance, proposals, pricing discretion, recurring obligations, and evidence that the business can survive beyond this payer. Colorado’s regulations expressly caution that working for multiple businesses can be relevant without being solely dispositive. One client is not automatically an employee, but a business created only because one company required an “LLC” deserves a harder review.

A contract audit should compare each clause with what managers actually do

Take the signed agreement and build a two-column reconciliation. If it says the contractor chooses hours, compare that with calendar invites and coverage requirements. If it says there is no training, check onboarding decks and mandatory certification sessions. If it says payment is fixed by project, compare invoices for hourly billing. If it says the contractor may work for others, look for practical exclusivity created by full-time availability expectations.

Document contradictions instead of deleting them. A contradiction does not automatically determine status, but it tells you where the rebuttable presumption is vulnerable. It also gives the business an opportunity to change operations prospectively rather than discovering during a UI audit that the contract and the workplace evolved in opposite directions.

Use the totality-of-circumstances rule to explain mixed facts rather than score them

Colorado’s regulation says the Division considers the totality of the circumstances and may consider factors beyond the enumerated contract items. That makes simple red-green scoring risky. A worker may use personal equipment yet operate under a manager’s daily sequence. Another may have no second client during a long project but maintain a viable consulting practice with marketing, fixed costs, pricing discretion, and a history of projects before and after this engagement.

The final memo should therefore identify which facts carry the most weight for this occupation and why. For a highly regulated profession, some supervision may exist because law requires it; the regulation specifically distinguishes direction or control exercised pursuant to state or federal requirements. The useful question is what control the company adds beyond what the law itself demands.

Colorado’s nonbinding advisory opinion can be a pre-audit decision tool

Part XVII of Colorado’s unemployment regulations provides a process for a business to request a nonbinding advisory opinion on worker classification. That is different from waiting for a claimant, audit, or tax assessment to create the question. For a planned engagement that is genuinely borderline, the option can be more useful than collecting a generic “contractor checklist” from the internet.

Treat the request as a disclosure exercise, not a sales pitch. Assemble the actual scope, control boundaries, pricing, business history, tools, customer-market evidence, and draft contract. If the facts are likely to change after launch, create a review date as well. An opinion based on one operating model is not a substitute for rechecking a relationship that later becomes full-time, indefinite, or manager-directed.

Use the advisory-opinion route for a genuinely unresolved relationship, not as a substitute for fact collection. The request should describe the actual service, contract rights, operating practices, and independent-business evidence that make the question difficult. Because Colorado describes the opinion as nonbinding, preserve the underlying file and continue monitoring the relationship after the opinion; later facts can change the practical risk even when the original submission was accurate.

Build a change trigger because a good Colorado file can become stale

A contractor may begin with a defined implementation project, then gradually receive internal credentials, fixed weekly coverage, company equipment, team training, and recurring tasks. The original contract may still be in the vendor folder, but the facts supporting it are gone. That is a classification problem caused by role drift rather than by a bad initial decision.

Create specific triggers: renewal beyond the original project, new manager supervision, fixed recurring hours, loss of outside customers, company-provided tools, employee-like benefits, or conversion from deliverable pricing to ongoing hourly work. When one occurs, re-run both Colorado conditions and the contract-to-operations reconciliation. Date the result so an auditor can see when the company noticed and responded to change.