Home › Sustainability, Decoded › EPDs vs. LEED

EPDs vs. LEED: What the Spec Is Actually Asking For

What is the difference between an EPD and LEED?

These two acronyms get conflated on bid documents constantly, and I understand why. They both live in the green section of a spec, they both sound official, and nobody stops to explain either one. So let me put them side by side and de-jargon them both, because they operate at completely different levels.

An EPD is an Environmental Product Declaration. It is a document about a product, in our case a specific concrete mix. It reports that mix's environmental footprint, most importantly its carbon, in a standardized, third-party-verified format. Think of it as a nutrition label for a mix. If you want the full picture of what it reports, I walked through it in what an EPD for concrete is.

LEED is a different animal entirely. It stands for Leadership in Energy and Environmental Design, and it is a rating system for a whole building. A project earns points across many categories, energy, water, materials, site, indoor quality, and the total score lands the building at a certification level. LEED is a report card for a project, not a receipt for a mix.

So the cleanest way to hold them apart is this. An EPD describes one product. LEED grades one building. One is an ingredient, the other is the whole meal.

How do EPDs and LEED interact?

They are not unrelated, which is exactly why they get confused. They connect at a specific hinge.

LEED includes credits that reward material transparency, using products that have published, verified environmental documentation. When a project uses enough qualifying products with EPDs, it can earn points toward its LEED score. Concrete is often a large share of a building by mass, so concrete EPDs frequently show up as a meaningful contributor to those credits.

That is the whole relationship. An EPD is one of the inputs a project team can use to chase certain LEED points. The EPD does not require LEED, and LEED does not require any specific mix to have an EPD. They meet at the material-transparency credits, and nowhere else.

Does an EPD or a LEED credit mean the concrete is low-carbon?

This is the misunderstanding I most want to clear up, because it trips up smart people. The answer is no, and I need to be a careful referee here.

An EPD reports a mix's carbon number, whatever that number is. A high-carbon mix can carry a perfectly valid EPD. The document is a disclosure, not a passing grade. Likewise, many LEED disclosure credits reward having the documentation, not hitting a low number. So a mix can have an EPD, help earn a LEED credit, and still not be what anyone would honestly call low-carbon.

If a low carbon number is what your project actually needs, do not stop at "it has an EPD" or "it earns a LEED point." Read the GWP on the EPD and check it against your target. The document proves the number exists. It does not promise the number is low.

What does a producer provide, and what does a specifier own?

A lot of confusion clears up the moment you sort out who is responsible for what, because EPDs and LEED sit with different parties.

A concrete producer provides EPDs. A producer is not LEED certified; that is not a thing. LEED certification belongs to the whole building, and it is pursued by the project team, the owner, architect, and engineers who assemble the submission. What the producer feeds into that process is EPDs for the mixes on the job, plus the mix documentation behind them.

So when a spec seems to ask a producer for LEED, the real request is almost always the EPDs and material documentation that the project team needs for its LEED submission. Reading it that way saves a lot of back-and-forth.

• The producer owns: the EPD for each supplied mix, built from real plant data and verified, plus the mix design and test data behind it.
• The specifier and project team own: the LEED strategy for the building, deciding which credits to pursue, and assembling the EPDs and other documentation into the submission.

How is this different from a Buy Clean requirement?

One more distinction, because all three of these show up together and get mashed into one green blob on a spec. EPD, LEED, and Buy Clean are three different things.

Buy Clean is government procurement, and it can set a hard GWP limit that a mix must come in under to be eligible for the work. That is a gate. Miss the number and you are out, the same as missing a strength requirement. LEED, by contrast, is a voluntary building rating where EPDs earn optional points. That is a scorecard, not a gate. And the EPD itself is neither; it is just the disclosure document both of the others rely on. I laid out the procurement side in Buy Clean laws, explained for concrete producers.

So on the same project you can face all three at once: an EPD requirement to have the document, a Buy Clean limit the number must stay under, and a LEED goal your EPD helps the project reach. They are related, but they are not interchangeable, and treating them as one requirement is how producers get surprised.

The one-page takeaway

An EPD describes a product; LEED grades a building. EPDs earn LEED material-transparency credits, which is the only place the two meet. Neither one guarantees the concrete is low-carbon, so read the actual GWP if a low number is what you need. A producer provides EPDs, not LEED; the project team owns the LEED submission. And Buy Clean is a third thing again, a hard limit rather than a voluntary point.

When a spec mentions both EPDs and LEED, separate the asks before you bid:

1. Does the spec require an EPD for your mix, and is there a GWP limit attached? That is the hard eligibility question.
2. Is the project pursuing LEED credits your EPD would help earn? That affects the project's score, not usually your eligibility.
3. Is a Buy Clean rule also in play, setting a carbon ceiling you must meet? That is a separate gate again.
4. If a low carbon number is the real goal, are you reading the GWP, or just confirming the paperwork exists?

Sort those four out and the green section of the spec stops being a blur. The acronyms are not the hard part. Knowing which one is a gate, which one is a scorecard, and which one is just a document is what keeps you from answering the wrong question.