Paying Crews Across Multiple Jobsites: How Multi-Rate Payroll Allocation Actually Works

A single electrician works Monday and Tuesday on a federally funded highway project at the Davis-Bacon prevailing wage rate for that county. Wednesday through Friday, the same electrician moves to a private commercial build across town at the contractor's standard hourly rate. The two projects carry different wage rates, different fringe benefit obligations, different tax jurisdictions, and different reporting requirements, but the worker receives one paycheck at the end of the week.

For trade contractors running multiple active projects, this scenario is not an edge case. Nearly 50% of payroll professionals in construction rate tracking and applying different pay rates across sites as moderately to extremely challenging, according to a survey reported by Construction Owners Association of America. Every hour must be allocated to the correct project, paid at the correct rate, costed to the correct job code, and reported on the correct compliance document. Any error in that chain creates either a wage violation or a job costing inaccuracy.

Why the Same Worker Earns Different Rates on Different Projects

In most industries, an employee has one pay rate. In construction, a single worker can earn multiple rates within the same pay period, and the rate is determined by the project, not the person.

What Drives Rate Variation

Several factors can change a worker's hourly rate from one jobsite to the next:

• Prevailing wage determinations. A worker on a Davis-Bacon or state prevailing wage project earns the rate specified in the wage determination for that project's location and trade classification. The same worker on a private project earns whatever rate the contractor has agreed to pay.

• Trade classification. A worker who performs electrical rough-in on one project and general labor on another may fall under different classifications, each with its own rate, even if both projects are prevailing wage.

• Geographic location. Prevailing wage rates vary by county. A contractor with projects in two adjacent counties may need to apply different rates for identical work performed by the same crew.

• Union versus non-union projects. Workers covered by a collective bargaining agreement on one project may work at a different rate on a non-union project.

A single payroll run for a contractor with five active projects might process the same 20 workers at three or more different rates, split across different cost codes, tax jurisdictions, and compliance categories.

How Hours Must Be Tracked for Multi-Rate Payroll

Accurate payroll allocation starts with accurate time capture. A total weekly hour count is not enough. The system must capture where each hour was worked, under which classification, and on which project.

Project-Level Time Capture

Every hour must be recorded against a specific project and cost code at the point of entry. A worker who spends four hours on a prevailing wage bridge project and four hours on a private renovation in the same day generates two separate time entries, each tied to the correct job. ​Field and labor tracking systems that capture project and classification at clock-in prevent the allocation from becoming a manual exercise at the end of the week.

Why Weekly Totals Are Not Enough

A timecard showing "40 hours, John Smith" without project-level breakdown forces the payroll administrator to reconstruct the allocation by calling the foreman or checking the ​crew schedule. That reconstruction introduces errors and produces unreliable ​job costing data.

How Overtime Works With Multiple Pay Rates

Overtime calculation becomes significantly more complex when a worker earns different rates during the same workweek. The Fair Labor Standards Act (FLSA) provides two methods for calculating overtime when multiple rates apply.

The Weighted Average Method

Under FLSA, when a worker earns two or more rates in the same workweek and works more than 40 hours, the employer may use a weighted average to determine the overtime premium. The weighted average is calculated by dividing total straight-time earnings across all rates by total hours worked, then paying an additional half of that average rate for each overtime hour.

A worker earning $35/hour for 24 hours on a private project and $52/hour for 20 hours on a prevailing wage project has $1,880 in straight-time earnings across 44 hours. The weighted average is 42.73/hour,andtheovertimepremiumforthe4overtimehoursishalfofthat(21.36/hour) on top of the rate earned during the overtime hours.

Prevailing Wage Overtime Rules

On Davis-Bacon projects, overtime requirements under the Contract Work Hours and Safety Standards Act (CWHSSA) may apply separately. CWHSSA requires time-and-a-half for hours over 40 per week on covered federal contracts, calculated on the basic rate of pay (not including fringe benefits). The overtime calculation on the prevailing wage project must follow federal rules regardless of how overtime is computed on the contractor's private work.

