Colorado Proposition 128 and Gig Worker Benefits Requirements

Someone searching "Colorado Proposition 128 gig worker benefits" this year is going to end up reading about parole eligibility for violent felons. Someone searching "Colorado Proposition 128 gig worker benefits" this year is going to end up reading about parole eligibility for violent felons, and that's literally what happens. Proposition 128 passed on November 5, 2024, with 62.11% of the vote (1,869,231 yes to 1,140,284 no, out of a total in the low millions of ballots cast), and it raised the parole eligibility threshold for violent felony offenders, things like murder, assault, kidnapping, arson, burglary, and robbery, from 75% to 85% of a sentence served. Three-time violent offenders now have to serve the full term. None of that touches delivery drivers, contractor classification, or app-based work in any way.

Searches for "Colorado Proposition 128" and Gig Work That Lead Operators to the Wrong Place

The mix-up makes sense once you see how it happens. Colorado's gig economy rules have genuinely been in motion for the past few years, so anyone typing "Colorado" plus "gig" plus "new law" into a search bar is fishing in a pond that actually has fish in it. Proposition 128 is a criminal justice measure, full stop, and no ballot initiative by that number or name deals with contractor classification, delivery network companies, or worker benefits anywhere in its text. It's a criminal justice measure, full stop, and no ballot initiative by that number or name deals with contractor classification, delivery network companies, or worker benefits anywhere in its text.

The real story is duller than a ballot measure and more consequential: three bills, passed in three straight legislative sessions, that quietly rebuilt how gig-economy companies operate in Colorado. None of them got a punchy number the way ballot props do. They got the legislative equivalent of parking tickets: SB23-098, SB24-075, HB 25-1001. Try putting that on a yard sign.

The actual legislative cluster shaping Colorado's IC landscape: SB23-098, SB24-075, and HB 25-1001

SB23-098 is the foundation. It requires delivery network companies and transportation network companies to tell drivers what a customer actually paid versus what the driver actually received for a given task, closing the gap where a driver sees a fraction of what the customer paid for a delivery and has no idea where the remainder went. The bill also forces companies to spell out how driver termination and rehire work, and it gives terminated drivers a right to administrative review instead of a permanent, unexplained blacklist. Colorado's Division of Labor Standards and Statistics can levy fines, and drivers or consumers can sue directly if they get burned.

SB24-075, passed a year later, went further into rideshare-specific territory. It required TNCs to write and publish a formal deactivation and suspension policy, including a process to contest a deactivation, by May 1, 2025, with actual compliance kicking in June 1, 2025. It also created a semiannual reporting requirement to the Division, covering completed trips and driver deactivations, with the first report due August 1, 2026. It's a recurring obligation that companies now have to build into their operating calendar the way they'd build in quarterly tax filings.

HB 25-1001 is where things get personal, literally. It expanded the definition of "employer" under the Colorado Wage Act to include any individual who owns or controls at least 25% of a business, and an owner can be held personally liable for wage violations unless they can prove they fully delegated day-to-day operations to someone else. The bill also set automatic fines for misclassifying workers as independent contractors: $5,000 for a first willful violation, scaling up for repeat, unremedied violations (sources differ on whether the ceiling is $25,000 or $50,000, and operators should confirm the current figure directly rather than guess). Separately, the wage claim jurisdiction handled by the Division jumps from $7,500 to $13,000 starting July 1, 2026, so more disputes get resolved at the state level instead of needing a courtroom.

Colorado's Transparency Requirements for Delivery Network Operators Day-to-Day

The bill numbers aside, the actual operational asks are pretty concrete. Before a driver accepts a delivery task, the driver needs to see the estimated or actual earnings (including tips and reimbursements), how many transactions are bundled into the task, the pickup and drop-off addresses, direction from the driver's current location, and estimated time and distance. When a customer tips, the company has to show the full amount the customer paid and the full amount the driver received, and the entire tip has to pass through to the driver, not get quietly absorbed into a "service fee." Multi-delivery, time-block arrangements get the same treatment, just applied to the block as a whole instead of a single stop.

Deactivation policy can't just be a paragraph buried in a terms-of-service PDF nobody reads. It has to be written, published, and include an actual reconsideration procedure, so a driver who gets cut off has a real, documented path to appeal it. And starting August 1, 2026, the semiannual reporting requirement means operators are on the hook for an ongoing compliance rhythm.

Colorado House Democrats have pointed out that over 60% of Denver delivery app drivers rely on gig work as their primary source of income, which is the context for why lawmakers keep treating these disclosure rules as real worker protections rather than paperwork. When most of your workforce depends on the gig for rent money, "we'll get back to you" isn't an acceptable deactivation policy.

Colorado's enforcement posture: why the classification risk is higher here than in most states

Colorado presumes workers are employees unless the company proves otherwise. The burden sits on the operator, not the worker. That's a meaningfully different starting line than states that default the other way, and it means a shaky classification decision doesn't get the benefit of the doubt, it gets scrutinized from the jump.

