About Us  |  About IntelliConnect®  |  Contact Us

WKL&B WorkDay Blog

Subscribe to the Employment Law Daily RSS Subscribe

Proposed Equal Pay Report would be ineffective and is not needed, according to NELI experts

November 21st, 2014  |  Cynthia L. Hackerott  |  Add a Comment

The OFCCP’s proposed Equal Pay Report will not be effective in meeting the goals stated by the agency and it is not needed, retired attorney David Copus told the audience at the National Employment Law Institute’s (NELI) Thirty-Second Annual Affirmative Action Briefing in Chicago, Illinois. Noting that compensation is the number one focus of the OFCCP, Copus, along with John C. Fox, a former OFCCP official and current president of Fox, Wang & Morgan P.C. in San Jose, California, discussed the OFCCP’s current initiatives regarding compensation discrimination, focusing in particular on the proposed Equal Pay Report and the OFCCP’s newly revised audit scheduling letter.

Equal Pay Report proposal. Current regulations require that all employers in the private sector with 100 or more employees, and some federal contractors with 50 or more employees, annually file the EEO-1 Report with the Joint Reporting Committee (a joint committee consisting of the EEOC and the OFCCP). Under a proposed rule published in the Federal Register on August 8, 2014 (79 FR 46562- 46606) with corrections published on August 20 (79 FR 49260-49261), some covered federal contractors and subcontractors would also be required to electronically submit an annual “Equal Pay Report” on employee compensation. The OFCCP’s proposal would revise its regulations at 41 CFR Part 60-1, which set forth the reporting obligations of covered federal contractors and subcontractors under Executive Order (EO) 11246.

Coverage. The Equal Pay report would be required of prime contractors and first-tier subcontractors who file EEO-1 Reports, have more than 100 employees, and a contract, subcontract, or purchase order amounting to $50,000 or more that covers a period of at least 30 days, including modifications. The OFCCP estimates this new reporting obligation would cover about 21,251 contractors and 67,578 establishments. Copus pointed out that about 48,422 establishments – 42 percent of all establishments subject to OFCCP audit – would not be covered under the proposal. In addition, the proposal would not cover: (1) educational institutions; (2) almost all construction contractors; (3) state and local governments; and (4) possibly TRICARE subcontractors (given the five-year moratorium on enforcement of the obligations related to affirmative action programs and recordkeeping of all TRICARE subcontractors set forth in Directive 2014-01, effective May 7, 2014).

Data required. The proposal would require covered contractors to submit the following three pieces of information: (1) the total number of workers within a specific EEO-1 job category by race, ethnicity and sex; (2) total W-2 wages defined as the total individual W-2 wages for all workers in the job category by race, ethnicity and sex; and (3) total hours worked, defined as the number of hours worked by all employees in the job category by race, ethnicity and sex. No individual pay information would be submitted.

Reporting period. The filing period for the proposed Equal Pay Report would be January 1 to March 31 of each year. The report would cover total W-2 Wage and Tax Statement earnings and total work hours for the calendar year, January 1 – December 31, for all employees included in the contractor’s most recent EEO-1 Report(s) (which are due annually on September 30).  The number of employees would include all employees whether or not they are still employed by the contractor on December 31st.

The reasoning behind the March 31 deadline for the Equal Pay Report is that, by that time, employers will have submitted their W-2s from the previous year, Copus explained. This information would be submitted as a supplement to the employer’s most recent EEO-1 Report(s) filed the previous September.

Public comments. Public comments on this proposal are due by January 5, 2015. [WK Note: At the time of the NELI briefing, the comment deadline was November 6, 2014, but, in an October 31 announcement and subsequent Federal Register notice (79 FR 65613-65614), the OFCCP extended the comment period for an additional 60 days.] Fox noted that there is no deadline for final rule approval by OMB, and Copus said the rule may not be finalized within the time remaining for the Obama Administration. However, contractors concerned about this proposal shouldn’t just wait around for a final rule, but rather should file comments to bring those concerns to the attention of the OFCCP, both Copus and Fox suggested.

The OFCCP won’t give much weight to public comments when formulating the final rule, according to Copus, who said that public comments will be like “water off a duck’s back” to the OFCCP. Nevertheless, these comments will constitute evidence in any litigation that might challenge a final rule, Fox pointed out. Congress will be more willing to consider contractor concerns, Copus stated, recommending that contractors who are really agitated by this proposal should also voice their concerns to Congress.

