The 2017 repeal of the contractor labor-disclosure rule kept the integrity check, not the data it would supply

On March 27, 2017, Congress disapproved the Fair Pay and Safe Workplaces rule and the President revoked its executive orders. Contracting officers kept their duty to judge contractor integrity, but never got the labor law disclosures, advisors and systems the rule was to supply.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

On March 27, 2017, Congress disapproved the Fair Pay and Safe Workplaces rule and the President revoked its executive orders. Contracting officers kept their duty to judge contractor integrity, but never got the labor law disclosures, advisors and systems the rule was to supply.

  1. The week On March 27, 2017, two federal actions ended the Fair Pay and Safe Workplaces program for government contractors.
  2. What was erased: a rule treated as never having existed The FAR Council explained the legal effect in November 2017.
  3. What was live and then removed: paycheck transparency One part of the rule had gone into effect.
  4. What was never built: the data and the people The rule depended on federal systems.
  5. What returned by another route: forced arbitration The 2016 clause had limits.
  6. How the outcome affects different organizations The rule applied to federal contractors, and federal contractors work in every sector.
  7. Objections, in order Contracting officers had the integrity standard before and after the rule. [7] The 2016 rule argued that they needed structured information to apply it to labor law. [3] [4] Whether the standard alone is enough depends on what information reaches the officer.
  8. What procurement and compliance leaders could check The four parts translate into checks for agencies and contractors alike.
  9. With hindsight The Council also explained why the removal’s cost savings were mostly notional.

The week

On March 27, 2017, two federal actions ended the Fair Pay and Safe Workplaces program for government contractors. The President signed House Joint Resolution 37, which became Public Law 115-11. [2] The same day, he signed Executive Order 13782, Revocation of Federal Contracting Executive Orders. [1]

The joint resolution was one sentence long in substance. Congress disapproved the rule submitted by the Department of Defense, the General Services Administration and NASA relating to the Federal Acquisition Regulation, published at 81 Fed. Reg. 58562 on August 25, 2016. [2] It said the rule shall have no force or effect. [2] The legislative history listed House passage on February 2 and Senate consideration and passage on March 2 and 6, 2017. [2]

The executive order revoked Executive Order 13673 of July 31, 2014 and Executive Order 13738 of August 23, 2016. [1] It also revoked section 3 of Executive Order 13683 of December 11, 2014. [1] It directed agencies to consider promptly rescinding any orders, rules, regulations, guidance or policies implementing the revoked orders. [1] The order appeared in the Federal Register on March 30, 2017. [1]

The program the two actions ended had been built over the preceding years. Executive Order 13673 set its policy: agencies should contract with responsible sources who comply with labor laws, for the sake of economy and efficiency. [3] For contracts above $500,000, it required offerors to represent whether any administrative merits determination, arbitral award or civil judgment had been rendered against them in the previous three years for violations of listed labor laws. [3]

The order listed 14 federal labor laws and executive orders, plus equivalent state laws. [3] They included the Fair Labor Standards Act, the Occupational Safety and Health Act and the National Labor Relations Act. [3] They also included the Family and Medical Leave Act, Title VII of the Civil Rights Act and the Americans with Disabilities Act. [3] Contracting officers, advised by a new agency labor compliance advisor, were to consider the disclosures in deciding whether an offeror had a satisfactory record of integrity and business ethics. [3]

The order did more than require disclosure. It required paycheck transparency: contractors had to give workers a document each pay period showing hours, overtime, pay, and additions and deductions. [3] For contracts above $1 million, it limited the use of pre-dispute arbitration for claims under Title VII and for torts related to sexual assault or harassment. [3]

The FAR rule implementing the order was published on August 25, 2016, effective October 25, 2016. [4] It phased in the disclosure requirement, starting with solicitations of $50 million or more and moving to those over $500,000 after April 24, 2017. [4] Subcontractor requirements were to start on October 25, 2017. [4] The paycheck transparency clause was to apply to solicitations from January 1, 2017. [4]

The rule never ran as written. On October 24, 2016, a federal district court in Texas issued a preliminary injunction in a suit brought by contractor associations. [5] As the FAR Council later described it, the order barred implementation of the labor law disclosure and reporting requirements and enforcement of the arbitration restriction. [5] The injunction did not reach paycheck transparency. [5]