Workers' compensation makes this sharper. Colorado requires nearly all employers to carry workers' comp coverage, and misclassifying a contractor who should've been an employee means that coverage was never in place when it needed to be. The penalties for not carrying it include fines, personal liability for the injured worker's claims, and an additional 25% penalty tacked onto whatever benefits that worker was owed. That's not a rounding error in a budget, that's a business-ending sequence of events for a smaller operator.

A state labor agency has also picked up the pace. Audits rose 40% between 2024 and 2025, recovering $12 million in back wages across more than 500 investigations. Those audits have leaned construction-heavy so far, but the methodology, cross-checking payroll and unemployment insurance data against who's actually on-site doing work, translates directly to 1099-heavy delivery operations along the Front Range. And the federal backstop that used to give companies some cover just evaporated: on May 1, 2025, a federal labor agency's wage and hour division announced it would stop enforcing the 2024 Biden-era independent contractor rule under the FLSA. That leaves state regulators like CDLE as the main enforcement authority for a lot of Colorado operators, which is a bit like finding out the backup goalie just quit mid-game.

Portable Benefits in the Transparency and Enforcement Framework

None of these three laws, SB23-098, SB24-075, or HB 25-1001, require operators to provide benefits to independent contractors. They're transparency and enforcement statutes, not benefits mandates. A separate bill, HB 25-1291, might have pushed Colorado further into TNC regulation, but it was vetoed and its provisions never took effect.

Portable benefits are a live national conversation, just not yet a Colorado one in any confirmed sense. As of early 2026, three states, Utah, Alabama, and Tennessee, have enacted portable benefits laws, and others introduced bills during the 2026 session. Some aggregator sources list Colorado among states that passed portable benefits legislation between 2024 and 2026, but that claim isn't backed by a primary legislative citation and shouldn't be treated as settled until it is.

At the federal level, Senators Cassidy, Scott, and Paul introduced a four-bill package in mid-2025: the Unlocking Benefits for Independent Workers Act, which would create a safe harbor letting companies offer voluntary benefits without triggering reclassification risk; the Modern Worker Empowerment Act, aimed at standardizing worker classification at the federal level; and the Association Health Plans Act, which would let gig workers pool into shared health coverage. Together the package is aimed at a large share of the independent workforce, and the package has reportedly attracted bipartisan interest beyond prior attempts at this kind of reform.

California's Proposition 22 remains the reference point everyone measures against nationally: it permanently classifies app-based drivers as independent contractors while requiring a narrow benefits package, including a quarterly health stipend for drivers who qualify. Colorado has nothing like it on the books. For now, the obligation on Colorado operators is transparency and correct classification. Benefits are a policy conversation happening elsewhere.

A Compliant Colorado IC Operation in Practice

Compliance starts with the classification decision itself. A well-worded independent contractor agreement means very little if the underlying economic relationship, how much control the company exercises, how the work actually gets performed day to day, doesn't hold up under Colorado's employee-presumption standard. The contract is decoration. The relationship is the substance.

Onboarding and credentialing affect audit exposure, because Colorado's framework assumes the company can document who its contractors are, what they agreed to, and what they were told about their rights. That documentation trail appears in an audit. And because CDLE's enforcement approach examines the economic relationship over time, a contractor arrangement that looks clean on day one but drifts toward employee-like patterns later creates exposure retroactively. A single classification review at onboarding isn't enough. The relationship needs ongoing monitoring.

Disclosure has to run on a system, not on a person remembering to do it. Per-task earnings disclosures, published deactivation policies, and semiannual Division reports are recurring, structural obligations. Any operator managing more than a handful of contractors is going to find that manual tracking breaks down fast, because the volume of tasks and disclosures at scale makes a spreadsheet-and-good-intentions approach mathematically unworkable.

Colorado's Framework Through the 2026 Session and Beyond

The veto of HB 25-1291 wasn't the legislature backing off TNC regulation, it was a redirect. Further legislative activity on transportation network company rules is anticipated as the 2026 session proceeds. The Colorado General Assembly's summary of 2026 labor and employment legislation, published August 3, 2026 by Legislative Council Staff, is the document to check for whatever actually passed since then.

Broader shifts in Colorado's employer-worker legal terrain remain possible through future legislative or ballot activity, none of which targets independent contractor networks directly but all of which shapes the environment delivery operators sit inside, the way a change in zoning laws doesn't touch your house directly but changes what gets built next door.

Portable benefits are still unresolved at the federal level, and that's the one to watch. If federal portable benefits legislation moves forward, it could change the math for operators who've been cautious about voluntary benefit offers and the classification questions those offers can raise. Right now, voluntary benefit offers exist in a legally uncertain space under current classification standards. A federal safe harbor, if enacted, could clarify that space, and Colorado operators would be some of the first to test what that actually looks like in practice.