Davis-Bacon Fringe Benefits: The Mixed-Week Trap for Temps

A laborer clocks in Monday at a federally funded school renovation. Wednesday, dispatch pulls her to a private warehouse fit-out. Friday, she is back at the school. Payroll runs Sunday.

If your system applies a single blended rate across that week, you are either overpaying and killing margin, or underpaying and building audit exposure. Davis-Bacon fringe benefits do not average out at the week level. They attach hour by hour, jobsite by jobsite, classification by classification — and that is the fault line where staffing agencies get caught.

This is the mixed-week problem. It never shows up cleanly on a WH-347, and it is exactly what DOL investigators are now trained to find.

The Mixed-Week Problem Nobody Puts on the WH-347

The rule is unambiguous. Prevailing wages, including fringe benefits, must be paid on all hours worked on the site of the work. Not per week. Not per project. Per hour on covered ground.

For a general contractor with one crew on one federal project, that is manageable. For a staffing agency dispatching temps across a portfolio of federal, state, and private jobsites in the same pay period, it is a data problem the timekeeping system was never designed to solve.

Consider the mechanics. The same worker on the same W-2 might touch three different wage determinations in five days. Each covered hour needs the base rate for that classification on that determination, plus the fringe obligation attached to that rate. Each non-covered hour reverts to your agency's standard comp package. Blend those hours and you break the math in both directions.

How the Fringe Math Actually Splits Across Jobsites

Start with the two-part structure. The Davis-Bacon prevailing wage is the combination of the basic hourly rate and any fringe benefits listed in a Davis-Bacon wage determination. The contractor's obligation can be met by paying each laborer the applicable prevailing wage entirely as cash wages or by a combination of cash wages and employer-provided bona fide fringe benefits.

That flexibility is where the operational trap lives. On non-covered hours, the worker gets whatever your agency provides — health premium, PTO accrual, 401(k) match, whatever the standard package is. On covered hours, the fringe component has to hit the wage determination floor for that classification, either through bona fide benefit contributions or cash-in-lieu paid on top of the base rate.

The annualization rule is the piece most agencies miss. To annualize the cost of providing a fringe benefit, a contractor must divide the total cost of the fringe benefit contribution by the total number of hours worked on both private work and work covered by the Davis-Bacon Act during the time period to which the cost is attributable to determine the rate of contribution per hour.

Read that carefully. You cannot fund a benefit plan disproportionately from Davis-Bacon hours and claim full credit against the fringe obligation. If a $200-per-month health premium translates to a $1.15 per-hour credit across all hours worked, that $1.15 is what offsets the fringe requirement — not the full fringe amount listed on the wage determination.

A worked example

Assume a carpenter classification with a $32.00 base rate and $12.50 fringe. Your agency provides health insurance worth $1.15 per hour and a 401(k) match worth $0.85 per hour, both annualized across all hours worked.

Hour type	Base owed	Fringe owed	Benefit credit	Cash-in-lieu required
Davis-Bacon carpenter hour	$32.00	$12.50	$2.00	$10.50
Private warehouse hour	Agency rate	Agency package	$2.00	$0.00
Davis-Bacon laborer hour	Lower base	Lower fringe	$2.00	Determination-specific

If your payroll system does not know which hour belongs to which bucket at the time the timecard is cut, the cash-in-lieu column is guesswork.

The Classification Trap When Duties Change by Jobsite

The fringe split is only half the problem. The other half is classification, and the DOL is explicit that job titles do not save you. Employers must match job duties, rather than job titles, to assign the correct wage determination rates. This means that when classifying workers, it's important to look at the specific duties the workers perform to evaluate how local prevailing practice would classify the work.

For a staffing agency, that is a duty-level capture problem, not a dispatch-level capture problem. You cannot mark a worker as "laborer" in the ATS and let that ride across every jobsite. If she frames on Tuesday and hauls debris on Thursday, those are two classifications on one W-2 in one pay week.

A recent enforcement case makes the stakes concrete. In one action, a company had to pay $596,443 in back pay and fringe benefits, and the DOL Wage and Hour Division debarred the company and its owner from bidding on federal construction contracts for three years because of clearly willful efforts to violate the Davis-Bacon Act. The underlying violation: misclassifying skilled trades as lower-skilled laborers to save on rate.

Why 2026 Enforcement Makes This Worse for Staffing Agencies

Enforcement posture has shifted, and the shift is bad for anyone running a dispatch model. The final rule that went into effect in October 2023 was the first major update to the Davis-Bacon regulations in four decades, and it changed the risk profile permanently.

Three changes matter for staffing agencies:

1. Mandatory three-year debarment. The Final Rule attempts to make uniform debarment standards by eliminating the "aggravated or willful" standard that appears in certain Related Acts and uniformly applies a three-year mandatory debarment period.
2. Daily-compounded interest on back wages. New language in the Final Rule requires interest, compounded daily, to be added to back wages and other monetary relief.
3. Prime contractor liability for subs, regardless of intent. The FAR clause that accompanies the Final Rule requires prime contractors and upper-tier subcontractors to pay back wages when their lower tier subcontractors violate the Final Rule. In appropriate circumstances, violations by a lower-tier subcontractor may subject the prime and upper-tier contractors to debarment. Prime contractors are now responsible for a subcontractor's back wages, regardless of any showing of intent on the part of the prime contractor.

