Gig economy workers should be classified as employees

What's this about?

People disagree about whether app-based workers should count as staff, not as self-run business owners.

The key question is whether the app firm controls the main parts of their work.

What supporters say

• App firms may set pay, choose jobs, track work, rate people, and block workers from using the app.
• Choosing work hours does not stop workers from facing shaky pay, unpaid wait time, and few job rights.
• Staff status could bring fair pay rules, job-loss aid, injury help, paid-in tax funds, and group talks.

What critics say

• Some workers like contractor status because they can choose when to work or use many jobs.
• Staff rules might make some apps offer fewer jobs or stop serving some places.

How to read this

The number of points on each side does not show who is right; strong proof matters more than a long list.

The bottom line

The case for staff status has real support, especially when an app firm acts like a boss.

But we are not sure how a broad rule would affect all workers, apps, or jobs.

The debate over gig work is not simply whether everyone on a digital platform should be called an employee. The stronger question is whether workers should receive employee status when a platform controls the key conditions of their work, while genuinely independent businesses remain contractors.

The case for

Many platforms operate much like employers, even when they formally call workers independent contractors. They may set or influence prices, decide which jobs workers receive, rank their performance, monitor activity and use customer ratings or deactivation as disciplinary tools. When algorithms control these basic economic conditions, workers may have little real power to negotiate.1

That matters because contractor status can leave workers carrying risks that employers usually bear. Employee classification could provide access to minimum wages, unemployment insurance, workers’ compensation, employer payroll contributions and collective bargaining rights. Supporters argue that these protections are especially important when a platform depends on workers’ labor but shifts the costs of benefits and unstable work onto them.2

The claim is also not defeated by workers’ ability to choose when to log on. Research and reviews suggest that flexible schedules can exist alongside financial insecurity. Workers may face unstable earnings, unpaid waiting time, uncertain access to benefits and weak bargaining power. Choosing when to work does not necessarily mean someone is running an independent business.3

This case has meaningful support from legal, ethical and labor-market research. But much of that support brings together several lines of analysis rather than offering a single, consistent estimate of what would happen if workers were reclassified.

The case against

A uniform employee rule could remove options that some workers genuinely value. People who use platforms only occasionally, combine the work with other jobs or prefer to choose their own schedules may benefit from contractor arrangements. Those models can lower barriers to entering the market and allow workers to fit platform work around other commitments.4

The value of that flexibility, however, varies from worker to worker. It may be particularly important to people who are financially independent from platform income, while mattering less to workers who rely on one platform for most of their earnings.

There is also uncertainty about how platforms would respond to new employee obligations. Higher payroll, compliance and scheduling costs could lead companies to raise prices, reduce service areas, limit access to work or replace some tasks with automation.5 These outcomes are plausible, but existing analyses do not establish how large or consistent the effects would be across platforms.

The evidence is stronger on the fact that flexibility can matter to some workers than on predictions about the broader economic results of employee mandates. The available research also lacks a common test for deciding how much platform control is enough to make someone an employee. It does not clearly show how often particular practices occur or what reclassification would do to prices, earnings and service availability at scale.

The bottom line

The evidence favours employee status when a platform controls core economic conditions, but only with moderate confidence about the consequences of any specific legal rule. The strongest conclusion is not that every platform worker should automatically become an employee. It is that legal status should reflect actual control and economic risk.

Workers are closer to employees when platforms set prices, control access to jobs, impose performance standards and can end their participation. Workers are closer to genuine contractors when they set their own prices, market their services, serve multiple clients and bear real business risks.

A control-sensitive presumption of employee status, combined where necessary with enforceable hybrid or portable benefits, best fits the evidence. California’s approach—preserving some contractor flexibility while offering selected protections—illustrates one possible model, though its success depends on benefit levels, enforcement and how dependent workers really are. The evidence is strong that control and risk allocation should guide the decision, but incomplete on the effects of reclassification and on how workers’ preferences differ across occupations, jurisdictions and levels of dependence.