Electronic submission. One concern about the proposal is that it would require contractors to submit their data electronically using a web-based data tool. The OFCCP states that the web-based portal for reporting and maintaining compensation information will be designed so that it “conforms with applicable government IT security standards.”  The agency will also establish a process for requesting an exemption to the electronic filing requirement. However, the proposal does not point out what steps the agency will take to secure the data against hackers, Copus observed, noting that this omission would be a good point to discuss in public comments.

Fox cited a 2013 report from the National Research Council (NRC) of the National Academies of Sciences (NAS), entitled “Collecting Compensation Data from Employers,” which recommends that if the OFCCP were to utilize a pay data collection instrument, it should formulate ways to mask the data submitted by contractors. Moreover, both Copus and Fox told the audience that they need to “perturbate,” – i.e. disguise – all the data submitted to the OFCCP.

One way to protect data is to code sensitive information, such as employee names, job titles, and geographic locations and provide the key to the OFCCP separately from the data files, Fox suggested. Another way to protect data is via a File Transfer Protocol (FTP) website, he added.

Other concerns. Copus and Fox detailed several other concerns about the proposal, including their assessment that the proposal won’t serve the two stated purposes cited by the OFCCP, which are to: (1) allow the agency OFCCP to target facilities most likely to have pay violations; and; (2) encourage contractors to conduct self-audits and take corrective action where appropriate. The proposal is vague on exactly how these two goals will be accomplished, Copus said.

Targeting. The OFCCP proposes to accomplish the first objective by developing an “industry standard” appropriate for each facility, that would be by NAICS primary codes. These codes are very broad, grouping together industries that encompass very disparate types of jobs, Copus explained. To illustrate his point, he cited NAICS Primary Code 11 which includes “Agriculture, Forestry, Fishing and Hunting.” Data on the average hourly compensation by race, sex, and ethnicity for each EEO-1 category would be combined with undefined external labor market data to create the “industry standard.”  But it’s unclear whether this data would be aggregated by state, metropolitan areas, or contractor size or whether national or regional aggregations would be used, he noted.

For the next step in the targeting process, the OFCCP would compare an individual contractor establishment’s compensation pattern with the “industry standard.”  However, the proposal leaves unanswered exactly what comparisons would be made, Copus noted. On this point, he questioned: (1) whether these comparisons would be made by race/sex/ethnicity for each EEO-1 category separately or for all EEO-1 categories aggregated and weighted; and (2) would there be different comparisons for different industries and different comparisons for different size companies?

In the next targeting step, the OFCCP would select establishments for audit that depart in some unspecified way and degree from the “industry standard.” Yet, the proposal is unclear as to what kind of disparity would trigger an audit, Copus said. The unanswered questions about such a disparity include whether the disparity must be statistically significant, and if so, for how many EEO-1 groups?

Moreover, the proposal fails to explain how any targeting mechanism based on the Equal Pay Report would be coordinated with any other targeting schemes for contractors not covered by the report, Copus observed. Currently, the agency has separate targeting schemes — aside from the general establishment audit targeting system for supply and service contractors — for contractors with Functional Affirmative Action Programs, construction contractors, glass ceiling compliance reviews, contractors that are educational institutions, and pre-contract award reviews. Moreover, as noted previously, about 42 percent of all establishments subject to OFCCP audits would not be covered by the Equal Pay Report.

In sum, the proposal presents more questions than answers about targeting, he said, concluding that the report will not work as a targeting mechanism because there are too many unanswered questions to be worked out.

Self-evaluations. Not only will the Equal Pay Report not work as a targeting device, but it won’t work as a self-evaluation tool, either, Copus concluded. Under the proposal, contractors could voluntarily compare their own compensation pattern with the “industry standard” according to some unspecified criteria and take corrective action where appropriate. But even if the OFCCP publishes industry standards as the proposal suggests, those standards will be summary data only with no identification of specific facilities or companies.

