Clements, Mitchell v. WP Operations, LLC

CourtDistrict Court, W.D. Wisconsin
DecidedMay 26, 2021
Docket3:19-cv-01051
StatusUnknown

This text of Clements, Mitchell v. WP Operations, LLC (Clements, Mitchell v. WP Operations, LLC) 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
Clements, Mitchell v. WP Operations, LLC, (W.D. Wis. 2021).

Opinion

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

MITCHELL CLEMENTS, on behalf of himself and all others similarly situated,

Plaintiff, OPINION AND ORDER v. 19-cv-1051-wmc WP OPERATIONS, LLC,

Defendant.

In this putative class and collective action, Mitchell Clements brings suit against WP Operations, LLC, alleging violations of the Fair Labor Standards Act (“FLSA”), 29 U.S.C. § 201 et seq., as well as various Wisconsin labor laws and regulations. Plaintiff’s motion for conditional certification of the FLSA collective action and authorization of notice to similarly situated persons is now before this court. (Dkt. #18.) The court will grant plaintiff’s motion for the reasons discussed below. Subject to minimal alterations, the court will also allow the proposed notice to be posted and sent to potential class members. ALLEGATIONS OF FACT1 Defendant WP Operations runs a mining operation that produces industrial frac sand, including a sand mine located in Hixton, Wisconsin, and two railyards -- one located

1 When considering a motion for conditional certification, the court draws the relevant facts from “the complaint and any affidavits that have been submitted.” Bitner v. Wyndham Vacation Resorts, Inc., 301 F.R.D. 354, 357 (W.D. Wis. 2014) (quoting Austin v. CUNA Mut. Ins. Soc’y, 232 F.R.D. 601, 606 (W.D. Wis. 2006)). “Plaintiffs’ materials are the proper focus at this preliminary stage, not defendants’,” and any factual disputes are resolved in plaintiff’s favor. Id. in Taylor, Wisconsin (the “Taylor railyard”) and one located in Humbird, Wisconsin (the “Humbird railyard”). The Taylor railyard and the Humbird railyard are located two and fifteen miles from the Hixton mine, respectively.

Plaintiff Mitchell Clements worked for WP Operations as a Rail Operator at both the Taylor and Humbird railyards from July 2018 until December 2019. When work in the railyards was slow, he also worked at the Hixton mine. Clements’ position was paid on an hourly basis and non-exempt, meaning that under the FLSA, he was entitled to overtime pay for hours worked in excess of 40 per week. Other hourly, non-exempt

positions involved with WP Operations’ mining production process include Belt Press Operator, Dry Plant Operator, Load Out Operator, Logistics Coordinator, Maintenance Electrician, Maintenance Technician, Mine Utility, Plant Load Operator, Plant Utility Operator, Quality Control Lead, Quality Control Technician, Rail Foreman, Wet Plant Operator, and Working Foreman (collectively, “Production Employees”). WP Operations currently employs approximately fifteen to sixteen Production Employees at its Wisconsin

facilities, but within the last year and a half, it has employed as many as one hundred. Each Production Employee is to report to the foreman and team leader assigned for that position. Two other employees have opted in so far: Wendy Frosland, a Quality Control Technician, and Daniel Pokorny, a Railcar Operator. With respect to Production Employees at all of its Wisconsin locations, including plaintiff Clements, WP Operations: (1) established the work rules, policies, and procedures

by which they are to abide in the workplace; (2) controlled the terms and conditions of their employment; (3) provided them with work assignments and hours of work; (4) established their work schedules; and (5) tracked and recorded their hours of work. As a result, Clements and the other Production Employees frequently worked in excess of forty hours in a workweek.

In the three years before the filing of this lawsuit, all Production Employees were also subject to uniform timekeeping policies and practices. Those policies and practices were communicated in part through the WP Operations Employee Handbook (the “Handbook”), including that: (1) all Production Employees must “report and record all time worked”; and (2) a “failure to be at the work place, ready to work, at the regular

scheduled starting time” could result in discipline “up to and including termination.” (Saso Dep., Ex. 4 (“Handbook”) (dkt. #22-2) 14, 36-37.) WP Operations tracked employee times using Orbit Solutions, an electronic timekeeping system with corresponding software. Clements and other Production Employees used the timeclock to “punch in and out” each workday. The standard scheduled shift for Production Employees began at 5:45am and ended at 6:00pm. In a

written “Time Clock Policy,” WP Operations explained that “[e]ach employee needs to punch the clock within a 7 minute window of either shift start time or shift end time.” (Saso Dep., Ex. 3 (“Time Clock Policy”) (dkt. #22-2) 1.) Thus, Production Employees customarily “punched in” for the start of their shift at 5:38am each workday. Plaintiff further produced declarations from certain Production Employees representing that they performed various work activities immediately after punching in,

including but not limited to attending pre-shift meetings. During these meetings, instructions would be given for daily tasks. For example, John Taylor -- a Rail Team Lead -- would advise his team as to “what we were going to be doing that day, who was going to be working where, and what we were loading.” (Taylor Dep. (dkt. #23) 22:17-20.) All of these pre-shift meetings were either conducted (or at least attended) by a team lead such

as Taylor or a foreman. Taylor himself testified “[r]oughly” every pre-shift meeting that he conducted started before 5:45am. (Id. at 47:23-:25.) Taylor further testified that someone who missed the pre-shift meeting would not be formally disciplined, but would generally get “stuck with the job no one else wanted to do” that day. (Id. at 48:6-:11.) Still, the electronic timekeeping system automatically rounded to an employee’s scheduled

shift time, regardless of actual “punch in and out” times. Accordingly, an employee who clocked in at 5:38am, but whose shift did not begin until 5:45am, would only be compensated beginning at 5:45am. Over the statutory period, the total difference between Clements’ actual clock-in times and the timeclock software’s rounded “calc” times resulted in 27 hours and 32 minutes of uncompensated work to the benefit of WP Operations.2 (Pl.’s Reply (dkt. #34)

6.) Likewise, during the statutory period, the difference between all Railcar Operators’ actual clock-in time and the rounded time totaled roughly 1,555 hours and 18 minutes, to the employees’ detriment. (Id.) The punch-out times mirrored this same trend, with a difference generally favoring WP Operations between the actual and rounded time amounting to 608 hours and 48 minutes for all Railcar Operators. Id. For its part, defendant points to evidence arguably showing that employees did not

2 Under the FLSA, the statutory period for “look back” purposes is three years afte reh cause of action accrued where the cause of action arose from a willful violation. 29 U.S.C. § 255(a). engage in work before 5:45am -- or at least that it did not suffer or permit its employees to work before the beginning of their scheduled shift. Specifically, it explains that the “actual work time” for first shift railyard employees is generally from 6:00am to 6:00pm, but that

employees are paid starting at 5:45am to allow them 15 minutes to prepare for their shift. In particular, defendant points to declarations from Hamilton White, President of WP Operations, and Luke Boortz, WP Operations railyard foreman, who both represent that while employees were permitted to punch in up to seven minutes before their scheduled start time, they were prohibited from working until the scheduled start of their shift. (See

White Decl. (dkt.

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

Related

Hoffmann-La Roche Inc. v. Sperling
493 U.S. 165 (Supreme Court, 1990)
Kellar v. Summit Seating Inc.
664 F.3d 169 (Seventh Circuit, 2011)
Spoerle v. Kraft Foods Global, Inc.
527 F. Supp. 2d 860 (W.D. Wisconsin, 2007)
Jirak v. Abbott Laboratories, Inc.
566 F. Supp. 2d 845 (N.D. Illinois, 2008)
Russell v. Illinois Bell Telephone Co., Inc.
721 F. Supp. 2d 804 (N.D. Illinois, 2010)
Weninger v. Gen. Mills Operations LLC
344 F. Supp. 3d 1005 (E.D. Wisconsin, 2018)
Austin v. Cuna Mutual Insurance Society
232 F.R.D. 601 (W.D. Wisconsin, 2006)
Kelly v. Bluegreen Corp.
256 F.R.D. 626 (D. Wisconsin, 2009)
Bitner v. Wyndham Vacation Resorts, Inc.
301 F.R.D. 354 (W.D. Wisconsin, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
Clements, Mitchell v. WP Operations, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/clements-mitchell-v-wp-operations-llc-wiwd-2021.