Capped, Delayed, and Discounted: The Problem with Massachusetts Rideshare Sick Time for Uber and Lyft Drivers

I have been making this statement since I first learned that Massachusetts rideshare sick time was capped at 40 hours.

This was not something I started complaining about only after a delayed payout. I noticed it when I was looking at my sick-time balance, hoping to accrue more hours, and saw no movement. I kept checking it. I kept wondering why the number was not changing. Then I kept getting told the same answer: it is capped at 40 hours.

That is the problem.

And let me make this clear from the beginning: this is not only an Uber issue.

Uber is the company I am dealing with right now on this specific sick-time claim. But the larger problem is rideshare. This includes Lyft as well. The problem is the Massachusetts rideshare structure that was set up for app-based drivers under the Uber and Lyft settlement framework.

The companies get to say drivers have benefits. Lawmakers and regulators get to say they created protections. The press release sounds good. The talking points sound good. But when you actually drive under the system, the limits become obvious.

Massachusetts rideshare drivers are currently guaranteed at least $34.48 per engaged or active hour, depending on the platform’s wording. Lyft lists the Massachusetts guarantee as $34.48 per engaged hour as of January 2026, and Uber lists the current Massachusetts minimum earnings rate as $34.48 per hour. (Lyft) (Uber)

But sick time is not paid at that rate.

Uber’s Massachusetts benefits page says drivers can earn up to 40 hours of paid sick leave annually, paid at $21.22 per hour. Uber also says drivers accrue one hour of paid sick leave for every 30 hours of active time on rides beginning in Massachusetts, can accrue up to 40 hours per calendar year, and can claim up to 40 hours per calendar year. (Uber)

That means a driver reaches the full 40-hour sick-time cap after 1,200 active hours.

The math is simple:

40 sick hours × 30 active hours = 1,200 active hours.

Once a driver reaches that point, the benefit stops growing. The driver can keep working. The platform can keep earning from that driver’s labor. The driver still provides the vehicle. The driver still pays for gas, maintenance, cleaning, tires, brakes, insurance, inspections, and depreciation. The driver still absorbs the risk of being on the road.

But the sick-time protection stops moving.

That is why the 40-hour cap is such a problem for full-time drivers.

If someone drives part-time, maybe they never hit the cap. But for drivers who treat this as serious income, especially drivers who put in heavy active hours, the system cuts off the benefit while the work continues.

The driver keeps producing value.

The platform keeps receiving value.

The sick-time protection stops.

That is not a driver-centered benefit. That is a company-centered liability limit.

I could understand one compromise.

I could understand a 40-hour cap if the sick time were paid at the current active-time earnings rate. If the state says rideshare work has a minimum active-time value, then sick time could at least reflect that value.

I could also understand a reduced sick-time rate if there were no 40-hour cap. If the companies are going to pay a lower rate, then high-hour drivers should continue accruing sick-time protection as they continue producing active hours.

But that is not what drivers got.

Instead, the benefit is limited from every direction.

It is capped.

It is discounted.

And when claimed, it can be delayed.

Uber says paid sick leave claims can be made in one-hour blocks, up to 8 hours per day and 40 hours per year, and that after claiming paid sick leave in the driver app, drivers can expect payment within 14 days. (Uber)

That may be the stated policy, but that does not make the policy reasonable.

Usually, when I have claimed sick time, I have received it within about 24 hours. This time, I am now on the third day after requesting it. I had already requested the first portion. Then I requested the next portion. Then I requested the remainder I had available because I need to pay bills right now while money is not coming in.

Uber can point to the 14-day window and say it is following the policy. But the existence of a 14-day window is part of the problem.

Sick time is supposed to help when a worker cannot work. That means timing matters. A sick-time benefit that can sit pending while bills are due is not functioning like immediate income protection. It is functioning like a company-controlled IOU.

And again, this is bigger than Uber.

