EPDs and HPDs in one architect ready pack
Specs are won in the submittal. Architects want carbon numbers and material health proof at the same time, not a pile of mismatched PDFs. Here is a tight playbook to bundle EPDs, HPDs, VOC evidence, and Declare into a single, easy to approve package that speeds reviews and keeps your product in contention.
Why pair EPDs with HPDs now
Owners are setting carbon caps and ingredient rules on the same project. If the carbon story is strong but the Red List story is fuzzy, products stall. Put them together and the narrative clicks. It feels like packing a carry on that sails through security.
EPDs quantify impact. HPDs and related labels explain what is inside. Together they remove two major spec risks at once, which shortens back and forth and protects margin.
What a great submittal looks like
Great submittals read like a well organized playlist. Track one is carbon, track two is health, every file labeled, dates obvious, and nothing is left to guesswork.
Two details matter more than most. EPDs carry a typical validity window of five years depending on the program operator, which should be clearly shown on page one (EPD International, 2024). HPDs disclose down to at least 1000 ppm, with 100 ppm available for deeper inventory in the current Open Standard, so list the chosen threshold right up front (HPDC, 2024).
The carbon and health pack, component by component
We recommend one zip per product family with a readme that guides the reviewer.
- Product specific EPD PDF, declared unit and plant locations highlighted.
- HPD, disclosure threshold and version noted.
- VOC evidence for relevant uses, typically a CDPH or equivalent emissions test summary plus any applicable VOC content standard.
- Optional Declare label or ingredients summary, with the Red List status stated. Declare Red List Free means no Red List chemicals at or above 1000 ppm, which is the threshold used for assessment (ILFI, 2024).
- One page cheat sheet that maps each document to common submittal asks.
File anatomy that speeds approvals
File names do more work than most teams realize. Aim for human readable names that carry the essentials in the same order every time.
Example pattern: Brand_ProductName_Version_DU_GWP_A1A3_ValidTo_YYYYMMDD.pdf.
Place the readme first in the zip. It tells reviewers where to look. Keep version history inside the readme so older links in a contractor portal still make sense.
Data alignment rules that prevent rejections
Make the EPD declared unit match your sell unit or show the conversion clearly in the cheat sheet. If the EPD is per kilogram and you sell per square foot, include the math. Keep product naming identical across EPD, HPD, and marketing cut sheet. Review plant list consistency. If the HPD covers a range, state the exact SKUs that map to the EPD’s declared unit.
Dates matter. Put EPD validity and HPD publication dates in a small table in the readme. It looks simple, it reduces email churn, and it saves everyone time.
LEED v5 and common frameworks, decoded for submittals
LEED v5 is consolidating materials criteria, and teams still ask for familiar proofs. Your pack should enable quick checks for embodied carbon accounting and material ingredient disclosure without making the reviewer dig.
Say what each file covers. EPD supports embodied carbon accounting for A1 to A3, and sometimes A4 or beyond depending on scope. HPD satisfies material ingredient disclosure, with the threshold called out to match project rules. Declare status gives a quick Red List signal that many design teams prefer to scan first.
A 10 day sprint to assemble the first pack
Day 1 to 2, pull current EPDs and health documents from internal drives and program operator portals. Day 3 to 4, normalize names and versions, draft the readme and the cheat sheet. Day 5 to 7, fill gaps, especially VOC evidence for adhesives, coatings, or finishes. Day 8 to 9, run a red team review by sales engineering. Day 10, publish the zip in your portal and train sales on the new naming.
If data collection across plants is messy, bring in a partner who actually handles the wrangling instead of pushing spreadsheets back at you. That is where weeks vanish, and it is where speed is won.
Maintenance without the migraine
Set two recurring checks. Quarterly eyeball of expiry dates and version drift. Annual deeper check that aligns the next EPD refresh with any PCR updates and that the HPD reflects current formulations. Reliable averages for maintenance effort vary by portfolio size, so exact hours per SKU are hard to state credibly.
Practical tip. Keep a single spreadsheet as the source of truth for document status by SKU, plant, and market. Protect it. Everything else syncs from there.
Common pitfalls and quick fixes
Mismatch between declared unit and price list leads to confusion. Fix with a conversion note on page one. HPD threshold not stated makes reviewers guess. Fix by putting it in the filename and the readme. VOC proofs scattered across emails slow approvals. Fix by clipping the summary page into the pack every time.
One more. Avoid last minute PDF edits that change version numbers without logging a change. It sounds small, but it definately causes headaches during audits.
Tie the loop for sales and specs
Give sales one link per product family. Give spec writers the cheat sheet and the conversion math they can quote in emails. Give sustainability reviewers the dates, thresholds, and plant list in one place. That is how a carbon and health pack does its job. It keeps the conversation on the merits of the product instead of the paperwork.
Frequently Asked Questions
Do EPDs and HPDs need to cover the exact same SKUs to be useful in one submittal pack?
They should align at the product-family level at minimum. If scopes differ, list the SKUs that are fully covered by both and note any exceptions in the readme so reviewers know what is included.
What if our EPD declared unit is not the same as our sell unit?
Keep the EPD as is and add a transparent conversion in the cheat sheet. For example, per kilogram results can be converted to per square foot using product density and thickness. Show the math once and reuse it across bids.
How often should we refresh HPDs compared with EPDs?
EPDs typically refresh every five years subject to operator rules, while HPDs are updated when formulations change or to align with program updates. Review both quarterly for dates and annually for scope.
Is a Declare label required if we already provide an HPD?
Not required. Many design teams appreciate Declare for fast Red List screening. If available, include it. If not, ensure the HPD threshold and ingredient summary are easy to scan.
Where should VOC information live in the pack?
Include emissions test summaries and any applicable content standards in a dedicated folder named VOC. Mention which products or uses it applies to in the readme to prevent misapplication.
About the Author
John brings a clear, research-driven perspective on the EPD, LCA and HPD space and keeps a close pulse on environmental trends and standards in North America, helping clients understand where the industry is heading and how to get there.