Moreover, what value would knowledge of the industry standards provide to contractors? Copus asked. According to the OFCCP’s preamble to the proposal, “[e]mployers do not want to be known as one of the lowest paying members of their industry, and may voluntarily change their pay structure,” but Copus said this information has nothing to do with discrimination or the pay gap that the Equal Pay Report is supposed to address. Fox suggested this information would be useful to unions as leverage in negotiating collective bargaining agreements.

Fox also pointed out that the self‐analysis suggested in the Equal Pay Report will not satisfy the current regulatory requirement for contractor’s self‐analysis on pay.

Unlawful wage gap myth. The OFCCP maintains that the purpose of the Equal Pay Report and its other compensation discrimination enforcement efforts is to eliminate the gender wage gap in the federal contractor workforce caused by widespread unlawful denial of equal pay for equal work. However, Copus disagreed with the agency’s assertion that the gender wage gap is in fact caused by unlawful actions on the part of employers.

The White House’s claim that unequal pay for equal work causes the gender wage gap is simply not true, Copus said, explaining that many legitimate factors affect an employee’s current pay. For example, seniority is impacted by family responsibilities and the fact that a disproportionate number of women take off from the workforce to raise children is not discriminatory, but a fact of life, he noted.

Although the White House maintains that women earn an average of just 77 cents for every dollar earned by men, the 77 cents figure does not refer to the same work; rather, it includes all workers regardless of job, according to Copus. The OFCCP even admits that, “occupational differences may account for about half of the gender wage gap,” he pointed out. Thus, only a tiny portion of the gender wage gap is attributable to paying women less than men for doing the same work. Instead, the gender wage gap derives largely from the fact that females, on average, tend to work in lower paying jobs while men, on average, tend to work in higher paying jobs.

Copus cited a September 2, 2014 opinion piece in Time Magazine which states that the assertion that “[w]omen earn 77 cents for every dollar a man earns—for doing the same work” is a myth. According to the piece, “[n]o matter how many times this wage gap claim is decisively refuted by economists, it always comes back. The bottom line: the 23‐cent gender pay gap is simply the difference between the average earnings of all men and women working full‐time. It does not account for differences in occupations, positions, education, job tenure or hours worked per week. When such relevant factors are considered, the wage gap narrows to the point of vanishing.”

Furthermore, the OFCCP’s own enforcement data shows that there is not widespread wage discrimination against women in federal contractor workplaces, Copus said. During the period between fiscal year (FY) 2009 and FY 2014, in which the OFCCP conducted 23,734 audits, the agency found compensation violations, including violations impacting men and minorities, in only one half of one percent of all audits. Of the cases involving gender bias, most involved less than four women, and only two of those were large enough to warrant a press release, he noted. Fox added that over the last 30 years and 10 presidential administrations, the OFCCP has simply not been able to find any evidence of widespread wage discrimination due to gender bias.

Current pay focus is erroneous. Even so, any purported wage gap in current pay is irrelevant because “any analysis of current pay is irrelevant,” Copus asserted. The OFCCP concedes, in Directive 2013-03 (previously numbered as Directive 307) and related policy statements, that it is bound by Title VII when conducting compensation enforcement under Executive Order (EO) 11246. Yet, the agency’s focus on current pay does not comport with the Supreme Court’s 2007 holding in Ledbetter v Goodyear Tire & Rubber Co (89 EPD ¶42,827) that the correct focus under Title VII is pay decisions, Copus explained. The only change the Lilly Ledbetter Fair Pay Act of 2009 made to Title VII law was to extend the charge filing period indefinitely when an employee challenges a discrete pay decision; it did not, however, change the requirement in the Ledbetter decision that Title VII claimants must identify and challenge discrete pay decisions, he emphasized. Accordingly, the OFCCP cannot claim pay discrimination under the relevant legal standard unless it identifies a specific pay decision (meaning an event that impact pay such hiring, promotions, pay freezes, bonuses, and demotions) and proves that decision is discriminatory, he said.

Even though the OFCCP’s practice of looking only at current pay is a “fatal flaw” that is “demonstratively wrong,” the agency is sticking with it because the contractor community is not contesting it, Copus said. In addition, the compensation analysis advice offered by some vendors and law firms focuses only on current pay, and ignores analyzing pay decisions, cautioned Copus.

