Core rules to prevent greenwashing in digital sustainability

Rule 1. Be precise about the scope

Specify exactly what the claim covers. Indicate which product feature, page, region, or part of the lifecycle you mean. Vague phrases create risk; avoid leaving scope implied. If a claim only applies to the energy used by a hosting provider for a specific service, say that explicitly.

Rule 2. Use measurable terms and units

Prefer numbers and units over qualitative adjectives. State the metric you measured, the time period, and whether the number is per user, per month, per visit or for the entire service. When you present percentages include the reference baseline that defines the denominator.

Rule 3. Substantiate with evidence you can produce on request

Any public sustainability statement should be traceable to documentation you can supply within a reasonable timeframe. That includes methodology notes, dates, data sources and any third party verification. If you cannot produce evidence, do not publish the claim.

Rule 4. Avoid absolute and timeless claims unless fully verifiable

Do not use words that imply permanence or totality unless supported by robust proof. Words such as entirely, zero impact, totally, or permanent are risky. Use timebound and conditional phrasing instead.

Rule 5. Distinguish between measured reductions and compensations

Make clear whether a reported improvement comes from reducing operational impacts or from offsetting actions. If offsets or credits are part of the claim, name the mechanism and the standard under which the credits were issued.

Rule 6. Avoid confusing environmental categories

Do not conflate social, privacy or accessibility improvements with environmental benefits. If you describe multiple benefits, separate them and provide evidence for each category.

Rule 7. Keep channel wording aligned with documentation

Different channels require different brevity but not different facts. Ensure headlines, product pages and marketing copy are consistent with the supporting documentation and the substantiation checklist.

Examples of high risk claims and safer rewrites

1. Risky: Sustainable hosting

   Safer: Hosting for this service is sourced from a data center that reports renewable electricity purchases specific to the hosting account. See our methodology page for the contract dates and supplier statements.

2. Risky: Carbon neutral

   Safer: We have offset the estimated operational emissions from this feature for the period January to December 2025 using registered carbon credits from recognized registries. Offsets are documented in our offsets register.

3. Risky: Zero emissions

   Safer: We reduced data transfer per page view by 30 percent relative to October 2024 through image compression and caching. Measured metrics and test methodology are available on our technical report.

4. Risky: Environmentally friendly

   Safer: This product reduces average page payload by X kilobytes compared with the previous version. Reduction measured across a representative sample of live traffic between dates A and B.

Substantiation checklist every claim must meet

1. Define the claim scope and the unit of measurement.

2. Record the measurement methodology and time period.

3. Store raw data and aggregated results in a retrievable location.

4. Identify any third party standards, registries or certificates relied upon and retain the relevant documentation.

5. Document assumptions and any applied conversion factors.

6. List limitations and known uncertainties that affect the claim.

7. Prepare a short public explanation that links the claim to the evidence.

An approval workflow that reduces greenwashing risk

1. Draft and label Start with a working claim draft that contains scope, unit, timeframe and the supporting evidence references. Label drafts by channel and estimated audience reach.

2. Technical review An engineer or analyst verifies the data sources, measurement method and whether the claim matches the numbers. Flag any gaps as non negligible and return draft for revision.

3. Legal and compliance review A reviewer checks for regulatory exposure and aligns language with legal requirements and relevant guidance from enforcement bodies.

4. Marketing edit A marketer adapts language for the intended channel while preserving the verified facts and adding a link to the substantiation page.

5. Sign off and publish The final approver confirms that evidence is accessible to consumers and that the claim is consistently presented across channels.

6. Periodic recheck Schedule a review at an interval matching the claim timeframe. Update or remove claims when the underlying data or standards change.

Wording templates that reduce ambiguity

Use templates that force specification of the scope and evidence. Replace placeholders with your verified details before publishing.

1. Efficiency claim template: From date to date we reduced [metric name] for [scope] by [number and unit] measured against [baseline reference]. Methodology and raw metrics available at [URL].

2. Offset claim template: For [scope and period] we offset [quantity and unit] using credits issued under [registry or standard]. Offset transactions are recorded at [URL] with transaction IDs.

3. Supplier claim template: Hosting for [service] is supplied by [provider]. The supplier reports renewable energy purchases for the account covering [period]. Documentation: [URL or file reference].

How regulators and standards inform wording choices

Regulatory guidance and international standards converge on the same practical priorities: clarity about scope, measurable claims, and verifiable evidence. Using precise, timebound language and naming the data sources aligns your statements with common enforcement expectations. When you mention third party verification name the verifier and link to the certificate or registry entry.

Practical checks for product and marketing teams before publishing

1. Can you produce the supporting data within five working days?

2. Does the copy state who measured the result and when?

3. Is the claim consistent across headline, body copy and technical pages?

4. Have you identified limits and applicable exclusions in plain language?

5. Have legal and technical reviewers both signed off?

When to avoid a public claim

Do not publish environmental claims when data is preliminary, based on a pilot sample that is not representative, or when the measurement method is still being developed. It is better to present a work in progress as ongoing improvement and link to a roadmap and measurement plan than to assert results you cannot substantiate.

Implementing safer claim language across channels

Public webpages should link to a single substantiation page that contains the raw metrics, methodology summary and documents. Short social posts can use condensed templates but must include a link to the substantiation page. Paid campaigns need the same level of substantiation as organic content because regulators treat paid messaging as high impact.

Final implementation notes

Train teams on the templates and the checklist. Automate evidence capture where possible so measurement artifacts are stored by default. Maintain a register of active claims with review dates to avoid stale or unsupported statements.