The FAR Council responded the next day with a memorandum to agencies. [5] It told them not to include the enjoined representations and clauses in new solicitations, to amend solicitations already issued, and to take no action on information submitted in response. [5] On December 16, 2016, the FAR was amended to mark each enjoined section, provision and clause. [5]

So by the week of March 27, 2017, the program was partly frozen and partly live. The disclosure and arbitration pieces were enjoined. [5] The paycheck transparency clause had been prescribed in solicitations since January 1, 2017. [4] [5] The joint resolution and the executive order then ended the whole of it. [1] [2]

The March 27 actions are easy to file under deregulation. We read them for what they left behind. The disapproved rule had tried to give contracting officers a new feed of information for a decision they already had to make. [3] [4] The disapproval removed the feed. It did not remove the decision. [7]

Under the FAR, a contract may be awarded only to a responsible prospective contractor, and the contracting officer must make an affirmative determination of responsibility. [7] One of the general standards is a satisfactory record of integrity and business ethics. [7] That standard was there before the 2016 rule, and it is in the current FAR text. [7]

Our argument is that the 2017 disapproval changed what agencies knew, not what they were responsible for. Contracting officers still had to judge integrity. They lost the prospect of a structured, self-reported source on labor law violations, and of an advisor role built to interpret that source. For agencies, and for contractors in every sector, the question became where the information would come from instead.

We take the outcome in four parts, one for each fate the rule’s pieces met:

  1. What was erased: the rule as a whole, treated by law as never having taken effect.
  2. What was live and then removed: the paycheck transparency clause already in contracts.
  3. What was never built: the systems and roles that would have carried the disclosures.
  4. What returned by another route: limits on forced arbitration, in a 2022 statute.

Each part covers a distinct set of provisions, and together they cover the whole rule. After them we look at how the outcome affects different organizations, take the objections in order, and end with checks a procurement or compliance leader could run.

What was erased: a rule treated as never having existed

The FAR Council explained the legal effect in November 2017. Under the Congressional Review Act, a rule may not take effect or continue once Congress enacts a joint resolution of disapproval. [6] A rule that took effect and is later disapproved is to be treated as though it had never taken effect. [6] Congress had disapproved the entire FAR rule, so the removal rule took out all of it, including the December 2016 amendments. [6]

The Council drew the practical consequence. All clauses in the final rule were unenforceable and considered never to have taken effect, even if included in a contract. [6] Contracting officers were directed to modify existing contracts, to the maximum extent practicable, to remove the related provisions and clauses. [6]

The executive order’s separate role

Executive Order 13782 did different work. The joint resolution voided the FAR rule. The executive order revoked the orders that had authorized it. [1] [6] In our reading, without them there was no executive basis for a replacement rule on the same design. The order also told agencies to consider rescinding anything else implementing the revoked orders. [1]

The removal rule noted a gap the two actions left. Neither the public law nor the order addressed the Department of Labor’s guidance specifically. [6] The Council said the guidance had no legal effect without the FAR rule, and that the Department of Labor was publishing its own rescission. [6]

Why two instruments were used

The two actions did different jobs, and in our reading each would have left something behind on its own. A disapproval without the revocation would have voided the FAR rule but left the orders in force, directing agencies to implement them. [1] [2] A revocation without the disapproval would have removed the authority but left the rule in the FAR until a new rulemaking took it out.

Used together, they closed both routes on the same day. The removal rule in November 2017 cited both as its basis. [6] In our reading, the pairing also explains the timing of the cleanup. The legal effect was immediate, but the FAR text still needed a rule to remove the provisions, and that took until November. [6]

What the erased rule had required

The disclosure design was detailed. Prospective prime contractors would have publicly disclosed four pieces of information about each covered violation: the law violated, the case number, the date of the decision and the name of the body that made it. [4] Information about mitigating factors and remedial measures would not be made public unless the contractor chose. [4]

The assessment design was also detailed. An agency labor compliance advisor would give written analysis on whether violations were serious, repeated, willful or pervasive, their number and nature, and any mitigating factors. [4] The rule said that disclosure of a labor law decision did not automatically make a contractor nonresponsible. [4] The contracting officer had to document how the advisor’s analysis was considered. [4]

What counted as a decision

The rule defined its inputs broadly. A labor law decision meant an administrative merits determination, an arbitral award or decision, or a civil judgment resulting from a violation of a listed law. [4] Arbitral awards counted even if not final or subject to court review, and even if they came from confidential proceedings. [4] Civil judgments counted even if not final or subject to appeal. [4]

