| Scope boundary | The EU proposal targets voluntary explicit environmental claims made by businesses to consumers about a product, service, or trader, including claims that state or imply positive impact, lesser negative impact, no impact, or improvement over time. | The FTC side should be handled separately for US-facing claims. Use the FTC review track when the same marketing copy will appear in the United States, and do not assume the EU scope rules answer the US question. | Classify each claim by market, audience, product or trader boundary, and whether a more specific EU rule already governs the claim before deciding whether the EU Green Claims proposal is the right control set. |
|---|
| Covered actors | Treat the EU file as proposal-stage work, not as a final directive. Grounding shows the Commission proposal, Parliament's 12 March 2024 first-reading position, and the Council's 17 June 2024 general approach, so teams should track text changes before locking controls. | For a US launch or US website version, start a separate FTC Green Guides review and keep it in its own file. That lets the team make a clean choice between EU proposal controls and US review controls. | Keep an EU proposal tracker with versioned Commission, Parliament, and Council references. Keep any FTC analysis in a separate file populated from official FTC sources outside this artifact's grounding set. |
|---|
| Trigger | The EU proposal requires claim substantiation to rely on widely recognised scientific evidence, accurate information, relevant international standards, relevant environmental impacts, and trade-offs across the claim boundary. | Use the FTC lane as the US counterpart when the claim is not EU-only. The practical trigger is simple: if the same claim will be published in the US, review it under FTC materials in a separate workstream. | Build the EU evidence pack around the claim wording: claim scope, method, data source, relevant impacts, excluded impacts, trade-offs, assumptions, and the evidence version approved for publication. |
|---|
| Core obligations | The EU proposal adds ex-ante verification: Member States would set procedures, independent accredited verifiers would check claims and labelling schemes, and a certificate of conformity would be issued where the claim complies. | For US-facing claims, the comparison point is not an EU certificate process. Use the FTC track to check how the claim should be supported and reviewed under the separate US regime. | For EU claims, plan a verifier-ready file before publication: claim text, substantiation report, communication materials, label scheme documentation if relevant, verifier contact, certificate record, and change log. |
|---|
| Evidence record | The EU proposal addresses environmental labelling schemes as well as claims. It limits aggregate scores to labels established under Union law, controls new public schemes, and requires new private schemes to show added value and meet approval requirements. | Use the FTC side to decide whether the same label or seal can be used in the US. The comparison value is that the US review should be handled separately from the EU label scheme analysis. | Separate ordinary claim review from label scheme review. For EU-facing labels, document the scheme operator, governance, criteria, monitoring, third-party verification, approval route, and whether Union law already regulates the label. |
|---|
| Timing and deadlines | The EU proposal treats claims relying on offsets as high-risk. Climate claims must separate the trader's own emissions performance from greenhouse gas offsets, disclose the extent of offset reliance, distinguish reductions from removals, and address offset integrity and accounting. | If the claim uses carbon-neutral, offset, or renewable-energy wording in US marketing, send it to the FTC review lane as well. The main point is to avoid treating EU offset rules as a substitute for the US review. | For EU-facing climate claims, do not bury offsets inside a headline. Keep the emissions-reduction basis, offset volume, offset type, integrity evidence, accounting treatment, and claim wording in the same review file. |
|---|
| Enforcement | EU evidence may include life-cycle assessment material, Environmental Footprint data, claim substantiation, communication disclosures, label governance records, verifier certificates, and the source text version used for approval. | Use the FTC review to decide what evidence the US version of the claim needs. The comparison page should help you split the work, not merge the two regimes into one checklist. | Reuse raw evidence, not conclusions. A crosswalk should map each public claim to the EU proposal requirement it supports and leave FTC conclusions blank until official FTC sources are added. |
|---|
| Overlap and reuse | Treat the EU file as proposal-stage work, not as a final directive. Grounding shows the Commission proposal, Parliament's 12 March 2024 first-reading position, and the Council's 17 June 2024 general approach, so teams should track text changes before locking controls. | The FTC lane is a separate US review path. Use it when the same environmental claim appears in US-facing copy so the team can compare, rather than confuse, the two regimes. | Keep an EU proposal tracker with versioned Commission, Parliament, and Council references. Keep any FTC analysis in a separate file populated from official FTC sources outside this artifact's grounding set. |
|---|
| Practical decision rule | Treat the EU file as proposal-stage work, not as a final directive. Grounding shows the Commission proposal, Parliament's 12 March 2024 first-reading position, and the Council's 17 June 2024 general approach, so teams should track text changes before locking controls. | Use the FTC Green Guides review when the claim is for the US market or the US version of a cross-market campaign. Use the EU proposal file when the claim is for the EU market or the EU version of the same campaign. | Keep an EU proposal tracker with versioned Commission, Parliament, and Council references. Keep any FTC analysis in a separate file populated from official FTC sources outside this artifact's grounding set. |
|---|