Most contractors know Davis-Bacon applies to federal construction work. Fewer realize that a large share of public construction never touches federal money at all, and still comes with its own prevailing wage rules.
More than 30 states have adopted their own prevailing wage laws, often nicknamed “little Davis-Bacon Acts.” These laws apply to state- and municipally-funded projects, and while they’re built on the same basic idea as the federal law, the details (thresholds, rate-setting, reporting, even worker residency rules) can vary significantly from one state to the next.
In this article, you’ll learn:
- How state prevailing wage laws work and how they differ from state to state
- Why multi-state contractors face a uniquely difficult compliance puzzle
- How myComply helps standardize compliance across jurisdictions
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 applicable state labor agency before making compliance decisions.
Table of Contents – Click Links to Jump to Each Section:
What are State Prevailing Wage Laws?
Why State Laws Vary So Much
The Real Challenge: Multi-State and Mixed-Funding Projects
How myComply Supports Multi-Jurisdiction Compliance
Getting Started
Conclusion
What are State Prevailing Wage Laws?
State prevailing wage laws set minimum pay requirements, base wage plus fringe benefits, for workers on public construction projects funded by state or local governments, independent of any federal involvement. Where Davis-Bacon is triggered by federal funding, these state laws are triggered by state or municipal funding, and each state that has one sets its own rules for how it applies.
That’s the key distinction to hold onto: there is no single “state prevailing wage law.” There are dozens of separate state statutes, each with its own thresholds, agencies, and reporting requirements.
Why State Laws Vary So Much
A few examples make the range of variation clear:
- Different dollar thresholds. California’s prevailing wage law applies to public works projects over $1,000, a much lower bar than the federal $2,000 threshold. Other states set theirs considerably higher; Montana’s Little Davis-Bacon law, for instance, applies to state and local contracts of $25,000 or more.
- Different registration requirements. Some states require contractors to formally register before bidding on public work. California requires contractors to register with its Department of Industrial Relations and pay an annual fee just to be eligible to bid on public projects.
- No law at all, in some cases. Georgia, Florida, and Indiana are examples of states without their own prevailing wage statute. On purely state- or locally-funded projects in these states, no prevailing wage requirement applies, but Davis-Bacon still governs the moment federal funding enters the picture.
- Different rate-setting methods. Some states run their own annual wage surveys independent of federal data; Montana’s Department of Labor and Industry, for example, sets its own rates through yearly surveys rather than adopting federal Davis-Bacon determinations for state-funded work.
- Unique conditions layered on top. A handful of states add requirements beyond wages, such as worker residency minimums on certain state-funded projects.
The Real Challenge: Multi-State and Mixed-Funding Projects
For a contractor working in a single state, on projects funded a single way, this is manageable: learn the rules once, apply them consistently. The difficulty comes when either of two things happen:
You work across state lines. A regional or national contractor might be tracking Davis-Bacon requirements for a federal highway project in one state, a $1,000-threshold state law in another, and no prevailing wage requirement at all in a third, sometimes on overlapping timelines, with different reporting formats for each.
Your project has mixed funding. When a project combines federal and state dollars, contractors generally need to comply with both sets of requirements and pay whichever rate is higher for each classification. That means tracking two wage determinations, potentially two certified payroll formats, and being able to prove which rate was applied and why.
In both cases, the underlying problem is the same: manual, spreadsheet-based tracking doesn’t scale once you’re juggling more than one jurisdiction’s rules at a time.
How myComply Supports Multi-Jurisdiction Compliance
Because myComply captures attendance, classification, and jobsite data at the point of work, rather than relying on paper timesheets reconciled after the fact, it gives contractors a consistent compliance process no matter which prevailing wage law applies to a given site.
Configurable digital orientations per project. Set up jobsite-specific onboarding that reflects the requirements of that project’s governing law, whether that’s a federal wage determination, a state-specific one, or both.
Worker badging is tied to project and classification, so a worker moving between a federal job and a state-funded job doesn’t require rebuilding your tracking process from scratch. Each project’s badge reflects the classifications and rules relevant to that site.
Custom forms by jurisdiction allow compliance teams to standardize data capture even when the underlying reporting format differs from state to state.
And because everything lives in one auditable system across projects, contractors and their compliance teams get a single source of truth. A company running projects in five states isn’t stuck maintaining five disconnected manual processes.
Getting Started
If you’re bidding on public work across multiple states, the first step is mapping out which prevailing wage rules actually apply to each project (federal, state, or both) before you build your compliance process. From there, myComply’s digital orientation, badging, and attendance tools can be configured per project, so your team isn’t reinventing its process every time you win a bid in a new jurisdiction.
Conclusion
Davis-Bacon gets most of the attention, but for many contractors, state and local prevailing wage laws create just as much compliance complexity, if not more, especially once you’re working across state lines or on mixed-funding projects. Understanding how your state’s rules differ from the federal standard, and building a compliance process flexible enough to handle both, is essential for avoiding penalties and staying competitive on public bids.
For a deeper look at how the federal law and state laws relate, see our guide on Davis-Bacon vs. prevailing wage. And for the federal-specific requirements, check out our Davis-Bacon Act compliance guide.
Book a demo with myComply today to see how one system can support compliance across every jurisdiction you build in.