The rule then sorted violations by gravity. It used the categories serious, repeated, willful and pervasive, drawing on the Department of Labor’s guidance. [4] A repeated violation meant another violation of the same or a substantially similar requirement within the prior three years. [4] Pervasive violations meant a pattern reflecting basic disregard for labor laws, judged without a fixed count. [4]

That design explains why disclosure mattered. The Councils said enforcement agency databases did not collect civil judgments or arbitral awards, and that existing systems lacked all the information the order required. [4] In their view, some level of disclosure by contractors was therefore necessary. [4] Without disclosure, a large part of the record the rule wanted to see had no other channel.

The phase-in that never finished

The rule was staged. From October 25, 2016 through April 24, 2017, the prime contractor disclosure requirement applied to solicitations of $50 million or more. [4] After April 24, 2017, it would apply to solicitations above $500,000. [4] The disclosure period would cover decisions from October 25, 2015 to the date of the offer, or the three preceding years, whichever was shorter. [4]

The injunction stopped the first stage before any offeror had to comply. [5] The disapproval came before the second stage began. [2] In our reading, that sequence means no agency ever ran the full disclosure process at scale. The rule was tested in court and in Congress, not in contracting offices.

What erasing it meant for agencies

For agencies, the erased rule had been a set of instructions for a judgment. It told contracting officers what to collect, who would interpret it, and how to record the result. Removing it did not leave contracting officers with no guidance. It returned them to the general responsibility standards and the information already available through the federal performance and integrity system. [7]

The current text gives the officer some direction. It says contracting officers shall use sound judgment in weighing the relevance of information in the federal integrity system to the present acquisition. [7] It notes that the system may hold information covering a five-year period, some of which may not bear on present responsibility. [7] It lets a prime contractor post mitigating factors in the system, for example about subcontractor violations recorded against it. [7] Those provisions describe how to weigh what is in the system. They do not add categories of information the system lacks.

In our reading, that left a gap in method rather than in authority. A contracting officer could still weigh labor violations under the integrity standard. But no rule told the officer to look for them, no offeror had to report them, and no advisor existed to interpret them.

What was live and then removed: paycheck transparency

The clause that was in effect

One part of the rule had gone into effect. The paycheck transparency clause was prescribed for solicitations from January 1, 2017, for contracts with an estimated value above $500,000. [5] [6] The injunction had not reached it. [5] The removal rule said it may have been included in recently awarded contracts. [6]

The clause required a wage statement every pay period for individuals whose wage records were required under the Fair Labor Standards Act, the construction wage statute or the service contract statute. [4] The statement had to show hours worked, overtime hours, rate of pay, gross pay, and itemized additions and deductions. [4] Workers exempt from overtime need not see hours worked if the contractor told them in writing of their exempt status. [4]

Why the removal mattered

The clause had been operating for a short time. Contractors that received it had to produce compliant wage statements and flow the clause to covered subcontracts. [4] Under the disapproval, that clause was treated as never having taken effect. [6] Contracting officers were told to remove it where it had been included. [6]

A clause removed after award raises practical questions. A contractor that had changed its payroll statements to comply could keep the change voluntarily. A contractor that had not yet complied faced no further obligation under the clause. In our reading, the law’s fiction that the rule never took effect protected contractors from enforcement but did not unwind the work some of them had done.

What a contractor could keep

The disapproval removed the duty, not the practice. A contractor that had built itemized wage statements could keep issuing them. Nothing in the removal rule barred an employer from giving workers more information than the law required. [6] The choice became a business decision about cost, worker relations and consistency across contracts.

A contractor with both federal and commercial work faced a version of that choice. If it had applied the wage statement only to workers on covered contracts, removing it created no inconsistency. If it had applied it company-wide for simplicity, removing it would change statements for workers who had never been on a federal contract. Either way, the decision deserved a record. A contractor that later bid on work governed by a state wage statement law would also want to know whether its existing statements already met that law. The 2014 order had anticipated that overlap by treating substantially similar state or local requirements as sufficient. [3] With the federal clause gone, a state requirement, where one exists, became the remaining wage statement rule for that work.

Substitutes and independent contractors

