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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

facility to the next, or variations in the independent judgment <strong>and</strong> discretion exercised by<br />

employees subject to the “administrative” exemption,” have sometimes been relegated to<br />

the “decertification” stage of a Section 216(b) case, after Dukes these or similar inquiries<br />

may be critical very early, at the first, conditional certification stage.<br />

Likewise, in cases raising the “executive” exemption, plaintiffs often contend that they were<br />

improperly classified because they did not have the authority to make employment<br />

decisions with respect to their subordinates, performed non-managerial tasks as their<br />

primary duty, or otherwise. Courts’ resolution of certification issues based on these<br />

assertions could be based less on anecdotal evidence about the named plaintiffs <strong>and</strong> more<br />

on an analysis of whether there is a common thread tying those occurrences together on a<br />

collective basis.<br />

The Dukes Court also dispelled the notion that the merits of a case may not be considered<br />

during the “rigorous analysis” required to determine if class certification is appropriate. This<br />

could lead to challenges at the conditional certification stage about how much evidence is<br />

enough to extrapolate to the group. In practice, this may mean that the critical merits<br />

question of whether putative class members actually worked off-the-clock, actually failed to<br />

take meal <strong>and</strong> rest periods, or otherwise were subjected to a violation of wage-<strong>and</strong>-hour<br />

law, gets addressed far earlier in the litigation than has been the case until now.<br />

Following Dukes, plaintiffs should now be pressed earlier in litigation to put forth actual<br />

evidence, beyond mere allegations, that issues common to all class or collective action<br />

members exist. From a due process perspective, this requirement could limit much of the<br />

additional burden <strong>and</strong> expense of conducting broad discovery <strong>and</strong> litigating decertification<br />

where there is no evidence issues common to all class or collective action members.<br />

Indeed, this broad discovery is often so costly as to leave employers with little choice but to<br />

settle the case, which explains, at least in part, why employers have seen an explosion of<br />

wage-<strong>and</strong>-hour litigation in the last several years.<br />

Show Me [You Are Owed] The Money<br />

In the less controversial section of its decision, the Dukes Court held that Rule 23(b)(2)<br />

applies only when “a single injunction or declaratory judgment would provide relief to each<br />

member of the class,” not when individuals seek an individual award of monetary damages.<br />

By its very nature, the recovery of money is central to wage <strong>and</strong> hour litigation. Plaintiffs<br />

often argue that damages may be readily quantifiable based on a sample of the employer’s<br />

pay records or that backpay calculations for a r<strong>and</strong>om group of class or collective members<br />

can be utilized to extrapolate the damages on a classwide basis.<br />

Although the setting was different, the Court’s rejection in Dukes of a “Trial By Formula”<br />

approach to class litigation should undermine this formulaic approach to the viability of trials<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) 85

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

Saved successfully!

Ooh no, something went wrong!