Someone Signs That Payroll Under Penalty of Perjury
On private work, a timekeeping tool's defaults produce a wage dispute. On federally funded construction, the same defaults produce a weekly sworn statement that the payroll is correct and complete — signed by a person, about numbers a system decided.
Prevailing-wage coverage attaches through the contract, not the employer: federal construction contracts above the statutory threshold, and a long list of federally assisted programmes that incorporate the same requirements. Coverage brings a classification-specific rate from an applicable wage determination, a base-plus-fringe obligation, apprentice ratio limits, and a weekly certified payroll. Automation touches every one of those, and the certification converts an ordinary record-keeping error into a signed assertion.
One Week, Five Defaults, One Signature
None of the events below is misconduct. Each is a configuration choice that a reasonable operations team would make, and each survives into the payroll unchallenged because the output looks like every other week's output.
Crew clocks in via a geofenced mobile app; two workers are outside the fence on a staging lot and are auto-clocked in on arrival instead.
A carpenter spends the afternoon on covered demolition work under a different classification. The system carries the morning's trade for the full day.
Automatic 30-minute lunch deduction applies to the whole crew. Two workers ate on the wall and kept working.
A supervisor edits four timecards after a costing review; the tool records the edit but not a reason.
Apprentice scheduling filled a gap with a third apprentice on a two-journeyworker crew, exceeding the permitted ratio.
The weekly payroll and statement of compliance are generated from those records and signed.
The Settings That Have to Change on Covered Jobs
Most contractors run one timekeeping configuration across all work. The single highest yield change available is a covered-project mode: same tool, different defaults, applied per job rather than per company.
Classification Is a Legal Determination Wearing a Dropdown
The most consequential thing these systems do is not counting minutes. It is deciding which classification a worker's hours belong to, because that choice selects the rate from the wage determination. Software makes that choice from proxies — the crew, the cost code, the job title, sometimes a photograph or a task description — and proxies are exactly what the standard rejects. The rate follows the work actually performed, recorded in the hours actually spent on it.
The consequence of getting this wrong is not symmetric. A worker whose split time is unrecorded is owed the higher applicable rate for the disputed hours, back wages run across every similarly situated worker on the job, and the same misconfiguration repeats weekly until someone notices. A classification default is therefore a systematic error, not an isolated one, which is why these findings arrive at scale.
Who Actually Carries It
Captures time and proposes a classification. Owes accuracy to nobody in a legal sense.
Transcribes the output into a weekly payroll. Rarely in a position to question a classification.
Certifies the payroll is correct and complete, under penalty of perjury, weekly, across every covered job.
Generally responsible for subcontractor compliance on the covered contract; faces withholding and debarment exposure.
Withholds funds, orders restitution, and refers wilful conduct onward.
Read downward, the chain explains why vendor indemnity is a poor substitute for configuration. Liability concentrates on the two rows in the middle — the people whose names are on the certification and the prime whose contract is at risk — and neither of them chose the rounding rule.
What to Do Before the Next Covered Award
Run one covered job's week end to end by hand and compare it against what the system produced. The exercise takes an afternoon and finds every default that matters, in the only form anyone will later care about: the difference between the hours a crew worked and the hours a signed payroll says they worked. Do it before an award rather than after a complaint, because the same weekly cadence that makes the exposure repetitive also makes an early fix cheap and a late one retroactive across months.
Related Reading
- FLSA exposure from AI timekeeping and idle detection — the same defaults on ordinary private work.
- False Claims Act risk for federal contractors using AI — what a certification attached to a federal contract can escalate into.
- Algorithmic productivity quotas and workplace safety — the other place automated measurement of work becomes a legal duty.
Check What Your Site Claims About Compliance
"Davis-Bacon ready", "automatic certified payroll", "prevailing wage compliant" — capability pages, vendor badges and case studies age badly, and they are read as representations by the people who rely on them.
See every claim your site is making in one pass. Run a free scan and check each against what your systems actually do.
This article is general information and not legal advice. Prevailing-wage coverage, thresholds, wage determinations, apprenticeship rules and state analogues vary and change; several states impose their own prevailing-wage requirements on state-funded work with different terms. Consult qualified counsel before relying on any conclusion here.