Revised audit documents. The OFCCP’s standard practice for a conducting a compliance review begins with a desk audit in which the agency sends the contractor its standard Scheduling Letter and accompanying Itemized Listing seeking the contractor’s written Affirmative Action Program (AAP) and supporting documentation. On September 30, 2014, the Office of Management and Budget (OMB) approved revisions to these documents, and the OFCCP began using the revised versions in mid-October.

Paragraph 19. Paragraph 19 of the revised Itemized Listing requires contractors to submit “[e]mployee level compensation data for all employees (including but not limited to full-time, part-time, contract, per diem or day labor, temporary) as of the date of the workforce analysis in [the contractor establishment’s] AAP.”  Contractors are required to provide gender and race/ethnicity information and hire date for each employee as well as job title, EEO-1 Category and AAP job group in a single file.

After 35 years of trying, the OFCCP finally got one of its fondest hopes – it can now seek individual, employee-level compensation data via the Itemized Listing, rather than attempting to get this information via supplemental document requests (SDRs) after the contractor submits its response to the Itemized Listing, Fox observed. The importance of this change is that contractors cannot negotiate what information they will provide to the OFCCP in response to the Itemized Listing, whereas they can negotiate what information they will provide in response to SDRs, both Fox and Copus pointed out. They also observed that the demand for individualized pay data in Paragraph 19 differs from the proposed Equal Pay Report requirement of aggregate pay data.

Paragraph 19 also requires submission of “[d]ocumentation and policies related to compensation practices of the contractor” and it invites the contractor to submit “any additional data on factors used to determine employee compensation.” Copus advised against submitting the optional additional data, saying that doing so may constitute an admission against interest for the contractor.

Job group formulations. Contractors need to be aware of their AAP job groups and carefully review them, Fox advised, because the OFCCP will likely assert that putting jobs in the same group for AAP purposes is an admission on the part of the contractor that these jobs are similar for the purpose of compensation discrimination analysis as well. “Make your job groups equal to similarly-situated employees,” he said. Copus advised that AAP job groups should be very narrow, and he also recommended that AAPs should include a statement that job groups do not influence pay.

Responding to OFCCP data demands. Given that the OFCCP will be sticking to its erroneous focus on current pay, rather that the relevant legal standard of focusing on pay decisions, how should contractors respond to the demand for current pay data in Paragraph 19?

The decision on whether to resist the OFCCP’s demand for current pay data is a policy decision that contractors must make when they first respond to the revised Scheduling Letter and Itemized Listing, Fox stated. Attorneys should put their clients on notice that the law does not require contractors to submit current pay data because data on current pay is irrelevant under Title VII, he advised. Accordingly, attorneys need to get their clients’ permission before submitting data on current pay to the OFCCP. Even so, contractors who chose to respond by supplying current pay data to the OFCCP should note in their responses that the relevant legal standard for Title VII compensation analysis is pay decisions, both Fox and Copus agreed.

Although Paragraph 19 only requires contractors to submit current pay data, and not any analysis of that data, Fox recommended that contractors analyze their current pay data under attorney-client privilege prior to submitting that data to the OFCCP so that the contractor can identify disparities and understand why these disparities exist. Moreover, because the relevant legal standard is pay decisions, contractors should analyze their pay decisions for unlawful disparities as well. Indeed, attorneys who don’t put their clients on notice that they should analyze pay decisions are risking malpractice suits, Fox warned. Copus recommended that contractors proactively examine recent pay decisions – such as starting pay, promotional pay increases, and merit pay increases – using multiple regression analysis.

The presenters. Copus has more than 35 years of litigation and counseling experience and has regularly represented employers in OFCCP matters, including hundreds of standard OFCCP compliance evaluations and “glass ceiling” audits. He began his legal career in 1969 at the Equal Employment Opportunity Commission (EEOC), where for many years he headed the National Programs Division. In 1977, he entered private practice representing employers, and he recently retired from Ogletree Deakins in Morristown, New Jersey.

Fox is the President and a founder of Fox, Wang & Morgan P.C. in Los Gatos, California. He leads large and complex litigation matters in state and federal courts, in cases involving wage-hour and discrimination class actions, trade secret claims, employment contract disputes, wrongful termination, corporate investigations, and the use of statistics in employment matters. Fox previously served as Executive Assistant to the Director of the OFCCP, where he was responsible for all enforcement and policy matters.

