Prevailing Wage and Davis-Bacon: Compliance That Can't Be an Afterthought

The federal Davis-Bacon Act and its Related Acts require payment of locally prevailing wages and fringe benefits on federal and federally assisted construction contracts above a threshold dollar amount. Most states have their own prevailing-wage statutes — often called 'little Davis-Bacon' acts — covering state and local public works, and some apply to privately owned projects that receive public subsidies or financing.

The reach is broader than many contractors expect. Public funding in the capital stack — a grant, a tax-increment-financing component, federally backed financing — can trigger prevailing-wage obligations on a project that does not otherwise feel governmental. Determining whether prevailing wage applies, and under which determination, is a threshold question that has to be answered before the bid, not after the award.

Covered contractors must classify each worker correctly by trade, pay the applicable prevailing wage and fringe-benefit rate for that classification, and submit certified payroll records documenting compliance, typically every week. The prevailing rates come from a wage determination tied to the project's location and type, and they can be substantially higher than a contractor's ordinary rates.

Additional requirements frequently travel with the wage rates: apprenticeship ratios and registered-apprenticeship participation, posting of wage determinations at the jobsite, and detailed recordkeeping that must be preserved and made available for inspection. The compliance burden is administrative as well as financial.

Enforcement of prevailing-wage law is robust, and the consequences of non-compliance are severe. Violations can lead to withheld contract payments, liability for back wages and fringe benefits owed to underpaid workers, liquidated damages, and — in serious or repeated cases — debarment, which bars the contractor from bidding public work for a period of years. Debarment can be an existential penalty for a firm whose business depends on public projects.

Misclassification is a common and dangerous pitfall: paying a worker at a lower classification's rate than the work actually performed warrants is a form of underpayment that triggers back-wage liability even where the contractor believed it was compliant.

Identify the governing wage determination and the full set of compliance obligations before bidding, and build prevailing-wage rates and the certified-payroll process into estimating and payroll systems from the start. Treating prevailing-wage compliance as an administrative afterthought — to be sorted out after work begins — is how firms accumulate back-wage liability and risk debarment.

At contract review, confirm which prevailing-wage regime applies, that the wage determination is attached and current, and that the contract's flow-down of these obligations to lower tiers is matched by the contractor's ability to enforce compliance down the chain.

A point that catches contractors off guard is that prevailing-wage liability can flow upward. On many public projects, a general contractor can be held responsible for a subcontractor's failure to pay prevailing wages — through withheld contract funds, joint liability for the unpaid wages, or both. The upstream contractor cannot simply assume that handing the obligation down the chain ends its exposure.

That makes two things essential at the subcontract level. First, flow the prevailing-wage obligations down explicitly, with a requirement that lower tiers submit certified payrolls to the contractor, not just to the agency. Second, build in audit and withholding rights so the contractor can verify compliance and hold back payment if a sub's payrolls are deficient — turning the contractual obligation into something the contractor can actually monitor and enforce before liability lands on it.