United States: Administrative Law Judge Winnows OFCCPs Data Request

Last Updated: July 31 2017
Article by William H. Weissman

On July 14, 2017, an administrative law judge issued a 43-page set of recommendations and order ("Order") on the Office of Federal Contract Compliance Programs' ("OFCCP") data requests issued to Google, significantly winnowing much of the OFCCP's voluminous requests. While the OFCCP may appeal the ALJ's Order, it represents a significant victory against unreasonably intrusive data requests by the OFCCP, while providing a good roadmap for when and how to push back against such data requests. Importantly, the Order has nothing to do with the merits of the OFCCP's audit, which is ongoing.


The OFCCP is the agency within the Department of Labor charged with auditing government contractors to determine whether they are complying with certain contractually-imposed anti-discrimination and affirmative action obligations. While Google had been a covered federal government contractor at various times between 2007 and 2012, the company's obligation to submit to an OFCCP audit arose on June 2, 2014, when it signed a contract with the General Services Administration for advertising and marketing services ("AIMS contract").

Google was selected for a random audit of its headquarters' location in September 2015. It cooperated with the OFCCP's initial data requests and made multiple managers available for interview.1 In June and September 2016, the OFCCP requested significant additional data, focusing largely on compensation issues.2 Google complied with these requests. In total, Google produced 844,450 compensation data points for 21,114 employees on the September 1, 2015, snapshot date.

The OFCCP then requested more data, including (1) a September 1, 2014, snapshot including all the same data points as the September 1, 2015, snapshot; (2) a salary history for each employee over the entire time employed, including back to the company's founding in 1998 for some long-term employees; and (3) the name, address, telephone number and personal email address of every employee covered by either the 2014 or 2015 snapshot. The parties could not agree on the scope of these three requests, triggering the OFCCP's enforcement action.

In support of its position, the OFCCP asserted that its requests were relevant because it found indications of pay disparity based on gender at the time of hire, and needed all the historical data to look at the causes of such alleged pay disparity during the review period. Thus, it needed two snapshots to look at pay over time as well as pay history from inception for each employee. OFCCP also added that research shows (1) women do not negotiate as well as men, and (2) if starting salaries are negotiated, female negotiators remain behind better negotiators for their entire careers.3 With respect to contact information, OFCCP asserted it wanted to contact employees to get their views without Google knowing who it contacted. Google countered that the OFCCP did not provide information about the issues it was finding, such that it would evaluate whether the OFCCP's additional requests were relevant. It also added that the data requests were burdensome and interfered with its business operations.

The Order's Analysis

The OFCCP's data requests are akin to an administrative subpoena, and thus must comply with the Fourth Amendment's prohibition against unreasonable searches and seizures. The OFCCP asserted that Google waived its Fourth Amendment rights by entering into the AIMS contract. The ALJ rejected this sweeping position and instead analyzed whether the requests were so unreasonable and burdensome as to violate the Fourth Amendment.

While finding that the OFCCP was acting within its authority, the ALJ nonetheless found some of the requests violated the Fourth Amendment, stating:

OFCCP should be able to identify specific areas that are relevant to its investigation rather than willy-nilly search anywhere and everywhere for practices that might be causing a disparity in the compensation data. Relevance need not and cannot be established on conjecture or speculation.

Against this backdrop, the ALJ turned to the three requests in dispute.

2014 Snapshot: With respect to the 2014 snapshot, the ALJ found that the OFCCP offered "nothing more" than its "conclusory statement" that the 2015 snapshot showed pay disparities based on gender. In fact, "OFCCP refused any explanation of its analysis," citing the deliberative process privilege. Nonetheless, the ALJ concluded that the OFCCP met its burden of showing relevance of certain information for the employees that worked at Google during both periods. The relevant information, however, was largely basic compensation information, and not some of the more far-reaching categories the OFCCP was seeking. For example, the ALJ noted that the OFCCP's investigative authority is limited to discrimination based on national origin, but that does not require the OFCCP to know employees' places of birth, citizenship or visa status. As such, Google need not provide those data points.4

Employee contact information: With respect to the OFCCP's request for the personal contact information for more than 25,000 employees, the ALJ stated that "OFCCP's request for contact information is unreasonable in that it is over-broad, intrusive on employee privacy, unduly burdensome, and insufficiently focused on obtaining the relevant information." The ALJ discussed concerns with data breaches, specifically citing the 2015 data breaches at the Office of Personnel Management that exposed millions of federal government employees' data, data breaches during the recent presidential election and ransomware attacks against the Department of Labor. The ALJ went on to point out that Google's 25,000 employees have no right to opt-in or opt-out of having their personal information provided to the government and may not want to do so. He added that OFCCP failed in any way to consider how providing this information will impact Google's relationship with its employees.

As a result, the ALJ ordered the disclosure of 5,000 employees' contact information, a sufficiently large sample to allow the OFCCP to conduct the roughly 100 to 300 interviews that are likely to occur. The ALJ allowed the OFCCP to select the employees. If after interviews the OFCCP needs to conduct additional follow up interviews, it may be entitled to another 3,000 employees' contact information.

Salary and jobs history: As noted, the OFCCP argued that pay disparities occur at time of hire, and are perpetuated by giving pay increases in proportion to current salaries. To test its theory, the OFCCP claimed it needed the pay history. The ALJ rejected this argument as "legally questionable and factually unsupported at this point," finding the "OFCCP's theory is little more than speculation."

