Prevailing Wage and Davis-Bacon, Explained

How wage determinations are set, why they attach to the job rather than the worker, and what the fringe portion actually requires.

·By Dan Agarwal

A prevailing wage is the minimum hourly rate, plus a fringe benefit amount, that must be paid to workers in a specific trade classification working in a specific locality on a covered public project. It is not a negotiated rate and it is not the employer's usual rate. It is a published figure the project itself carries.

That last point is the one that reshapes payroll. The obligation belongs to the job, not to the person, which means the same worker can be owed different amounts in the same week depending on where they worked.

What is a prevailing wage?

It is a floor set by government rather than by market or agreement.

The idea behind it is straightforward: when public money funds construction, contractors should not compete by paying below the local going rate for skilled trades. So a rate is published for each classification in each area, and any contractor doing covered work has to meet it.

Two components make up the obligation. There is the basic hourly rate, and there is a fringe benefit amount stated separately. Both are mandatory. A contractor who pays the correct hourly rate but ignores the fringe portion has not met the obligation, and this is one of the more common ways compliance goes wrong in practice.

How does the Davis-Bacon Act determine rates?

The Davis-Bacon Act applies to federal contracts in excess of $2,000 for the construction, alteration, or repair of public buildings and public works. Related legislation extends similar requirements to a wide range of federally assisted projects, which is why the reach is broader than the headline threshold suggests.

Rates are published by the Department of Labor as wage determinations. A determination covers a geographic area, usually a county, and lists rates by classification: electrician, carpenter, ironworker, laborer, and so on, often with subdivisions within a trade. Each entry gives the basic hourly rate and the fringe amount.

The determination applicable to a project is generally the one incorporated into the contract, which is why contractors work from the determination attached to their contract documents rather than looking up a current rate. A determination can be updated, and whether an update applies to work already underway depends on the contract and its terms.

Classification is where the practical difficulty starts. A wage determination lists rates by trade classification, so someone has to decide which classification each worker's actual work falls under. That decision is not always obvious, and it has direct financial consequences.

Why does a wage determination attach to the job rather than the worker?

Because the policy is about the project, not the employee's employment terms.

An employee has an employment relationship with a contractor, with a normal rate of pay. When that employee performs covered work on a covered project, the prevailing wage obligation attaches to those hours, in that locality, under that classification. When the same employee works on a private job the following day, the obligation does not apply.

The practical consequence is that a single employee, in a single week, can generate hours at several different rates. Monday on a federal project in one county. Wednesday on a private job at their standard rate. Friday on a state-funded project in a different county with a different determination. All in the same pay period, on the same paycheck.

That is the structural reason construction payroll is harder than headcount suggests, and it is covered in more depth alongside the other moving parts of construction payroll. The rate is not an attribute of the person. It is an attribute of each hour.

What is the fringe portion, and what are the two ways to satisfy it?

The fringe is a stated amount per hour, separate from the basic rate, and it can be satisfied in one of two ways.

The first is to contribute the amount to a bona fide benefit plan on the worker's behalf: health coverage, retirement, apprenticeship training, and similar. The second is to pay the equivalent amount to the worker in cash, added to their wages.

Both are permitted. They are not equivalent in their consequences.

Cash in lieu is simpler to administer but it is wages, which means it is generally subject to payroll taxes and is included in the rate on which overtime premium is calculated. Plan contributions are not wages in the same sense, and the treatment differs accordingly. An employer who contributes part of the fringe to a plan and pays the remainder in cash has to track both, per hour, per project.

This is the single most common source of certified payroll error. Not because the rules are obscure, but because the calculation has to be right per worker, per classification, per project, per week, and because the two methods often coexist in the same workforce. The reporting side of that obligation is covered in what certified payroll actually certifies.

How do apprentice ratios and steps affect the rate?

Apprentices may be paid less than the journeyman rate, but only under specific conditions.

The apprentice must be enrolled in a registered apprenticeship program. Their rate is a percentage of the journeyman rate for their classification, determined by their step or period within the program, which advances as they accumulate hours. So an apprentice's rate is not static: it changes as they progress, and payroll has to reflect that progression.

Programs also carry ratio requirements: a permitted number of apprentices relative to journeymen on site. Exceed the ratio, and the excess apprentices are generally owed the full journeyman rate for that work.

For payroll, this means apprentice hours cannot simply be priced at a discount. The program, the step, the effective date of any step change, and the on-site ratio all have to be tracked, and all of it has to be reportable, because certified payroll requires apprentices to be identified as such.

What makes prevailing wage hard to administer at scale?

Not any single rule. The multiplication of them.

A contractor with one covered project and one classification has a simple problem. A contractor with a dozen active projects across several counties, multiple trades, apprentices at different steps, split-classification weeks, and both cash and plan fringe arrangements has a fundamentally different one, and it is not solved by knowing the rules better. It is a data problem.

The information needed lives in several places. Which project each hour belongs to comes from field time capture. Which classification applies comes from the work performed, which is often known on site rather than in payroll. The applicable determination comes from contract documents. The apprentice step comes from program records. Fringe treatment comes from benefit administration. Payroll has to combine all of it, weekly, correctly, and then produce a signed report proving it did.

Where that combination is manual, it competes for time with the pay run itself and repeats every week for the life of every project. That is why prevailing wage administration tends to strain first as a contractor takes on more public work, and why the strain shows up as reporting errors rather than as a decision to stop bidding public jobs.

This article is general information about payroll operations and reporting practice. It is not legal advice, and it does not replace the specific requirements of a contract, a wage determination, or a jurisdiction.

Frequently asked questions

Does prevailing wage apply to private projects? Generally no. The obligation attaches to public projects, or to projects receiving public funding or assistance, as defined by the applicable federal, state, or local law. A privately funded commercial project typically carries no prevailing wage requirement, which is why contractors often run covered and non-covered work simultaneously.

What is the difference between Davis-Bacon and state prevailing wage laws? Davis-Bacon is the federal statute covering federally funded or assisted construction. Many states have their own prevailing wage laws, sometimes called "little Davis-Bacon" acts, that apply to state and local public projects. They can differ in threshold, classification structure, rate determination method, and reporting requirements, and a project can be subject to both.

Can fringe benefits be paid as cash instead of into a plan? Yes. Paying the fringe amount as additional cash wages is a permitted method of satisfying the obligation. The difference is in treatment: cash in lieu is generally wages for tax purposes and affects the overtime calculation, whereas contributions to a bona fide plan are handled differently. Many contractors use a combination, which is what makes the tracking demanding.

How are wage determinations updated? The Department of Labor issues and revises determinations periodically. Whether a revision applies to an in-progress project depends on the contract, the timing of the revision relative to bid or award, and the applicable rules. Contractors generally work from the determination incorporated into their contract rather than from the current published version.

What happens when a worker moves between covered and non-covered jobs in one week? The hours are treated separately. Covered hours carry the prevailing wage obligation for the applicable classification and locality; non-covered hours are paid at the worker's ordinary rate. Both appear on the same paycheck, and the covered hours must be reportable separately for certified payroll. Overtime calculation across mixed weeks requires care, since the regular rate reflects all hours worked.

See it on your own payroll data.

The pilot runs the pipeline against your live payroll data, in your environment.