JOC Procurement

JOC Prevailing Wage and Davis-Bacon Requirements

9 min read · PreCon JOC

Every JOC solicitation defines multiple coefficient categories — and the distinction between them is labor law, not accounting. The JOC coefficient a GC submits for "normal hours, prevailing wage" (F3) must reflect actual prevailing wage labor costs. The Davis-Bacon coefficient (F5) reflects federally determined wage rates that apply when federal funds touch the project. Getting these wrong means the GC is either underpaying workers or the agency is paying an inflated rate — both are audit findings.

The three labor categories in a JOC coefficient structure

The standard 7-factor JOC coefficient structure separates work into three wage categories, each appearing in both normal hours and other-than-normal hours:

F1 / F2

Non-prevailing wage

Work not subject to any prevailing wage law. Applies when the task order is funded entirely by local or state funds that do not trigger state prevailing wage statutes, and the project is not subject to federal Davis-Bacon.

F3 / F4

Prevailing wage (state)

Work subject to the applicable state prevailing wage law — in Texas, the Texas Prevailing Wage Act for public works contracts above the statutory threshold. The GC must pay journeymen and helpers at the wage rates published by the Texas Department of Insurance for the county where the work occurs.

F5 / F6

Davis-Bacon (federal)

Work on projects receiving federal financial assistance — HUD grants, FEMA reimbursements, federal highway or transit funds, EPA grants, ESSER, and others. Davis-Bacon wage determinations are issued by the U.S. Department of Labor and are specific to the county, work type, and prevailing craft.

What determines which category applies to a task order

The determination is made at the task order level based on the funding source for that specific task order — not the program as a whole. A single JOC contract can generate task orders in all three categories depending on how each individual task order is funded.

Funding sourceWage categoryCoefficient
Local general fund, no federal nexusNon-prevailingF1 / F2
State appropriation, Texas public works threshold metTexas prevailing wageF3 / F4
HUD CDBG, FEMA PA, ESSER, federal grantsDavis-BaconF5 / F6
Mixed funding (federal + local)Davis-Bacon applies to entire task orderF5 / F6

Mixed funding rule

When any federal funds touch a task order — even a small supplemental grant — Davis-Bacon applies to the entire task order, not just the federally funded portion. The "federal nexus" taints the whole scope. Many agencies learn this only during a DOL compliance review.

What Davis-Bacon compliance requires from the GC

When a task order is subject to Davis-Bacon, the GC's obligations go well beyond paying the right wage rate. Federal compliance includes:

The agency is responsible for verifying that the GC is in compliance — a failure to monitor is itself a finding. Agencies must have a monitoring plan that covers random payroll audits, site interviews, and certified payroll review before payment releases.

Common wage determination errors and their consequences

HIGH

Using an outdated wage determination

Davis-Bacon wage determinations are updated periodically. The determination that must be used is the one in effect on the date the task order is issued, not the date the JOC contract was awarded. Using an older determination that has since been superseded means workers may be underpaid — the GC owes back wages, and the agency may face grant clawback.

HIGH

Using the wrong classification

Every trade has a specific classification under Davis-Bacon. A worker doing framing classified as a laborer instead of a carpenter is underpaid under the determination. If the worker's actual duties match a higher classification, the higher rate applies — regardless of what the GC calls the job.

HIGH

Applying prevailing wage instead of Davis-Bacon on a federally funded task order

Texas prevailing wage rates and Davis-Bacon rates are different. For federally funded work, only Davis-Bacon applies — state prevailing wage does not substitute. Applying the lower (or different) state rate on a task order with a federal nexus results in underpayment.

MEDIUM

No certified payrolls on file

The agency collected task order deliverables but never collected certified payrolls. This is a standard finding in FEMA and HUD audits on JOC programs. Without the payrolls, there is no way to demonstrate compliance, and the auditor's default assumption is noncompliance.

MEDIUM

GC uses F1/F2 coefficient on a task order that required F5/F6

Because the Davis-Bacon coefficient is typically higher (the GC has higher labor costs), using the non-prevailing coefficient on a Davis-Bacon task order means the agency underpaid for the work and the GC absorbed a margin squeeze. More importantly, Davis-Bacon wage obligations still applied — underpaying workers is not excused by the coefficient error.

What your solicitation must address

A JOC solicitation that handles wage requirements correctly will include:

For GCs: building your F3 and F5 coefficients correctly

Your F3 (prevailing wage) and F5 (Davis-Bacon) coefficients must be higher than F1 (non-prevailing) because your labor costs are higher on those task orders. The difference should reflect the actual delta between your open-shop labor rates and the applicable prevailing or Davis-Bacon rates for the county.

A common mistake is to submit nearly identical coefficients across all seven factors. This suggests the GC either did not model actual wage costs or is planning to absorb losses on prevailing wage task orders. Both are red flags: the first creates compliance exposure; the second creates financial risk that may surface as change order abuse later in the contract.

Example — reasonable spread

F1Normal · Non-prevailing1.0750
F3Normal · Prevailing wage1.1120
F5Normal · Davis-Bacon1.1340

The spread from F1 to F5 (3.7 pts) reflects meaningfully higher labor costs — not an arbitrary markup.

Coefficient compliance

Flag wage category mismatches before award

PreCon JOC checks each task order's funding source against the coefficient used and flags mismatches — so a Davis-Bacon task order issued under a non-prevailing coefficient is caught before payment.

Set up your program →