Written by Brabners LLP
The widely anticipated Supreme Court judgment in the case of Uber and others v Aslam and others was handed down on 19th February 2021, drawing further attention to the gig economy and the notion of false self-employment.
The decision
The high-profile and ongoing debate over “worker” versus “self-employed” status was triggered in part by a case brought in 2016 by Mr Aslam, an Uber driver, who claimed that he and other fellow drivers should be paid the National Minimum Wage and should also receive holiday pay, in accordance with the Working Time Regulations 1998, for time spent when they were logged onto the Uber app and ready and willing to accept passengers. Mr Aslam and other Uber drivers would only be entitled to such rights if they were deemed to be workers, rather than self-employed.
Uber vehemently denied throughout the proceedings that its drivers were workers, arguing that the drivers were independent and self-employed. Uber argued that contracts were made between the driver and the passenger and that the drivers were at liberty to choose whether or not to accept an assignment each time a taxi journey was requested by a potential passenger. Uber’s position was that it merely provided a technology platform (i.e the Uber app) to facilitate the provision of taxi driving services between drivers and passengers; Uber argued that it did not provide those services itself, the drivers did.
However, the Employment Tribunal found in favour of the Claimants and labelled Uber drivers as “workers”.
Uber appealed the decision all the way to the highest court in the land; the Supreme Court. Unfortunately for Uber, the Supreme Court agreed with the Employment Tribunal and ruled that the drivers in question were workers, not self-employed.
The Supreme Court looked at whether the Uber drivers deserved the protection of the law – was the degree of subordination and control to which they were subjected by Uber such that, in reality, the drivers did not have the discretion to negotiate the terms of the contract with their passengers? If not, then that indicated that they were not genuinely self-employed. The greater the control exercised by one party (in this case, Uber) over the other (here, the drivers), the stronger the case for classifying the individual as a worker rather than self-employed.
Importantly, in making their decision, the Supreme Court stressed that it was not appropriate to treat the written contract as the starting point in determining worker status. The Supreme Court noted that an ‘employer’ is often in a position to dictate the contractual terms, and workers usually have little to no scope to negotiate those terms. Instead, the Court considered the reality of the situation.
Further, the Supreme Court made it clear employment law (including worker status) protections cannot be contracted out of, so any terms in a contract which seek to skirt around protective provisions will be void on public policy grounds. The written contract should not be ignored, but a contractual document will not contain all of the parties’ rights and obligations towards each other and there is no rule that a contract represents the full and accurate agreement just because an individual has signed it (given the imbalance of power between the parties referred to above).
In response to the decision, Uber has stated that the case does not apply to their drivers now and only applies to the specific drivers who brought the case and were engaged in 2016 because Uber have subsequently made changes to their business model which, in Uber’s view, means that their current drivers are genuinely self-employed. Whether Uber’s current drivers challenge that assessment remains to be seen.
What does this mean for Umbrella companies?
The Supreme Court decision does not mean that all contractors and individuals engaged in the gig economy and temporary labour market are workers. Worker status needs to be considered on a case by case basis, taking into account the reality of the relationship between the parties and factors such as the extent to which one party is subordinate to, and dependent on, the other.
Umbrella companies which engage self-employed contractors should be alive to the risk that such individuals could be deemed to be workers in certain circumstances, and that regardless of how tightly worded their contract is, a court will consider the reality of the situation when assessing the individual’s status.
The fact that a contractor may wish to be engaged on a self-employed basis does not mean that this is the most suitable way of working, and umbrella companies should consider and discuss whether other models (such as employment) may be more appropriate.
This bulletin is for general guidance purposes only and should not be used for any other purpose.
© Freelancer and Contractor Services Association Ltd 2022.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by our website to allow the us to implement or change the website's content in real-time. |
hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep a record of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
__hssc | 30 minutes | HubSpot sets this cookie to keep a record of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
__hstc | 5 months 27 days | This is the main cookie set by Hubspot, for recording visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 30 minutes | HubSpot sets this cookie to keep a record of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
Cookie | Duration | Description |
---|---|---|
hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep a record of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
_hjIncludedInSessionSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's daily session limit. |
__hstc | 5 months 27 days | This is the main cookie set by Hubspot, for recording visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
Cookie | Duration | Description |
---|---|---|
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
Cookie | Duration | Description |
---|---|---|
baqend-speedkit-user-id | 5 months 27 days | No description available. |
heyzine_session | 3 months | No description |
_hjSessionUser_2855694 | 1 year | No description |
_hjSession_2855694 | 30 minutes | No description |