NELI’s Thirty-Second Annual Affirmative Action Briefing was held in Chicago on October 16-17, 2014. For more information on NELI, including its publications and future programs, call (303) 861-5600 or go to NELI’s website at: www.neli.org.

Add a Comment


Employee awarded unemployment benefits because employer failed to follow drug testing protocol

November 18th, 2014  |  Ron Miller  |  Add a Comment

A South Carolina employer loss its challenge to an award of unemployment benefits to an employee discharged after a positive drug test because it failed to use a testing laboratory that was certified by a statutorily designated accrediting association. Although sympathetic to the employer’s position, the South Carolina Supreme Court held in Nucor Corp v. South Carolina Department of Employment and Workforce, that an administrative law court was correct to consider the laboratory’s lack of proper certification when deciding that the employee could receive unemployment benefits.

Employee fails drug test. The employee was fired from her job with a steel production company, after she tested positive for marijuana use and failed a random drug test in violation of the company’s drug policy. To administer the test, the company used a laboratory certified by the Department of Health and Human Services. However, the employee had an independent test performed at a different laboratory. That test came up negative. She applied for unemployment benefits, but the company argued that she was ineligible under S.C. Code Ann. sec. 41-35-120. That statute disqualified workers from receiving unemployment benefits if they were terminated for violating a company’s policies (subsection (2)), failing a drug test administered by a laboratory certified by one of three approved organizations (subsection (3)), or failing to comply with state or federal drug testing and use regulations (subsection (4)).

The case eventually made its way to an appellate panel at the Department of Employment and Workforce (DEW), which held that the employee was eligible for employment benefits because the independent drug test, which had come back negative, showed that she had not violated the company’s drug policy or any drug statutes, meaning that she did not fall under subsections (2) or (4). The company appealed that decision to an Administrative Law Court (ALC), which affirmed the decision of the DEW Panel as to subsections (2) and (4), but remanded the matter so that the Panel could rule on the applicability of subsection (3). After clearing a number of additional hurdles, the DEW Panel ruled that the employee had not run afoul of subsection (3), since the company’s chosen laboratory was not certified by any of the three organizations specified in the statute. The company did not appeal that ruling. Instead, it re-appealed the ALC’s original decision to the Supreme Court.

Appealability. Despite the employee’s protests, the court held that the company was not required to appeal the DEW Panel’s decision concerning subsection (3) before being allowed to appeal the ALC’s decision regarding subsections (2) and (4), although that probably would have been the more prudent course of action. The reason the company could not immediately appeal the ALC’s decision in the first place was because the ALC had remanded consideration of subsection (3) back to the DEW, meaning that its decision on subsections (2) and (4) was not yet final. By making a ruling on subsection (3), the DEW Panel had transformed the ALC’s decision on subsections (2) and (4) into a final, appealable decision.

Improperly certified laboratory. By appealing a decision based purely on subsections (2) and (4), the company tried to avoid consideration of its laboratory’s lack of statutorily required credentials. However, that fact still crept into the Supreme Court’s reasoning. The company argued that the ALC had been wrong to consider the employee’s off-site drug test in determining that she was not barred from receiving unemployment benefits. The company’s own drug tests, it argued, were all the ALC needed, and because neither subsections (2) nor (4) said anything about laboratory standards, the fact that its laboratory was not certified as required under subsection (3) did not matter. However, the only reason the company was relying on subsections (2) and (4) was because it knew that it could not rely on subsection (3), which made its laboratory’s lack of credentials relevant to all of the subsections. The ACL had been correct to consider that fact when making its decision that the employee could receive her unemployment benefits, a decision the Supreme Court affirmed.

Add a Comment


Progress report on status of people with disabilities released

November 14th, 2014  |  Deborah Hammonds  |  Add a Comment

The National Council on Disability (NCD) recently released its 2014 edition of National Disability Policy: A Progress Report which provides details on the status of people with disabilities in the United States. The annual report gives an overview of the progress this country has made promoting and protecting the rights of individuals with disabilities. The report also identifies opportunities to promote public policies that contribute to a more inclusive environment.

NCD’s report identifies six areas as being important to the wellbeing of people with disabilities: employment access and inclusion, subminimum wage, the Convention on the Rights of People with Disabilities (CRPD), education outcomes, Medicaid managed care, and mental health care. Recommendations to improve these areas are also included. For example:

