A product of
Wisconsin's prevailing wage requirements add complexity and cost to public and prevailing-wage-funded projects, but getting rates wrong in your estimates costs thousands. We'll walk you through the 2026 rate structure and show how a Milwaukee GC avoided a $47K labor underestimation using AI-accelerated takeoffs and scope clarity.
Wisconsin's 2017 repeal of state-mandated prevailing wage laws did not eliminate prevailing wage requirements for general contractors bidding public work. Federal Davis-Bacon rates still apply to any federally funded project in the state, and state agencies may elect to adopt federal wage determinations for their own projects. For senior estimators and preconstruction VPs working on public schools, municipal buildings, or infrastructure funded with federal dollars, understanding the 2026 Davis-Bacon wage structure for Wisconsin—and building those rates correctly into your estimate—remains a critical competency that directly affects bid accuracy and project profitability.
The difference between a compliant, profitable bid and an under-priced disaster often comes down to how you handle base wages, fringe benefits, apprentice ratios, and payroll burden. Missing or miscalculating any of these components can erode 8–15% of your labor margin before the first shovel hits dirt. This article walks through Wisconsin's current prevailing wage landscape for 2026, breaks down rate structures by trade, examines a real-world case study where scope ambiguity and manual spreadsheet estimating nearly cost a GC $47,000, and offers concrete best practices for integrating prevailing wage compliance into your estimating workflow.
Since the 2017 repeal of Wisconsin Statutes §§ 66.0903 and 229.8275, state and local public works projects funded solely by state or municipal tax revenue no longer mandate state-specific prevailing wage rates. However, this does not mean prevailing wage laws have disappeared from Wisconsin construction. Any project receiving federal funding—whether through grants, loans, or direct appropriations—must comply with the federal Davis-Bacon Act and related acts (collectively, DBRA). Common project types include:
Each of these projects requires you to pay workers the locally determined prevailing wage rate published by the U.S. Department of Labor's Wage and Hour Division. These rates are county-specific, trade-specific, and updated periodically based on surveys of union agreements and, in some cases, weighted averages of non-union rates. If your project bid documents reference a specific Davis-Bacon wage determination number—such as WI20260026 or WI20260005—you must apply those rates to every hour of on-site labor performed by craft workers, apprentices, and helpers.
Although DSPS no longer publishes mandatory state prevailing wage rates, state agencies retain the authority to adopt federal Davis-Bacon determinations for their own projects. In practice, this means that if you bid a University of Wisconsin system building or a state-funded correctional facility, the project manual will specify whether Davis-Bacon rates apply. You cannot assume a public project is exempt simply because it is funded by state general obligation bonds; always verify the wage determination requirement in Division 01 of the specifications.
For federally funded work, the Department of Labor updates union prevailing wage rates continuously as new collective bargaining agreements are ratified. Non-union rates—labeled "SU" for single or survey-weighted rates—remain in effect until a new area survey is conducted, which may occur every two to four years depending on local activity. This means the 2026 rates you pull from SAM.gov in January may be superseded by a modification in March if a major trade union in Milwaukee or Madison ratifies a new contract. Best practice: download the wage determination at bid time and re-check it 48 hours before bid submission to catch any amendments.
Davis-Bacon wage determinations for Wisconsin counties in 2026 reflect both union scale and survey-weighted non-union rates. The following table summarizes typical base hourly wages and fringe benefit amounts for common trades in Milwaukee, Dane, and Brown counties, based on recent wage determination data:
Apprentices earn a percentage of the journeyperson base wage according to a DOL-approved apprenticeship program schedule. Typical progressions run 40%, 50%, 60%, 70%, 80% of journeyperson base for first through fifth year apprentices. Critically, apprentices receive 100% of the fringe benefit amount, not a percentage. This is a common estimating error: assuming an apprentice at 50% base wage also receives 50% fringe. In reality, a second-year electrician apprentice in Milwaukee County might earn $31.00/hr base (50% of $62.00) plus $26.00/hr fringe, totaling $57.00/hr—significantly higher than many estimators assume.
Fringe benefits are not optional. Davis-Bacon wage determinations break compensation into two components: the basic hourly rate (cash wages paid to the worker) and fringe benefits (employer contributions to health insurance, pension, apprenticeship training funds, and other bona fide benefit plans). You may pay fringes as cash-in-lieu if your subcontractor does not participate in a qualified benefit plan, but the total hourly cost remains the same. Your estimate must account for both.
Beyond the listed base and fringe, you must layer on payroll burden:
When you sum base wage, fringe, and burden, the true cost of an electrician journeyperson in Milwaukee at $62.00 base + $26.00 fringe becomes approximately $110–$120 per man-hour after all taxes and insurance. If your unit rate for rough-in electrical assumes $75/hr, you will lose money on every labor hour logged. This is why detailed labor assemblies—pre-built with prevailing wage rates, apprentice ratios, and burden factors—are non-negotiable for public work estimating.
A mid-sized general contractor in Milwaukee bid a four-story municipal office building in late 2025, funded by a combination of city bonds and a federal Community Development Block Grant. The project manual specified Davis-Bacon wage determination WI20260026. The estimator, working in Excel with PDF plan sets, performed a manual takeoff of electrical rough-in and calculated 800 man-hours based on receptacle counts, panel schedules, and conduit runs. He applied a blended labor rate of $65/hr—roughly the journeyperson base wage—assuming the electrical subcontractor would self-perform with a crew of licensed electricians.
Two problems emerged during sub bid leveling:
When the electrical sub submitted a detailed cost breakdown, the true labor cost was approximately $68,000 for 800 hours (blended rate ~$85/hr after crew mix and fringe). The estimator's spreadsheet showed $52,000. The $16,000 shortfall, combined with similar underestimations in plumbing and HVAC, put the GC $47,000 below the actual subcontractor total before any markup.
Forty-eight hours before bid due date, the preconstruction manager ran a parallel estimate using Build Intel's AI-accelerated takeoff and Dexter AI scope analysis. The AI-accelerated takeoff tool allowed the team to click once on receptacle symbols and linear conduit runs, auto-populating quantities with real-time collaboration from the lead estimator and an assistant. This cut measurement time by roughly 30%, freeing the estimator to focus on rate validation rather than manual digitizing.
More importantly, Dexter AI—the context-aware assistant embedded throughout Build Intel's estimating workflow—flagged three scope gaps during the electrical review:
The estimator used Dexter to draft a clarification email to the electrical sub, asking for a breakdown of journeyperson versus apprentice hours and confirmation of fringe benefit handling. The sub replied within six hours with a detailed spreadsheet: 400 hours journeyperson at $88.00/hr, 240 hours at 80% apprentice ($49.60 base + $26.00 fringe = $75.60/hr), and 160 hours at 60% apprentice ($37.20 base + $26.00 fringe = $63.20/hr). The weighted average came to approximately $80.00/hr, not $65.00.
The GC re-leveled all mechanical and electrical subs using this methodology, corrected the master estimate, and submitted a bid that was $220,000 higher than the original Excel version—but accurate and defensible. The project was awarded to another bidder who came in $8,000 lower, but post-award interviews revealed that competitor had underestimated fringe and later negotiated a change order for "unforeseen labor compliance costs." The Build Intel-assisted GC avoided that trap entirely.
Fringe benefits are the silent profit killer on Davis-Bacon work. Because they appear as a separate line in the wage determination, estimators accustomed to private-sector work sometimes treat them as optional or roll them into overhead. They are neither. Fringe benefits are a direct labor cost, due for every hour worked, and must be paid either into qualified benefit plans or as additional cash wages. Excluding them from your unit rate can reduce profit margin by 8–12% on labor-intensive trades such as Division 03 (concrete), Division 05 (metals), and Division 26 (electrical).
Consider a concrete placement assembly for a 10,000-square-foot elevated slab:
If you forget fringe and estimate laborers at $45/hr, masons at $48/hr, and operator at $54/hr, your total drops to $19,320—a $9,030 error on a single assembly. Multiply that across 15 divisions and you can see how quickly a bid becomes uncompetitive or, worse, appears competitive but loses money during execution.
Payroll taxes compound the problem. Workers' compensation rates for concrete work in Wisconsin typically run 10–15% of gross payroll, and FICA adds another 7.65% of base wages. When you layer these on top of forgotten fringe, the gap widens. Best practice: build unit rates in your estimating software that include base + fringe + burden as a single composite rate, and validate those rates against the most recent Davis-Bacon wage determination before each bid. If you're using spreadsheet estimating instead of purpose-built software, create a separate tab with a labor rate calculator that pulls from a master wage table, ensuring consistency across all CSI divisions.
Efficient subcontractors use apprentice labor to control costs while maintaining productivity. A typical electrical or plumbing crew on a commercial project might pair one journeyperson with one or two apprentices. The journeyperson handles complex work—panel terminations, fixture rough-in, code compliance inspections—while apprentices pull wire, install boxes, and perform repetitive tasks. This crew mix reduces the sub's average labor cost, and subs pass those savings to you in their bid—provided you model it correctly.
If your estimate assumes 100% journeyperson labor and the sub prices with 50% apprentice labor, you will over-estimate cost and risk losing the bid. Conversely, if you assume 100% apprentice labor (because someone told you apprentices are "cheaper"), you will under-estimate and either lose money or receive bids far above your budget because no sub can legally or practically staff a job with only apprentices.
The correct approach:
Scope ambiguity exacerbates this problem. If your ITB says "install all electrical devices per plans" without specifying device counts, mounting heights, or rough-in conditions, one sub may assume a two-person crew (one journeyperson, one apprentice) while another assumes a four-person crew (two journeypersons, two apprentices). The resulting bids will vary by 30–50%, and you will have no clear basis for leveling. AI-drafted scope narratives—such as those generated by Build Intel's scope generation tools—eliminate this ambiguity by producing detailed, trade-specific descriptions that include quantities, conditions, and assumptions, so every sub prices the same work with the same crew expectations.
Manual rate entry for every trade on every project is slow and error-prone. Instead, build a library of labor assemblies in your estimating platform—whether that's Sage Estimating, On-Screen Takeoff, STACK, or Build Intel—that incorporates prevailing wage rates, apprentice ratios, and payroll burden. Each assembly should include:
Once you build these assemblies, you can drag-and-drop them into any estimate, adjusting quantities from your takeoff without re-entering rates. This approach reduces estimating time by 20–30% and virtually eliminates rate transposition errors. If you are still using spreadsheet-based estimating workflows, consider migrating to a platform that supports assembly libraries—integration with takeoff, bid leveling, and reporting will pay for itself in accuracy and speed within two or three bids.
Prevailing wage compliance is a team effort. Your subcontractors must understand the wage determination requirements, apply the correct rates, and document compliance through certified payroll. If a sub misunderstands the fringe requirement or uses outdated rates, their bid will be too low, they will lose money during the project, and you may face delay claims or substitution requests.
The best defense is early, detailed communication. Send Invitations to Bid (ITBs) to multiple qualified subs three to four weeks before bid due date. In your ITB package, include:
Manual ITB distribution and follow-up is time-consuming. On a fast-track bid with 30 trade packages, you may send 200+ individual emails, track opens and declines, and make dozens of follow-up calls to subs who haven't responded. Build Intel's automated sub outreach feature eliminates this grunt work: you upload your sub database, select recipients by trade and geography, and the platform sends ITBs with drip campaign follow-ups, tracking opens, declines, and pending responses in real time. You see at a glance which subs have downloaded the plans, who has declined, and who needs a nudge, so you can focus phone calls on subs who are genuinely interested rather than cold-calling your entire list.
When sub bids arrive, level them in a structured format—ideally in bid leveling software that allows side-by-side comparison of scope, labor hours, and unit rates. Flag any sub whose labor cost is more than 15% below the next-lowest bidder; this is often a sign of missing fringe, incorrect apprentice ratios, or misunderstood scope. Call that sub, walk through their estimate, and confirm their assumptions. If they correct upward, you avoid a post-award surprise. If they stand by their number and can document compliance, you may have found a competitive advantage—but verify thoroughly before banking on it.
The authoritative source for Davis
AI-accelerated takeoffs, bid leveling, sub management, and proposals. Credit card required.
Start 20-Day Free Trial →We use cookies for analytics and to show you relevant ads on other sites. You can accept all, reject non-essential, or customize. See our Privacy Policy.