Prevailing Wage Compliance Software for public-works contractors.
Federal Davis-Bacon and state prevailing-wage rules turn a public-works job into a paperwork machine: wage determinations, classification calls, fringe accounting, weekly certified payroll, apprentice ratios, and an audit trail that has to survive a US Department of Labor or state-agency review. Clerxi runs that machine for you — so the project pays you, instead of the other way around.
What prevailing wage actually requires.
A prevailing-wage law requires contractors and subcontractors performing work on covered public-works projects to pay each worker no less than the locally-prevailing hourly wage rate, plus the locally-prevailing fringe benefits, for the classification of work that worker performs. The rate is published in advance by a government agency and locked into the contract at award.
At the federal level, the Davis-Bacon Act (40 U.S.C. 3141 et seq.) and the Davis-Bacon Related Acts apply to federal and federally-assisted construction contracts above the statutory threshold. The implementing regulations live at 29 CFR Parts 1, 3, and 5 and are administered by the US Department of Labor Wage and Hour Division.
In California, the parallel regime sits in Labor Code sections 1771 through 1814 and is enforced by the Department of Industrial Relations (DIR) and the Division of Labor Standards Enforcement. DIR publishes general prevailing-wage determinations by craft, classification, and locality, and requires online certified payroll via the eCPR system.
Roughly two dozen other states maintain their own “little Davis-Bacon” statutes — among them New York, New Jersey, Massachusetts, Illinois, Washington, Oregon, Hawaii, and Minnesota — each with its own wage-determination process, certified-payroll form, and enforcement body. Coverage thresholds, classification rosters, and apprentice rules differ by state, so a contractor working across state lines is effectively running multiple compliance regimes in parallel.
What the contracting officer actually checks.
Prevailing-wage compliance is not one document — it is a stack of interlocking obligations that have to be true at the same time for every worker, every week, for the life of the contract.
- Wage determinations. Federal determinations are published on SAM.gov and locked into the contract at award; California rates are published by DIR; other states publish through their labor agencies. The determination is keyed to project location and trade.
- Worker classifications. Each worker on covered work has to be paid as the classification matching the work actually performed — laborer, carpenter, operating engineer, electrician, ironworker, and so on — with split-rate calculations when a worker performs multiple classifications in the same week.
- Certified payroll reports. Federal jobs use form WH-347, signed under penalty of perjury as a Statement of Compliance. States typically require a state-specific certified payroll form — in California, electronic certified payroll filed through DIR eCPR. Reports are weekly and tied to the work performed in that pay period.
- Apprentice ratios and notices. Apprentices may be paid less than journey-level wages only if they are registered with an approved apprenticeship program and the contractor maintains the required ratio of apprentices to journey workers. In California, ratio enforcement runs through DAS 140 (notice of contract award) and DAS 142 (request to dispatch).
- Fringe-benefit accounting. The fringe portion of the prevailing rate can be paid in cash on the paycheck or contributed to a bona fide benefit plan, and the choice changes the math. Plan contributions have to be valued on an hourly equivalent that matches the rate book.
- Record retention. Federal Davis-Bacon records must be retained for at least three years after contract completion under 29 CFR 5.5(a)(3). State retention periods vary. The records have to be producible on demand.
- Audit response. When a complaint or compliance review opens, the contractor has to produce time records, classification calls, fringe calculations, apprentice documentation, and signed Statements of Compliance covering the entire period of inquiry.
The seven failure modes we see most often.
- Classification errors. The clearest example is a worker performing operating-engineer work — running a piece of heavy equipment — but being paid as a laborer or a carpenter on the certified payroll. The difference between trades is often several dollars an hour plus fringe, and the back-wage exposure compounds across weeks.
- Missed determination updates mid-project. Under 29 CFR 1.6 and analogous state rules, certain modifications to wage determinations have to be applied mid-job. Contractors that don’t track modifications can keep paying the original rate while the obligation has already moved.
- Fringe-rate miscalculation. Treating a plan contribution at face value instead of its hourly-equivalent value, or paying cash fringe but failing to report it correctly on the certified payroll, are common audit findings.
- Missing apprentice utilization. Paying apprentice rates without the registered-program documentation and ratio compliance to back them up converts the entire apprentice payroll into journey-rate exposure.
- Late certified-payroll filings. Late or missing weekly reports are often the first thing a contracting officer notices. Repeated lateness alone can trigger withholding and prompt a broader compliance review.
- Missing signed Statement of Compliance. The signature on the back of WH-347 is the contractor’s sworn statement. An unsigned, mis-signed, or boilerplate-only Statement of Compliance undermines the report regardless of whether the underlying numbers are correct.
- Prime-contractor liability for sub violations. Under 29 CFR 5.5(a)(6) and equivalent state provisions, the prime is responsible for compliance by all lower-tier subcontractors on the covered work. A sub’s payroll failure can become the prime’s back-wage liability.
End-to-end PW compliance, on one data layer.
Clerxi treats prevailing wage as a single workflow that begins at contract award and ends with the final certified payroll and audit-ready record. The pieces:
Wage determinations pulled by project
At project setup, Clerxi pulls the applicable wage determination by project location and trade — federal from SAM.gov for Davis-Bacon jobs, state-published rates where supported — and locks the determination to the contract record. Modifications are tracked against the locked determination so changes are explicit.
Classification validation
Worker classifications on each timecard are validated against the classifications present on the locked determination. Calls that don’t map cleanly — for example, a workaround for a missing classification — are flagged so a conformance request can be opened before the certified payroll is filed.
Fringe-rate engine (cash vs. plan)
The fringe engine handles cash and plan combinations on a per-classification basis, computes the hourly-equivalent value of plan contributions, and produces the breakdown the contracting officer expects to see on the certified payroll.
Weekly certified payroll generation
Each pay period, Clerxi generates the certified payroll record in the form the awarding agency requires — federal WH-347 for Davis-Bacon, California DIR eCPR upload format for California public works — with the Statement of Compliance attached and ready to sign.
Apprentice utilization vs. DAS 140 / 142
On California jobs, apprentice utilization is tracked against DAS 140 (notice of contract award) and DAS 142 (request to dispatch) filings, so the ratio math is auditable rather than asserted.
Immutable audit trail
Every classification call, fringe calculation, certified payroll submission, and Statement of Compliance signature is captured in an append-only audit trail bound to the project record. When a compliance review opens, the record is producible without reconstructing it from email and spreadsheets.
Anomaly detection on rate drift
Clerxi compares the rates being paid against the locked determination and against the contractor’s own historical baseline for the same classification, and surfaces drift — a rate that quietly fell behind a modification, a classification that started getting paid below trade — before the contracting officer finds it.
Federal first, California next, additional states by request.
The platform supports federal Davis-Bacon compliance — WH-347 generation, conformance workflow, fringe accounting, and the audit trail — across the United States. California public-works coverage includes DIR-published prevailing-wage determinations, eCPR-formatted certified payroll export, and DAS 140 / 142 tracking.
The data model and rate engine are designed for the broader family of state “little Davis-Bacon” regimes that mirror the federal structure with state-specific determinations, forms, and apprentice rules. Additional state coverage is being added on a customer-driven basis — if your backlog includes a specific state regime that isn’t listed above, contact support@clerxi.com and we will tell you honestly where that state sits in our current roadmap.
The penalty stack you are not exposed to.
The remedies for prevailing-wage non-compliance are layered and they compound. Each of the following is a published consequence under federal Davis-Bacon, California Labor Code, or both — actual outcomes turn on facts, intent, and the enforcing agency’s discretion.
- Back-wage liability. The starting point is paying the affected workers the difference between what they were paid and what they should have been paid, plus interest. The clock runs across the entire period of the violation.
- Contract withholding by the contracting officer. Federal regulations at 29 CFR 5.5(a)(2) authorize the contracting officer to withhold payments otherwise due to the prime in an amount sufficient to satisfy the unpaid wages. State regimes carry parallel authority. Withholding hits cash flow before any formal finding.
- False-Claims-Act exposure on the certified-payroll signature. The Statement of Compliance on WH-347 is a sworn statement to the federal government. Submitting a knowingly false certified payroll has been treated by federal courts as a basis for liability under the False Claims Act (31 U.S.C. 3729) in addition to Davis-Bacon remedies. The risk is real enough that the signature alone deserves attention.
- Federal debarment for willful violations. Under 29 CFR 5.12, contractors found to have committed aggravated or willful violations of Davis-Bacon can be placed on a list of contractors ineligible to receive federal contracts for up to three years. Debarment is the ceiling, not the floor, but it is a real consequence and the published list is public.
- State-level debarment and penalties. In California, willful violations of Labor Code 1771 and related sections expose the contractor to civil penalties and to debarment from public-works bidding under Labor Code 1777.1 and 1777.7 (apprentice-related) and related statutes.
Straight answers on the questions we get.
What counts as a public-works project?
In general, a public-works project is a construction, alteration, demolition, installation, or repair project paid for in whole or in part with public funds. Under the federal Davis-Bacon Act (40 U.S.C. 3141 et seq.), coverage attaches to federal contracts and federally-assisted construction contracts above the statutory threshold. State laws define the term independently — for example, California Labor Code section 1720 sets a broad definition that captures most state and local construction work above a dollar threshold. The specific test depends on the funding source and the awarding agency, so contractors should confirm coverage per project rather than assume.
Who actually has to pay prevailing wage?
Any contractor or subcontractor performing covered work on a covered project must pay the applicable prevailing wage rate plus fringe benefits to each worker for the classification of work that worker performs. On federal Davis-Bacon jobs the duty runs to the prime and to every tier of subcontractor. Under California Labor Code 1771, the obligation applies to all workers employed on public works, with limited exceptions defined by statute.
What happens if a worker is misclassified?
Misclassification — paying a worker the rate for a lower-paid trade or classification than the work they actually performed — typically results in back-wage liability for the difference, plus interest, and may trigger liquidated damages, contract withholding, or debarment depending on the statute and the facts. Repeat or willful violations carry heavier consequences. The contracting officer or the enforcing agency (US DOL Wage and Hour Division on federal jobs, state labor commissioner on state jobs) decides the disposition.
What is the difference between federal Davis-Bacon and state prevailing wage?
Davis-Bacon is the federal regime (Davis-Bacon Act and Related Acts, implemented at 29 CFR Parts 1, 3, and 5). State prevailing-wage laws — sometimes called "little Davis-Bacon" laws — are separate statutes that apply to state and local public-works projects in roughly half of US states. Rates, classifications, reporting forms, and enforcement agencies differ by state. On a federally-assisted state project, both regimes can apply; the higher rate generally governs.
How often do wage determinations change?
Federal Davis-Bacon wage determinations published at SAM.gov are updated periodically; modifications can be issued before contract award and, in some cases, must be incorporated mid-project under 29 CFR 1.6. State agencies such as California DIR issue their own predetermined rates, typically with semi-annual updates and effective dates that may post mid-period. Contractors are responsible for tracking the determination locked to their contract and any updates the contracting officer requires them to apply.
What is a conformance request?
A conformance (sometimes called an additional-classification request) is the process for adding a labor classification and rate to a Davis-Bacon wage determination when the work to be performed is not represented by any classification on the existing determination. Under 29 CFR 5.5(a)(1)(ii), the contractor, the contracting officer, the workers, and the US DOL all participate in setting the conformed rate. State systems have analogous processes.
How does Clerxi integrate with the existing payroll system?
Clerxi sits on top of payroll rather than replacing it. Time and pay data from the underlying payroll system is matched against the wage determination locked to each project and classification, fringe accounting is applied, and the certified payroll record is generated for filing. Where the contracting agency requires a specific upload format — for example California DIR eCPR — Clerxi formats the export to that specification. Customers connect Clerxi to their payroll system during onboarding; contact support@clerxi.com for the current integration list.
Prevailing-wage compliance overlaps tightly with three other workflows we cover: WH-347 certified payroll, DAS 140 / 142 filings, and COI cascade tracking across the prime and every tier of subcontractor.
Bring your next prevailing-wage job. We will show you the audit trail.
A 30-minute walkthrough on your wage determination, your classifications, and the way your certified payroll will look when Clerxi is running underneath it.