Assemble LEED and EPD documentation for a terrazzo installation
domain: usgbc.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Reference LEED v4.1's Materials and Resources credit (MRc2, Environmental Product Declarations) as the relevant credit pathway for terrazzo material documentation, verifying current credit language on usgbc.org since USGBC periodically updates rating system versions.
Collect product-specific EPDs (cradle-to-gate scope, publicly available, third-party critically reviewed) from the actual terrazzo material suppliers (aggregate, binder/resin) being used, not a generic industry-average EPD.
Confirm the project's minimum qualifying-product count for the applicable LEED credit option directly on usgbc.org rather than relying on an older LEED version's threshold.
Request supplemental sustainability documentation where available (Health Product Declarations, GREENGUARD Gold, recycled-content statements), since some terrazzo manufacturers publish these alongside EPDs to support multiple LEED credits.
Start documentation collection early in the submittal process — EPDs/HPDs are supplier- and formulation-specific documents that can take lead time to obtain for a specific color/product.
Known gotchas
A generic 'terrazzo is sustainable' claim is not credit-eligible — LEED MRc2 requires actual product-specific EPD documentation from the specific manufacturer/product being installed, not a general material-category claim.
LEED credit language and thresholds change between rating system versions (e.g., v4 vs. v4.1) — confirm which version the project is registered under on usgbc.org before citing specific credit requirements or product-count thresholds.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?