The org design problem hiding in plain sight
The EPD answer usually exists somewhere. The delay comes from no one owning rapid retrieval and external response. It is a relay race where the baton keeps hitting the track. We see handoffs from sales to technical service to sustainability that stretch replies to 1 to 4 weeks, while the thread with the specifier goes quiet. Internal awareness is often low enough that a team can publish an EPD yet never define who fields the first customer question about it.
Four broken models and the risks they create
Sales-only ownership turns reps into part-time compliance analysts. They over promise, paste outdated PDF snippets, or exit the conversation because digging takes hours they do not have. The spec walks.
Technical service as the gate for every answer creates a bottleneck. These teams protect quality, but they also protect uptime on the line. Queue grows, response slows, and urgent jobs consume the same experts needed for plant support.
Sustainability in a separate lane keeps the LCA logic correct but disconnected from live customer context. Answers land as textbook paragraphs when the buyer asked for a single product number and a declared unit. Momentum dies.
Product pulled in too late forces emergency rework. Roadmaps bend around last minute EPD asks. Teams burn trust because the question felt simple and became a sprint.
Join Parq Pulse!
Stay ahead with weekly insights on EPD ownership and response strategies to secure more project wins.
A cross-functional model that actually ships answers
Think newsroom. One editor routes and clears copy. Roles are crisp, timeboxed, and visible.
- First response within 24 hours: Sales or customer support owns the on-record reply, guided by an EPD Answer Card per product family. If the exact value is unknown, the reply confirms receipt and sets expectation on the next update window.
- Technical validation: Sustainability or the EPD program manager validates numbers, boundaries, and any claims before they publish to the customer. This step owns conformance to ISO 14025 and the product PCR.
- Document maintenance: Product management owns the canonical answer set, version history, and archive. They track changes like recipe tweaks, supplier shifts, site additions, and retests, then trigger updates to the Answer Card and public materials.
- Escalation: Technical service is the high-urgency lane for plant-specific or performance-adjacent questions, with a defined SLA for unblock. Complex cases can include the LCA practitioner when interpretation risk is high.
The playbook and artifacts you need
Create a single intake channel for EPD questions. Email alias or CRM queue, not personal inboxes. Route by product family and market. Publish a two-page EPD Answer Card per family that covers declared unit, system boundary, key modules included, program operator, verification type, and how to read the headline GWP result by scenario. Include where the latest PDF lives and when the next update cycle starts. Keep a live changelog. Short beats perfect.
What leadership should watch to know the model is failing
Look for growing average time to first response. Watch backlog age above two business days. Track percentage of answers that required correction after sending. Count escalations that stall longer than your SLA. Check for multiple public versions of the same EPD circulating. If you hear project teams say we sent something similar last month but cannot find it now, the system is slipping.
Guardrails that keep speed and quality intact
Make the first response a promise, not a guess. Teach reps to answer with a confident holding reply that names the next update time. Force validation to be visible in the same ticket. Require maintenance to close the loop by updating the Answer Card and notifying sales enablement. Run monthly fire drills that sample ten tickets and grade for clarity, correctness, and cadence.
When the work changes, the answers must change too
Recipe adjustments, new sites, energy mixes, or PCR revisions change answers. Treat each as a maintenance event with a tiny release plan. Refresh the Answer Card, retrain frontline teams with a five minute huddle, and update the public file location everywhere it appears. Do not let shadow PDFs live in old proposal folders.
Bring it together without adding headcount chaos
Ownership is a system. One intake. One accountable editor. Clear roles for first response, validation, maintenance, and escalation. The reward is simple. Faster replies that keep bids alive and fewer late-night scrambles across highly paid experts. It is not glamourous work, but it wins specs.
