Multi-State Prevailing Wage Compliance for Traveling Contractors

Why Multi-State Work Is a Headache

Most contractors start in one state, learn one set of rules, and get comfortable. Then a job pulls you across a state line — a bridge on the Oregon-Washington border, a federal highway contract that hops between Arizona and New Mexico, a data-center build somewhere you've never worked — and suddenly your compliance work isn't twice as hard. It's more like five times as hard.

Every state has its own prevailing wage law, its own certified payroll form, its own idea of what counts as "covered" work, and its own enforcement agency. Federal Davis-Bacon sits on top of all of that. Meanwhile your crew doesn't care about any of this. They just want the check to be right on Friday.

---

The Golden Rule: Project Location Wins

Here's the one thing to burn into your memory: the wage law of the state where the work is physically performed is the one that applies. Doesn't matter where your company is incorporated. Doesn't matter where the worker lives. Doesn't matter where the owner is based. The only question is: where were the worker's boots when they did the work?

Federal vs State Rates: Higher One Wins

When a project is covered by both federal Davis-Bacon and a state prevailing wage law (sometimes called a "little Davis-Bacon" act), you have to comply with both. In practice that means paying the higher of the two rates for each craft. About 27 states have their own prevailing wage laws. The ones you're most likely to run into:

• California: CA DIR rates, often higher than federal
• New York: NYSDOL rates, historically some of the highest in the country
• Illinois: IDOL rates, updated every year
• New Jersey, Massachusetts, Washington, Oregon, Minnesota, Hawaii: All have real state laws with teeth

So-called right-to-work states — Texas, Florida, Georgia — mostly don't have their own prevailing wage laws. On federal projects there, Davis-Bacon is the only rate you're chasing.

---

When Workers Split Time Across States

The hardest scenario is when one worker does covered work in multiple states in the same pay period. Think of a crane operator on a pipeline crossing the Colorado-Utah line, or a traveling electrician who bounces between three federal installations in three states in a week.

You have to:

• Track hours by project and by state — not just "how many this week"
• Apply the right wage determination to each bucket of hours
• File the right certified payroll form for each state and project
• Make sure the paycheck adds up correctly when you sum it all together

Tracking Hours by Project Location

Only one way to do this reliably: tag every time entry to a project. Generic timesheets that ask "how many hours this week?" fall apart the second a worker switches jobs mid-day. You need:

• Daily time entries tagged to a specific project ID
• Every project linked to its state, county, and wage determination
• Per-craft tracking — a worker can do two or three classifications in one day
• Geofenced or GPS-verified mobile punches if you want the strongest audit trail

Our Prevailing Wage Guide goes deep on worker classification, and our wage lookup tool lets you pre-load rates for every state and county your crews touch.

---

State-Specific Certified Payroll Forms

Every state with a prevailing wage law has its own form. If your project is federally funded and sitting in one of these states, you usually have to file both the federal WH-347 and whatever the state wants. The big ones:

• Federal WH-347: Required on every Davis-Bacon project, everywhere. See our WH-347 checklist and form generator.
• California DIR eCPR (XML): California public works need an electronic XML upload to the DIR portal
• New York PW4 / WH-38: PW-30 payroll reporting with a PW-3 transmittal
• Illinois Certified Transcript of Payroll: Monthly submission through the online IDOL portal
• New Jersey WR-35: Weekly certified payroll for NJ public works
• Ohio Prevailing Wage Payroll: Filed through the OH prevailing wage coordinator

Why Generic Payroll Software Falls Down Here

QuickBooks, ADP, Gusto — they'll cut you a paycheck. But they don't spit out a WH-347, a CA DIR XML, a NY PW4, or an IL Transcript. So contractors end up re-typing payroll data into Excel or fillable PDFs for every state, every week. A four-state project footprint means four state certified payroll forms a week, per project, plus the federal WH-347 on top. That's how payroll admins end up working Saturdays.

---

Multi-State Compliance Checklist

1. Before you bid: Pull the state + federal wage determination for every county the project touches
2. At contract signing: Lock in your determination numbers and save the PDFs
3. When the crew deploys: Tell your workers what rate they're on (they have a right to know, and it heads off complaints later)
4. Every pay period: Check that every hour is tagged to project, state, county, and craft
5. Every pay period: Confirm the wage rate is the higher of federal or state for each craft
6. Every pay period: Run OT under both federal and state rules
7. Every pay period: File the right certified payroll form for each jurisdiction
8. Monthly: Recheck SAM.gov and state DOL sites for mods
9. Quarterly: Pull a few random paychecks and audit them yourself before someone else does

---