It’s Tuesday morning at 8:14 AM and your federal contracting officer just called the office. The Department of Labor has opened a Davis-Bacon investigation on your $12 million highway resurfacing project in Oklahoma. They want certified payroll forms – WH-347s, for the past eighteen months, with hourly breakdown by prevailing wage classification, for every worker who set foot on the project. Your office produces the forms within forty-eight hours, exported from the cloud time tracking system you switched to last year. The contracting officer compares the WH-347s against site sign-in logs and the state-mandated electronic verification feed. They flag a problem on a Thursday.
The reported hours don’t tie to the supplemental data. Three workers are listed as Laborer Group 1 at $22 per hour for hours when video footage from a neighboring construction camera shows them operating powered hand tools, chainsaws, demolition saws, a small skid steer. That equipment operation triggers Operating Engineer Group 2 at $34 per hour under the applicable wage determination for that county. The investigator wants to know why your timekeeping system reported them as Laborer for those exact intervals. Your project manager has no answer that won’t make things worse.
Davis-Bacon and the Related Acts (collectively DBRA) represent the single most documentation-heavy compliance obligation in US federal construction. The basic rule sounds straightforward: federal projects over $2,000 require workers to be paid the locally-determined prevailing wage for the classification of work actually performed. The complexity is entirely in the audit trail. The worker’s classification can change within a single workday, a laborer who picks up a chainsaw for thirty minutes worked as a Group 2 Power Tool Operator for those exact thirty minutes, at a higher hourly rate. WH-347 must reflect this granularity. Anything less is a violation that escalates quickly into debarment proceedings.
Run one Davis-Bacon week with per-task classification on, and see whether your WH-347 lines stop being a reconstruction exercise.
No credit card, up and running in 2 minutes.
See sectorClassification by the hour, not by the day
Most prevailing wage violations come from the same root cause: classifying workers at the day or week level instead of at the hour level. The traditional paper timecard asks “what was your role today?” and the worker writes one job title at the top. That single-classification daily card is, in itself, a Davis-Bacon violation if the worker actually performed two or more classifications during the day. The right approach is per-task: each segment of clock-in time carries its own classification code, its own wage rate, and its own audit trail.
GPS time tracking systems that support task-based classification let the worker (or the foreman) tag each segment of the day with the actual work performed. The morning was tied-rebar-installation, mid-morning was hand-demolition, afternoon was equipment-operation. The certified payroll WH-347 export then reflects accurate hours per classification, ready for the contracting officer with no manual reconstruction. The investigator’s question, “why does this worker show as Laborer for hours when he was operating a power tool?”, can’t arise, because the system records the classification as the work happens, not the foreman’s memory of it three days later.
Geofence segregation for multi-project contractors
A larger general contractor often runs federal and non-federal projects simultaneously. The Davis-Bacon worker at the federal highway resurfacing site is paid the prevailing rate; the same worker the next day on a private commercial parking lot is paid the company’s standard contract rate. If your time tracking system doesn’t segregate hours by project, or worse, if it lets the worker manually pick which project to apply hours to, you can end up over-paying (eating margin) or under-paying (a DBRA violation with debarment risk and personal liability for officers under §3 of the Copeland Act).
GPS geofencing per project site solves this automatically. The system knows which project the worker is physically present at based on coordinates, applies the correct wage determination, and refuses to let hours be cross-allocated after the fact. The federal job gets its hours, the private job gets its hours, and the WH-347 never sees a confusion that has to be unwound during an audit. This single architectural choice removes ninety percent of the multi-project Davis-Bacon risk that mid-sized contractors face.
The apprentice ratio puzzle
Davis-Bacon requires that the ratio of apprentices to journeymen on site at any given time not exceed the ratio approved by the registered apprenticeship program for that trade. If the approved ratio is one apprentice per two journeymen, and you put three apprentices on site with only four journeymen, the third apprentice must be paid the full journeyman rate for those hours, retroactively, with penalties if discovered during audit.
The trap is that the ratio applies in real time, not on average. Two apprentices might check in at 6 AM with two journeymen. A third apprentice arrives at 8 AM. Between 8 AM and the next journeyman’s arrival, the ratio is broken. The third apprentice owes the journeyman rate for that window. GPS clock-in data shows precisely which workers were simultaneously on site and lets you compute the apprentice ratio for every minute of the project. Real-time alerts can warn the foreman before the violation accrues, instead of three months later when the investigator reads the timecards.
