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.

For each workday the employer fails to provide an employee with a required thirty-minute<br />

meal period or ten-minute rest break, the employee is entitled to recover one hour of pay at<br />

the employee’s regular rate. 113 Although the statute is unclear on how failure to provide<br />

multiple required meal or rest periods in a single day is punished, the DLSE has taken the<br />

position that one penalty for missed meal periods <strong>and</strong> one penalty for denied rest periods<br />

may be imposed per workday. 114 In 2009, a federal district court in Marlo v. United Parcel<br />

Service 115 analyzed the issue <strong>and</strong> agreed that an employee could recover both a meal<br />

period <strong>and</strong> a rest period penalty in the same workday. 116 However, the court determined<br />

that an employee can recover penalty pay for only one meal <strong>and</strong> only one rest period<br />

violation per day, even if the employee were to miss two meal periods or two rest<br />

periods. 117 This decision runs counter to an earlier district court decision that had<br />

decided—in a less detailed analysis—that an employee could recover penalty pay for only<br />

one violation per day, even if the employee were denied both meal <strong>and</strong> rest periods in the<br />

same workday. 118<br />

In 2011, the <strong>California</strong> Court of Appeal agreed with Marlo in deciding United Parcel Service,<br />

Inc. v. Superior Court. 119 There, the court noted that the legislative history demonstrated<br />

that Section 226.7 was specifically drafted to conform to the IWC wage orders. 120 Because<br />

the wage orders “provide[] a separate remedy for violations of meal period requirements<br />

<strong>and</strong> violations of rest period requirements . . . up to two premium payments are allowed per<br />

work day.” 121 Therefore, it appears that this issue has finally been settled.<br />

Many employers fail to maintain records that comprehensively establish that employees in<br />

fact took their meal <strong>and</strong> rest periods. This is especially the case when an employer has<br />

mistakenly classified a position as exempt, because employers are not required to keep<br />

time records for employees covered by the most common exemptions (administrative,<br />

executive, <strong>and</strong> professional). Section 7 of the <strong>Wage</strong> Orders requires employers to record<br />

meal periods of non-exempt employees, <strong>and</strong> the DLSE generally takes the position that in<br />

the absence of records proving that meal periods were taken, the employees are presumed<br />

113<br />

114<br />

115<br />

116<br />

117<br />

118<br />

119<br />

120<br />

121<br />

Lab. <strong>Code</strong> § 226.7. See, e.g., <strong>Wage</strong> Order 7-2001 §§ 11(D) <strong>and</strong> 12(B).<br />

DLSE Manual § 45.2.8 <strong>and</strong> 45.3.7.<br />

2009 WL 1258491 (C.D. Cal 2009).<br />

Id. at *7.<br />

Id.<br />

Corder v. Houston’s Restaurants, Inc., 424 F. Supp. 2d 1205, 1207 n.2 (C.D. Cal. 2006) (“Section 226.7(b) states that<br />

the employer is liable ‘for each work day’ that a break is not provided. Thus, the plain wording of the statute is clear that<br />

an employer is liable per work day, rather than per break not provided.”).<br />

196 Cal. App. 4th 57 (2011).<br />

Id. at 67-8.<br />

Id. at 68.<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) 31

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

Saved successfully!

Ooh no, something went wrong!