​Construction payroll teams processing workers who split time between federal and private projects must apply the correct overtime methodology to each set of hours.

How Multi-Rate Payroll Connects to Certified Payroll and Job Costing

Multi-rate payroll allocation does not end when the paycheck is issued. The same allocation drives two downstream outputs that contractors cannot afford to get wrong.

Certified Payroll Reporting

Each prevailing wage project requires its own ​certified payroll report showing only the hours, rates, and classifications applicable to that project. A worker who splits the week between two Davis-Bacon projects with different wage determinations appears on two separate WH-347 reports, each reflecting the correct rate for that project.

Reporting private-project hours on a prevailing wage certified payroll, or applying the wrong wage determination, creates discrepancies that surface during audits.

Job Cost Allocation

Every labor dollar must land on the correct project and cost code for job costing to produce meaningful data. When a worker earns $35/hour on one project and $52/hour on another, the fully burdened labor cost for each project is materially different. A payroll system that posts labor costs based on allocated hours and actual rates per project gives controllers accurate budget-versus-actual data. Averaging the rate or posting hours without project-level allocation distorts profitability on every active job.

Accurate ​payroll reports that break down labor cost by project, classification, and rate are the foundation of reliable job costing.

Common Multi-Rate Payroll Mistakes

Five errors recur across trade contractors managing crews on multiple active job sites.

• Paying one flat rate across all projects. Applying a single rate to a worker who should earn different rates on different projects results in underpayment on the higher-rate job and margin loss on the lower-rate job.

• Allocating hours to projects after the fact. Reconstructing project-level time from memory or foreman phone calls after the pay period closes introduces allocation errors that compound every cycle.

• Blending overtime across prevailing wage and private projects. Federal and private overtime rules may differ. Averaging the calculation across both creates compliance risk on the federal side.

• Using the wrong trade classification across sites. A worker who runs conduit on one project and pulls wire on another may fall under different classifications. Paying the same rate for both misclassifies the work.

• Failing to separate certified payroll by project. Each Davis-Bacon project requires its own certified payroll report. Combining hours from multiple projects on one report creates a submission error.

How Trayd Handles Multi-Rate Payroll Across Jobsites

Trayd is a back-office operating system built for construction that unifies ​payroll, HR, compliance, and job costing into a single platform designed for the complexity of trade contracting. For contractors managing crews across multiple active job sites with different wage rates, classifications, and compliance requirements, Trayd connects field-level time capture to payroll processing and certified payroll reporting, so every hour is allocated to the correct project, paid at the correct rate, and costed to the correct job code without manual reconstruction.

​Schedule a demo to see how Trayd handles multi-rate payroll allocation for trade contractors running crews across multiple job sites.

Frequently Asked Questions

Can the same worker earn different pay rates on different projects in the same week?

Yes. Construction workers commonly earn different rates based on project type (prevailing wage versus private), trade classification, geographic location, and union agreements. Each rate must be applied to the correct hours.

How is overtime calculated when a worker has multiple pay rates?

Under the FLSA, employers may use a weighted average method. Total straight-time earnings across all rates are divided by total hours to determine the average rate, and the overtime premium is half that average for each hour over 40.

Does each prevailing wage project need its own certified payroll report?

Yes. Each Davis-Bacon or state prevailing wage project requires a separate certified payroll report reflecting only the hours, rates, and classifications applicable to that specific project.

What happens if hours are allocated to the wrong project?

Incorrect allocation can result in underpayment on prevailing wage projects (a compliance violation), inaccurate job costing, and errors on certified payroll reports that surface during audits.

Why can't I use one flat rate for a worker across all projects?

Different projects carry different wage obligations based on prevailing wage determinations, trade classifications, and contract terms. Applying a single rate results in either underpayment or overpayment depending on the project.

How should field time be captured for multi-rate payroll?

Every hour should be recorded against a specific project and cost code at the point of entry. Weekly totals without project-level breakdown force manual reconstruction that introduces errors.