Prevailing-wage compliance is one of the highest-stakes administrative obligations in commercial construction. Mis-classify a worker, under-pay a fringe rate, or file a non-conforming certified payroll and your firm can face debarment from public-works projects, penalty assessments, and back-wage liability that ripples across every project on the same contract. This is a 2026 working guide for mid-market commercial subs on Davis-Bacon and state little-DB statutes, WH-347 certified payroll mechanics, fringe-benefit accounting, and the compliance pitfalls that catch firms most often.
If your firm bids public-works construction — federal projects, state projects, municipal projects, or projects with federal funding mixed in — prevailing wage and certified payroll are part of the job. The compliance overhead is real but manageable when the right systems are in place. The risk when they're not is also real: the Department of Labor and state labor commissioners take prevailing-wage enforcement seriously, and contractors with violations end up on debarment lists that shut them out of public work for years.
This post is for the mid-market commercial sub doing a mix of private and public work, or moving into public work for the first time. It walks through the statutory framework, the certified-payroll mechanics, the fringe-benefit math, and the recurring compliance failures that show up in DOL audits.
Davis-Bacon and the state "little Davis-Bacon" landscape
The Davis-Bacon Act (1931) requires that contractors and subcontractors on federally-funded construction projects of $2,000 or more pay laborers and mechanics the prevailing wage and fringe benefits for similar work in the locality where the project is performed. The Department of Labor's Wage and Hour Division publishes wage determinations specifying these rates per project, per locality, per classification.
Davis-Bacon applies to:
- Direct federal construction contracts ($2,000 threshold)
- Federally-assisted construction projects under various federal programs (HUD, DOT highway funds, EPA, etc.) — these "Davis-Bacon Related Acts" extend the requirement to a wide range of federally-funded work
- The Davis-Bacon Act was amended by the Department of Labor's 2023 update to add modern enforcement mechanisms
In addition to federal Davis-Bacon, most states have their own "little Davis-Bacon" statutes that apply prevailing-wage requirements to state-funded and sometimes municipal-funded construction. These include:
- California — Labor Code Sections 1720-1860; one of the strictest state regimes
- New York — Labor Law Article 8 (state) and Article 9 (NYC building services); rigorous enforcement
- New Jersey — New Jersey Prevailing Wage Act
- Illinois — Prevailing Wage Act, with county-by-county rate determinations
- Pennsylvania — Pennsylvania Prevailing Wage Act
- Massachusetts — Massachusetts Prevailing Wage Law
- Connecticut, Hawaii, Maine, Minnesota, Nevada, Oregon, Washington, others — varying frameworks
Conversely, some states have repealed or never enacted prevailing-wage laws — Florida, Texas, Georgia, and others, where state-funded construction doesn't trigger prevailing wage (though federally-funded work still does under Davis-Bacon).
The single most important takeaway: the controlling wage determination depends on the funding source, not the location of the work. A privately-funded project in California is not prevailing-wage. A federally-funded project in Texas is. A mixed-funded project may have portions subject to different determinations. Knowing the controlling regime per project is the foundation of compliance.
The WH-347 certified payroll form
For Davis-Bacon-covered work, contractors and subcontractors are required to submit weekly certified payrolls. The federal form is WH-347 (or an equivalent), filed weekly with the contracting agency for each pay period in which work was performed.
The WH-347 has the following key sections:
- Contractor identification — firm name, address, contract number, payroll number (sequential)
- Work week ending date
- Per-worker rows, each containing:
- Name and identifying information (often last four of SSN to protect PII)
- Work classification (per the wage determination — e.g., "Carpenter", "Electrician Journeyman", "Laborer Group 2")
- Hours worked each day, total straight time and overtime
- Rate of pay (base hourly rate per the wage determination)
- Gross amount earned
- Deductions (FICA, federal/state withholding, voluntary)
- Net pay
- Statement of Compliance — signed by an authorized officer of the contractor, certifying that the payroll is accurate, that fringe benefits have been paid, and that no rebates or kickbacks have occurred
The Statement of Compliance is the legally-significant signature: false certification is potentially a federal felony under 18 USC 1001. Most contractors take this very seriously; many state little-DB regimes have analogous certification requirements with similar penalties.
Fringe benefits: where the compliance math gets complex
Prevailing-wage rates have two components: the basic hourly rate and the fringe-benefit rate. The basic rate is the cash wage paid to the worker. The fringe rate is the value of benefits the contractor provides, OR (if not provided in benefits) the additional cash paid to the worker.
For example, a wage determination might specify:
- Classification: Carpenter Journeyman
- Basic rate: $35.50/hour
- Fringe rate: $18.75/hour
- Total prevailing wage: $54.25/hour
The contractor can satisfy the fringe rate in any combination of:
- Bona fide benefit-plan contributions (health insurance, retirement, vacation, apprenticeship training) where the contractor's annualized cost per worker can be expressed as an hourly equivalent
- Cash paid directly to the worker as part of their wages
- A mixture of the two
The complications:
1. Annualization. Benefit contributions have to be annualized based on actual hours worked across all projects (both private and public). A contractor whose health plan costs $8,400/year per employee, and whose employees work 2,000 hours/year, has an hourly benefit cost of $4.20. That's the credit allowed against the fringe rate — not the plan's "per-hour" cost as listed on the carrier's quote.
2. Public-work-only benefits. Benefit contributions that are made only on public-work hours (not on private-work hours) generally don't count toward the fringe credit. The DOL position is that bona fide benefit plans must apply to all hours, or the public-work contributions are treated as supplemental wages.
3. Cash in lieu. Cash paid to satisfy fringe requirements is subject to payroll tax. A contractor paying the full fringe rate in cash pays significantly more in payroll burden than one paying through bona fide benefit plans.
The fringe-benefit math is the most-audited and most-misunderstood part of prevailing-wage compliance. Mid-market subs often default to "pay the full fringe in cash" because it's simpler, but at scale this is expensive. Establishing bona fide benefit plans with the right annualization can save substantial labor cost on public work — but the plans have to be structured carefully and the compliance documentation has to be airtight.
The seven recurring compliance failures in DOL audits
From DOL enforcement records and from conversations with prevailing-wage compliance specialists, these seven errors account for the majority of findings:
1. Misclassification of workers. A worker performing carpentry work is paid as a laborer; a journeyman is paid as an apprentice. Misclassification is the most common DOL finding and one of the most expensive — back-wage assessments cover the difference for every hour the worker was misclassified, often across multiple projects.
2. Apprentice ratios exceeded. Apprentices can be paid lower rates if they're in a registered apprenticeship program, but only at the ratios specified by the program. Using more apprentices than the ratio allows means the excess apprentices have to be paid at the journeyman rate retroactively.
3. Fringe benefits over-credited. The contractor takes a fringe credit larger than the annualized value of the benefit. Often happens with self-insured health plans where the "per-hour cost" calculation isn't rigorously done.
4. Cash fringe under-paid. The contractor doesn't provide benefits and doesn't pay the full fringe in cash — the cash wage portion of the prevailing wage is short by the fringe amount. Easy error, often caught in audit.
5. Owner-operators and field supervisors misclassified. The owner of the firm who picks up a tool on a public project is doing covered work for those hours and must be paid prevailing wage. Field supervisors who do hands-on work for portions of their time are covered for those hours. Contractors who exclude these workers face back-wage findings.
6. Travel time and showup-pay errors. Time spent traveling between job sites or at pre-shift jobsite meetings is often compensable as covered work. Contractors who exclude this time face violations.
7. Certified payroll late or non-conforming. Filing late, filing in a non-conforming format, or filing with missing fields can trigger penalties even if the underlying wages were paid correctly.
The fines for these violations are typically computed as back wages owed plus liquidated damages plus, in serious cases, debarment from future federally-funded work for up to three years. For a sub whose public-works backlog is a significant share of revenue, debarment is an existential risk.
What good prevailing-wage compliance looks like
The fundamentals:
- The wage determination for each project is captured at project setup, with classification rates and fringe rates loaded into payroll
- Workers are classified per the wage determination, with the classification recorded against each worker per project
- Hours worked are tracked per worker per project per day per classification — not just total hours, because the classification may change if a worker does different work on different days
- Fringe benefits are annualized correctly with documented per-hour values that the DOL would accept in audit
- Apprentice ratios are tracked per project, with alerts if the project exceeds the registered apprenticeship program's ratio
- WH-347 (or equivalent) is generated weekly from the payroll record, not hand-built, with the Statement of Compliance attached and signed
- Audit trail is maintained per project for at least three years (Davis-Bacon record-retention requirement; state requirements vary)
How AOS handles prevailing wage and certified payroll
In AOS, prevailing wage is treated as a project-level attribute that propagates through payroll, timesheets, and reporting. Specifically:
- Wage determinations are captured at project setup, with all classifications and rates loaded. For federal projects, this can be pulled from SAM.gov; for state little-DB projects, from the state's published rates.
- Geofenced timesheets capture the classification per worker per shift, with the foreman able to specify if a worker performed different classifications during the day.
- Fringe-benefit annualization is computed centrally per worker, with the documented per-hour credit applied per project.
- Apprentice ratios are tracked per project, with alerts if the project hour mix exceeds the registered program's ratio.
- WH-347 (and state equivalents for California DIR, NY LS-66, etc.) is generated weekly from the payroll record, with the Statement of Compliance pre-filled for sign-off by the firm's authorized officer.
- Audit trail is field-level — every wage determination, every classification, every hour, every fringe calculation timestamped and attached to the project record for the 3-year retention requirement (longer for some state regimes).
- Multi-state and multi-jurisdiction work is supported natively — a firm working federal Davis-Bacon in three states and state little-DB in four others sees the controlling rates per project applied automatically.
The sub accounting role page covers the payroll workflow. For the connected pay-app cycle, see the AIA G702/G703 working guide. For the broader compliance backbone, see the compliance product page.
The prevailing-wage readiness checklist
- Do you have wage determinations loaded for every active public-works project, with all classifications mapped to your workforce?
- Are your timesheets capturing the classification per worker per shift, or do they aggregate hours without classification distinction?
- Is your fringe-benefit annualization documented well enough to defend in a DOL audit?
- Are your apprentice ratios tracked per project, with alerts before you exceed them?
- Is your WH-347 (or state equivalent) generated automatically from the payroll record, or hand-built in Excel?
- If audited, could you produce 3 years of certified payrolls per project in conforming format, with full audit trail?
- Do you know which workers on your crew — including the owner-operator, the field supervisors — are covered for which hours?
If most answers are "we manage with a payroll service plus Excel," that's the workflow AOS is built to replace.
One important caveat
Prevailing-wage compliance is a domain where the cost of being wrong is high and the rules are detailed. This post is informational and is not legal or compliance advice. If your firm does substantial public-works work, work with a construction attorney and a payroll specialist who specializes in prevailing-wage compliance. The software can automate the workflow, but the foundational compliance judgments (classification disputes, fringe-plan structuring, audit responses) need expertise.
If you'd like to see it
We're in private-beta design-partner mode for commercial subs and GCs. If you do public-works construction and want to walk through how AOS handles prevailing wage and certified payroll on a real project, apply to the beta.