Oregon

Subscribe to Oregon via RSS

Last week, the 9th Circuit held in two related cases from California and Oregon that FedEx misclassified approximately 2,600 delivery truck drivers as independent contractors, rather than as employees. The cases—Alexander v. FedEx and Slayman v. FedEx—are an important reminder for employers that reality matters more than labels when it comes to classifying workers. 

On that note, the most succinct (and most memorable) summary of the rulings appears in Judge Trott’s short concurrence in Alexander:

“Abraham Lincoln reportedly asked, ‘If you call a dog’s tail a leg, how many legs does a dog have?’ His answer was, ‘Four. Calling a dog’s tail a leg does not make it a leg.’ . . . Labeling the drivers ‘independent contractors’ in FedEx’s Operating Agreement does not conclusively make them so . . . .”

The two cases dealt with virtually identical facts. FedEx’s Operating Agreement (“OA”), which principally governed its business relationships with the 2,300 California drivers and 363 Oregon drivers in each class, contained several generalized clauses that suggested the drivers were independent contractors. For example, the OAs provided that “the manner and means of reaching [the parties’ “mutual business objectives”] are within the discretion of the [driver], and no officer or employee of FedEx . . . shall have the authority to impose any term or condition on the driver . . . which is contrary to this understanding.” The two opinions noted, however, that neither California nor Oregon law views a contract’s description of a worker as an independent contractor as dispositive of the worker’s true status.Continue Reading 9th Cir. Finds FedEx Delivery Drivers Are Employees, Not Contractors

Not to be outdone by its neighbors to the north–Portland and Seattle–Eugene, Oregon appears poised to become the next jurisdiction to pass an ordinance requiring employers to provide employees working within city limits with paid sick leave. A coalition of pro-sick leave advocacy groups, including Portland-based Family Forward, first brought the topic before the council in…

Today we continue with our recent New Years theme.  Not to be outdone by their neighbors to the south, the Oregon Legislature was also busy in 2013.  And now that 2014 is upon us so too are a slew of new Oregon employment laws. In areas ranging from social media to sick leave, Oregon employers should carefully review their policies and practices to ensure current compliance with these new laws.  Here is a round up of the major changes to employment laws enacted by the Oregon Legislature (and the City of Portland) that employers should be aware of in 2014:

  • Employers may not demand access to employees’ social media accounts. Beginning on January 1, 2014, employers may not demand access to employees’ or applicants’ personal social media accounts. House Bill 2654, which Governor Kitzhaber signed into law on May 22, 2013, prohibits employers from requiring an employee or applicant to disclose her username, password, or “other means of authentication that provides access to a personal social media account.” It further prohibits employers from requiring that an employee “friend” or otherwise connect with an employer via a social media account, and from compelling the employee to access the account in the employer’s presence such that the employer can view it. A number of other states have passed or are considering similar legislation.

Continue Reading Happy New Year from the Oregon Legislature: New Employment Laws To Watch Out For in 2014

In March 2013, the Portland City Council passed the new Portland Paid Sick Leave Ordinance requiring all but the smallest employers to provide paid sick leave (“PSL”) for employees who work within city limits. On November 1, the city released final regulations interpreting the Ordinance and fleshing out some of the requirements in more detail. Also, the original Ordinance was amended in early October while the regulations were being finalized. The law becomes effective January 1, 2014, so employers with employees in Portland need to review relevant policies to confirm they comply with the new ordinance.

Many of the Ordinance’s requirements will look familiar to employers used to dealing with other leave laws, particularly the Oregon Family Leave Act (“OFLA”). But this Ordinance has its own twists, many of which result from the fact that it’s not a state-wide law like OFLA but instead only applies to employees within Portland. This list of 25 frequently asked questions (“FAQ”) covers many of the the questions employers might have as they work through understanding the Ordinance and update their policies to ensure compliance. Yes, there are really 25 of them.

The Basics

 

1. What does the Ordinance require in 20 words or less?

Employers with six or more employees must allow employees in Portland at least 40 hours of PSL per year.  That’s 19 words!  But of course, there’s a lot more to it than that, so read on.

 Continue Reading Top 25 FAQs Employers May Have About Implementing the New Portland Paid Sick Leave Ordinance in 2014

Last week the Oregon Court of Appeals issued its opinion in Kemp v. Masterbrand Cabinets, Inc., holding that the plaintiff’s common law wrongful discharge claim was not precluded by the statutory remedies then available under Oregon or federal anti-discrimination laws, and that claim could properly be decided by a jury.  The case is another wrinkle in the ever-evolving and complex body of case law trying to define the contours of claims for common law wrongful discharge in Oregon.

Oregon Wrongful Discharge 101: A Quick Primer On When Common Law Wrongful Discharge Claims Can Be Precluded By Statutory Remedies

