Running One Crew Across Five Prevailing-Wage Regimes
A Delaware Valley mechanical contractor is common enough that the scenario writes itself: one crew, four projects in one week, three of those projects are public works, each in a different state. Monday the crew is in Wilmington. Wednesday they're on a PennDOT job outside Philadelphia. Friday they're on a Camden school. By Monday next week they're in Baltimore. Each of those jobs is covered by a different state prevailing-wage regime. The payroll person doing the certified-payroll filings for that week has five possible frameworks to navigate. This essay walks how to actually run it.
The core tension: one workforce, five regulatory worlds
Each of the five Mid-Atlantic states regulates prevailing wage on public works, but each has its own classification system, certified-payroll form or system, and trigger threshold. When the same carpenter or plumber works public projects in multiple states during one pay period, the administrative burden multiplies. The work is consistent; the paperwork isn't.
Most contractors who haven't done this before assume there's some shortcut — one payroll system that handles all five, or a way to classify workers once and have it carry. There isn't. The workflow is fundamentally per-state, per-project. What can be optimized is the data model behind the scenes.
Step 1: track hours by project, not just by week
The foundation is time tracking at the project level, not just at the week level. A worker who does 40 hours spread across four projects needs hours split by project so each project's certified payroll reflects that project's work. A single weekly timesheet aggregating hours won't suffice — the certified-payroll filing for each project needs project-specific hours.
Good field time-capture tools (whether spreadsheet, dedicated construction time app, or ERP-integrated) collect:
- Date.
- Worker identifier.
- Project identifier.
- Hours worked on that project that day.
- Work performed (for classification purposes).
If the crew performs multiple classifications of work in a single day — some hours as pipefitter, some as laborer — the time capture has to split those too, because each state's prevailing rate is classification-specific.
Step 2: map your crew to each state's classifications
The classifications aren't identical across states. Delaware, Pennsylvania, New Jersey, Maryland, and Virginia each publish their own craft classifications with their own hierarchies, sub-categories, and rate structures. A "plumber" in PA isn't necessarily assigned to the same rate row as a "plumber" in NJ.
The practical approach: for each worker, maintain a state-by-state classification mapping table. If Joe is a journeyman plumber, document which state's classification rows apply to him in each jurisdiction. Keep the table current when state classifications change (occasional but not frequent).
For multi-classification situations, document which work falls into which classification. If Joe sometimes performs plumbing and sometimes performs boiler mechanic work, the time breakdown drives which rate applies.
Step 3: obtain the applicable rates per state per project
Rate acquisition varies by state:
- Delaware: submit the Certified Prevailing Wage Rates Request Form to DE DOL per project. Rates come back specific to the project.
- Pennsylvania: look up rates through the PA DLI Request or Search Prevailing Wage Rates tool for the project's locality and craft.
- New Jersey: rates accessible through NJ DOL prevailing-rates portal for the specific project.
- Maryland: rates available through the MD Prevailing Wage Portal per project.
- Virginia: DOLI publishes wage determinations by locality and craft; check the determination schedule for the project's scope.
Do this for every project at bid time, not at payroll time. Rates are known at the point of bid; having them locked in early means pricing reflects actual obligation and prevents rate-discovery surprises mid-project.
Step 4: file certified payroll per state's required mechanism
Each state's filing mechanism is different:
- Delaware: DE-specific certified payroll form, per the Prevailing Wage Regulations.
- Pennsylvania: PA Certified Payroll Form, per the Prevailing Wage Act regulations. Paper / upload-based.
- New Jersey: NJ Wage Hub digital system is required. Per-worker, per-project filings.
- Maryland: Submit through MD Prevailing Wage Portal. Also covers contractor registration, which is pre-bid in MD.
- Virginia: DOLI Pay Scale Certification for Public Works Projects, per 12VAC5-410 requirements.
Five filing mechanisms. Each one is its own account, each one has its own submission cadence (usually weekly), each one needs its own completed data. The administrative workflow can't be compressed — it can be planned.
Step 5: federal Davis-Bacon when it applies
If any of the projects is federally funded (transportation, housing, infrastructure programs, many others), federal Davis-Bacon applies on top of the state requirement. That means:
- Pay the higher of the state or federal rate per classification.
- File federal WH-347 with the federal contracting agency in addition to the state filing.
- Follow the more stringent of the two sets of recordkeeping requirements.
Don't let a state filing substitute for the federal one or vice versa. They're separate obligations.
A practical weekly workflow
For a contractor running public projects across multiple Mid-Atlantic states, the weekly payroll routine looks something like this:
- Monday: Collect time records from field for the prior week, split by project and classification.
- Tuesday: Verify rate applicability per worker per project against state-specific classification-to-rate maps.
- Wednesday: Run payroll calculations. Pay workers at correctly classified rates.
- Thursday: Generate certified payroll submissions — one per project per state, using that state's required format or system.
- Friday: Submit all certified payroll filings. Check for receipt confirmations from each state's system.
The compliance burden for a 3-state, 4-project week can easily be 4-6 hours of dedicated payroll work. Budget for it.
Where costs sneak in
The traps for contractors not accustomed to multi-state public work:
- Wrong classification. Paying federal Davis-Bacon classifications on a state-only project, or PA classification on an NJ project, triggers back-wage liability.
- Wrong rate. Using a stale published rate instead of the current project-specific rate; using the non-union rate where the union rate applies.
- Wrong fringe handling. Each state treats fringe benefits slightly differently — cash equivalent vs. bona fide plan contribution, what counts, what doesn't.
- Late filing. Missing a weekly certified-payroll filing on one project can trigger compliance flags even if filings elsewhere are current.
- Non-covered work misclassified as non-covered. If a public agency later determines the project was covered under prevailing wage and workers weren't paid accordingly, retroactive back wages apply.
The audit risk is real. Investigations are often triggered by worker complaint, by competitor complaint on bid awards, or by routine compliance review. Clean recordkeeping is the defense.
Technology choices
A few workflow observations:
- Construction-focused ERP (Foundation, Sage 300 CRE, Viewpoint Vista, etc.) handles multi-state prevailing wage natively when configured. Setup cost is real but pays back on volume.
- Prevailing-wage-specific software (LCPtracker, Certified Payroll Cloud, etc.) focuses on the certified-payroll filing piece and plugs into general payroll systems.
- Spreadsheet workflows work for small firms with few public-works projects, but become unwieldy fast when volume grows.
- No single system handles every state's filing format natively. Wage Hub is NJ-specific. PA's forms have their own format. Expect at least some state-specific workflow even with good tools.
What to do with this
If you're a cross-state public-works contractor: invest in time tracking that captures project and classification at the transaction level, not just aggregated weekly. Build state-specific classification mappings for your workforce. Set up accounts in every state's filing system before you need them.
If you're considering expanding into public works from private: understand the administrative cost upfront. The bidding advantage of public-works work comes with real recordkeeping and compliance overhead.
If you're already in multi-state public works and it feels chaotic: audit your workflow. Most chaos comes from late data capture and late rate acquisition — both of which can be moved upstream.
For state-specific primary sources and workflow details, see our state prevailing wage navigators and the comparison hub:
- Delaware Prevailing Wage Navigator
- Pennsylvania Prevailing Wage Navigator
- New Jersey Prevailing Wage Navigator
- Maryland Prevailing Wage Navigator
- Virginia Prevailing Wage Navigator
- Mid-Atlantic Prevailing Wage Compared
About The Hive
The Hive builds tools and publishes essays for working construction and MEP professionals in the Delaware Valley and Mid-Atlantic. Primary-source-grounded, practitioner-voiced, free to use.