An EPD Does Not Approve Concrete: Build a Dual Carbon–Performance Gate

ISO 14025:2026, published in June 2026, sets current principles and requirements for environmental product declaration programmes and their EPDs. ISO 21930 supplies construction-specific core rules, including life-cycle modules, product category rules and conditions for comparison. Together they define a disciplined way to communicate potential environmental impacts; they do not certify that a concrete mixture is structurally suitable, durable, buildable or contract-compliant. [1][2]

ACI CODE-323-24 makes that boundary unusually clear: its low-carbon provisions are additional to the governing structural requirements and do not address strength, stability, serviceability, durability or integrity. The useful operating rule is therefore simple. Carbon evidence and engineering acceptance are two linked gates. Passing one never waives the other. [3]

An EPD number is comparable only within a compatible method. ISO 21930 distinguishes life-cycle stages and the rules under which products may be compared. EPA guidance separates a declared unit from a functional unit and cradle-to-gate modules A1–A3 from later transport, construction, use and end-of-life modules. EPA's PCR criteria also warn that data source, geography, time period, allocation and impact method can change results for apparently similar products. [2][4][5]

Before a value enters a tender, issue a one-page comparison card. Freeze the declared or functional unit, life-cycle modules, GWP indicator, PCR and version, EPD programme, verification level, data period, plant and supply geography, concrete strength basis, intended service conditions, validity date and treatment of missing data. If two submissions fail that card, show them as non-comparable; do not rank them to produce a convenient winner.

Concrete is regional. ACI's commentary says benchmark data should also be regional and permits locally developed values. GSA's procurement example groups limits by specified strength and makes a separate technical provision for high-early-strength concrete. GCCA likewise relates its concrete ratings to strength and says global ratings should be overlaid with local current averages and targets. These frameworks show why a foreign threshold cannot simply be copied into an Iranian specification. [3][6][7]

Create the project baseline from the suppliers, plants, materials and mixture families that could actually serve the site. Group data by comparable function: strength class, exposure and durability strategy, required age, workability and placing method, element type, density where relevant, and special requirements such as pumping or early stripping. Publish the sample size, range, median, data quality and exclusions. Where evidence is thin, set a disclosure-and-improvement requirement first instead of disguising a guess as a market benchmark.

ACI CODE-323-24 is a carbon requirement layered onto, not substituted for, structural design rules. GSA's programme similarly varies its concrete treatment by strength and recognises a controlled exception where high early strength is technically necessary. The transferable lesson is not the U.S. numbers; it is the separation of a carbon budget from the performance conditions that make the concrete fit for purpose. [3][6]

The engineer's schedule should state strength, exposure, durability indicators, service-life assumptions, cover interfaces, density, workability, temperature, finish, curing, test ages and acceptance. The carbon schedule should state the comparable GWP boundary, evidence class, limit or improvement route, submission dates, permitted averaging, verification and change rules. Link both schedules with one mixture identifier so procurement cannot accept a low number that belongs to a different technical product.

ISO 14025:2026 governs EPD programmes and declarations, while EPA's criteria focus on consistent PCRs, transparent data and comparability. GSA requires a product-specific, third-party-verified Type III EPD for its concrete route and prefers facility-specific data where feasible. These are examples of an evidence hierarchy: a spreadsheet estimate, an industry average and a verified product-specific EPD do not carry the same decision confidence. [1][4][5][6]

Use a staged route when the market is not yet ready. At tender, require a disclosure form and evidence-development plan from every bidder. Before mixture approval, close material quantities, sources, plant energy, transport assumptions, calculation method, reviewer and uncertainty. Call a project calculation what it is; do not relabel it an EPD. A provisional calculation can guide trials, but only the contractually defined evidence class should release a carbon acceptance or public claim.

GSA notes that a concrete EPD accounts for the whole mixture, including the effects of its cement, aggregates and admixtures, and it distinguishes product- and facility-specific evidence from averages. That means an approved carbon value cannot automatically follow a changed cement source, aggregate route, admixture, plant, mixture proportion or declared strength. The evidence boundary must travel with the physical product. [6]

Put the carbon identifier on the approved mixture sheet, batch record, delivery ticket, sampling record and placement zone. Define change triggers before production: material source, quantities beyond approved tolerance, plant, fuel or electricity dataset, haul route, strength or slump class, test age, curing route and approved exception. After a trigger, stop the carbon claim, assess technical consequences, update the calculation or EPD as required, repeat qualification proportionately and release the revised mixture through both gates.

Choose one consequential, repeatable family—such as foundations, a typical suspended slab or a non-structural external package. Survey the supply market, issue the comparison card, establish a provisional local baseline, tender both schedules, trial the candidate mixture, verify carbon data, witness production and curing, and reconcile the placed volume. Include one planned substitution scenario so the change route is tested before scarcity or programme pressure makes the decision urgent.

Use two scorecards. Carbon evidence: comparable submissions, primary-data coverage, verified versus provisional quantities, GWP distribution by mix family, unexplained changes and time to close an exception. Engineering delivery: trial success, fresh and hardened performance, durability indicators, curing continuity, rejected loads, finish defects, programme effect and open technical deviations. Report both with denominators; never celebrate a carbon reduction while hiding poorer performance or extra material.

Scale only when the project can reproduce the calculation, trace the delivered mixture and maintain engineering performance under actual supply and site conditions. International standards, U.S. programmes and an industry rating do not set an Iranian project's law, code or contract. Final limits, verification, structural design, durability, fire and safety requirements, material approval, testing, payment and claims remain controlled by applicable Iranian requirements, the signed contract and the responsible design, materials, sustainability, laboratory, construction and commercial professionals.