05.07.2014 Views

Litigating California Wage & Hour and Labor Code Class Actions

Litigating California Wage & Hour and Labor Code Class Actions

Litigating California Wage & Hour and Labor Code Class Actions

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The implications are significant for class actions because it is much more difficult for<br />

plaintiffs to argue that common issues predominate in a case if the employer can defend<br />

itself merely by establishing that individual employees have had a bona fide opportunity to<br />

take a meal break. By contrast, under the “m<strong>and</strong>atory” interpretations, the employer is very<br />

limited in its ability to raise individualized issues as to why the employees failed to take their<br />

meal breaks. If they failed to do so a jury could assess on a collective basis whether the<br />

employer made sufficient efforts to force them to take the meal period <strong>and</strong> enter a verdict<br />

for the class if the employer’s efforts were inadequate.<br />

Aside from the issue of class action liability, a “m<strong>and</strong>atory” interpretation would also require<br />

employers to overhaul oversight of employee meal breaks. In order to comply with the law,<br />

employers would have to implement systems to ensure employees take a full thirty-minute<br />

break. Employers would need to upgrade timekeeping systems <strong>and</strong> even discipline<br />

employees for not taking a full meal period. Without oversight, opportunistic employees<br />

might take a twenty-five minute break <strong>and</strong> then later claim an hour’s worth of pay, because<br />

the break did not last the m<strong>and</strong>ated thirty minutes.<br />

For years, the only published <strong>California</strong> decision to address the issue was Cicairos v.<br />

Summit Logistics, Inc. 130 The Cicairos decision held that an employer has an “affirmative<br />

obligation to ensure that workers are actually relieved of all duty” by taking a meal break.<br />

The Cicairos court further held that an employer cannot simply “assum[e] that the meal<br />

periods are taken.” 131 The court suggested that the st<strong>and</strong>ard for meal periods was akin to<br />

the st<strong>and</strong>ard of when an employer must pay overtime—i.e., when it either suffered or<br />

permitted the employee to work. The court found that the defendant did not “provide” meal<br />

breaks, because the plaintiff-truckers were deprived of a meaningful ability to elect to take<br />

breaks due to pressure from management to maximize deliveries, the lack of a<br />

companywide policy on meal periods, <strong>and</strong> the fact that the plaintiffs would be penalized for<br />

taking meal breaks as the timekeeping system was unable to record meal breaks. 132<br />

The Cicairos court did not define the scope of “relieving employees of all duty” <strong>and</strong> the term<br />

is subject to multiple possible interpretations. What if the employer scheduled a period<br />

each day within which the employee was told that he or she had no duty to perform any<br />

work? That sounds like it amounts to “relieving” the employee of duty, <strong>and</strong> an employee<br />

who chooses to work in that situation would have no claim for meal period penalty pay.<br />

What if the employee worked without supervision, the employer instructed the employee to<br />

take meal periods, <strong>and</strong> the employee failed to notify the employer that he had skipped meal<br />

breaks? These facts would seem to indicate that the employer neither “suffered nor<br />

130<br />

131<br />

132<br />

133 Cal. App. 4th 949 (2005).<br />

Id. at 962.<br />

Id. at 964.<br />

Seyfarth Shaw LLP | www.seyfarth.com <strong>Litigating</strong> <strong>California</strong> <strong>Wage</strong> & <strong>Hour</strong> <strong>Class</strong> <strong>Actions</strong> (12th Edition) 34

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!