Common Mistakes When Using Concrete EPDs

Environmental Product Declarations (EPDs) are the foundation of environmental transparency in the modern concrete industry. They provide a standardized, third-party verified framework for disclosing the environmental impacts of a specific mix. However, a document is only as effective as its interpretation.

The most frequent mistakes in handling EPDs do not stem from errors in the underlying math, but from misapplying the data. When an EPD is used outside its intended scope—particularly as a tool for direct product comparison—it can lead to misaligned specifications, procurement risks, and a gap between reported and actual project outcomes. To support credible decision-making, we must move past these primary misconceptions.

The Comparison Risk: Why EPDs Are Not "Leaderboards”

A common mistake is treating EPDs as a competitive leaderboard where the "lowest number wins". While EPDs provide standardized data, they are not naturally designed for direct "apples-to-apples" comparisons between different manufacturers.

• Mismatched Denominators: An EPD reports impacts for a specific declared unit (1 m³) of concrete meeting defined performance criteria. Comparing a high-strength mix directly to a standard paving mix is technically invalid because they serve different structural functions. Because results are scaled to this specific unit, treating EPDs with mismatched units as equivalent is a fundamental technical error.
• System Boundary Variation: North American concrete EPDs utilize Cradle-to-Gate boundaries (Modules A1–A3), which account for impacts from raw material extraction through manufacturing. This means the data is representative only up to the point the concrete leaves the production facility.
• In contrast, other regional frameworks—particularly in Europe—frequently apply broader boundaries that include transportation to the site, construction, use-phase scenarios, and end-of-life. Because these boundaries vary, Cradle-to-Gate results cannot be directly compared to project-level impacts or to EPDs from programs that include downstream factors like job site delivery, placement, and long-term durability.
• Modeling Assumptions: Environmental results are shaped by upstream technical choices, such as which background databases were used, regional energy grid intensity, and transportation logistics. These variables can cause two "identical" mixes produced in different regions to have significantly different results. Direct numerical comparison often overstates precision by ignoring these contextual differences.

The "GWP-Only" Tunnel Vision

While Global Warming Potential (GWP) is the primary metric in 2026, focusing on it exclusively can hide other critical environmental trade-offs.

• The "Rating" Misconception: An EPD is a disclosure, not a sustainability "score" or rating. It does not indicate whether a product is "good" or "green"; it simply reports the data derived from a Life Cycle Assessment (LCA).
• Ignoring Co-Indicators: Concrete EPDs also report indicators such as acidification potential, eutrophication potential, and net fresh water use (amongst many others). Optimizing solely for carbon might inadvertently increase these other environmental pressures.
• Overstating Small Differences: Drawing strong conclusions from small numerical differences in GWP is technically unsound. Minor variations often reflect modeling assumptions or data uncertainty rather than actual material innovation.

Methodological and Operational Risks

Even a verified document has limitations regarding its "shelf life" and the data sources used to build it.

• Software is a Control, Not an Authority: EPD software are typically independently verified systems that enforce the Product Category Rules (PCR) and ensure calculation sequences are followed. However, software does not resolve judgment-heavy decisions regarding data selection or representativeness; the results are only as accurate as the plant-level primary data provided.
• Expiration vs. Operational Changes: EPDs typically have a five-year validity period. However, if a facility undergoes major changes in its energy source or material supply (such as switching cement sources), the EPD may need an update sooner to remain representative of current operations.
• Engineering Judgment: EPDs are not designed to predict structural performance, workability, or curing times. They are environmental disclosures that should be used alongside—not as a replacement for—engineering judgment.

Clarifying the Concept: FAQs

If two EPDs have different GWP values, why shouldn't I just choose the lower one?

A lower GWP value on a document doesn't always indicate a "better" mix. The difference could be due to standardized modeling assumptions, such as shorter transport distances or different versions of a background database, rather than a physical difference in the concrete's performance. Direct comparison without understanding these upstream choices can be misleading.

Can I use an industry-average EPD to meet my project's procurement requirements?

Generally, no. While industry averages are excellent benchmarks for early design, they are statistical aggregates that "smooth out" plant-level differences. Though project requirements will vary, most 2026 projects will require Product-Specific and Facility-Specific EPDs to confirm the actual impacts associated with the specific material delivered to the site.

Does third-party verification mean the EPD data is a perfect prediction of project impact?

No. Verification confirms procedural integrity—that the producer followed the PCR and international standards (ISO 14025). It ensures the disclosure is methodologically valid, but it does not make different EPDs equivalent or directly comparable across different programs or regions. Because EPDs are not developed with a traditional financial-style audit process, the responsibility for the accuracy of the underlying production data remains with the producer.

EPDs are most useful when they inform questions. Not when they are treated as final answers. Understanding these limitations allows stakeholders to use EPD data with the discipline required for credible sustainability reporting.

Have questions? Want to learn more? Contact Climate Earth.

‍