U.S. EQUAL EMPLOYMENT OPPORTUNITY COMMISSION v. MCLANE COMPANY, INC.
No. 13-15126
United States Court of Appeals, Ninth Circuit
October 27, 2015
804 F.3d 1051
Argued and Submitted March 12, 2015.
With respect to subsection (a)(2), the majority finds that the words “that is,” when read together with the rest of the contract, demonstrate that the list of claims for which sovereign immunity has been waived is non-exhaustive.
The phrase “that is” is commonly thought of as a shorthand version of the phrase “that is to say.” It is used to preface a more specific delineation of the preceding contractual language. Here, to further clarify the limitation of the waiver, the parties stated, “that is, only injunctive, specific performance, including enforcement of a provision of this Compact requiring payment of money to one or another of the parties, or declaratory relief is sought ....” (emphasis added). The use of the word “only” is routinely defined to mean alone, solely or exclusively. The monetary damages awarded here do not qualify as injunctive, specific performance or declaratory relief. Because the law demands that waivers of sovereign immunity ordinarily derive only from “the most express language” or “such overwhelming implications from the text as [will] leave no room for any other reasonable construction,” there can be no waiver found here. Edelman v. Jordan, 415 U.S. 651, 673, 94 S.Ct. 1347, 39 L.Ed.2d 662 (1974) (citation and internal quotation marks omitted) (alteration in original). I find no other implications from the text, and certainly not overwhelming implications, of sovereign immunity waiver.
James Tucker (argued), Attorney, P. David Lopez, General Counsel, Lorraine C. Davis, Acting Associate General Counsel, Daniel T. Vail, Acting Assistant General Counsel, U.S. Equal Employment Opportunity Commission, Washington, D.C., for Plaintiff-Appellant.
Ronald E. Manthey (argued) and Ellen L. Perlioni, Morgan, Lewis & Bockius Before: J. CLIFFORD WALLACE, MILAN D. SMITH, JR., and PAUL J. WATFORD, Circuit Judges.
OPINION
WATFORD, Circuit Judge:
This is a subpoena enforcement action brought by the Equal Employment Opportunity Commission (EEOC) against McLane Company. The EEOC is investigating a charge of sex discrimination filed against McLane by one of its former employees, who was fired when she failed to pass a strength test after returning from maternity leave. The subpoena seeks information about the company‘s use of the test and the individuals who have been required to take it. The main issue before us is whether the district court correctly held that some of the information sought by the subpoena is not relevant to the EEOC‘s investigation. The court refused to enforce that portion of the subpoena, and the EEOC has appealed.
I
In January 2008, Damiana Ochoa, a former employee of a McLane subsidiary in Arizona, filed a charge with the EEOC alleging sex discrimination (based on pregnancy) in violation of Title VII of the Civil Rights Act of 1964. Ochoa alleged that when she tried to return to work after taking maternity leave, McLane informed her that she could not resume her position as a cigarette selector—a position she had held for eight years—unless she passed a
The EEOC notified McLane of Ochoa‘s charge and began an investigation. During the early stages of the investigation, McLane disclosed that it uses the strength test at its facilities nationwide for all positions that are classified as physically demanding. All new applicants for such positions and employees returning to such positions from a leave longer than 30 days are required to pass the test as a condition of employment.
McLane voluntarily provided general information about the test and the individuals who had been required to take it at the Arizona subsidiary where Ochoa worked. That information included each test taker‘s gender, job class, reason for taking the test, and score received (pass or fail). However, McLane refused to disclose what the parties have referred to as “pedigree information” for each test taker (name, social security number, last known address, and telephone number). Instead of identifying the test takers by name and social security number, McLane identified them only by an “employee ID number” created solely for purposes of responding to the EEOC‘s investigation. McLane also refused to disclose, for those employees who had taken the test and were later terminated, when and why their employment was terminated.
The EEOC eventually expanded the scope of its investigation to include all McLane facilities nationwide within the grocery division (the division in which Ochoa worked), since all of those facilities used the same test for the same purposes. The EEOC sought the same information described above for each of the test takers at McLane‘s facilities nationwide. McLane ultimately provided most of that information, but it again refused to provide either pedigree information or, for those test takers who were ultimately terminated, the reasons for termination.
The EEOC then issued an administrative subpoena demanding production of the withheld information. McLane petitioned the EEOC to revoke or modify the subpoena, but the agency denied the petition. Upon McLane‘s continued refusal to provide the disputed information, the EEOC filed this subpoena enforcement action.
The district court granted in part and denied in part the EEOC‘s request for enforcement. The court required McLane to disclose the following information: the gender of each test taker, the date the test was given, the score the test taker received, the position for which the test was taken, the passing score for the position in question, and any adverse employment action imposed within 90 days of an employee‘s taking the test. (McLane had already provided some, but not all, of that information.) The court refused to enforce the subpoena to the extent it required McLane to divulge two categories of information: (1) the pedigree information for each test taker; and (2) for those employees who were terminated after taking the test, the reasons for termination. With respect to the pedigree information, the court concluded that the EEOC did not need such information to determine whether McLane had used the test to discriminate on the basis of sex. Thus, in the court‘s view, the information was not relevant at this stage of the EEOC‘s investigation. With respect to the reasons for termination, the court did not explain why it refused to require production of that information. However, in a parallel subpoena enforce-
II
Title VII grants the EEOC broad power, within specified limits, to investigate potential violations of the statute. The agency‘s investigative authority is triggered by the filing of a charge alleging that an employer has engaged in employment practices made unlawful by the statute. A charge may be filed either by an EEOC Commissioner or, as in this case, by “a person claiming to be aggrieved.”
Once the EEOC receives a charge, the statute states that the agency “shall make an investigation thereof.”
When an employer refuses to comply with the EEOC‘s requests for information, as occurred here, the EEOC may issue an administrative subpoena and bring an enforcement action to compel compliance.
III
With that background in mind, we turn to the specifics of the dispute before us. McLane does not contest that the EEOC has followed the proper procedural requirements. Nor can it seriously contest that the subpoena relates to a matter within the EEOC‘s investigative authority, since Ochoa‘s charge alleges discrimination in employment on the basis of sex. See
A
We begin with the district court‘s refusal to compel production of the pedigree information, which the court held is not relevant at this stage of the EEOC‘s investigation.
The relevancy limitation imposed by
Under this standard, we think the pedigree information is relevant to the EEOC‘s investigation. Ochoa‘s charge alleges that McLane‘s use of the strength test discriminates on the basis of sex. To decide whether there is any truth to that allegation, the EEOC can of course speak to Ochoa about her experience with taking the test. But the EEOC also wants to contact other McLane employees and applicants for employment who have taken the test to learn more about their experi-
McLane raises a series of arguments resisting this that Ochoa‘s charge alleges only a disparate impact claim, not a pattern-or-practice disparate treatment claim. That assertion is wrong. Ochoa‘s charge does not allege discrimination based on any particular legal theory, and it did not need to do so. See EEOC v. Kronos Inc., 620 F.3d 287, 300 (3d Cir. 2010). A charge is valid if it is sufficiently precise “to describe generally the action or practices complained of.”
Second, McLane contends that, given all of the other information it has produced, the EEOC cannot show that production of the pedigree information is “necessary” to complete its investigation. But the governing standard is not “necessity“; it is relevance. If the EEOC establishes that the evidence it seeks is relevant to the charge under investigation, we have no warrant to decide whether the EEOC could conduct the investigation just as well without it. The EEOC does not have to show a “particularized necessity of access, beyond a showing of mere relevance,” to obtain evidence. University of Pennsylvania v. EEOC, 493 U.S. 182, 188, 110 S.Ct. 577, 107 L.Ed.2d 571 (1990). Congress has not left it to employers accused of discrimination to decide what evidence may be necessary for the EEOC to complete its investigation. Id. at 193.
For similar reasons, the district court erred when it held that pedigree information is irrelevant “at this stage” of the investigation. The court reasoned that the evidence McLane has already produced “will enable the E.E.O.C. to determine whether the [strength test] systematically discriminates on the basis of gender.” The court suggested that if the EEOC‘s analysis of that evidence reveals systemic discrimination, the pedigree information might become relevant and obtaining that information might then be “necessary.” The EEOC argues that the district court improperly required it to substantiate the allegation of systemic discrimination before it could obtain access to relevant evidence. We doubt that is what the district court meant, as the Supreme Court has made plain that courts may not condition enforcement of EEOC administrative subpoenas on a threshold evidentiary showing that the allegations under
Finally, McLane contends that the pedigree information is not relevant because Ochoa‘s charge alleges only a “neutrally applied” strength test, which by definition cannot give rise to disparate treatment, systemic or otherwise. McLane‘s argument misconstrues the charge. Ochoa alleges that McLane requires all employees returning from medical leave to take the strength test before they can return to work, but she does not allege that the test is neutrally applied. (She alleges just the opposite—that the test was discriminatorily applied as to her.) Even though McLane requires everyone to take the test, the test could still be applied in a discriminatory manner—if, for example, the company were to routinely excuse the failure of male employees to pass the test but grant no such exemptions to similarly situated female employees. The very purpose of the EEOC‘s investigation is to determine whether the test is being neutrally applied; the EEOC does not have to take McLane‘s word for it on that score. See Merritt v. Old Dominion Freight Line, Inc., 601 F.3d 289, 296-99 (4th Cir. 2010).
One additional note is in order regarding the EEOC‘s request for social security numbers. The EEOC seeks that information so that it can accurately identify individual test takers in the data sets it has received from McLane. As explained above, other employees’ experiences might cast light on the allegations against McLane, whether by substantiating them or showing them to be unfounded. Information that helps the EEOC determine whom to contact to learn more about McLane‘s use of the test is therefore relevant to the investigation. McLane contends that the employee ID numbers should suffice for these purposes, but that is not McLane‘s call to make. Furthermore, McLane does not assert any undue burden associated with producing this information, nor could it, for the original data sets contain employee social security numbers. If anything, McLane has imposed an extra burden on itself by removing that information from the data sets before producing them to the EEOC.
McLane suggests in a footnote that it is simply attempting to protect its employees’ privacy interests by withholding their social security numbers, but the Supreme Court has already rejected an analogous argument. See University of Pennsylvania v. EEOC, 493 U.S. 182, 192-93, 110 S.Ct. 577, 107 L.Ed.2d 571 (1990). Congress has struck the balance between granting the EEOC access to relevant evidence and protecting confidentiality interests by imposing strict limitations on the public disclosure of information produced during the course of an EEOC investigation. Id.; see
B
That leaves the second category of information in dispute: the reasons for
We do not think it would be prudent for us to address the undue burden issue in the first instance. We therefore vacate the district court‘s order denying enforcement of the subpoena‘s request for the reasons for termination, and remand so that the district court can rule on whether requiring McLane to produce that information would in fact be unduly burdensome.
REVERSED in part, VACATED in part, and REMANDED.
M. SMITH, Circuit Judge, concurring:
I concur in the majority opinion. I write separately to discuss McLane‘s suggestion that it was justified in withholding its employees’ Social Security Numbers to protect their privacy interests. The majority opinion rejects that argument, following University of Pennsylvania v. EEOC, 493 U.S. 182, 110 S.Ct. 577, 107 L.Ed.2d 571 (1990). It bears noting, however, that University of Pennsylvania predates the rash of “data breach” incidents that plague a world interconnected by computers.
Of particular relevance is the United States government‘s dismal performance in protecting even its own employees’ sensitive data. See, e.g., Office of Personnel Management Cybersecurity Resource Center, Cybersecurity Incidents, “What Happened,” https://www.opm.gov/cybersecurity/cybersecurity-incidents/#WhatHappened (detailing the discovery in June, 2015 of the theft from the Office of Personnel Management of 21.5 million Social Security Numbers, an undisclosed number of interview records, 5.6 million fingerprints, and an undisclosed number of usernames and passwords).
Thus, it may be that the EEOC‘s insistence here on obtaining Social Security Numbers and other information that could be used to steal an employee‘s identity will endanger the very employees it seeks to protect. While we, as a court, are not in a position in this case to weigh the concerns present in any particular data gathering and storage protocol, the EEOC would be well advised to consider these issues in the collection of data in this case.
