Google's new emissions report shows AI's carbon problem moving from the power switch to the concrete truck
Google's 2026 environmental report pins about 2.3 million tons of CO2-equivalent on data center construction and its semiconductor supply chain. Hyperscalers are already pushing carbon paperwork onto the mechanical, electrical, and concrete subs who build these buildings — here's what that means at bid stage.
Google's 2026 environmental report, released June 30, shows electricity use climbing 37% last year — expected, given the AI buildout. The number that should catch a mechanical or electrical sub's attention is a different one: supply-chain emissions grew 25% year-over-year, and Google attributes about 2.3 million tons of that growth to data center construction itself, mostly semiconductor manufacturing on carbon-heavy grids in Taiwan, Japan, Vietnam, and India. AI's carbon problem is shifting from the power switch to the concrete truck — and hyperscalers are already pushing that accounting down to the subs who pour the slabs and run the conduit.
What did Google's report actually say?
Google cut its own operational emissions (Scope 1 and 2) by 2% year-over-year, the ninth straight year it has matched 100% of its electricity use with renewable purchases. But Scope 3 — everything in its supply chain, including construction — now makes up roughly 80% of total emissions and is moving the wrong direction. The report singles out data center construction and hardware manufacturing as the biggest drivers, a signal that Google's own AI buildout is outrunning its ability to decarbonize the grids it depends on.
That gap is exactly why Google, alongside Microsoft, Meta, and AWS, has spent the past two years tightening what it asks contractors to prove before a shovel goes in the ground.
Why does this land on a sub's bid desk?
Because "sustainability" on a hyperscaler job has stopped being a marketing checkbox and become a bid requirement. Google, Microsoft, and AWS now instruct contractors to submit third-party-verified, product-specific Environmental Product Declarations (EPDs) for materials — not a general statement that a supplier "cares about the environment." A concrete or steel package that shows up at bid stage without a current EPD and a credible life-cycle-assessment trail risks losing points against a scored spec, or getting disqualified outright.
Concrete and rebar get the most explicit numeric targets, but they're not the biggest piece of the footprint. Mechanical, electrical, and plumbing systems carry up to 70% of a data center's upfront embodied carbon and as much as 88% of its whole-life embodied carbon, according to industry life-cycle assessments — meaning the MEP sub's equipment selections, refrigerants, and cabling matter as much to this scorecard as the slab does.
What are the actual numbers hyperscalers are specifying?
| Material | Baseline / typical | Hyperscaler target |
|---|---|---|
| 4,000-psi ready-mix concrete | ~352 kg CO2e / m³ | 284–326 kg CO2e / m³ preferred |
| Rebar | Regional average | 611–760 kg CO2e / metric ton |
| Hot-rolled steel sections | Regional average | 686–869 kg CO2e / metric ton |
| Meta's concrete design spec | Regional baseline | Up to 20% below baseline (some pours report ~35% reduction) |
Microsoft has gone further on specific projects, piloting mass-timber structural elements and a deal with low-carbon cement maker Sublime to cut concrete's footprint directly rather than just measuring it.
What should a sub do with this now?
- Ask your ready-mix and steel suppliers if they have current, product-specific EPDs — not a corporate sustainability PDF, but a facility- and mix-specific declaration a GC's precon team can drop into a bid package.
- Get your MEP equipment and refrigerant data organized before it's requested. If your firm bids mechanical or electrical scope on hyperscaler work, expect the carbon-intensity conversation to reach ductwork, chillers, and cable insulation, not just structural materials.
- Don't assume this is only a data-center problem. Google, Microsoft, and Meta's procurement habits tend to migrate to other large corporate and institutional owners within a year or two once the paperwork exists. Building the EPD habit now is cheaper than building it under deadline later.
- Watch your contract language, not just your materials. Most standard-form subcontracts don't yet address who's liable if a declared EPD number is wrong or a supplier substitutes material mid-job. That gap is a legal problem your firm's risk manager should flag before it's a change-order fight.
None of this replaces the actual decarbonization work — Google's own numbers show measurement and pilots (Meta's low-carbon concrete, Microsoft's mass timber and cement deal) are still ahead of anything close to industry-wide adoption. But the paperwork requirement is already real and already showing up at bid stage on hyperscaler jobs. A sub that can produce a verified EPD on demand wins points a competitor without one can't match — regardless of whether their concrete is actually greener.
Construction AI Brief covered the electrical and mechanical labor squeeze behind the same data center boom two weeks ago. This is the other side of that same bid package: the paperwork now sitting next to the labor question.
Friday one chart. Every week, one piece of data that should change a decision on your project. Subscribe at constructionaibrief.com.
Forward this to whoever preps your firm's sustainability documentation on data center bids.
- What did Google's 2026 environmental report say about data center construction?
- Released June 30, 2026, the report shows Google's electricity use rose 37% in 2025 — its largest single-year jump ever — while supply-chain (Scope 3) emissions grew 25% year-over-year. Google attributes roughly 2.3 million tons of CO2-equivalent of that growth to data center construction, largely tied to semiconductor suppliers on carbon-heavy grids in Taiwan, Japan, Vietnam, and India.
- Do hyperscalers require Environmental Product Declarations (EPDs) from construction subs?
- Increasingly, yes. Google, Microsoft, and AWS now instruct contractors bidding data center work to provide third-party-verified, product-specific EPDs for materials like concrete and steel rather than general sustainability statements, and a bid can lose points or get disqualified without one.
- Which trades are most exposed to embodied-carbon requirements on a data center job?
- Concrete and steel suppliers face the most explicit numeric targets, but mechanical, electrical, and plumbing subs carry the largest share of the building's embodied carbon overall — MEP systems can account for up to 70% of upfront embodied carbon and as much as 88% of a data center's whole-life embodied carbon, according to industry lifecycle assessments.
- What carbon targets are hyperscalers setting for concrete on data center jobs?
- Meta has set design specs calling for concrete up to 20% below regional carbon baselines, with some site pours reporting about 35% reductions. Typical better-than-average 4,000-psi ready-mix targets now run near 326-352 kg CO2e per cubic meter, with premium mixes targeting closer to 284 kg CO2e.
- Is this only a data-center-construction issue?
- For now, yes — the EPD-at-bid-stage requirement is concentrated on hyperscaler-owned data center projects. But Microsoft, Google, and Meta set procurement patterns other large owners tend to copy, so subs who build the documentation muscle now (EPDs, LCA trails) are better positioned when the requirement spreads to other institutional and corporate work.