EPDs + HPDs: One Spec‑Ready Pack
Architects rarely ask for carbon or health documents in isolation. They want a clean bundle they can drop into a submittal and move on. Build a single, spec‑ready package that carries your product from short‑list to “approved” without back‑and‑forth scavenger hunts.
Why pair EPDs and HPDs now
LEED v5 elevated both embodied carbon and material health, and it was ratified by USGBC members on March 28, 2025, signaling that product transparency remains central to specs (USGBC, 2025). (USGBC, 2025).
The health side is scaling fast. The HPD Public Repository lists roughly 13,000 published reports covering 40,000+ products, which means design teams expect to find credible disclosures quickly (HPDC, 2025). (HPDC, 2025).
What architects look for in minutes
They scan for a verified, product‑specific Type III EPD with a clear declared unit and system boundary. They check an HPD that inventories to 100 ppm, ideally v2.3, and notes any residuals.
They confirm low‑emitting documentation against CDPH Standard Method v1.2 that reports the 14‑day TVOC measure because many teams key on that line (USGBC Credit Library, 2024). (USGBC, 2024).
The pack: your plug‑and‑play submittal
Build one folder per product. Keep filenames simple and consistent so nothing gets lost in email or portals.
- Product one‑pager that maps commercial name to SKU, finish options, plant, and MasterFormat code.
- EPD PDF with version date, program operator, declared unit, modules, and validity.
- HPD PDF with version, inventory threshold, and any third‑party validation noted.
- VOC proof: CDPH v1.2 test report or a recognized certificate that cites v1.2 and the scenario used.
- Material ingredient label if available, such as a Declare record with status and expiration.
- Contact sheet listing a single technical owner and a single sustainability owner.
Make the data match
Align names, SKUs, and finishes across EPD, HPD, and VOC files. If the EPD covers a family with options, spell out the finish or density range that was modeled, then mirror that in the HPD’s product naming. Dont let “White Panel 123” become “Panel 123 White Matte” in a different document.
Resolve common friction before it starts
- Declared unit vs. sell unit. If the EPD uses m² or kg and sales uses boxes, include a quick conversion note on the one‑pager so estimators can sanity‑check takeoffs.
- Plant changes. If production can shift, note it. Some projects care whether the EPD plant matches reality, especially for transport in A4.
- Confidential ingredients. If the HPD uses confidential business information, make sure hazards are still disclosed and the residuals approach is explained.
Version control that doesn’t break
Put version and expiry in every filename. Set calendar holds six months before any expiry to start refresh work, then three months for a final check. Keep a lightweight change log so sales and reps know exactly what changed and when.
Submission etiquette that wins time back
Package files as one ZIP per product and include a plain‑English cover note explaining scope, versions, and who to contact for alternates. Mirror that pack in your product page so specifiers can self‑serve. A tidy pack shortens review cycles and reduces substitution risk when a project is racing.
Proof points architects can verify
- LEED v5 is live and pushes decarbonization and health forward, with member ratification in March 2025 and roll‑out steps published by USGBC (USGBC, 2025). (USGBC, 2025).
- HPD ecosystem scale matters. The repository cites about 13,000 published reports representing more than 40,000 products, a strong signal that HPDs are fast to find (HPDC, 2025). (HPDC, 2025).
- Declare keeps gaining traction. ILFI reports nearly 1,500 labels representing 16,000+ products, giving teams a recognizable health signal they can cross‑reference with your HPD (ILFI, 2024). (ILFI, 2024).
A one‑week sprint to get there
Day 1 creates the product list and maps SKUs to plants. Day 2 to 3 collects current EPDs, HPDs, and VOC proof and fixes naming alignment. Day 4 builds the one‑pager template and fills it. Day 5 runs a final QA, zips the pack, and posts it to your site. From here, renewals are routine instead of last‑minute.
Frequently Asked Questions
Do we need a Declare label if we already have an HPD?
No, but it helps. Many project teams use Declare as a quick Red List screen alongside HPDs. ILFI cites nearly 1,500 labels covering 16,000+ products, so the signal is familiar to reviewers (ILFI, 2024).
Is CDPH v1.2 required for every product?
Not universally. It is a common pathway for low‑emitting claims used by LEED and several codes. When you have it, report the 14‑day result so reviewers can compare like for like (USGBC, 2024).
Will older but valid EPDs hurt my chances?
If still within validity, most buyers accept them. Problems arise when they are weeks from expiring. Put renewal reminders six months out to avoid re‑submittals.
About the Author
Eric works at the intersection of sustainability, regulation, and business strategy, helping manufacturers navigate the evolving landscape of EPDs and LCAs. Having spoken with hundreds of teams across North America, brings a deep understanding of what drives ROI, what regulators are asking for, and how companies can stay ahead with smart, scalable approaches to environmental reporting.
