BARBARA B. CRABB, District Judge.
This is a civil action for monetary relief under the Fair Labor Standards Act (FLSA), 29 U.S.C. §§ 201-219, and Wisconsin overtime compensation laws. Plaintiff Jacob Lewis contends that defendant Epic Systems Corporation misclassified him and other technical writers as exempt from overtime wages and failed to pay them wages of one and one-half times their regular rates of pay for any overtime hours that they worked. The proposed collective includes technical writers employed by defendant as of April 2, 2014, when defendant disseminated an arbitration agreement allegedly applicable to wage claims. (Another former employee of defendant has filed a similar collective action on behalf of technical writers whose employment ended before April 2, 2014.
In 2015, I concluded that the arbitration agreement at issue this case was invalid and stayed proceedings in this case (but not in
After considering the arguments of the parties and conducting an independent review of the declarations and other documents in the record, I conclude that plaintiff has met his burden of showing "modest" proof that some factual nexus connects him to other potential plaintiffs as victims of an unlawful practice. Although there are individual variations in the employment experiences of the members of the putative collective, at its heart, the inquiry in this case is whether plaintiffs are exempted from overtime wages under federal law by their primary job duties and the practices and processes applied to all technical writers. Accordingly, I am granting plaintiff's motion to conditionally certify the FLSA collective action and notify potential members of the existence of this lawsuit.
Plaintiff's proposed notice, consent form and response period appear reasonable, dkt. #71, exh. #1, but defendant did not object or otherwise respond to them, presumably waiting for a ruling on the underlying motion for conditional certification. Therefore, I will allow defendant an opportunity to file any objections it may have to the content and method of the proposed notice and consent form.
In determining whether the class should be certified conditionally, I have considered the allegations in the complaint and the affidavits, documents and deposition transcripts attached to the parties' briefs.
Defendant Epic Systems Corporation makes software applications for medical groups, hospitals and integrated healthcare organizations. It employs more than 100 technical writers, who are members of the Technical Communications group and supervised by "team leads."
Named plaintiff Jacob Lewis and opt-in plaintiffs Charles Blackburn, Karen Campbell, Dale Erlandson, Emily Harris, Rebecca Rodgers and Lauren Weber all worked as technical writers for defendant on or after April 2, 2014, in one or more of the following application areas: clinical inpatient (healthcare in inpatient settings), clinical ambulatory (healthcare in outpatient settings) and revenue and reporting (billing, accounting and practice management). Defendant's customers may use applications from any or all of these areas. The applications cover a wide range of topics, may have different functions and are used by different types of health care professionals and administrators.
Lewis and many of the opt in plaintiffs describe their primary duty as producing or revising standardized documents that describe how defendant's software works. These descriptions are derived from templates and instructions and information provided by defendant's software developers, implementers and trainers. Defendant has one job description for the position of technical writer, which states that "you'll create documentation about the nuts and bolts of our world class software."
Technical writers provide different types of written materials or "deliverables" for different audiences and specialize in particular applications. For example, implementation writers prepare written materials targeted to analysts working for a customer who is installing software for the first time. Support writers develop written materials for analysts who are maintaining and updating an application. Training writers develop written materials that teach end-users, such as clinicians and administrators, how to use software applications. Technical writer may work on a special project or spend some amount of their time on nonwriting tasks.
The opt-in plaintiffs all followed the same process in producing written materials for defendant. After receiving writing assignments from their team leads or defendant's project management software program, EMC2, they gathered information from subject matter experts, which include defendant's software developers, implementers or trainers. Technical writers then prepared written documents by inserting the information that they gathered into templates. Defendant controlled both the content and language of the written materials to insure consistency and the individual writer's anonymity. Its style guide outlines the terms, format, conventions and other writing rules to be used by technical writers. In addition, technical writers rely on defendant's intranet (or "wiki"), which contains step-bystep instructions on what information to include in written documents. Subject matter experts reviewed all completed deliverables for accuracy and other technical writers reviewed them for compliance with defendant's writing standards.
Since creating the technical writer position over 20 years ago, defendant has classified technical writers as salaried, exempt employees and pays them similar starting salaries. Defendant did not assess the work of individual technical writers to determine whether different technical writers should be classified as exempt. Technical writers consistently worked over 40 hours a week, and defendant made clear that it expected them to do so.
Defendant used a standard set of criteria to evaluate prospective technical writers and provided new technical writers the same training. All of the opt-in plaintiffs attended "Epic 360" (an orientation week for all new hires), an "App Camp" (classes on specific Epic software applications), "Tech Boot Camp" (information on producing deliverables) and "Writing at Epic" (instruction about defendant's writing conventions).
Under the Fair Labor Standards Act (FLSA), employees are entitled to overtime pay equal to one and one-half times their regular rate of pay for any hours worked in excess of forty hours per week, unless they come within one of the various exemptions set forth in the Act. 29 U.S.C. §§ 207(a), 213.
If an employer does not provide required overtime pay, the statute authorizes an employee to bring suit against his or her employer, not only on behalf of him or herself, but also on behalf of other "similarly situated" employees. 29 U.S.C. § 216(b);
This court applies a two-part test to determine whether an FLSA claim may proceed as a collection action.
The parties are at the first stage of this process. Plaintiffs are seeking conditional certification of the following class:
Dkt. #70 at 4. Contrary to defendant's assertion, plaintiff has not included the position of team lead in the collective action and apparently is not seeking damages for the period of time that he or others worked as a team lead.
Plaintiff has alleged that he and other technical writers were all subject to the same unlawful practice because defendant made a general decision to classify technical writers as exempt, expected all technical writers to work overtime and did not pay any of them overtime wages for the hours they worked in excess of 40 in a work week. Defendant contends that plaintiff cannot meet the requirements for conditional certification because determining whether technical writers were characterized properly as exempt requires a series of individualized determinations that cannot be satisfied through representative proof. For example, defendant asserts that technical writers are exempt from overtime pay as administrative employees whose "primary duty" (1) is "[t]he performance of office or non-manual work directly related to the management or general business operations of the employer or the employer's customers;" and (2) includes "the exercise of discretion and independent judgment with respect to matters of significance." 29 C.F.R. § 541.200(a)(2) and (3). It also argues briefly that at least some of the putative class members may qualify for the "highly compensated worker exemption" or the "computer employee exemption" of the basis of their job duties and salary. Defendant then goes to great lengths to point out that the potential members of the collective action had different primary job duties because they spent different amounts of time performing non-writing tasks, provided different types of writing for different software applications, wrote for different audiences, managed different special projects and exercised different levels of discretion and independent judgment.
Individual circumstances are inevitably present in a collective action. In some circumstances, the individualized nature of the plaintiffs' claims may make certification inappropriate. However, I have rejected the notion that individualized differences preclude conditional certification at the first stage of the conditional certification analysis.
In support of conditional certification, plaintiff has presented seven declarations from putative class members describing similar employment settings. Defendant criticizes plaintiff for offering "only a collection of vague and mostly boilerplate declarations" that "do not offer any account of their actual job duties or how the declarants actually spent their time, both of which are required to determine exempt status." Dkt. #78 at 15. I am not persuaded by defendant's challenges to the small number of declarations or their content. As I stated in
The declarations suggest that all of defendant's technical writers had the same basic responsibility of developing written documents related to software and that they performed that function in essentially the same way, using company-mandated processes and templates. The opt-in plaintiffs all explain that after receiving a writing assignment, they created a written deliverable to explain various aspects of a software application using standardized style guides and templates and submitted their documents for review and approval. Plaintiff has supported these statements with defendant's internal documents describing the uniform nature of a technical writer's work, implying that defendant viewed technical writing as a common function regardless of the topic. The evidence also shows that putative class members had the same job description, worked in the same job position in the same department, received the same training, were recruited and hired according to common criteria and generally performed the same function of producing defendant's standardized documents in conformance with templates and rules. In fact, much of the evidence submitted by plaintiff is the same as I found sufficient to defeat defendant's motion for decertification in
As I found in
In sum, because plaintiff has made a colorable showing that he is similarly situated to the putative class members with respect to nonpayment of overtime pay, I will grant his motion for conditional certification of the class proposed in the complaint and allow him to notify potential members of the class.
IT IS ORDERED that plaintiff Jacob Lewis's motion for conditional certification of the FLSA collective action and court-authorized notice, dkt. #69, is GRANTED. Defendant shall have until October 21, 2016 to file any objections it may have to the content and method of the proposed notice and consent form, and plaintiff shall have until October 28, 2016 to respond.