EPD published. Now what? Your first 90 days

The real gap: adoption, not certification

An EPD without an adoption plan is shelfware. The failure pattern is simple: teams finish the verification, publish, then pause. It is like shipping a killer feature and forgetting to tell sales where the button lives.

Commercial impact follows attention. If reps do not know how to use the document, they either skip EPD‑driven bids or lean on price. We see this play out even in skilled teams where only one or two people can explain what the EPD actually covers.

0–30 days: stage an internal launch that feels like product

Treat the EPD like a release. Host a 20‑minute all‑hands with three slides: what the document proves, where it lives, how it gets us specified. Record it and post in the LMS.

Ship a one‑page narrative that reps can read in two minutes: when to mention the EPD, which specs it satisfies, and the three most common customer questions with crisp answers. Add a 90‑second demo video that shows exactly how to attach the PDF in a submittal.

Set a simple KPI for day 30: every rep can answer yes or no to “do we have an EPD for this SKU” and can find it in under 30 seconds.

0–30 days: fix the basics on your website

Add an obvious Environmental Product Declaration section to relevant product pages with a short sentence in plain language. Link to the program‑operator listing and the direct PDF download. Place it near submittals, not buried in corporate sustainability.

Create a consistent file name scheme so proposals never misplace versions. Example: Product_Family_Model_EPD_Verifier_YYYYMMDD.pdf. Mirror the same asset in your DAM, PIM, and the sales portal. Small housekeeping prevents big, embarassing mistakes.

31–60 days: turn sales into confident messengers

Run 15‑minute role‑plays per region with two talk tracks: one for architects, one for GCs. Build a pocket battlecard that covers when a project needs product‑specific versus industry‑wide, what modules are in scope, and how to respond if a competitor waves a generic claim.

Embed one paragraph for proposals and submittals so reps stop rewriting. Example opener: “This product has a third‑party verified, product‑specific EPD that aligns with current project disclosure requirements. See attached document and operator listing for verification details.”

31–60 days: make the document discoverable everywhere

Update distributor portals, sample request pages, and BIM libraries with the EPD link. Add the asset to standard submittal packets and to your spec bundles. Post a short release on LinkedIn that points to a product page rather than a gated library.

Ensure external search works. Add the exact phrase “Environmental Product Declaration (EPD)” to product pages, not just acronyms. Check that a search for “ EPD ” returns the right page in the first results. If it does not, fix titles and meta descriptions.

61–90 days: track influence, route requests, escalate fast

Add three CRM fields to opportunities: EPD required yes or no, EPD attached to submittal yes or no, and document type product‑specific or industry‑wide. Require updates at each stage gate so marketing can measure influenced revenue.

Set a two‑business‑day SLA for technical EPD questions with a named owner, a backup, and a shared inbox. Route RFP questions that smell like LCA modeling to the sustainability lead and timebox first response at 24 hours for active bids. If the same gap appears in three deals, escalate to product management with a one‑page brief and a go or no‑go by the next pipeline review.

Create a renewal tickler in month 54 so the team refreshes on time. Most program operators set EPD validity at five years, so a calendar reminder helps avoid last‑minute scrambles (EPD International GPI, 2023).

Your starter FAQ for reps

What is it in one sentence? A third‑party verified summary of cradle‑to‑gate impacts that customers use to compare like products.

When do I bring it up? Early if the spec lists disclosure requirements, late if the buyer is price‑only. Mention it whenever a competitor claims “low carbon” without documentation.

Which file should I send? The current PDF from the product page or sales portal. Never email a screenshot. Link the operator page as proof of verification.

What if they ask for something we do not have? Log the request in CRM, attach the spec section, and trigger the escalation rule. A fast no is better than a slow maybe.

Watchouts: clear signs the adoption motion is failing

• Sales avoids the topic or punts to “someone in sustainability.”
• Only one or two people can explain what the EPD covers in plain language.
• The PDF sits on a website, but submittal packets still miss it.
• No one can point to deals influenced by the document in CRM.
• Response time for EPD questions exceeds two business days.
• Versions float around with random file names and outdated dates. That is definately avoidable.

Why this matters to commercial leaders

Projects that require disclosure penalize products without product‑specific documentation by forcing conservative defaults, which quietly moves you out of contention even when performance is strong. An adoption motion fixes that by making the EPD easy to find, simple to explain, and fast to deploy inside live deals.

In practice, the first 90 days are about choreography. Launch it, make it findable, teach the chorus, and wire the escalation. Do this and the EPD stops being a badge. It becomes a lever for revenue and spec resilience.