“Employment is one of the most important pathways to economic self-sufficiency and independence for Americans, yet people with disabilities experience higher unemployment and lower pay rates than those without disabilities. NCD explores how such factors as transportation, workplace culture, and technology impact employment experiences and opportunities. The NCD advocates for an inclusive approach to these (and other) factors so that people with disabilities can focus on pursuing employment interests rather than on mediating obstacles that serve as barriers to employment.

Extending subminimum wage based on disability status has no place in American culture. This policy option was introduced in an era lacking protective legislation, such as the Rehabilitation Act and the ADA, and innovations in technology that now afford greater opportunity for Americans with disabilities to engage prominently throughout society. The NCD urges the U.S. Department of Labor to adopt its approach to phasing out subminimum wage provisions as they relate to people with disabilities.”

Data trends in disability policy are also highlighted in the report.

“With our 2014 Progress Report, NCD acknowledges the cultural context of the past while setting a vision for the future that is grounded in high expectations for both people with disabilities and the policymakers who are responsible for shaping an inclusive society,” said Councilmember Janice Lehrer-Stein in an agency statement.

NCD has reported on the status of people with disabilities since its inception. This year’s report takes on added significance as the agency celebrates its 30th anniversary. NCD was first established in 1978 as a small advisory Council within the Department of Education and in 1984 transitioned to its current status as a federal agency.

A copy of NCD’s 2014 Progress Report, including key findings, recommendations and objectives, is available on the agency’s website, www.ncd.gov.

Add a Comment


Public comment period for OFCCP Equal Pay Report proposal extended to January 5

November 11th, 2014  |  Cynthia L. Hackerott  |  Add a Comment

Stakeholders now have an additional period of 60-days to comment on an OFCCP proposal that would require covered federal contractors and subcontractors to submit an annual “Equal Pay Report” on employee compensation, the agency announced on October 31, 2014. The proposed new report would apply to companies that file EEO-1 Reports, have more than 100 employees, and hold federal contracts or subcontracts worth $50,000 or more for at least 30 days. The comment period opened when a Notice of Proposed Rulemaking (NPRM) was published in the Federal Register on August 8, 2014 (79 FR 46562- 46606); corrections to the NPRM were published on August 20 (79 FR 49260-49261). A notice of the comment period extension was published in the Federal Register on November 5 (79 FR 65613-65614). The original deadline for comments was November 6, but, with the extension, the new deadline is January 5, 2015.

Proposed reporting requirements. Current regulations require that all employers in the private sector with 100 or more employees, and some federal contractors with 50 or more employees, annually file the EEO-1 Report with the Joint Reporting Committee (a joint committee consisting of the EEOC and the OFCCP). The OFCCP’s proposal would revise its regulations at 41 CFR Part 60-1, which set forth the reporting obligations of covered federal contractors and subcontractors under Executive Order 11246. Specifically, the proposal would amend the regulation at 41 CFR 60-1.7 to require that:

• covered federal contractors and subcontractors submit to the OFCCP two columns of additional information to the EEO-1 Report in a new Equal Pay Report. Covered employers would submit the following three pieces of information: (1) the total number of workers within a specific EEO-1 job category by race, ethnicity and sex; (2) total W-2 wages defined as the total individual W-2 wages for all workers in the job category by race, ethnicity and sex; and (3) total hours worked, defined as the number of hours worked by all employees in the job category by race, ethnicity and sex.

• covered federal contractors and subcontractors electronically submit the proposed Equal Pay Report using a web-based data tool. The OFCCP states that the web-based portal for reporting and maintaining compensation information will be designed to so that it “conforms with applicable government IT security standards.”  The agency will also establish a process for requesting an exemption to the electronic filing requirement.

• contract bidders make a representation related to whether they currently hold a federal contract or subcontract that requires them to file the proposed Equal Pay Report and, if so, whether they filed the report for the most recent reporting period.

The filing period for the proposed Equal Pay Report would be January 1 to March 31 of each year. The report would cover total W-2 Wage and Tax Statement earnings and total work hours for the calendar year, January 1 – December 31, for all employees included in the contractor’s most recent EEO-1 Report(s) (which are due annually on September 30).  The number of employees would include all employees whether or not they are still employed by the contractor on December 31st.