The 2014 order allowed one substitute. Its wage statement requirement was deemed met if a contractor complied with state or local requirements that the Secretary of Labor found substantially similar. [3] The order also required a contractor that treated a worker as an independent contractor, not an employee, to give that worker a document saying so. [3]

Both provisions fell with the rest. In our reading, the second is worth noticing. A notice of independent contractor status gives a worker a record of how the employer classified the relationship. The disapproval removed a written record that would have existed from the start of the work.

Who carried the change

Payroll systems carry clauses like this one. A contractor would implement the wage statement in its payroll software or through a payroll provider. Removing the clause meant deciding whether to keep that configuration. The decision fell to payroll, human resources and contracts teams, not to the contracting officer.

That is a reminder for any organization that implements a new contract clause quickly. Its implementation may outlast the clause. Keeping a record of which clauses drove which system changes lets an organization decide deliberately what to keep when a requirement disappears.

What was never built: the data and the people

The systems

The rule depended on federal systems. Offerors would have entered disclosures in the System for Award Management, and certain information would have been published in the Federal Awardee Performance and Integrity Information System. [4] [6] After the injunction, GSA’s Integrated Award Environment immediately stopped work to release the system changes that would have supported those submissions and disclosures. [6]

That detail is easy to pass over. It means the data pipeline the rule assumed was never delivered. Even if the rule had survived, its information would have depended on those systems being completed. In our reading, the disclosure regime existed on paper in October 2016 but not yet in the systems contracting officers used.

Subcontractors and the Department of Labor

The final rule changed how subcontractor disclosures would work. Under the proposed approach, primes would have assessed subcontractor disclosures. The final rule adopted an alternative in which subcontractors disclosed to the Department of Labor, which would assess them. [4] The subcontractor would then give the prime information about that assessment. [4] If the subcontractor disagreed, it would tell the prime and give its reasons. [4]

That design placed a federal agency in the middle of private supply chains. It would have required the Department of Labor to build intake and assessment capacity for subcontractors across the government’s contracts. The requirement was to start on October 25, 2017. [4] The disapproval came first. [2]

The advisors

The order created a new position, the agency labor compliance advisor, a senior official designated in each agency. [3] [4] The advisor was to consult enforcement agencies, analyze disclosures using the Department of Labor’s guidance, and advise contracting officers. [3] [4] After award, the advisor was to monitor the system for updated information and bring it to the contracting officer’s attention. [4]

With the order revoked, that role lost its basis. [1] Whatever capacity agencies had begun to build for it had no program to serve. The contracting officer remained, with the same responsibility standard and without a designated interpreter of labor law decisions. [7]

The reporting burden

The 2016 rule estimated the paperwork it would create. Its summary of annual reporting burden listed 24,183 respondents and 417,808 total annual responses. [4] It estimated 2,166,815 hours a year, at an average rate of $61.43 an hour, for an annual cost to the public of about $133 million. [4] It put initial start-up costs at about $322 million. [4]

Those estimates describe the scale of what was never built. Each response would have been a disclosure, an update or an assessment. Each would have needed a place to go in federal systems and a person to read it. In our reading, the numbers show that the regime was as much an operational program as a legal one.

The advisor’s wider role

The 2014 order gave the labor compliance advisor duties beyond reviewing disclosures. The advisor was to meet quarterly with the agency’s deputy secretary or equivalent official. [3] The advisor was to work with the acquisition workforce and contractors to raise awareness of labor law requirements, and to coordinate help for contractors trying to prevent violations. [3]

Those duties described an agency function as well as a review step. With the revocation, agencies were free to drop the function or keep parts of it under their own authority. [1] The sources we cite do not record what each agency did. An agency that wants to know whether such capacity survives inside it would have to look at its own organization.

The cost estimates

The removal rule restated the costs the 2016 rule would have imposed. It showed total monetized employer costs of about $458 million in the first year and about $414 million in the second. [6] Government costs were about $16 million in the first year and $10 million in the second. [6] The annualized total, at a 7 percent discount rate, was about $412 million. [6]

The Council framed those figures carefully. Because most of the rule had been enjoined before compliance was required, the impacts of removal measured against actual practice were negligible. [6] Measured against a baseline in which entities complied, the removal would eliminate the costs, less any already incurred in preparing for the parts not enjoined. [6]

What the absence means for evidence