The Massachusetts settlement framework was not just a random company perk. It came out of a legal and political fight over rideshare driver classification, wages, and benefits. In 2024, Uber and Lyft agreed to a $175 million settlement with Massachusetts, including a minimum active-time wage standard and benefits such as paid sick time, health insurance stipends, and accident insurance. WBUR reported at the time that the settlement resolved a years-long legal fight over whether rideshare companies were misclassifying drivers as independent contractors rather than employees under state labor law. (WBUR)

So when drivers criticize this system, we are not only criticizing one app’s customer service. We are criticizing the structure that lawmakers, regulators, and companies allowed to become the model.

Drivers did not get a clean choice between different versions of sick time.

We did not get to choose between a 40-hour cap at the full active-time rate or a reduced rate with continued accrual.

We got the reduced rate and the cap.

That is the part I have been saying since I first noticed my balance stopped moving.

At 40 hours, sick time paid at $21.22 per hour is worth $848.80. If those same 40 hours were paid at the $34.48 active-time earnings floor, they would be worth $1,379.20. That is a difference of $530.40.

So when people say, “You have sick time now,” the answer is: yes, but what kind of sick time?

It is not full-value income replacement.

It is discounted income protection.

And once the cap is reached, it stops being additional protection at all.

This matters even more because rideshare drivers are still expected to carry the cost of the job. We are the ones who own or finance the vehicles. We are the ones who maintain them. We are the ones who keep them clean, safe, inspected, and ready to work. The platforms can create new measurements, new ratings, new safety scores, and new requirements, but the driver is still the one paying for the machine that makes the work possible.

That is the strange bargain of rideshare.

The platform wants control.

The driver carries the cost.

The platform gets the data.

The driver gets the depreciation.

The platform gets to advertise benefits.

The driver gets capped, delayed, discounted sick time.

And now there is another issue sitting in the background: automation.

Uber has already said autonomous vehicles are gradually becoming available on the Uber app in select cities, including Atlanta, Austin, Dallas, and Las Vegas, while describing its long-term approach as a hybrid marketplace where autonomous vehicles and drivers both serve customers. (Uber)

The company says autonomous vehicles are designed to complement drivers, not replace them. But drivers have every reason to take the long-term implications seriously. If platforms are building systems where human drivers carry the vehicle costs today while autonomous vehicles are introduced tomorrow, then driver protections need to be stronger before displacement becomes a larger problem.

That is where the union question comes in.

Massachusetts rideshare drivers now have the App Drivers Union, certified to represent nearly 70,000 Uber and Lyft drivers in the state. Reuters reported that the union certification followed a 2024 ballot measure that created a framework allowing app-based drivers to bargain collectively over pay and benefits. (Reuters)

That matters. It could become important. But only if the fights are the right fights.

It is not enough to bargain over today’s rates while ignoring the structure of the benefits. It is not enough to celebrate the existence of sick time while leaving the cap, the lower rate, and the delayed payout system untouched. It is not enough to talk about drivers having a seat at the table if the table is still built around protecting company exposure more than driver stability.

The sick-time system should be revisited.

There are two cleaner options.

Option one: keep the 40-hour annual cap, but pay sick time at the same rate as the active-time earnings floor.

Option two: keep the reduced sick-time rate, but remove the 40-hour cap so high-hour drivers continue accruing protection as they continue producing value.

What does not make sense is the current version: reduced rate, 40-hour cap, and delayed access.

That is not one compromise.

That is three compromises stacked together.

If these are earned sick-time benefits, then they should behave more like a real earned-benefit account. The hours should be clear. The value should be clear. The money should be protected. And when a driver claims it, the payment should move quickly because the whole point is to cover lost income when the driver is not working.

A benefit that exists only on paper until the company decides to process it is not enough.

A benefit that stops growing after 1,200 active hours is not enough for full-time drivers.

A benefit paid far below the active-time standard is not enough to call real income replacement.

That is the issue.

Massachusetts rideshare drivers have paid sick time now. But the version we received is capped, delayed, and discounted.

And that is why I have been saying this since I first saw my sick-time balance stop moving: this was not designed around the reality of full-time rideshare drivers. It was designed around a controlled maximum exposure for Uber and Lyft.

So yes, Uber is the company I am dealing with today.

But this is not just an Uber problem.

This is a Massachusetts rideshare problem.