A claim for wrongful discharge is a common law tort claim developed by Oregon courts.  Many states’ courts have recognized the tort; Oregon’s Supreme Court first did so in the 1970s in Nees v. Hocks.  The specifics about what makes a discharge from employment “wrongful” and therefore tortious hinges on whether the employee’s termination violates an important public policy, usually where an employee is fulfilling an important job-related right or public duty.  As we have blogged about previously, courts have had difficulty wrestling with defining “wrongfulness” in specific cases, and divergent results can make it difficult to clearly understand which public duties and job-related rights are covered by the tort.  For example, being discharged for complaining about the employer’s fire code and safety violations (Love v. Polk County Fire Distr.) has been found wrongful, but a car salesman being fired for complaining about the employer’s allegedly deceptive sales tactics (Lamson v. Crater Lake Motors) or private security guards being fired for restraining or arresting concert-goers suspected of drug use and violent behavior (Babick v. Oregon Arena Corporation) was not.  Further, some courts have held wrongful discharge usually covers only conduct-based discrimination (taking action against an employee because of what they do, commonly known as “retaliation”), not status-based discrimination (based on a protected personal characteristic such as race, gender, or age), although this distinction is often inconsistently applied.Continue Reading Oregon Court of Appeals Continues Debate About Status of Wrongful Discharge Claims In Oregon in Kemp v. Masterbrand Cabinets, Inc.

Coming as no big surprise since other states, like Utah and California, have been passing similar laws, the President of the Oregon Senate recently signed the final version of HB 2654, which will prohibit Oregon employers from compelling employees or applicants to provide access to personal social media accounts, like FaceBook or Twitter.  The law will also keep off limit to employers other sites that allow users to create, share or view user-generated content (like videos, still photos, blogs, videos, podcasts or instant messaging, email or website profiles), and also prohibits requiring that employees allow the boss to join or "friend" them on social media sites.  It also prohibits retaliation against any employee or applicant who refuses to provide access to accounts or to add the employer to his or her contacts list. The law becomes effective in January 2014.

Specifically, under the new law Oregon employers will not be allowed to:

  • Require or ask an employee or applicant to share a username or password allowing access to a personal social media account;
  • Require employees or applicants to add their employers to their contacts or friends lists;
  • Compel employees or applicants to access the accounts themselves to allow the employer to view the contents of a personal social media account;
  • Take or threaten to take any action to discharge, discipline or otherwise penalize an employee who refuses to share their account access information, allow their employer to view content, or add the employer to their contact or friends list (or fail or refuse to hire an applicant for the same things).

Continue Reading Oregon Legislature Passes HB 2654 Prohibiting Employers From Requiring Access To Employee Social Media Accounts

A single Ninth Circuit judge, in his capacity as chair of the Circuit’s Standing Committee on Federal Public Defenders (“the Standing Committee”), recently ruled in the unpublished decision of In the Matter of Alison Clark that the federal Defense of Marriage Act (“DOMA”) and Oregon’s Measure 36 violate the United States and Oregon Constitutions by unlawfully discriminating against same-sex couples.

Alison Clark, a federal public defender in Oregon, married Anna Campbell in Canada in 2012. Clark’s marriage was not recognized in Oregon, due to Measure 36, a ballot initiative passed in 2004 that defined marriage as between only a man and a woman. In addition, the federal government did not recognize Clark’s marriage, as DOMA similarly defines marriage as a legal union between one man and one woman.Continue Reading Ninth Circuit’s Standing Committee on Federal Public Defenders Finds DOMA and Oregon’s Measure 36 to be Unconstitutional

We previously advised you that the Portland City Council was considering an ordinance that would require Portland employers to provide sick leave to employees. The Council voted unanimously to approve the ordinance on Wednesday, meaning that Portland will now join a handful of jurisdictions (including Connecticut, San Francisco, Seattle, and Washington, D.C.) that require employers to give employees time off for illness. Similar bills have also been introduced in the state legislature, although it is too soon to predict whether they will pass.

The Portland ordinance, which takes effect on January 1, 2014, generally requires private employers to provide 40 hours of sick leave per year to eligible employees. For employers with six or more employees, the time must be paid; for smaller businesses, leave may be unpaid. Employers that already provide sick leave equivalent to or in excess of what the ordinance requires do not need to make any changes.Continue Reading Portland City Council Approves Sick Leave Ordinance

Most people understand that employment in Oregon, as in most states, is at will, meaning that either the employer or the employee can end the relationship at any time for any reason or no reason at all, absent a contractual, statutory, or constitutional requirement to the contrary.  Of course, that last clause provides that there are limits on at-will employment.  An employer can’t end the relationship because the employee becomes disabled, needs to fulfill duty obligations in the armed forces reserves, files a complaint against the employer, or a myriad of other unlawful reasons.  Some plaintiff’s lawyers would argue that the at-will employment doctrine is so riddled with exceptions that it doesn’t really exist.  And good employer defense attorneys will advise their clients that, while the doctrine still exists, every termination should be supported by clear, legitimate business reasons – and ideally with good documentation.  But it is clear that no employee can have a reasonable expectation of continued employment, since he or she could be fired at any time.  But what about an applicant?

Suppose an applicant meets with a hiring manager and, after the interview, the manager shakes the applicant’s hand and says “You’re hired!  Come in tomorrow to sign the paperwork.”  The applicant has another offer and the hiring manager encourages him to turn it down.  The applicant does so and, the next day, shows up at his new employer’s offices.  There he is told that they have changed their minds and don’t need him after all.  The applicant is devastated because not only does he not have this job, but the other offer he turned down has already been filled.  The employer, on the other hand, reasons that it could have fired the applicant anyway on his first day on the job under the at-will doctrine, so where is the harm?  The employer argues that if the applicant has a claim, how long does an employer have to employ new hires?   Continue Reading Oregon Supreme Court Takes Another Big Bite Out of the At-Will Employment Doctrine in Cocchiara v. Lithia Motors