Without the pipeline, labor law information reaches contracting officers only in other ways. The current FAR requires a contracting officer, before awarding a contract above the simplified acquisition threshold, to review the performance and integrity information available in the federal system. [7] That information includes data from exclusions and past performance records. [7] It does not include the labor law decision disclosures the 2016 rule would have required, because those were never built. [4] [6] [7]

What returned by another route: forced arbitration

The 2016 design

The 2016 rule included an arbitration clause for contracts above $1 million. [3] [4] Contractors would agree that the decision to arbitrate Title VII claims, or torts related to sexual assault or harassment, would be made only with the employee’s voluntary consent after the dispute arose. [4] The clause excepted employees under collective bargaining agreements and some pre-existing arbitration contracts. [4] The injunction barred its enforcement, and the disapproval erased it. [5] [6]

Exceptions in the 2016 clause

The 2016 clause had limits. It did not apply to employees covered by a collective bargaining agreement. [4] It did not apply to employees or independent contractors who had entered a valid arbitration contract before the contractor bid on a covered contract. [4] That exception fell away if the contractor could change the agreement’s terms, or when the agreement was renegotiated or replaced. [4] Contractors had to flow the clause into subcontracts above $1 million, other than for commercial items. [4]

Those exceptions show the design’s approach. It tried to change future agreements without overriding existing collective bargaining. It worked through procurement, so its reach stopped at the edge of the government’s contracts.

The 2022 statute

On March 3, 2022, the Ending Forced Arbitration of Sexual Assault and Sexual Harassment Act of 2021 became Public Law 117-90. [8] It amended title 9 of the United States Code. [8] At the election of the person alleging sexual harassment or sexual assault, no pre-dispute arbitration agreement or pre-dispute joint-action waiver is valid or enforceable for a case relating to that dispute. [8] A court, not an arbitrator, decides whether the chapter applies. [8]

What the statute added and omitted

The 2022 statute reached one thing the 2016 clause had not mentioned: pre-dispute joint-action waivers. [4] [8] It defines them as agreements that prohibit or waive a party’s right to join a joint, class or collective action about a dispute that had not yet arisen. [8] Under the statute, such waivers are also unenforceable at the claimant’s election in covered cases. [8]

The statute did not restore anything else from the 2016 program. It contains no disclosure duty, no wage statement and no role for contracting officers. [8] It is an amendment to the arbitration title of the Code, and it works through courts. [8] It applies to disputes or claims that arise or accrue on or after its enactment on March 3, 2022, so it does not reach older disputes. [8]

How the two compare

In our reading, the statute recovered one strand of the 2016 clause and changed its reach. It was not limited to federal contractors or to contracts above a dollar threshold. [8] It applied to sexual assault and sexual harassment disputes, not to Title VII claims generally. [4] [8] It worked through the enforceability of agreements, not through a contract clause. [8]

For employers, the practical effect is different from the 2016 design. A contractor in 2016 would have accepted a clause as a condition of a contract. An employer after 2022 faces a rule about which arbitration agreements a court will enforce. The 2022 law applies whether or not the employer holds a federal contract. Organizations should ask counsel to review their agreements against it.

How the outcome affects different organizations

The rule applied to federal contractors, and federal contractors work in every sector. We set out how the 2017 outcome affects different kinds of organizations, as analysis rather than as findings of the sources.

Federal agencies as buyers

Contracting officers in federal agencies kept the duty to determine responsibility. [7] They lost a required disclosure and an advisor. An agency that wants labor compliance information in its responsibility decisions has to decide how to get it within existing authority. The current FAR tells contracting officers to use sound judgment in weighing the information available in the federal integrity system. [7]

State and local governments as buyers

State and local procurement offices were not bound by the FAR rule. Their own laws govern responsibility and labor compliance. The 2017 outcome did not change those laws. For a state or county buyer, the federal episode offers a design to study, not a requirement to follow.

Banks and financial institutions that hold federal contracts

A bank holding a federal contract above the rule’s threshold would have been within its scope. After March 2017, it was not. Its labor and employment compliance remained subject to the underlying laws, which the disapproval did not change. [3]

Health systems and health companies with federal contracts

A health organization holding a covered federal contract faced the same position. The 2016 rule would have asked them to disclose covered labor law decisions, which include workplace safety and leave decisions. [3] The disapproval removed that disclosure. It did not remove the safety and employment obligations themselves.

Contractors that had begun to comply

