Merschdorf, Kyle v. DC Industries Inc.

CourtDistrict Court, W.D. Wisconsin
DecidedNovember 24, 2020
Docket3:19-cv-01037
StatusUnknown

This text of Merschdorf, Kyle v. DC Industries Inc. (Merschdorf, Kyle v. DC Industries Inc.) is published on Counsel Stack Legal Research, covering District Court, W.D. Wisconsin primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Merschdorf, Kyle v. DC Industries Inc., (W.D. Wis. 2020).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE WESTERN DISTRICT OF WISCONSIN

KYLE MERSCHDORF, on behalf of himself and all others similarly situated,

Plaintiff, OPINION and ORDER v. 19-cv-1037-jdp DC INDUSTRIES INC. and DANIEL CAHEE,

Defendants.

Plaintiff Kyle Merschdorf filed this proposed collective and class action against defendants DC Industries Inc., which operates several Domino’s Pizza restaurants in Wisconsin, and Daniel Cahee, DC’s owner and manager. Merschdorf contends that defendants owe DC’s delivery drivers unpaid wages under the Fair Labor Standards Act (FLSA) and Wisconsin wage law. The parties have filed a joint motion for preliminary approval of a proposed settlement of this lawsuit. Dkt. 17. In their motion, the parties seek certification of a collective under 29 U.S.C. § 216(b) and a class under Federal Rule of Civil Procedure 23 for the purpose of settlement, along with appointment of a class representative and class counsel and approval of a class notice. The court will grant the motion with a modification, direct Merschdorf to send notice to the collective and class members, set a deadline for a motion for final approval, and set a date for a telephonic fairness hearing. ANALYSIS Merschdorf seeks to bring claims on behalf of himself and other DC delivery drivers under the FLSA and Wisconsin wage law. He contends that defendants violated the FLSA and Wisconsin wage law in three ways: (1) defendants required drivers to use their own vehicles for deliveries without reimbursing them for costs such as gasoline, insurance, and maintenance, which caused drivers’ effective hourly pay to fall below the minimum wage; (2) defendants paid drivers an effective hourly rate below the minimum wage when they performed in-store duties such as preparing food and assisting customers; and (3) defendants took tip credits on drivers’

wages—that is, they paid drivers at an hourly rate below the minimum wage based on the drivers’ tips—without obtaining signed tip declarations from the drivers. The first two claims are based on both the FLSA and Wisconsin wage law, and the third is based solely on Wisconsin wage law. Collective actions under the FLSA are governed by 29 U.S.C. § 216(b); class actions under Wisconsin wage law are governed by Rule 23. The primary difference between the two standards is that employees must opt in to a collective, but they must opt out of a class. See Espenscheid v. DirectSat USA, LLC, 705 F.3d 770, 771 (7th Cir. 2013). Plaintiffs are permitted

to join a collective action under the FLSA with a class action, and “the case law has largely merged the standards” for the two types of actions with merely “terminological differences.” Id. at 772. So the court may treat both suits “as if [they] were a single class action” under Rule 23 for the purposes of certification. Id. The court has subject-matter jurisdiction over Merschdorf’s FLSA claim under 28 U.S.C. § 1331 because it arises under federal law, and the court may exercise supplemental jurisdiction over his state-law claim under 28 U.S.C. § 1367 because it is part of the same case or controversy.

A. Collective and class certification The parties propose the following definition for both the proposed state-law class and the proposed FLSA collective for the purpose of settlement: All current and former hourly-paid, non-exempt Delivery Driver employees employed by Defendants within the two (2) years immediately preceding the filing of the complaint. Dkt. 17-1, at 1–2. Although the parties have settled, the court must still certify that the proposed class satisfies Rule 23’s requirements. There are three requirements for class certification under Rule 23: (1) the class must be clearly defined with objective criteria, Mullins v. Direct Digital, LLC, 795 F.3d 654, 657 (7th Cir. 2015); (2) the class must satisfy the threshold requirements of numerosity, commonality, typicality, and adequacy of representation under Rule 23(a); and (3) the class must meet the requirements of at least one of the types of class actions listed in Rule 23(b). The parties have satisfied the first requirement because they have clearly defined a class that can be identified using objective criteria: the class includes all delivery drivers who worked for defendants within a two-year period, were paid on an hourly basis, and weren’t exempt

from minimum-wage requirements. Defendants didn’t challenge delivery drivers’ non-exempt status in their answer, see Dkt. 9, ¶ 35, so defining class membership in terms of exemption status doesn’t make the class a so-called “fail-safe class,” in which class membership is improperly defined by success on the merits. See Mullins, 795 F.3d at 660. Numerosity requires the proposed class to be so numerous that joinder is impracticable. Fed. R. Civ. P. 23(a). The court of appeals has deemed classes of 40 members to be sufficient. See Swanson v. Am. Consumer Indus., Inc., 415 F.2d 1326, 1333 n.9 (7th Cir. 1969). The parties say that there are approximately 37 members in the class, and they submit a list of 37 class

members and their proposed awards. Dkt. 17-1, at 19. The parties contend that joinder of the class would be impracticable because forcing class members “to relitigate the common issues present in this case would unnecessarily increase the cost of litigation.” Dkt. 18, at 13. And several of the claims are of low value; many of the class members stand to receive awards of less than $500, with five of them below $100. See Dkt. 17-1, at 19. Although the class is not especially large, the court concludes that joinder would unnecessarily increase the cost of litigation, particularly for class members with low-value claims. So the numerosity requirement

is satisfied. Commonality requires that the action involve “questions of law or fact common to the class.” Fed. R. Civ. P. 23(a)(2). In other words, a proposed class meets this requirement if “determining the truth or falsity of [a] common contention will resolve an issue that is central to the validity of each claim.” Chi. Teachers Union, Local No. 1. v. Bd. of Educ., 797 F.3d 426, 434 (7th Cir. 2015). The claims in this case involve several common questions, all of which would share common answers: whether defendants reimbursed drivers for their driving expenses; whether drivers performed untipped in-store duties such as food preparation, and

whether defendants adjusted their wages to account for this work; and whether defendants obtained tip declarations from drivers before taking tip credits. The determination of these issues, regardless of outcome, will resolve the allegations of the entire class. So the requirement of commonality is satisfied. Typicality requires the class representative’s claims to be typical of the claims of the proposed class.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
Merschdorf, Kyle v. DC Industries Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/merschdorf-kyle-v-dc-industries-inc-wiwd-2020.