Thread regarding Oracle Corp. layoffs

Federal Layoff Law - 90-day Aggregation

When assessing whether there will be a sufficient number of employees suffering an employment loss to trigger WARN, an employer must be cognizant of WARN’s 90-day aggregation rule. Under this rule, separate layoffs during a 90-day period at a single site, each of which is less than the minimum number of employees required to trigger WARN, but which in the aggregate exceed that minimum number, are presumed to be part of the same plant closing or mass layoff. The employer can rebut the presumption by demonstrating the employment losses are the result of separate and distinct actions and causes and not an attempt by the employer to evade WARN. 29 USC §2102(d).

In Morton v. Vanderbilt University, 809 F3d 294 (6th Cir. 2016), the U.S. Court of Appeals for the Sixth Circuit recently examined whether two separate layoffs were within 90 days and, therefore, subject to WARN under its aggregations provision. Plaintiffs were a group of 194 individuals terminated by defendant in July 2013. The number of individuals terminated in July 2013 was insufficient to constitute a mass layoff under WARN. A second group consisting of an additional 279 employees of defendant was notified on Sept. 17, 2013. that their jobs would be eliminated 60 days later, on Nov. 16, 2013. Although the individuals in the second group were told to no longer report to work effective immediately, they continued to receive pay and benefits until November 2013. The district court held the second layoff occurred when the termination notices were given in September—less than 90 days after the first layoff—and therefore both layoffs were subject to WARN under its aggregation provision.

The Sixth Circuit reversed, holding the date of the second layoff was not until Nov. 16, 2013, and, since such date was more than 90 days from the plaintiffs’ terminations, the second layoff could not be aggregated to meet the mass layoff definition under WARN. The court held that for so long as the second group of employees continued to receive their full pay and benefits, there had not been a permanent cessation of employment. The Sixth Circuit noted there is no obligation under WARN for employers to permit employees to continue to perform work after proper notice is given.

by
| 4692 views | | 8 replies (last August 17, 2017) | Reply
Post ID: @OP+ONqWui9

8 replies (most recent on top)

WARN act requires the employer to provide the 60-day notice to the employee. If the company fails to do that, it has to pay the employee the damages - 60 day of pay plus all the regular benefits. Many companies actually opt to do just that and this practice is called "payment in lieu of WARN". For example, since Oracle already provides four weeks of pay as the part of the package, they would only have to add roughly a month of pay and extend the paid COBRA coverage accordingly to avoid giving WARN notice regardless of the number of people being laid off.

So basically, Oracle's reasoning for going with small layoffs is to save money, not to avoid bad publicity.

by
| | Reply
Post ID: @1ajk+ONqWui9

Someone correct me if I am wrong. But I am not convinced by people's interpretation of WARN here.

I found two versions of WARN by googling. One from federal and the other from state California.

Federal:

Plant closings involving 50 or more employees during a 30-day period require notice. Layoffs within a 30-day period involving 50 to 499 full-time employees constituting at least 33 percent of the full-time workforce at a single site of employment requires notice. Layoffs of 500 of more employees are covered regardless of the percentage of workforce (29 USC, et seq., 2101 and 20 CFR 639.3).

State California:

Plant closings, layoffs or relocation of 50 or more employees within a 30-day period regardless of the percentage of workforce requires notice. Relocation is defined as a move to a different location more than 100 miles away (California Labor Code Section 1400 (c) and (d)).

But neither of them mentions 90 days. Also I heard cases where Oracle was able to overturn lawsuits by asserting that layoff happens actually 60 days later when the employees were removed from company. This means August 3rd layoff in ZFS group may not prevent Oracle from laying off people in August. Oracle law teams are really dangerously creative in interpreting WARN acts.

by
| | Reply
Post ID: @1uai+ONqWui9

Wow, that's pretty clever on their part. Too bad they can't be that clever when it comes to competing in the cloud! Hopefully some folks will benefit from their same mistake this time around.

by
| | Reply
Post ID: @1gvh+ONqWui9

They actually screwed up back in January and laid off enough people in SCA to trigger a WARN. To get around this, they kept some people in the payroll system an extra couple of months and told them to stay home. That's why a number of folks who were RIF'd didn't get removed from ARIA until April.

by
| | Reply
Post ID: @1nkg+ONqWui9

Oracle has lots of experience dealing with this. They've had plenty of layoffs, but I don't recall one ever triggering a WARN notice, at least not on the hardware side of things. I think most people assume a layoff of more than 50 employees at a site will trigger a WARN notice, but I don't believe that's completely true. The number can be as high as 499 as long as the number is less than 1/3 of the employees at that site. Trust me, if there's a way around this, Oracle will find it. They may not be the best at technology, but you certainly have to give them credit when it comes to accounting and legal.

by
| | Reply
Post ID: @1uvj+ONqWui9

So it might pay to be laid of at the end of a 90 day period, so they could WARN your group, pushing the effective layoff out into the next quarter, rather than have everyone in the 90 days aggregated and bump over the limit.

Not sure this would help the Austin or Broomfield sites. Maybe SCA.

by
| | Reply
Post ID: @enr+ONqWui9

No. Reread WARN act and prior threads about severance.

by
| | Reply
Post ID: @kwj+ONqWui9

so if O send us all home we get 90 days pay plus a week for every year spent at O?

by
| | Reply
Post ID: @fpy+ONqWui9

Post a reply

: