Prevailing wage is the minimum hourly compensation — a base hourly rate plus a fringe-benefit rate — that a contractor is legally required to pay each worker on a publicly funded construction project, set by the government per work classification, per locality, and per type of construction. It is the answer to a single question the law asks on every public-works job: what does a worker doing this exact task, in this exact county, on this exact kind of project, actually get paid?
The phrase shows up constantly in the same breath as Davis-Bacon, certified payroll, and the WH-347 form — and operators tend to fuse them together. They're related but distinct. Prevailing wage is the rate itself. Davis-Bacon is the federal law that mandates the rate. Certified payroll is the weekly filing that proves you paid the rate. Get the prevailing wage wrong and everything downstream — the payroll, the certification, the audit trail — is wrong with it. So it's worth defining the rate precisely before anything else.
Who sets the prevailing wage, and how
On federally funded projects, the U.S. Department of Labor sets the prevailing wage. It publishes wage determinations — documents that list, for a given geography and construction type, the required base rate and fringe rate for every recognized labor classification. A single determination might carry dozens of classifications: electrician, low-voltage technician, sheet-metal worker, roofer, laborer, operating engineer, each with its own line. The determination is attached to the contract, and the rates on it are the rates that govern the job from notice-to-proceed forward.
DOL builds those determinations primarily from wage surveys of the local construction market — what contractors in the area actually pay for each classification — with collectively bargained (union) rates often setting the figure in markets where union density is high. The determination is geographic and granular: the prevailing rate for an electrician in one county can differ materially from the rate in the county next door, because the underlying labor markets differ.
States layer their own systems on top. Most states with significant public construction run "little Davis-Bacon" statutes that set state prevailing wages for state- and municipally funded work. California's is administered by the Department of Industrial Relations; New York, New Jersey, Illinois, Massachusetts, Washington, and others each run their own determinations, their own classification lists, and their own thresholds. A contractor working a state-funded school in California and a federal courthouse in the same week is reading two different rate books for the same crew.
Base rate plus fringe — the part operators get wrong
A prevailing wage is not one number. It's two: the base hourly rate and the fringe-benefit rate. The base is cash wages. The fringe is the hourly value of benefits — health insurance, pension or retirement contributions, vacation, apprenticeship training funds — that the contractor either provides through a bona fide plan or pays out as additional cash on the check.
The combined obligation is what matters for compliance. A determination reading $42.00 base plus $24.00 fringe means the contractor owes $66.00 per hour of total compensation for that classification. If the contractor's actual benefit plans are worth $18.00 per hour, the remaining $6.00 of fringe has to be paid in cash. Miscount the fringe and the worker is underpaid against the determination even if the base looks correct on its face — and underpayment against a determination is exactly what triggers back-wage liability, withheld contract payments, and debarment.
This is the most common place the math goes sideways, because fringe accounting is genuinely fiddly. The value of a benefit plan has to be annualized and converted to an hourly figure; overtime hours are paid at one-and-a-half times the base but generally not one-and-a-half times the fringe; and the credit a contractor can take for its plans depends on whether the plan is bona fide under the regulations. None of this is hard once; all of it is error-prone every two weeks across a multi-classification crew.
Prevailing wage is not minimum wage
The two get conflated, and they shouldn't be. Minimum wage is a single floor that applies to nearly all employment in a jurisdiction, set by a legislature, indifferent to what work is being done. Prevailing wage is a much higher, much more specific floor that applies only to covered public-works construction, set by survey or bargaining, and indexed to the exact classification of the exact task.
The practical gap is large. A jurisdiction's minimum wage might be $15-$17 an hour; the prevailing wage for a journeyman electrician on a public project in the same jurisdiction can be three to four times that once base and fringe are combined. The whole point of prevailing-wage law is to keep public construction dollars from being won on the back of underpaid labor — to stop a contractor from underbidding the market by paying construction workers a fast-food wage. So the determination is deliberately pinned to skilled-trade compensation, not the statutory floor.
Classification is where it gets expensive to be sloppy
The single hardest operational fact of prevailing wage is that the rate follows the work, not the worker. A technician is not paid a prevailing wage because of their title or their pay grade back at the shop. They're paid the prevailing wage for the classification of the task they're physically performing, hour by hour.
That means the same person can — and routinely does — earn more than one prevailing rate inside a single pay period. A crew lead pulling low-voltage cable in the morning is paid the low-voltage technician rate for those hours; if they spend the afternoon terminating line-voltage circuits, those hours are paid at the electrician rate; if they direct the crew as foreman, that's a third classification. Split-classification timekeeping isn't an edge case on commercial public work — it's the normal case.
Get the classification wrong and you've either overpaid (eroding a margin that was already thin on a hard-bid public job) or underpaid (creating back-wage liability and a certified-payroll filing that no longer matches reality). This granularity is the part general-purpose payroll services are generally not built to track, because most were designed for a world where a worker carries one rate. Where a contractor already runs a payroll service it trusts for ordinary wage-and-hour work, that tool may stay the right call for that piece; the gap shows up specifically on split-classification prevailing-wage work.
Where the burden actually lands
The prevailing-wage burden is heaviest on exactly the commercial installation trades Forge is built for. Electrical and security and fire-alarm contractors carry it most acutely, because so much of their work is on schools, hospitals, courthouses, transit, military installations, and federally backed housing — all public-works jobs, all governed by wage determinations. Commercial roofing, mechanical, HVAC, low-voltage, and solar contractors hit it constantly on the public side of their books.
And the cost isn't only the wages themselves — those are simply the cost of doing public work. The hidden cost is the labor of compliance: pulling the right determination for each project, mapping every worker's hours to the right classification at the right base-plus-fringe rate, reconciling the fringe credits, and producing a weekly WH-347 that certifies all of it under penalty of federal perjury. On a contractor running two or three prevailing-wage projects at once, that reconciliation becomes a multi-day filing every pay period — the part of the business that quietly eats the bookkeeper's weekend.
Most commercial contractors don't lose money on prevailing-wage jobs because the rates are high. They lose money because the rate lookup, the split-classification timekeeping, and the fringe math live in three disconnected tools that don't talk to each other — so the same hours get re-keyed, re-classified, and re-checked by hand every two weeks.
How Forge handles prevailing wage
Treasury — the payroll drawer of Forge — is built to carry prevailing wage as a native module rather than an integration bolted onto a general-purpose payroll service. Davis-Bacon and state wage determinations pull per project, so the right rate book is attached to the right job from the start. The prevailing wage is calculated per technician per task — at the base-plus-fringe rate for the classification the work falls under, not the operator's home classification — so split-classification crews are handled the way the law actually reads.
Because the timekeeping, the classification, the fringe accounting, and the certified-payroll filing all live in the same ledger rather than across separate tools, the WH-347 generates from the same data that ran payroll. That's the federation principle Forge is built on: the modules share architecture, so the bookkeeper isn't re-keying hours from a dialer into a spreadsheet into a payroll service into a compliance form. The audit trail comes from the same ground-truth data that ran the pay period, instead of being reassembled by hand after the fact.
The rate itself doesn't change — the law is the law, and prevailing wage is a legal floor no software can lower. What Forge is designed to change is the tooling that makes paying it correctly, and proving you paid it correctly, something other than a recurring weekend tax. Charter members on prevailing-wage-heavy verticals like security and fire and electrical help shape how that workflow lands in practice.