TRACI in 2026: the version your EPD should use
The U.S. EPA’s current TRACI release is 2.2, with site‑generic characterization factors and site‑specific eutrophication factors introduced in 2021. The TRACI page shows a last update on December 12, 2025, so you’re looking at the latest info.
).
Ensure that you use no text, as this illustration will be used on international translations of the article..
Use an illustrative style (e.g. isometic) and don't generate in a photorealistic style.](/_next/image?url=%2Fapi%2Fmedia%2Ffile%2F1b736ce71898.webp&w=3840&q=75)
TRACI, in construction terms
Think of TRACI like the equalizer on a sound board. It turns raw foreground data for a product into comparable “tracks” such as global warming potential, acidification, eutrophication, smog, human toxicity, and ecotoxicity so your EPD speaks the same language as project specs.
Which version should your EPD cite right now
Use TRACI 2.2 unless your governing PCR explicitly locks you to 2.1. Most North American PCRs that predate 2021 reference 2.1 and remain valid under their own rules. If you are starting a new EPD or a renewal, check the PCR and your program operator guide first, then document the LCIA method and version directly in the declaration.
What changed from 2.1 to 2.2 that you might notice
EPA updated eutrophication to include spatially resolved characterization factors in 2021. That improves how nutrient releases translate to impact in different watersheds, which can shift results for water‑adjacent manufacturing or high nutrient outputs (Henderson et al., 2021) (Henderson et al., 2021). The site‑generic factors remain available as a single spreadsheet release labeled TRACI ver 2.2 (EPA TRACI, 2025) (EPA TRACI, 2025).
Will LEED v5 change what you report
LEED v5 was ratified by USGBC members on March 28, 2025. It continues to rely on third‑party EPDs created under PCRs and standards, so your job is to follow the PCR and clearly state the LCIA method and version. Projects will still read your GWP and other indicators directly from the EPD (USGBC, 2025) (USGBC, 2025).
Practical moves to avoid rework
- Confirm the PCR’s LCIA method and version in writing before data collection. If it lists TRACI 2.1, ask the operator whether 2.2 is acceptable and how to report it.
- Lock your software libraries to the cited TRACI version and note the publication year in your LCA report and EPD draft.
- For eutrophication, decide whether you will use the site‑generic or site‑specific factors and document the choice consistently across all products in scope.
- Keep the TRACI spreadsheet in your project archive with a versioned filename. Future auditors love that.
How this affects timelines and internal effort
Clarifying the LCIA method up front means fewer reruns and fewer EPD redlines. It also keeps R&D and plant teams focused on supplying data once rather than twice, which is where most schedules slip. This saves alot of email volleying.
Bottom line for 2025
If your PCR allows it, cite TRACI 2.2 and move on. If it prescribes 2.1, comply and note the version transparently. Either way, make the choice early, document it visibly in the EPD, and keep the team rowing in the same direction with one clean dataset. That’s how you publish fast without sacrificing trust.
Frequently Asked Questions
Is TRACI 2.2 a new method or just updated factors?
It is the same TRACI method family with updated characterization factors. The most notable change is the 2021 release of spatially resolved factors for eutrophication potential (Henderson et al., 2021).
Do I need to rerun older EPDs that used TRACI 2.1?
No. Existing EPDs remain valid for their stated term under the PCR and program operator rules. Switch to TRACI 2.2 at the next revision when permitted by the PCR.
Where do I download the current factors?
EPA hosts the site‑generic TRACI ver 2.2 spreadsheet and the separate site‑specific eutrophication files on its TRACI page (EPA TRACI, 2025).
About the Author
With a passion for sustainability and a love for complex data, Toby helps manufacturers efficiently collect data from across their organization and get their EPDs done right. He’s especially interested in how AI can support human expertise, helping R&D and factory teams work faster, smarter, and with less friction.
