Wisconsin Added 10,500 Construction Jobs This Year. About Half of Them Trace Back to Data Centers.

At peak construction, about 3,000 union tradespeople were working the site at once. Over the roughly two years it took to build, close to 10,000 different workers cycled through it. That's Microsoft's Fairwater data center campus in Mount Pleasant, Wisconsin, which finished its first phase in June, ahead of schedule. Bowen Wallace, Microsoft's corporate vice president overseeing the project, put a smaller, steadier number on it in May, telling a Racine County economic development event that the company had "hired over 375 full-time Microsoft employees" so far, with that headcount expected to reach roughly 500 once the first facility is fully staffed and as high as 800 once a second building comes online.

Those are two different kinds of job numbers, and the gap between them is the actual story.

The statewide number nobody was predicting a few years ago

Wisconsin's Department of Workforce Development, drawing on federal Bureau of Labor Statistics data, reported that the state added 10,500 construction jobs over the twelve months ending in August — roughly half of all the state's nonfarm job growth for the year landed in one industry. The Daily Reporter, a Milwaukee-based construction trade publication, traced a large share of that directly to data center building: Fairwater's construction workforce in the southeast part of the state, plus active sites in Port Washington and Beaver Dam. This isn't a company's self-reported jobs estimate. It's a state labor agency counting paychecks that have already been issued, for work that's already been done.

Chris Mambu Rasch, executive director of Building Advantage, the group representing union construction trades in southeastern Wisconsin, told Wisconsin Public Radio that data center projects in the region have already phased thousands of union workers through, one job ending roughly when the next one's framing started. He called it a "decade-long runway" for union construction work tied to data centers — not a one-time spike that construction crews build out and then move on from, but a sequence of projects long enough that a worker can plan a career around it rather than just a job.

One campus, then fifteen more

Fairwater isn't a one-off. Microsoft and Gov. Tony Evers announced a $4 billion expansion of the Mount Pleasant investment, and Microsoft's own plans call for up to fifteen more data center buildings on the same site over time, which is the real basis for Mambu Rasch's decade-long framing — it isn't one construction job restarting, it's a sequence of them already laid out. Ninety minutes east, in Port Washington, OpenAI, Oracle, and Vantage Data Centers are building a separate $15 billion campus under the Stargate program, with more than 4,000 majority-union construction jobs at peak, over 1,000 permanent jobs once it's running, and a projected $2.7 billion contribution to the regional economy once four planned buildings are delivering close to a gigawatt of capacity by 2028. A third site in Beaver Dam rounds out what's now three active hyperscale construction zones in one state at the same time, which is most of why a statewide labor report is picking up the industry at all.

The number worth trusting, and the one worth checking

I've spent most of this stretch of posts writing about jobs projections that came from a developer's own press release — a number attached to a groundbreaking, before a single permit clears or a single worker is hired. Those numbers aren't fabricated, usually, but they're estimates of an outcome, made by the party with the most reason to want that outcome to sound big. Wisconsin's 10,500 is a different kind of fact: it's a state agency counting employment that has already happened, built from payroll data the same way every other month's jobs report is, for an industry that didn't need a press release to get counted.

That distinction matters past Wisconsin. In a Kill Test, we grade a site's own power, zoning, water, and commercial-readiness claims on an evidence ladder precisely because a sponsor's announcement and a verified fact aren't the same rung, even when the announcement turns out to be true. A county weighing whether to welcome the next campus, or a contractor deciding whether to bid on the next one, should be running the same check on the economic-impact side of the ledger: is this jobs number a projection from the company building the thing, or is it a count from the agency whose job is to track employment whether or not a data center asked them to? Wisconsin's construction workers didn't need a company to tell them the work was real. The state's own numbers already said so.