Some contractors had begun preparing in 2016. The removal rule acknowledged that a relatively small portion of costs may already have been incurred in preparing for the parts not enjoined. [6] Those organizations held tracking systems, procedures and payroll changes that no rule now required. For them, the 2017 outcome was a decision about what to keep.

Small businesses

The 2016 rule said it would have a significant impact on small entities. [4] Small contractors would have faced the same disclosure and paycheck requirements above the thresholds. For them, the disapproval removed a compliance cost that would have weighed more heavily against smaller administrative staffs.

Small businesses also compete against larger firms for awards. A disclosure regime applied evenly could have helped or hurt them depending on their records. The 2017 outcome removed that variable from competition. Responsibility determinations for small businesses also follow the separate certificate of competency process the FAR describes. [7]

Universities and research institutions

Universities hold federal contracts as well as grants. The FAR rule reached procurement contracts above its thresholds, not grants. [3] [4] A research university with a large contract portfolio would have faced the disclosure regime for those contracts. Its human resources and sponsored programs offices would have needed to coordinate in a way grants did not require.

Subcontractors

The subcontractor requirements were set to begin on October 25, 2017. [4] They never started. The 2014 order had expected primes to consider subcontractor disclosures; the final rule routed them to the Department of Labor instead. [3] [4] After 2017, primes kept their general duty to manage subcontractors under their contracts, but without the specific labor law disclosure process.

Objections, in order

1. The rule never operated, so its removal changed nothing

By the FAR Council’s account, most of the rule’s provisions were enjoined before compliance would have been required. [6] The FAR Council itself said the impacts of removal against actual practice were negligible. [6] But paycheck transparency had operated, and the removal reached contracts that contained it. [6] More importantly, the removal decided the future: no disclosure regime would be built on the revoked orders. [1] [6]

2. The integrity standard was always enough

Contracting officers had the integrity standard before and after the rule. [7] The 2016 rule argued that they needed structured information to apply it to labor law. [3] [4] Whether the standard alone is enough depends on what information reaches the officer. The current FAR directs review of the federal integrity system, which does not hold the labor law decision disclosures the 2016 rule designed. [6] [7]

3. Disclosure would have been unfair to contractors

Commenters argued that the rule raised due process and other legal problems; the FAR rule’s preamble listed those comment topics. [4] A federal court enjoined the disclosure provisions. [5] We do not resolve that dispute. The injunction was preliminary, and we cite no final ruling in the case. [5] The objection still has force as a design point. Any disclosure regime must decide how unadjudicated or non-final decisions are weighed, and the 2016 rule chose to count them. [4] Our point is narrower: after the rule fell, the integrity judgment stayed with contracting officers, with less structured information for one category of risk.

4. Labor law compliance is the Department of Labor’s job, not procurement’s

Enforcement belongs to enforcement agencies. The 2014 order rested on a different premise: that compliance bears on economy and efficiency in contracting. [3] The responsibility standard already links integrity to award. [7] In our reading, procurement does not enforce labor law. It decides whether to do business with a contractor, and that decision can consider the contractor’s record.

5. The 2022 arbitration law shows the rule was unnecessary

The 2022 law covered sexual assault and harassment disputes under any predispute agreement, whether or not a federal contractor was a party. [8] It did not cover Title VII claims generally, and it did not touch disclosure or paycheck transparency. [4] [8] It shows that one strand of the 2016 design could be enacted by statute on different terms. It does not show the other strands were redundant.

6. Executive orders can be reissued, so nothing was settled

A future order could pursue a similar policy. But the joint resolution did more than revoke an order; it disapproved a rule, with the legal effect that the rule is treated as never having taken effect. [2] [6] A future program on the same design would have to be built again from the start, through whatever process the law then requires. Organizations should check with counsel on the limits that apply.

7. Existing government databases already held the information

A commenter on the 2016 rule, echoing many others, suggested using existing reporting and disclosure systems instead of creating new ones. [4] The Councils responded that enforcement agency databases did not collect civil judgments or arbitral awards. [4] If that response was accurate, the disapproval left those categories of decisions outside any federal procurement record. Agencies relying on databases alone would see only part of a contractor’s history.

What procurement and compliance leaders could check