One problem the ALJ found is that there was no evidence Google was ever a covered federal contractor prior to 2007, and as such, the OFCCP's investigative jurisdiction did not extend back to periods prior to 2007. Thus, the OFCCP lacked the legal authority to investigate for such periods, even if the OFCCP could extend the review period back prior to the generally applicable two-year period of review.

Another problem is the legal sufficiency of the OFCCP's starting salary theory of discrimination, with the ALJ citing to Rizo v. Yovino, 854 F.3d 1161 (9th Cir. 2017), which held that "prior salary alone can never be a 'factor other than sex.'" The ALJ then went on to point out that even after two days of interviews with Google's executives and managers, the OFCCP failed to establish "that Google engages in what most would consider negotiation when it sets starting salaries." The Order goes on to conclude that "OFCCP's case is even weaker on starting salaries for Google employees who are promoted."

The Order concludes with an explanation of the iterative process and what the OFCCP needs to do in order to justify the need for additional information. It also chastised the OFCCP for its failure to accurately understand Google's pay practices, adding that had it done so the OFCCP "could have made an entirely different showing on relevance." Lastly, it rejected the OFCCP's contention that "Google is so large and profitable that no burden is too great" as failing to recognize not merely the financial costs, but interruption to its normal business operations, can be burdensome.


The tenor of the Order made clear that Google had reasonably attempted to comply with the OFCCP's data requests. For example, the ALJ noted that Google had turned over 740,000 pages of information. In addition, the ALJ recognized the relative benefits versus the burdens of being a government contractor, noting that the AIMS contract at issue had a value of only $600,000, but Google spent nearly $500,000 complying with the OFCCP's data requests. In addition, the OFCCP's failure to accurately understand Google's pay practices, coupled with what was little more than speculative legal theory, led to the decision to find the requests partially burdensome and unreasonable, and as such, narrowed them considerably. But it should also be recognized that while the OFCCP did not get everything it was asking for, it still is receiving substantial amounts of data.

In light of the Order, covered federal government contractors facing data requests that appear overbroad, unreasonable or unduly burdensome should consider:

  • The extent to which the contractor has complied with data requests to date.
  • Its attempts to reasonably narrow the scope of data requests.
  • The OFCCP's theory of potential liability or basis for making additional data requests.
  • The time periods when a company qualifies as a covered federal contractor to determine if the requests might exceed the scope of the OFCCP's investigative authority.
  • The ability of the OFCCP to safeguard personnel information and how to balance employees' privacy rights with the OFCCP's right to conduct an investigation.
  • The overall burden in complying with the requests, including the amount required to be spent to retrieve and review the data before turning it over to the OFCCP.


1 These requests included a snapshot for September 1, 2015, of its employees' gender, "race/ethnicity," hire date, job title, EEO-1 category (such as clerical or executive), job group, base salary or wage rate, hours worked in a typical workweek, and other compensation or adjustments to salary (bonuses, incentives, commissions, merit increases, locality pay, and overtime), as well as documentation and policies relating to compensation practices. Google was also "invited to submit additional data related to compensation, 'such as education, past experience, duty location, performance ratings, department or function, and salary level/band/ range/grade.'"

2 These additional requests included snapshot data of the employees' name, date of birth, bonus earned, bonus period covered, campus hire or industry hire (i.e., hired directly out of school or from another employer), whether the employee had a competing offer, current "CompaRatio," current job code, current job family, current level, current manager, current organization, department hired into, education, equity adjustment, hiring manager, job history, locality, long-term incentive eligibility and grants, market reference point, market target, performance rating for past 3 years, prior experience, prior salary, referral bonus, salary history, short-term incentive eligibility and grants, starting CompaRatio, starting job code, starting job family, starting level, starting organization, starting position/title, starting salary, stock monetary value at award date, target bonus, and total cash compensation, and "any other factors related to Compensation." The OFCCP also requested employee's ID, country of citizenship, secondary country of citizenship, visa (yes/no), visa type and place of birth.

3 In a footnote, the ALJ stated that "OFCCP offered no academic literature or other research to support [its] contention about how women's negotiating skills adversely affects their starting pay." While the OFCCP did cite to an article on slate.com and an article in the Washington Post in its closing brief, the ALJ refused to consider those citations because they were not provided in the pre-trial disclosures.

4 Other data points that Google was not required to provide included the employees' age of birth, department hired into; job history; salary history; starting "compa-ratio"; starting job code; starting job family; starting level; and starting organization.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

William H. Weissman
In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:
  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.
  • Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.
    If you do not want us to provide your name and email address you may opt out by clicking here
    If you do not wish to receive any future announcements of products and services offered by Mondaq you may opt out by clicking here

    Terms & Conditions and Privacy Statement

    Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

    Use of www.mondaq.com

    You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


    Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

    The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


    Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

    • To allow you to personalize the Mondaq websites you are visiting.
    • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
    • To produce demographic feedback for our information providers who provide information free for your use.

    Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

    Information Collection and Use

    We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

    We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

    Mondaq News Alerts

    In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


    A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

    Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

    Log Files

    We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


    This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

    Surveys & Contests

    From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


    If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


    From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

    *** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .


    This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

    Correcting/Updating Personal Information

    If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

    Notification of Changes

    If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

    How to contact Mondaq

    You can contact us with comments or queries at enquiries@mondaq.com.

    If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.

    By clicking Register you state you have read and agree to our Terms and Conditions