"The Davis-Bacon Act requires that workers on federally funded construction projects be paid at least the “prevailing wage” for their trade in the local area.
Mike Schmidt, Director of the CHIPS Program Office, has an excellent piece on how Davis-Bacon impacted the CHIPS program. My initial understanding was that it simply required paying construction workers more—an unnecessary transfer from taxpayers to a politically favored group, but not one that would impede efficiency. I was wrong.
Start with the complexity. Davis-Bacon’s prevailing wage isn’t a simple minimum wage: plumbers are not electricians are not fitters, and the required rate varies by locale. The Department of Labor maintains a list of more than 130,000 (!) wage rates to implement it.
That’s complicated enough. But it gets worse. Some firms building fabs used their own employees rather than contractors—and Davis-Bacon applies regardless but it covers only the portion of time an employee spends on “construction” work:
[A]pplying Davis-Bacon to company employees rather than contractors proved to be a big hurdle. Davis-Bacon required tracking every hour each employee spent on covered construction activities — by trade classification, with a different prevailing wage applying to each — and paying a wage differential for that portion of their work as distinct from fab operations work or non-Davis-Bacon construction work. The company also relied heavily on profit-sharing (where a portion of employees’ pay was tied to the firm’s profits) and Davis-Bacon’s guaranteed wage floor was difficult to reconcile with a pay structure that was inherently variable. Moreover, Davis-Bacon has a statutory requirement to pay wages weekly, meaning the company would need to change its payroll systems for a portion of the pay for a portion of its workforce.
Thus, DB required that two salaried employee with equal salaries and profit-sharing plans be paid differentially depending on whether one of them did “construction” work. This created internal strife.
Davis-Bacon was passed in 1931, when a carpenter was a carpenter. How does it apply to building a semiconductor factory?
The construction tasks involved in building and modernizing semiconductor fabs don’t always map cleanly onto DOL’s Davis-Bacon classifications, so applicants must go through a construction plan line-by-line to determine which rate applies to which activity. In traditional Davis-Bacon contexts this is less burdensome because contractors know the system and have processes in place. But semiconductor construction was a novel application, and all of our applicants — and most of their contractors — were navigating Davis-Bacon for the first time.
For large recipients, the administrative cost of this work was real but manageable relative to project scale: they could hire consultants, procure software systems, and build internal compliance capacity….
Perhaps the biggest fiasco involved timing. The government wanted firms to move quickly and encouraged them to break ground before the Act’s rules were finalized. But when Davis-Bacon was added to the Act it required that the firms pay the prevailing wage *retroactively*:
The financial and operational implications of retroactive application were significant. A leading-edge project might have 10,000–12,000 construction workers on site at peak, with a rotating workforce totaling perhaps 30,000 individuals over the project’s life. Working through 300-plus subcontractors across multiple tiers, retroactive application could require identifying wages paid to 20,000 workers who had already cycled off the project, determining what each worker should have been paid under Davis-Bacon, and paying the difference — resulting in hundreds of millions of dollars in additional cost.
The retroactive pay exposes the law’s true nature. Firms and workers had already struck voluntary agreements; the work was done, the wages paid. No one can pretend this has anything to do with incentives. Workers received a pure windfall (“DB Christmas!”) for one reason only: “construction workers” are a politically favored class. Janitors and scientists got nothing extra.
Moreover, a large fraction of the cost wasn’t the higher wages at all—it was compliance. Firms likely spent as much reworking payroll systems and hunting down thousands of former workers in this Byzantine classification system as they spent on the wage premiums themselves. Every dollar transferred to workers may have cost firms—and ultimately taxpayers—two dollars or more. A very leaky bucket indeed.
If the Trump administration is serious about cutting regulatory costs and reviving industrial competitiveness, Davis-Bacon is an obvious target. It delivers little to workers, plenty to lawyers and consultants, and a bill to taxpayers for both. Rescind it."
"The Trump administration will reportedly raise the overtime pay salary threshold from $23,660 to $36,000 in the coming weeks. Anyone below the current threshold is eligible to be paid at least one-and-a-half times their regular wage for any hours worked above 40 per week. The proposed change would make approximately 1.3 million extra people eligible for overtime pay.
Economically, such a regulatory change is a great big nothing burger. It will do nothing to affect long-term overall compensation, but will bring mild labor market dysfunction and adjustment costs along the way.
Yes, in the short-run, employers have business practices and contracts with their employees that take time to change. Some workers will therefore benefit from higher total compensation in the immediate aftermath of the rule change, as employers are now legally obliged to pay them extra for overtime. This, no doubt, will be the outcome the Trump team trumpets.
But as time goes by, employers will adjust.
That might come initially through managing their workforce to minimize the likelihood of paying overtime rates - changing shifts patterns, recategorizing workers into exempt categories, outsourcing tasks, or trimming the workforce. Basic economics tells us, though, that what employers ultimately care about are the total costs of employment. In time, the overwhelming response will be employers cutting base pay rates or other perks and benefits (relative to where they would have gone) such that overall employment costs remain unchanged. This is exactly the response that empirical research has found.
So the broadened scope of the rule will do little for workers beyond the short-term. But we’d expect it to modestly reduce the efficiency of the economy in other ways. For example, more employers might decide to spend time tracking their employees’ hours closely, disallow “working from home,” or adjust contracts towards hourly wages that are less appropriate for the nature of their industries."