Summary (TL;DR) of what this guide is about
- EPDs (Environmental Product Declarations) are increasingly required for public tenders across Europe – without them, your concrete products may not qualify for bids.
- Cement is usually the single largest contributor to a concrete mix’s carbon footprint (often up to 70-85% of concrete’s environmental impact), so accurate supplier and product data is the foundation of credible EPDs.
- At €10,000-12,000 per EPD, documenting 50-100 concrete mixes across plants and locations means a six-to-seven figure investment with traditional LCA consulting services – a cost that often directs most manufacturers toward LCA automation software like Ecochain.
- LCA automation software solutions make it practical to create EPDs across large product portfolios, reducing per-product costs significantly compared to hiring LCA consultants for each mix.
- This guide walks you through what concrete EPDs measure, where the biggest data challenges are, and how to approach EPD creation at portfolio scale.
Why concrete manufacturers need EPDs for tenders and compliance
An Environmental Product Declaration (EPD) for concrete is a verified document that provides data about the environmental impact of your concrete products and manufacturing process. It follows the EN 15804+A2 standard, which defines harmonized rules for different products, as well as construction product EPDs so procurement teams can compare products on a level playing field.
For concrete manufacturers, EPDs have become a business requirement – not just a sustainability initiative.
Public tenders across Europe increasingly require EPDs as part of bid submissions. Private developers building to green certification standards ask for them too. If you don’t have EPDs, your products don’t make the shortlist.
What’s the biggest challenge? Most concrete manufacturers produce 50+ different mixes. Different strength classes, exposure categories, plants, regional specifications.
And traditional consultant fees for a single construction product EPD often run into the tens of thousands of euros once life-cycle modelling, verification and program fees are included. Documenting 50 products quickly becomes a six-figure investment.
So, if do a simple math – let’s say on average an LCA consultant charges €10,000-12,000 per EPD, and you need 100 EPDs across your portfolio and different locations. The total investment will be in the range of one million euros – even with quantity discounts.
That doesn’t scale. That’s why manufacturers are shifting toward LCA automation software like Ecochain that makes EPD creation practical at portfolio level.
This article covers what concrete EPDs measure, why cement data matters most, the challenges of scaling EPDs across a large product range, and how to choose the right approach for your portfolio size and budget.
What a concrete EPD measures: carbon footprint, CO₂, and other environmental impacts
A concrete EPD quantifies environmental impacts across life‑cycle stages defined in EN 15804+A2. For concrete mixes, the product stage (A1–A3) is usually the starting point:
- A1 – Raw materials: Everything that goes into your concrete: cement, aggregates, supplementary materials, admixtures. Cement clinker dominates this stage and can account for well over half of the concrete mix’s global warming potential, depending on the mix design (can often be in the range of 70-85% of total impact).
- A2 – Transport to your plant: Emissions from delivering materials to your batching facility. Distance and transport mode (truck, rail, barge) determine the impact.
- A3 – Manufacturing: Your batching operations: mixers, conveyors, water treatment, curing. This is usually the smallest contributor for concrete.
Together, A1–A3 represent the “cradle-to-gate” product stage – the part of the life cycle that most concrete specifications and databases focus on today – and the declared unit is typically 1 cubic meter of a specific mix design.
Some tenders also require additional modules such as A4 for transport to site and A5 for installation, and EN 15804+A2 expects end‑of‑life modules C1–C4 and module D to be declared as well, but A1–A3 results still form the core of most concrete procurement comparisons today.
Why cement and binder data are the biggest drivers in your concrete EPD
One key thing we’ve mentioned a couple of times in this guide: cement is typically the main driver of your concrete’s environmental footprint.
The clinker production process releases CO₂ from both fuel combustion and the chemical transformation of limestone. No other input comes close.
This has practical implications:
- For accuracy: Your EPD is only as good as your cement data. Generic industry averages create uncertainty. Product-specific EPDs from your cement supplier give you defensible numbers.
- For reduction: If you want to lower your concrete’s footprint, start with cement. Lower-clinker cements or supplementary materials (fly ash, slag) can reduce A1 impact by 20-40%.
- For differentiation: When competing products have similar strength and performance, verified low-carbon cement content becomes a tender advantage.
The portfolio problem: scaling EPDs across your concrete product range
Creating one EPD is manageable. Creating 50 is a different challenge entirely.
The 4 most common challenges when scaling EPD generation across your portfolio:
- Data gathering multiplies: Each product needs supplier documentation, batching records, transport data, and energy consumption figures. Multiply that across your full portfolio and multiple plants.
- Systems don’t connect: Your ERP tracks materials. Batching systems track energy. Logistics tracks transport. Bringing this together for each product means manual exports, spreadsheet consolidation, and version control headaches.
- Regional requirements vary: The same concrete mix may need different documentation for different markets. Tender requirements differ across the Benelux, DACH, and UKI regions.
- Consultant costs don’t scale: External LCA specialists are excellent for flagship products. But at €5,000–€15,000 per EPD across 50+ products, the budget math breaks down quickly.
This is why software-based approaches built for sustainability teams have become practical necessities for larger portfolios. The economics shift from per-product consulting fees to infrastructure that serves your entire product range.
What data you need to create a concrete EPD
Creating EPDs requires gathering data from across your operations. Here are some ideas on what to prepare:
From your cement and materials suppliers:
- EPDs or carbon footprint declarations for cement products
- Documentation for supplementary materials (fly ash, slag, silica fume)
- Aggregate source information
- Admixture specifications
From your batching records:
- Mix designs with material quantities per cubic meter
- Production volumes by product
- Which materials went into which batches
From your operations:
- Plant energy consumption (electricity, fuel)
- Water usage
- Transport distances from suppliers to plant
- Transport modes (truck, rail, barge)
Tip: The hardest data to obtain is usually cement supplier EPDs. It’s worth requesting these early – it can take weeks to get product-specific documentation rather than generic industry averages.
How to approach concrete EPD creation: consultant, platform, or hybrid
Option 1: LCA consultant-led (best for one product footprint reporting or an extremely small portfolio – one-off project)
Hire an LCA specialist to create EPDs product by product. This works well if you need 1-5 EPDs and don’t plan to update frequently.
- Cost: €5,000–€15,000 per EPD
- Timeline: 6-15 weeks per product
- Best for: Flagship products, one-time needs, small portfolios
Option 2: Software-assisted (best for larger portfolios, multi-location businesses)
Use LCA automation software to create EPDs systematically. Can something require a higher upfront investment, but usually dramatically lower per-product costs at scale.
- Initial investment: Varies by software and portfolio size
- Marginal cost per EPD: Usually drops significantly after data infrastructure is established
- Payoff threshold: Typically 8-10 EPDs per year
- Best for: 10+ products, ongoing EPD needs, multi-plant operations
Option 3: Hybrid approach
Use LCA consultants for complex or high-visibility products. Use software for standard products and portfolio expansion.
Getting started with concrete EPD creation: a practical roadmap
Step 1: Define scope and audit your portfolio
Which products face the most urgent EPD requirements? It helps to prioritize based on tender deadlines, customer requests, and strategic importance – you don’t need an EPD for everything at once. In parallel, clarify which life‑cycle modules (at minimum A1–A3, plus any A4, A5, C, and D requirements) and which EPD programme / PCR you will use, because these choices affect your data needs and modelling.
Step 2: Secure supplier data
Cement supplier EPDs are usually the longest lead‑time item, so it’s worth reaching out early, even if you’re months away from creating EPDs. Do the same for key admixtures and supplementary cementitious materials where product‑specific data will materially influence your results.
Step 3: Map your data sources
Identify where batching records, energy data, and transport information live in your systems. Understand what’s available, what’s missing, and what needs manual collection, and set up a simple data quality check so obvious gaps are caught before verification.
Step 4: Choose your approach
Based on portfolio size and budget, decide between consultant‑led, software‑assisted, or hybrid approaches. For larger portfolios, evaluate LCA platforms based on:
- Concrete-specific calculation support
- Ability to connect to your data systems
- Regional compliance features
- Expert support for setup and verification
Continue reading: Choosing the right EPD software for construction manufacturers: 7 key factors to consider
Step 5: Build your first EPDs
Many manufacturers find it helpful to begin with 2–3 products to establish templates and workflows. This reveals data gaps before scaling to the full portfolio and gives you an internal “playbook” for future EPDs.
Step 6: Verify and publish
Third‑party verification is required for formal EN 15804 / ISO 14025 EPDs published through an EPD program. Verification review typically takes anywhere from 2–8 weeks depending on program, complexity, and data quality. Once verified, you can register with an EPD program operator to make declarations publicly available.
Optional Step 7: Maintain and update
After publication, track triggers for updates – for example, a 10% change in key impact indicators, major process changes, or the 5‑year validity limit that many programs apply. Establishing a light “EPD maintenance” routine upfront avoids last‑minute renewals and keeps your declarations aligned with reality.
FAQs about concrete EPDs and environmental declarations
How long does it take to create a concrete EPD?
With LCA consultancies, generating an EPD for concrete products can take from 5 up to 15 weeks per product, sometimes even longer. With LCA automation software solutions like Ecochain, once you setup you data foundation, you can get to a stage where you generate e.g., 50+ EPDs in days.
What does a concrete EPD cost?
To generate EPDs through LCA consultancies, you can expect a fee typically €5,000–€15,000 per product. Software-based approaches like Ecochain LCA automation software lets you generate EPDs at portfolio scale for as low as 50 euros per EPD.
Do I need LCA expertise to create EPDs for my concrete products?
No, you don’t need LCA expertise to create EPDs for concrete products. LCA automation software like Ecochain handle the methodology. You provide production data and material specifications, then model the product impact of your products. The hard part – calculation – are done in the background. You also often get expert support that comes with the LCA software that can help you with the setup and complex scenarios.
Which standard do concrete EPDs follow?
EN 15804+A2 is the core European product category rule for construction product EPDs, with that concrete products too, and most European EPD programmes are based on it. To be used as a Type III EPD under ISO 14025 – for public tenders, building certifications, and most national databases – your declaration should be third‑party verified and published by a recognized programme operator.
Do I need separate EPDs for each plant in my concrete manufacturing business?
EPDs are always created for specific concrete products (or product families), not for plants in the abstract, but you can decide whether those product EPDs are plant‑specific or based on averages across several sites. A plant‑specific EPD means ‘this concrete mix, produced at this particular plant’ using that site’s real energy, materials, and transport data, and the plant is explicitly named in the declaration. If you sell the same mix from multiple plants and your customers only require product‑level data, you can often use one averaged product EPD across several locations, provided you follow the EPD programme’s rules for multi‑plant declarations.
What if my cement supplier doesn’t have an EPD?
If your cement supplier doesn’t have EPD, you can use industry average data as a placeholder, but flag this as lower quality. It’s worth encouraging your supplier to provide product-specific documentation – it improves both your accuracy and their market position.