The four parts translate into checks for agencies and contractors alike.

  1. For agencies: what information do our contracting officers use today to assess a contractor’s labor law record under the integrity standard?
  2. For contractors: do any of our contracts still contain clauses from a rule that no longer has effect?
  3. For contractors: which of our payroll or HR changes were made to meet a clause that was later removed, and have we decided whether to keep them?
  4. For both: do we have a record of which clauses drove which system changes?
  5. For employers: have counsel reviewed our arbitration agreements against the 2022 statute?

The checks follow the parts. The first concerns what was erased and never built. The second and third concern the clause that was live and removed. The fourth applies to all of them. The fifth concerns what returned.

Each check has an owner. The first belongs to the agency’s senior procurement executive. The second belongs to contracts management. The third belongs to payroll and human resources. The fourth belongs to whoever keeps the compliance inventory. The fifth belongs to the general counsel.

Each check also leaves evidence. An agency can document, in its acquisition policy, what labor compliance information contracting officers consider and where it comes from. A contractor can keep a clause register that records when a clause entered a contract, why, and when it was removed. An auditor reviewing either one can then see whether a change in the law produced a matching change in practice.

A short exercise makes the 2017 outcome concrete. Take one recent award. List the information the contracting officer reviewed to find the contractor responsible. Mark which items speak to labor law compliance. If none do, the agency is applying the integrity standard without the information the 2016 rule tried to supply. [4] [7] That may be acceptable. It should be a choice, not an accident. Repeat the exercise for a contractor’s side of the same award: list the clauses in the contract, find the source of each, and confirm each still has force. A clause whose source was disapproved in 2017 should not still be shaping payroll or hiring in 2026. [6]

With hindsight

The FAR Council completed the removal on November 6, 2017. [6] Its final rule rescinded the August 2016 rule in full, including the December 2016 amendments that had implemented the injunction. [6] It cited both Public Law 115-11 and Executive Order 13782. [6]

The removal rule applied to solicitations issued and contracts awarded before, on or after October 25, 2016. [6] It said all the clauses were unenforceable by law and considered never to have taken effect, even if included in a contract. [6] It directed contracting officers to remove them from existing contracts to the maximum extent practicable, and said the paycheck transparency clause would need to be removed where included. [6]

The Council also explained why the removal’s cost savings were mostly notional. Most of the 2016 rule had been enjoined before compliance would have been required. [6] Against actual practice, the impacts were negligible. [6] Against full compliance, the removal eliminated about $412 million in annualized costs at a 7 percent discount rate, less the small portion already incurred. [6]

The Department of Labor’s guidance went with the rule. The Council said the guidance had no legal effect without the FAR rule, and that the Department was publishing its own rescission. [6] The agency labor compliance advisor role, created by the revoked order, lost its basis. [1] [3]

The responsibility framework stayed. As checked on November 15, 2026, the current FAR text still requires an affirmative determination of responsibility before award. [7] It still lists a satisfactory record of integrity and business ethics among the general standards. [7] It still requires contracting officers to review the information in the federal performance and integrity system before awarding a contract above the simplified acquisition threshold. [7]

One strand of the 2016 design returned through Congress. On March 3, 2022, Public Law 117-90 made pre-dispute arbitration agreements and joint-action waivers unenforceable, at the claimant’s election, in cases relating to sexual assault or sexual harassment disputes. [8] It is not limited to federal contractors or to employment, it applies to disputes arising on or after its enactment, and it does not reach Title VII claims as a class. [8] The 2016 clause had reached both kinds of claim, for contracts above $1 million. [3] [4]

What held up from March 2017 is the legal finality of the disapproval. The removal rule treated the 2016 rule as never having taken effect, and we cite no later rule on the same design. [6] The executive order’s revocation of the authorizing orders also stands in the record we cite. [1] As checked on November 15, 2026, the FAR provisions we cite contain no labor law disclosure requirement of the kind the 2016 rule created. [7]

What did not hold up was any expectation that removing the rule would settle how agencies judge contractor integrity on labor matters. The judgment stayed with contracting officers. [7] The information the rule would have supplied did not arrive by another route in the sources we cite. The systems work that would have carried it stopped in October 2016. [6]

For agencies and contractors, the lesson of the week is about records. A rule can vanish while the duty it served remains. Organizations were better placed after March 2017 if they knew which of their practices came from the rule, and which from the duties beneath it.

Spotted an error? Tell us and we will check it and correct the article where needed.

  • federal procurement
  • Congressional Review Act
  • FAR
  • contractor responsibility
  • labor law
  • arbitration