Certified Payroll & Prevailing Wage: A Contractor's Survival Guide
TL;DR — 30 seconds
Certified payroll and prevailing wage compliance guide — Davis-Bacon basics, WH-347 fields mapped to time-card data, common violations, and a software checklist. See it on your plans →
Public work pays well and audits hard. Federal and state prevailing wage requirements — most famously Davis-Bacon on federally funded construction — obligate contractors to pay government-set minimum wages and then prove it weekly through certified payroll. Contractors lose more money here to penalties, withheld payments, and disqualification than the compliance ever cost to do properly. This guide maps what the rules demand onto the time-card data you already collect.
Davis-Bacon in Plain Terms
The framework, heavily simplified:
- On most federally funded or assisted construction contracts above modest dollar thresholds, workers must be paid at least the prevailing wage for their classification in that county, as published in the contract’s wage determination
- Wages include a base rate plus often a fringe benefit amount per hour
- Thresholds, applicability, and enforcement details vary by funding program, and many states run their own “little Davis-Bacon” laws on public work with their own rates and forms
Treat this as orientation only: which law applies, at what threshold, and with which wage determination is established by your specific contract documents. Read them before mobilizing, not before the first payroll submission.
WH-347: Mapping Fields to Time-Clock Data
The standard federal certified payroll form is the WH-347, submitted weekly. Every field traces back to field time capture — which is why sloppy construction time tracking makes certified payroll painful.
| WH-347 element | Where it comes from |
|---|---|
| Employee name & identifying number | Employee records (last 4 of SSN commonly used) |
| Work classification | Per-project classification assigned at clock-in — laborer, operator, carpenter, etc. |
| Day & date, hours worked each day | Daily time entries, not weekly totals |
| Total hours + overtime split | Clock-in/out times versus daily overtime thresholds |
| Hourly base rate paid | Payroll setup per employee per project |
| Fringe benefits (paid or contributed) | Benefit plan contributions or cash-in-lieu amounts |
| Gross earned this project | Hours × applicable rates, computed per classification |
| Deductions & net wages | Standard payroll deductions |
Notice the structural requirement hiding in that table: hours must be tracked by day and by classification per project. A foreman’s Friday summary saying “Jose, 40 hours” cannot produce a compliant WH-347 if Jose ran an excavator Tuesday and poured Wednesday.
The Violations That Sink Contractors
Enforcement actions cluster around a handful of failures:
- Misclassification: paying someone at a lower-rated classification than the work performed — whether intentional or from lazy timekeeping
- Fringe failures: keeping the fringe amount as wages without documentation, or paying cash-in-lieu where bona fide plan contributions were required; fringe math errors are among the most common findings
- Overtime miscalculation: prevailing wage overtime is computed on the total prevailing rate including fringes under federal rules — a detail many payroll systems miss
- Missing or late submissions: certified payroll typically due weekly to the contracting agency; chronic lateness can freeze payments
- Apprentice ratio violations: apprentices must be registered and paid per program schedules, within supervision ratios
Penalties escalate from withheld payments to debarment from public work — the latter being an existential business threat for contractors built on public projects.
Software Requirements Checklist
Manual certified payroll means retyping hours into forms every week, and every retype is an error waiting for an auditor. Systems worth using provide:
- Per-project, per-day, per-classification time capture as a native output of field entry
- Wage determination storage with rates and fringes applied automatically by classification
- Automatic WH-347-format reporting (and equivalents for state programs)
- Fringe handling supporting both bona fide plans and cash-in-lieu with clean audit trails
- Overtime logic configured for prevailing-wage rules rather than generic FLSA-only math
- Immutable edit history so corrections are documented, not overwritten
- Submission tracking showing what went to which agency and when
Verified GPS-stamped time entries strengthen everything downstream — see how GPS time clocks feed defensible hours into exactly this pipeline.
BidSync AI captures classified daily hours in the field and drives payroll, job costing, and certified-payroll-ready reporting from that single entry. See field operations capabilities or book a demo to watch a week of time cards become a compliant submission.