Element B is a little less clear, but I think it would be difficult for Uber/Lyft to overcome. Drivers would argue that the normal workplace is actually the streets. Uber/Lyft could of course argue that it's HQ, but given the number of drives on the street and the number of employees at HQ, this is no slam-dunk for the companies.
Background: I am a (former) lawyer who worked on employee/contractor issues in the realm of tax law (which uses different tests than state law).
EDIT: They might be able to redefine themselves as purely a software company for the drivers to remain contractors.
If I’m an independent developer, and I frequently refuse to accept your contract work, you might “punish” me by not offering me as much work in the future. That doesn’t change the fact that I always have the choice to accept offered work or not.
It means that the driver is unable to choose their work, which was one of the key differences between a contractor and employee.
If I run an advertising agency and I've got 4 freelance film makers I regularly use and one of them stops taking my calls or almost always says no, I'll eventually stop calling him and add someone else to my regulars. It's just business, no point me wasting my time calling him.
I think there's a load of companies abusing the gig economy at the moment, but Uber aren't the worst and definitely not for things like they provide a GPS or set the rate, it's all the delivery companies and the gas-servicing people who all have to wear uniforms and work full days.
But that's different than the situation with Uber/Lyft. In your story, the person has the ability to find new clients. If you're an Uber/Lyft driver, you can't exactly "go it alone", so to speak. You're kinda stuck with Uber/Lyft.
"I think there's a load of companies abusing the gig economy at the moment, but Uber aren't the worst and definitely not for things like they provide a GPS or set the rate, it's all the delivery companies and the gas-servicing people who all have to wear uniforms and work full days."
I disagree; I feel setting the price unilaterally is a huge part of why they're abusing things. By doing that, they are kind of dictating the wages that the driver can earn. If Uber/Lyft decide to change the per mile rate, there's nothing the driver can do. By contrast, something like Angie's List allows the different providers to set their own rates.
Of course, I imagine that sort of process would make it much harder to actually get a ride and make it far less interesting to the users.
The service is not outside of business standard variety. Other cab companies have client driven matchmaking systems too now... They also employ office workers. The workplace for a cab driver is his car.
Therefore, what Uber does would make them a cab company that abuses contractors instead of employing employees.
However, the key point here is the test A. If Uber is specifically telling the drivers to pick up specific fares or otherwise forcing them to pick up fares beyond the number and/or time, they are actually employees not contractors. Fudging with scoring system to fire those who do not follow such orders indirectly could be construed as such as well.
"the services provided were either outside the usual course of business or performed outside of all the places of business of the enterprise"
Regarding other cab companies, most cab drivers have been traditionally classified as contractors. The idea that Uber introduced this practice is propaganda.
To iterate; the statement sets out two conditions, either of which are sufficient independent of the other, and claims that each of a number of services met one of those conditions.
Usually, when a statement of "choose either x or y" is made, then the only valid options are exclusively x or exclusively y (None and Both are not valid).
Though, when the statement of "if either x or y then do action" is made, then the action is done with any of three valid options: x, y, or x and y (only None is not valid).
To change the second statement to mean the first, you could say "if only x or only y then do action." The "only" cancel Both as being an option.
Either-or does imply exclusive-or, but it is often used less formally, so you will sometimes see it made explicit as "either x or y, but not both."
Surely companies must be allowed some method to ensure the quality of work they desire.
E.g. It's the difference between: a scoring system that uses a coding style standard and unit tests on the resulting code to build a score; and a scoring system that uses hours logged into the computer manipulating the IDE and lines of code written per hour to build a score (the contractor could use that as a way to score himself and for billing, but not the company).
My guess is that B comes down firmly on the side of Uber/Lyft drivers being employees, unless they can convince a judge that their business is merely "providing an app that lets people find car companies" and not "giving people rides."
And there are a host of companies that offer similar services. They derive their value from being able to facilitate business interactions.
Angie's List is another example, and I can totally see similar businesses passing the "B" part of the test, because although they may implement some quality-control measures, such as requiring the independent contractors to abide by certain terms or meet certain standards, they are pretty hands-off in terms of HOW the recommended plumber fixes the clogged drain, or HOW the recommended carpet cleaner schedules its appointments.
But with Uber/Lyft, the HOW is much more like an employee relationship.
By comparison most point of sale (POS) venders just provide hardware and software don't involve themselves in the actual business enough though they may provide phone apps etc. Marketplaces like App stores or Amazon get more involved, but they don't dictate prices.
So yeah, I agree that Angie's List is clear of B and Uber/Lyft much less obviously so.
I pessimistically assume, however, is that assuming the A/B fight is a lost battle for gig economy compnaies, the next step is to limit these employees to being part-time with some kind of <20 hours per week or something rule.
Background: I am a spitballing layman
How does 20 hrs/week factor in here? I didn't see a reference in the Bloomberg article. Though this is actually a good point — if time spent working isn't a factor, then someone who works for Uber, Lyft, Grubhub, and Google Express could end up as en employee of all of these companies. That seems like kind of a weird result.
Walmart used the part-time distinction to great effect to increase their profits and decrease workers wages. Much has been written about this.
And in general quality issues can be handled by ratings. If a driver takes bad routes or has a dirty car they’re going to get complaints / bad ratings.
I’d be surprised if they couldn’t offer drivers “suggestions” on how to receive good ratings.
While I agree element B would be difficult for them to overcome I would give it around 50/50 that they can successfully argue the drivers are not a part of the normal workplace.
To put it another way, if you're a plumber who is working for a plumbing company, are you doing your plumbing in the office?
> equally dumb
I was defending why I think there is a 50% shot that Uber could make part B not apply. It seems like you think it is more like a 1% shot which you might be right, I am not a lawyer.
What about the Post Office??
This is going to create an interesting situation for the supremacy clause.
(1) the employer neither exercised control over the worker, nor had the ability to exercise control in terms of the completion of the work;
(2) the services provided were either outside the usual course of business or performed outside of all the places of business of the enterprise; and
(3) the individual has a profession that will plainly persist despite termination of the challenged relationship.
In many tech companies you can't even tell the difference between who is an employee and who is a contractor, unless you ask.
Many employees skip the financial meeting. Contractors are often ignored when they sneak into the holiday lunch. For most contractors the bonus is the biggest difference, and the courts tend to agree that is not enough and force the contractors to get the bonus as well.
Things like knowing when the contract ends aren't visible.
I was a contract consultant for over a decade; I didn't hide any work. I usually didn't work out of their office, but when I did use their resources my working assumption was that any artifact left behind was theirs, modulo any agreement to the contrary.
Intermediate documents, experimental code, etc. weren't offered to customers, but I can't imagine what I'd want to hide. (Aside from my shame, given how a couple projects went.)
The differences between employees and contractors may reside in the work they do, but doesn't need to, it's in the legal basis of their employment - which other workers can't see. Just like you can't see the wage another worker is getting, rat doesn't mean they're getting the wage you think they are.
The way you know someone is a contractor is they leave after a few months, or they retired and still work there. You can't necessarily tell by their work output.
If an employee and contractor are digging ditches the only difference is likely to be in the paperwork; though possibly the contractor uses their own PSE and tools, but not necessarily.
Different agencies have different criteria, but the IRS considers several factors:
https://www.nolo.com/legal-encyclopedia/independent-contract...
The agency [IRS] is more likely to classify as an independent contractor a worker who:
can earn a profit or suffer a loss from the activity
furnishes the tools and materials needed to do the work
is paid by the job
works for more than one company at a time
invests in equipment and facilities
pays his or her own business and traveling expenses
hires and pays assistants, and
sets his or her own working hours.
On the other hand, the IRS is more likely to classify as an employee a worker who: can be fired at any time
is paid by the hour
receives instructions from the company
receives training from the company
works full time for the company
receives employee benefits
has the right to quit without incurring liability, and
provides services that are an integral part of the company’s day-to-day operations.Though as presenters they have a better chance of beating ir35 as they can legitimetly work out side of the BBC in a way that a developer cant - eg pa's at events etc
EDIT: typo
https://corporate.findlaw.com/human-resources/employee-or-in...
The IRS' concerns aren't exactly the same as the state law concerns, but the lists they use to qualify contractor versus employee seem pretty similar, just with the CA state law test being more simplified (though IANAL, the more simplified CA state law list seems no less likely for companies to run afoul of with this sort of relationship).
- dictate how job performed
- dictate when performed, on a very regular basis
- oftentimes work is identical to other teams members, only difference is pay structure
For A, does that only mean working hours (i.e. can't make someone work 11am-7pm EST)? Does that affect scheduling milestones or tasks to be completed?
For C, what does 'independently established role' mean? Like job title?
Thanks in advance.
C: The contractor (ideally) works for many companies (i.e. has many clients) and not just for you. Is the contractor (individual or company) independently established? When determining C, the authorities might look specifically at things like whether the contractor has an established business location, whether the contractor has employees, how much work the contractor does for any individual client, etc.
(B would be a surprising change for consultants and trainers if it were about location, but it seems to avoid that.)
I'm framing this as an argument that the plumber could be considered an employee of the plumbing company, not the retail store.
(I'm not sure if/how this breaks down if company 2 exists solely to provide people to work for company 1 and has no meaningful independent existence, which ... is probably the case for many Uber drivers now, so that's a relevant question.)
'B' is downright apocalyptic for contract developers in all sorts of roles. Sounds like massive judicial overreach to me. If your summary is accurate, I wouldn't expect that particular guideline to survive appeal.
It's a California state law issue and this is a decision of the California Supreme Court upholding the decision of the Court of Appeals, which had upheld the Superior Court. This has already survived the whole chain of appeals.
So you're saying it can't possibly raise any (US) constitutional questions?
As an example, consider what happens when one of the affected contractors is in another state. That makes it a Commerce Clause issue. You can wave your hands and sputter indignantly all you want, but Wickard and Filburn are going to wave right back at you.
Labor law is meant to protect those in the employer <-> employee relationship, and most contractual work explicitly weaken this relationship a lot. So contractual work really shouldn't be the norm in a business.
If you can't provide your main business without this set of people, then those people are probably your employees?
That's not the case. A home builder may exclusively hire various sub-contracting companies to assemble a home, put in electricity, add finishings, etc. Those sub-contractors contract for many other home builders or landlords and are not employees of the home builders. That is the case, even though a home builder would go out of business without the sub-contractors.
Here is a different example. If a programmer works for one tech firm which calls the programmer a contractor, then if the programmer also create a personal website or side project for income, they may have established themselves as contractors.
One class is "contract employee". These people are basically treated as second-class employees (with just enough arbitrary restrictions to enforce that) of the company they effectively work for.
The other class is "employee of a contractor". These people are real employees of a company that hires them and provides them benefits. The company they work for then sub-contracts to various other companies and uses those people to fulfill the work under that contract.
Since both cases use the term "contractor", and the former is far more common in the minds of everyone here, its easy to get the two distinctions confused.
Maybe we need better terminology?
In my experience "contract employees" normally work for a third party company that gets contracted by the hiring company. Then, the third party contracting company pays their employees after deductions and taxes. Otherwise, if not working for a third party company those individuals may be classified as independent contractors. When they are classified as independent contractors there already are limits on the number of hours that can be worked before they get turned into employees.
They wouldn't, because they could drop in a replacement contractor. In your example the house builder relies on contractors but not the specific set of people doing the contracting (as in the parent), so any contractor can be replaced readily from the pool of contractors.
In theory a contractor can send someone else in to do the work, as long as the work in the contract is completed. If you demand a specific person to do work then they're likely an employee.
All you've done is restate my comment.
> In theory a contractor can send someone else in to do the work, as long as the work in the contract is completed. If you demand a specific person to do work then they're likely an employee.
That theory is wrong. If Business A depends upon the specific person B, and B does other work outside of A, then B is not necessarily an employee of A. There are many people with specialized knowledge that others do not have. The acquisition of that knowledge doesn't make them employees. It makes them valuable.
Also some type of lawyers are self employed if it's ok for a Barrister why not me.
The problem is when you get mcjob companies who abuse minimum wage staff - its well paid individual contractors that get hit.
This doesn't make any sense. Farmers are not employees of grocery stores. Factory foremen are not employees of drop shippers. Amazon warehouse staff are also not employees of drop shippers. Comcast cable layers are not employees of YouTube.
You think farmers aren't employees of grocery stores because the stores could buy the same food from different farmers? That's just as true of the IT company and its contract developers.
This matches some conrractors, of course. But it also extremely doesn't match many contractor developers.
Are you required to be online 4-6 hours a day? Do some of the companies employees not even know if you are actually a contractor? Are you the one picking up the metaphorical phone when the company's client is calling with a support issue? You might actually be an employee
If you show up with a deliverable , can go on vacation without clearing it with anyone, and are actually your own boss... Well that's different of course
It was different, but my point is that the 'B' clause ("Service is outside the business' normal variety", whatever that means) can be interpreted to remove this distinction.
A lot of people are cheering for this bullshit without thinking it all the way through.
Devs don't care simply because the pay is high enough and there are a ton of jobs available.
When I was an employee I always had to beg to do anything, as well as suck up whatever shite projects the accounts would figure out would mean a sweet billability streak... dammit, the humiliation...
Another good test is, are you allowed to subcontract your work or not?
Several years ago Italy introduced CoCoCo contracts to capture this concept of temporary professional employment, between an employee on your payroll and a butcher you buy a stake from.
Eventually companies abused it and applied it to completely subordinates such as call center operators. It was - rightfully, given the circumstances - repealed.
I wonder if we could have something like that again, it would be easier than this pantomime.
That said, my (non-lawyer, pre-coffee) reading of what B actually says is that while it won't turn consultants into employees of the place they consult for, it will turn specialists into employees, whether or not they work on site. If a company occasionally submits patches to an open-source project they use, and then they hire a maintainer full-time for a few months, that sounds like B would require them to hire the maintainer as an employee.
https://www.bloomberglaw.com/public/desktop/document/Hargrov...
I honestly am not 100% sure of the ramifications, but I am sure that these companies are going to act in their best interest, and with the current imbalance in the labor market (some might argue that the markets are right where they should be), I'm relatively certain that will mean employees being turned into contractors, or worst case they'll take the walmart route and make everyone work "part-time", drivers will think they're pulling a fast one by working for more than one company but they'll really just be driving their own wages and benefits down.
If anything, this makes it easier for contractors to prove they ought to be employees.
The answer is it won't affect them, because they'll do what it takes legally to act in their best interest, like they have always done (and have had way more resources than the average worker to do). So nothing will change, outside of a likely reduction in lawsuits for companies most able to navigate the new legal climate.
But how does that follow? You're essentially saying that no law can ever affect them, since they'll always "do what it takes legally to act in their best interest".
What I was trying to say is that this legislation is unlikely to affect the most successful gig economy companies very much, if at all, because they'll likely find the best way to circumvent it. Even if they don't there's already very large corporations doing their best not to pay employees higher wages by taking advantage of the differences in protection for part-time and full-time classified workers.
Basically, the most upside I see for the worker with this legislation is every driver in a company like Uber needing to become an "employee". Let's assume that happens. I would expect Uber or any of the other companies to immediately take steps to reconfigure to evade this -- which I think in the "worst" (for the company, as in they weren't able to evade well) case is accepting employees but limiting them to part-time status -- it's already worked very well for companies like Walmart (and badly for the communities and workers there).
On the other hand, there is also an upside for Uber/gig economy companies -- the reduction in risk in the legal arena makes them much more attractive as an investment. Up until now, it's been an open question -- this will do much to close it. That benefit will ripple to the other lesser gig economy companies, because they will have a playbook to follow.
That said, I'm not sure I agree that part-time wouldn't be that bad. It works for Walmart because their employees have low fixed costs for working (essentially just the commuting), so working fewer hours is still worthwhile.
But Uber depends on drivers buying new cars, which often they pay off by driving many hours per day. Once you limit that, they will lose everyone except the casual drivers.
The alternatives I see to this are not great for Uber: they either have to (1) buy and maintain their own fleet, or (2) accept competition so that drivers can fill up their daily schedule by working for multiple companies.
I definitely agree with the rest of your comment -- but I think the affects of (1) and (2) might actually be net positives for Uber:
(1) More fleet for their self-driving efforts seem like not a bad thing, also I don't really want to do the numbers but the 10k spent in a year on the cars as capital instead of employee benefits might look at lot better on a balance sheet (especially tax wise).
(2) I think this is only true if the supply stays the same as now -- when people hear "oh uber pays more now", I think the supply might increase a little. The increased cost per worker will be spread over all the competition, and as long as the per-worker cost isn't too high for part-time vs contractor.
As an aside to all this, uber has also started (long ago?) charging people what it thinks they can afford so that's also a factor, it's not even a single consistent percentage anymore (if it ever was).
(1) "10k spent in a year on the cars as capital instead of employee benefits" - Right, but nowadays they are spending on neither :)
(2) Right, but that means Uber can't take over the market. That's a pretty big blow.
> If A, B, or C isn’t present, the worker is considered an employee.
> A. Freedom from control over how to perform the service
> B. Service is outside the business' normal variety or workplace
> C. Worker is engaged in independently established role
So if any one of those conditions isn't the case, you are an employee under the law. I see people in this thread wondering how it'll affect companies like Uber/Lyft/whatever -- and I think it will actually be good for them, because now they'll use some of that warchest to hire the the best lawyers to figure out exactly how to best navigate the law (in california at least), and write their contracts in whatever way that best makes sure all 3 are present and they still get a healthy supply of drivers. Other smaller gig economy companies will then follow that lead so they can stay afloat and not purchase the legal work done by Uber/Lyft.
If I was invested in Uber/Lyft, I would welcome this, because it removes an avenue of risk, stabilizing the lawsuit risk.
[EDIT] - In the article there's a link to the decision from which the test comes from:
https://www.bloomberglaw.com/public/desktop/document/Hargrov...