If you work in construction, you’ve probably heard “Davis-Bacon” and “prevailing wage” used as if they mean the same thing. They’re closely related, but they’re not identical, and knowing the difference matters for figuring out which rules actually apply to your project.

In this article, you’ll learn:

  • The difference between the Davis-Bacon Act and prevailing wage laws
  • How to tell which one applies to your project
  • Why the distinction affects your compliance and reporting requirements

Compliance requirements, thresholds, and rates referenced in this guide reflect information available as of July 2026 and are subject to change. Always verify current requirements with the U.S. Department of Labor or the applicable state agency before making compliance decisions.

The Short Answer

 

The Davis-Bacon Act is a specific federal law. Prevailing wage is the broader concept it belongs to.

Davis-Bacon applies to direct federal contracts over $2,000 for construction, alteration, or repair of public buildings or works, with rates set by the U.S. Department of Labor. Prevailing wage is the general term for wage floors set on public projects. It includes Davis-Bacon at the federal level, but also covers dozens of state and local laws that apply even when no federal money is involved.

The short version: every Davis-Bacon project is a prevailing wage project, but not every prevailing wage project is a Davis-Bacon project.

What Is the Davis-Bacon Act?

 

The Davis-Bacon Act, passed in 1931, requires contractors on federally funded or assisted construction projects over $2,000 to pay workers no less than the locally prevailing wage and fringe benefits for their trade. Rates are determined by the Department of Labor, published by county and job classification, and apply specifically when federal funding is involved, whether through direct contracts, grants, loans, or loan guarantees.

What is Prevailing Wage?

 

“Prevailing wage” describes the underlying wage-floor standard: the combination of base hourly pay and fringe benefits that workers must receive on a given type of public project in a given area. This concept isn’t unique to the federal government. More than half of U.S. states have their own prevailing wage laws, often called “little Davis-Bacon Acts,” which apply to projects funded by state, county, or municipal governments, independent of any federal involvement.

These state and local laws can differ from federal Davis-Bacon requirements in several ways:

  • Threshold amounts that trigger coverage (some states start well above or below the federal $2,000 mark)
  • Rate-setting methods, since states may survey and calculate prevailing wages differently than the DOL
  • Covered project types, as some states extend prevailing wage rules to renovation or maintenance work that Davis-Bacon wouldn’t cover

Key Differences at a Glance

 

Davis-Bacon Act Prevailing Wage (State/Local)
Scope Federal law only Broader term; includes state and local laws
Trigger Federal funding over $2,000 Varies by state; often no federal funding required
Rate-setting body U.S. Department of Labor State labor departments or agencies
Applies to Direct federal contracts, federally assisted projects State- or municipally-funded public works
Reporting Certified payroll reports (federal format) Varies by state; some mirror federal certified payroll

Why the Distinction Matters for Contractors?

 

Knowing which rules apply, and sometimes both at once, has real consequences:

Mixed funding means dual compliance. If your project has both federal and state dollars, you may need to comply with Davis-Bacon and your state’s prevailing wage law, generally paying whichever rate is higher for each classification.

Reporting requirements can differ, too. Certified payroll formats, submission frequency, and documentation standards aren’t always identical between federal and state requirements. Treating them as interchangeable is a common source of compliance errors.

And penalties apply either way. Whether it’s a federal Davis-Bacon violation or a state prevailing wage violation, the consequences look similar: withheld payments, fines, and risk to your ability to bid on future public work.

For contractors juggling projects across multiple jurisdictions, the practical challenge isn’t understanding the definitions. It’s keeping track of which rules apply to which project, and proving compliance for each one.

How myComply Helps, Regardless of Which Law Applies

 

Whether a project falls under federal Davis-Bacon, a state prevailing wage law, or both, the underlying compliance challenge is the same: you need accurate records of who worked, when, and in what classification.

myComply’s digital orientations, worker badging, and real-time attendance tracking capture that data automatically, regardless of which wage law governs the project. That means contractors working across multiple jurisdictions (federal, state, and local) can maintain one consistent, audit-ready process instead of managing separate manual systems for each.

Conclusion

 

Davis-Bacon and prevailing wage aren’t the same thing, but they’re closely connected: Davis-Bacon is the federal law, and prevailing wage is the broader standard it’s built on, which many states and municipalities have adopted in their own form.

For contractors, the real work is figuring out which rules apply to a given project, then building a compliance process that holds up no matter which wage law is in play.

Book a demo with myComply today to see how one system can support compliance across federal, state, and local public projects.

Loading...

Discover more from myComply

Subscribe now to keep reading and get access to the full archive.

Continue reading