Product-Specific vs Industry-Average Concrete EPDs

As environmental considerations move from the sidelines into the heart of procurement, the concrete industry is seeing a massive shift in how materials are evaluated. We have already established what an Environmental Product Declaration (EPD) is—a standardized, verified disclosure of environmental data. However, as the market matures, simply "having an EPD" is no longer enough.

Producers and specifiers now need to understand data resolution. Not all EPDs provide the same level of detail; their "zoom level" depends on how specific the underlying data is to a particular plant or mix design.

Two Layers of Specificity

According to the ACLCA’s guidance on determining EPD types, an EPD is categorized by its "specificity" across two distinct layers: Manufacturing and Product. Understanding these layers is critical for accurate sustainability reporting and avoiding misaligned specifications.

Layer 1: Manufacturing Specificity

This layer identifies how many companies or facilities are represented in the data and can be defined as:

• Industry-Average: Data provided by multiple manufacturers within a defined sector or region. These are often created by industry associations like the NRMCA.
• Manufacturer-Average: Data from a single company, but averaged across multiple plant locations.
• Facility-Specific: Data from a single manufacturer at one specific plant location.

Layer 2: Product Specificity

This layer identifies how many different mix designs or products are grouped together, and is defined as:

• Product-Average: An EPD representing a group of similar products where environmental impacts fall within a ±10% range.
• Product-Specific: An EPD representing one specific mix design (or a group of mixes with equivalent characteristics).

Product-Specific Concrete EPDs: The "High-Res" Snapshot

What is commonly referred to as a product- or mix-specific EPD is in reality a product-specific and facility-specific EPD. These concrete EPDs reflect actual operational conditions at a particular plant rather than statistical averages. They are built from primary data—measured directly from the plant—including specific mix quantities, plant energy and fuel consumption, and real-world transportation distances.

Advantages:

• Reflects Operational Excellence: Highlights the effects of a producer’s specific investments in high-efficiency plants or carbon-reduction technologies.
• Mix-Level Accuracy: Sensitive to changes in mix design, such as higher supplementary cementitious material (SCM) substitution or improved aggregate gradation.
• Procurement Precision: Provides the most relevant data for project-specific submittals and as-built modeling.

Limitations:

• Data Maintenance: Requires ongoing collection and validation. Changes in cement sourcing or material availability may require the EPD to be revised and/or reverified to remain representative.
• Regional Variance: Because they reflect local realities (like a specific electricity grid or SCM availability), two "identical" mixes produced in different regions may have significantly different GWP results.

Industry-Average Concrete EPDs: The Baseline

These EPDs rely on aggregated data from multiple producers to create a general environmental profile for a region or category.

Advantages:

• Design Benchmarking: Provides a reliable reference point for architects and engineers during the conceptual phase before a specific supplier is chosen.
• Standardized Baselines: Establishes a common yardstick that can be used to set project goals or public-sector carbon thresholds.
• Accessibility: Offers a disclosure option when plant-specific data is not yet available for a producer (though they are usually not sufficient for true procurement requirements in the concrete industry).

Limitations:

• Smoothed Variability: Industry averages "smooth out" differences. They can obscure the carbon-heavy supply chain of one plant or the high material efficiency of another.
• Not a Performance Predictor: They should not be used to make claims about a specific facility's performance or as a substitute for project-level submittals.

The "Comparison Trap" and Risk Management

It is a common mistake to treat EPDs like a leaderboard where the "lowest number wins". Comparing a Facility-Specific EPD to an Industry-Average baseline can show deviation from the norm, but it does not establish absolute material superiority.

Environmental results are not just about the mix; they are shaped by upstream choices like logistics, energy grid intensity, and background data assumptions. When teams ignore these contexts, they risk overstating precision or drawing conclusions the underlying data cannot support.

Frequently Asked Questions (FAQs)

Is a Product-Specific EPD "better" than an Industry-Average EPD?

Neither is inherently better; they serve different purposes. Industry-average EPDs are for broad benchmarking and early design. Product-specific EPDs are for procurement and proving the impact of specific mix optimizations at the plant level.

What is a "Supply Chain Specificity" (SCS) score?

Introduced in the ACLCA guidance, the SCS score is the third layer of specificity and reports the percentage of an EPD's carbon footprint (A1-A3) represented by measured data from the actual supply chain (e.g., using a specific cement plant's EPD) rather than generic averages.

Do EPDs expire?

Yes. EPDs are typically valid for five years, but they must also use background data that is representative and current. If a facility undergoes major changes in energy source or material supply, the EPD may need an update sooner.

Are your EPDs ready for 2026? As specifications move toward facility-specific requirements, staying informed is the simplest way to stay competitive.

👉 Sign up for the Future of Concrete webinar series to join the industry discussion.

‍