A webpage with FAQs and other information on the proposal is available at: http://www.dol.gov/ofccp/EPR.

Add a Comment


Fired for using “n-word,” reporter then sues for race bias

November 10th, 2014  |  Joy Waltemath  |  Add a Comment

About 18 months ago, I wrote a post asking whether employers would fire an employee for using the n-word.  I looked at a slice of relevant case law and concluded that, despite what seemed to late, ineffective, or no discipline at all for reported n-word usage in those cases, employers that did discipline and/or terminate individuals who used inexcusable racial language in the workplace likely were not the ones getting sued.

OK, so they fired him. But then I came across the case of the white male Fox TV reporter who was fired after he used the “n-word” (in a non-pejorative manner) while discussing a story during a newsroom editorial meeting. And he did sue his employer. Denying the employer’s motion for summary judgment, the court said management was aware that the reporter was being judged by a social norm deeming it acceptable for African-Americans, but not whites, to use the n-word. Treating it under the cat’s paw theory of liability, the court found a triable fact issue as to whether the TV station negligently permitted the discriminatory animus of one co-anchor (among others) to influence the firing decision.

The n-word incident. During the editorial meeting, the racially diverse coworkers discussed a story about an NAACP Youth Council that was holding a symbolic burial for the n-word. Participants at the burial reportedly used the word “at least a hundred times or more,” prompting the employee to ask: “Does this mean we can finally say the word ‘ni**er?’” One African-American colleague replied, “I can’t believe you just said that!” Other attendees were also offended, as were others in the office as reports of the meeting spread, and even though he apologized, his black co-anchor reportedly told him “because you’re white you can never understand what it’s like to be called a ni**er and that you cannot use the word ‘ni**er.” He was suspended, issued a final warning, and required to take sensitivity training.

The newsroom leak. That was not the end of the matter. Instead, a local newspaper published a story about the employee’s suspension for his reportedly “‘bizarre’ and ‘shocking’ sermon in which he insisted there’s nothing wrong with a word most commonly referred to as ‘the N-word.’” Of course, this story got picked up by other print and online media outlets. No investigation was conducted into the leak, even though the leak violated the station’s policies. The reporter was not allowed back on the air and his contract was not renewed. He sued, and ultimately his Title VII cat’s paw race discrimination claim survived a summary judgment motion (including an interesting discussion about whether cat’s paw cases survive given the tension between Staub and Vance, as well as a discussion of vicarious liability for acts outside the scope of employment under Sec. 219(2)(d) of the Restatement (Second) of Agency).

Should anyone say that word? Essentially, the court found evidence that the employee’s co-anchor acted with discriminatory animus based on her belief that African-Americans, but not whites, could say the n-word in the workplace. She encouraged other workers to complain about the employee. Even after he completed sensitivity training and was awaiting reinstatement, she continued to complain, intervening with HR to say she had heard from black journalist associations and from people on the street about the employee’s language. There was evidence she intended to, and did, cause the station to change direction — from planning to reinstate the employee to letting his contract expire – because two days later, he was told that his contract would not be renewed.

In allowing the case to go to a jury, the court also found a fact issue as to whether the station was negligent, noting the employee had no opportunity to defend himself during the investigation, nor was there any investigation into who leaked information about the editorial meeting to the media, which then created adverse publicity that resulted in his firing. Instead, it seemed to the court that the station “simply rubberstamped” the co-anchor’s desire to see him fired.

What would you do? Is this a “damned if you do, damned if you don’t” scenario? Should you have an absolute prohibition on the use of the word? A straightforward policy barring anyone from saying the n-word could have protected the employer to some extent here, but is that realistic in a newsroom, an educational setting, or for any media business? Earlier this year, for example, the NFL considered and rejected a specific ban on the use of the n-word, finding instead that its existing unsportsmanlike conduct rule, which covers “abusive, threatening or insulting language, or gestures to opponents, teammates, officials or representatives of the league” was sufficient. The academic community has grappled with the word in the educational context; see here and here.  Context obviously matters. What about who is speaking?  Determining the correct approach requires careful thought and cultural competence. Don’t let your managers make this decision on their own.

Add a Comment