

What California is signaling
Draft CARB materials point to large commercial and multifamily projects disclosing product‑level global warming potential for in‑scope categories as the program phases in. CALGreen code workstreams have been aligning language so project teams can request verifiable, product‑specific EPDs rather than lean on sector averages. Translation for flooring suppliers: association EPDs help with education, but compliance and procurement confidence will hinge on declarations tied to the exact SKU and facility.
Regulatory text will evolve. The direction of travel is clear enough to plan against today without guessing exact thresholds.
Type III, product‑specific, plant‑specific explained
Type III means the EPD follows ISO 14025 and EN 15804 rules, is based on an independently verified LCA, and is program‑operator published. Product‑specific means the model reflects one defined product or family with consistent formulation and declared unit. Plant‑specific means the inventory uses real data from the manufacturing site supplying the job, not a pooled average across multiple factories.
Think of the PCR as the rulebook of Monopoly. Ignore it and the game falls apart. Follow it and your numbers are comparable and defensible.
Why industry‑wide EPDs become a liability
Industry‑wide or association EPDs often reflect averaged, conservative inputs. They educate the market and can be a bridge. Under a rule that asks for Type III product‑ and plant‑specific declarations, they rarely meet the letter of the ask. When buyers must report GWP per product, absent data forces them to apply conservative defaults that make bids look heavier on carbon than they are, which can quietly move a product out of contention.
If a product‑specific EPD exists beside an industry‑wide document, procurement will default to the specific one every time. Because it removes guesswork.
Want to ace your EPD strategy for resilient flooring?
Follow us on LinkedIn for insights that help you get ahead in compliance and unlock new project opportunities.
Timing realities and reporting windows
Standing up credible coverage takes calendar time. Data discovery, utility pulls, waste logs, transport mapping, and allocation choices come before the LCA math. External review and program‑operator publication add more time. Lead times are measured in weeks, not days. EPDs are typically valid for five years, which lets teams align refresh cycles with roadmap changes rather than chase one‑off updates.
If your volume peaks in multifamily, plan by shipment region and plant. If commercial TI is your core, map to the SKUs specifiers actually name in bid files. Then build the publication sequence in that order. Simple beats perfect.
How scope works for resilient flooring
Resilient flooring often blends polymers, plasticizers, fillers, glass or fiber scrims, and adhesives. That mix pushes it into the spotlight for embodied‑carbon rules that focus on plastic‑rich categories. Scope is likely to be defined by product type used in commercial and multifamily construction, not by consumer channels.
Expect project size and building type to influence reporting first, with smaller projects potentially entering later. Where a product spans manufactured housing, RV, and multifamily, assume the multifamily use case will pull the whole line into planning.
A lean plan to stand up coverage
- Confirm the right PCR and declared unit so results are comparable to peers.
- Select the program operator early to lock formatting and reviewer expectations.
- Inventory plants, formulations, and finish lines that ship to California.
- Build a clean data room for utilities, inputs, yields, scrap, and transport routes.
- Publish priority SKUs first, then expand to variants and secondary plants.
We prefer partners who remove friction in data collection so engineers can keep producing, while the documentation still ships on time. That white‑glove posture is what actually protects schedule.
Verification, operators, and digital deliverables
Third‑party review is the gate. Choose a recognized operator so the EPD is easy for design teams to trust and for code officials to accept. Ask for machine‑readable outputs so buyers can ingest GWP and meta‑data into procurement tools without copy‑paste.
If formulations differ by plant, publish plant‑resolved EPDs. If a single model truly represents multiple facilities, document representativeness and keep auditable evidence ready. Little details like consistent declared units and clear system boundaries save days of back‑and‑forth later.
What good looks like before the first reporting date
Coverage for top‑selling resilient SKUs, each with a Type III, product‑specific, plant‑specific EPD. Evidence that the PCR matches your competitive set. Digital files delivered in operator PDF plus structured format. A renewal calendar that aligns with product changes, not the other way round. And a playbook that lets sales point to a verifiable GWP number the moment a spec is on the table.
Do this and embodied‑carbon paperwork becomes a tailwind, not a tax. Miss it and teh scramble will set your schedule, not your strategy.