For a staffing agency, that third point cuts both ways. Your GC clients now have direct financial exposure to your compliance failures, which means they will push their diligence downstream to you. And if you sit in the middle of the tier — placing labor under a subcontractor who bills the prime — you will be squeezed from both sides. Read the Department of Labor's own guidance on the final rule for the authoritative text.

The Real Cost of Getting It Wrong: Back Wages, Penalties, Debarment

The financial exposure is not theoretical, and it is not capped at the underpayment. On federally funded construction projects governed by the Davis-Bacon Act, fringe benefits must be calculated accurately and reported alongside base wages to satisfy prevailing wage requirements and avoid penalties, including back wage assessments, fines up to $10,000 per violation, and debarment from future federal contracts.

Back wages are assessed per worker, per week, for the full look-back window. Interest compounds daily. Fines stack per violation. Debarment removes you from the federal contracting market entirely.

Contractors that disregard obligations to employees or subcontractors under the DBRA are now subject to a three year debarment period with no early removal option. This debarment and loss of federal contracts covers not only the violating entity but could also cover any other entity with an interest in the debarred entity and the individual officers of the debarred entity that were responsible for the failure to comply.

Read that last sentence twice. Debarment can attach to affiliated entities and to individual officers. For a staffing group with multiple operating companies under a parent, one bad temp week on one federal project can radiate across the org chart.

A single fringe math error on one classification, replicated across a hundred temps for a hundred weeks, is not a rounding issue. It is an existential liability.

The Operational Fix: Jobsite-Aware Time Capture and Rate Tables

Everything upstream of payroll has to know which hour belongs to which project. That is the only way the fringe math resolves cleanly. Blended-rate approaches, spreadsheet reconciliations, and Friday-night manual splits all fail the same way — they treat classification and jobsite as attributes of the worker, when they are actually attributes of the hour.

The fix has four layers:

• Jobsite-anchored clock-in. Every punch must attach to a specific jobsite record, not just a client or a project code. GPS verification confirms the worker was on covered ground when the hour was worked.
• Wage determination versioning. Each jobsite record carries the current wage determination from SAM.gov, versioned by effective date so retroactive changes do not corrupt historical timecards.
• Duty-level classification capture. When a worker performs multiple trades in a shift, the timecard must support splitting hours across classifications with supervisor sign-off.
• Two-part rate tables. Base rate and fringe rate stored separately per classification per determination, so cash-in-lieu is computed per hour, not per week.

This is why job-site time tracking and GPS-verified clock-in are not nice-to-haves for federal-adjacent staffing work. They are the substrate the compliance layer sits on.

Certified Payroll Without the Weekly Fire Drill

WH-347 is the visible artifact, but the fire drill starts long before Friday. If your hour data is not jobsite-tagged and classification-split at the moment of capture, someone in payroll is reconstructing it from dispatch logs, GC sign-in sheets, and text messages between supervisors. That is where transcription errors enter, and transcription errors are what auditors flag.

Manual entry is where the majority of errors originate. Human eyes miss the difference between a $28.50 rate and a $28.05 rate. By the time you catch it, you may have filed ten weeks of incorrect reports.

The Statement of Compliance on page 2 of the WH-347 is not a formality. It is a signed legal certification. False certifications in certified payrolls can create costly False Claims Act exposure. That converts a payroll error into potential fraud liability — a different order of magnitude of legal risk.

A clean pipeline looks like this:

1. Timecard closes with jobsite, wage determination, and classification already attached.
2. Rate engine applies the correct base and fringe per hour, computing cash-in-lieu where benefit credits fall short.
3. Exception queue flags any punch missing a jobsite tag, any duty-classification mismatch, and any determination change since last week.
4. WH-347 generates directly from the ledger with no manual splitting.
5. Signatory reviews exceptions, not the whole file.

That exception-handling and compliance-report layer is what makes weekly certified payroll a review workflow instead of a reconstruction workflow. See how admin tools structure this for operators running dozens of concurrent federal projects.

What to Audit in Your Own Process This Quarter

Before the next mixed pay week hits, walk your own stack through these four checks:

1. Can your timekeeping system distinguish covered vs. non-covered hours within a single shift? If a worker leaves the federal jobsite at 11:00 a.m. and shows up at a private site at noon, does the system record that as two segments with two rate structures?
2. Are wage determinations pulled from SAM.gov and versioned by project? All Davis-Bacon wage determinations are published on SAM.gov — the single authoritative source for prevailing wage information. If your team is pulling PDFs by hand, you have already accepted latency and version drift.
3. Does your fringe allocation itemize plan contributions vs. cash-in-lieu per hour? A blended annualized credit is not enough. You need the split visible per punch so the WH-347 columns tie back to source data.
4. Do you flag classification changes when a worker's duties shift mid-week? A carpenter framing on Tuesday and hauling debris on Thursday is two classifications. Your system should force a supervisor decision, not silently ride the dispatch label.

For staffing operators running crews across federal and private work, this is what the operational floor has to look like. If any of the four checks fail, that is where the next audit finding is already forming.

Staffing agencies that treat Davis-Bacon as a payroll problem lose. Agencies that treat it as a time-capture problem win. See how Teambridge structures this for agencies dispatching across federal and private construction work.