Sustainability pages for digital properties: essential disclosures
Organizations that publish sustainability information about websites, apps or other digital properties should aim for clarity, traceability and verifiability. A strong sustainability page does three things at once. It shows what was measured, how it was measured, and what governance and assurance exist around the numbers. The sections below describe the elements to include and why each one matters.
1. Clear scope and boundaries
State precisely which digital assets the disclosure covers. Typical boundaries to define include the URLs, subdomains, mobile apps, APIs and content delivery arrangements included in the measurement. Clarify whether the disclosure covers production traffic only or also includes staging, test environments or partner platforms.
Define the emission scopes used. Use plain language to explain whether the numbers represent direct operational energy, energy for hosting and infrastructure, third party services such as analytics and advertising, and upstream supplier emissions. If your reporting uses a known taxonomy or protocol to classify scopes, name it.
2. Primary metrics and units
Publish the main sustainability indicators that readers can compare across reporting periods. For digital properties these typically include measured or estimated greenhouse gas emissions expressed in carbon dioxide equivalent per period and per user or per page view. Provide the units next to each metric and avoid mixing units without explanation.
Also include operational metrics that support interpretation. Examples are monthly active users, total page views, data transferred, average page weight, and total compute hours for backend services. These contextual metrics help readers understand why emissions changed from one period to the next.
3. Measurement methodology
Explain the approach used to calculate emissions. State whether figures are derived from real user measurement, server logs, network transfer estimates, provider bills, or a blended model. Describe any calculators or models employed and the data inputs they require.
If you applied assumptions or emission factors, list them. Where possible provide the source and version of those factors so a reader can reproduce or audit the computation. If you use conservative assumptions to avoid overstating reductions, say so.
4. Baseline, reporting period and update cadence
Identify the reporting period and the baseline year used to track progress. Explain how changes to the baseline are handled when scope or measurement methods change. State how often the page is updated and provide timestamps for the latest data and the last methodology revision.
5. Data breakdown and granularity
Publish a breakdown that separates major contributors. Helpful groupings include hosting and infrastructure, content delivery networks, third party scripts and services, on device activity, and development or staging environments. For each group show the metric value and the percentage of the total.
Offer downloadable data in machine readable formats such as CSV or JSON. A simple downloadable table with metric names, reporting period, values and units enables journalists, auditors and technical teams to test and reuse the numbers.
6. Targets and progress
Describe any time bound sustainability targets that apply to digital operations. For each target include the baseline value, the target value, the target year and the interim progress to date. Explain how reductions achieved through procurement such as renewable energy purchasing are accounted for relative to operational measures such as optimisation work.
7. Governance, roles and responsibilities
State which teams or roles are responsible for data collection, calculation and sign off. Note who owns strategy and who is accountable for technical changes. If the organisation has a sustainability or ESG committee, indicate how digital reporting feeds into that governance structure.
8. Assurance, third party review and evidence
If the numbers are externally assured, provide the assurance statement, the scope of assurance and a link to the assurance report. If assurance is internal, explain the internal review process and list supporting documents that are available on request. Where audits or independent reviews are planned, state the expected timing.
9. Supplier and third party disclosures
Digital products often rely on numerous vendors. Explain how third party services are treated in your accounting. For major suppliers include a short description of how their emissions were estimated or the supplier data used. Where suppliers have published their own sustainability data, link to those sources so readers can verify the chain.
10. User privacy and data handling
Reporting that relies on real user measurement must address privacy. Describe how user level data is protected, whether personal data was processed, and what aggregation or anonymization steps were applied. Explain any trade offs made between measurement granularity and privacy preservation.
11. Accessibility and readability
Make the sustainability page accessible to non technical readers without hiding the technical detail. Use short summary numbers up front and provide expandable sections for methodology, data tables and raw exports. Ensure the page meets recognised accessibility standards so the disclosure is usable by a broad audience.
12. Visualisations and narrative
Include charts that show change over time, breakdowns and the relationship between traffic and emissions. Each visual should have a clear caption that explains the data source and the time range. Use narrative text to highlight the main drivers of change and the actions taken during the reporting period.
13. Risk, uncertainty and limitations
Be explicit about uncertainty and known limitations. If certain values are estimates rather than measurements, label them as such and provide an estimated uncertainty range if available. Note any data gaps and the steps planned to close them.
14. Action plan and operational measures
Describe the specific operational interventions and product changes that contributed to reductions or that are planned. Examples include asset optimisation, CDN configuration, script rationalisation, infrastructure rightsizing, and procurement of lower carbon hosting. For each measure state the expected impact and the implementation status.
15. Credible wording and claims
Avoid absolute claims that cannot be supported with documented evidence. Use precise phrasing for achievements and ensure that any claim about being carbon neutral, net zero or similar is accompanied by the accounting that supports it and links to relevant policies or offsetting instruments when applicable.
16. Contact details and feedback channel
Provide a named contact or functional inbox for questions about the disclosure and for requests for more detailed data. Invite feedback and specify expected response times for data requests or clarification queries.
Practical checklist for a publishable sustainability page
- Scope and assets included
- Reporting period and baseline
- Main metrics with units
- Measurement methodology and assumptions
- Data breakdown by contributor
- Targets, progress and timelines
- Governance and assurance statement
- Downloadable machine readable data
- Privacy note for measurement methods
- Contact for enquiries and correction requests
Presentation patterns that increase trust
Show raw numbers and derivation steps rather than only top line percentages. Link to original data sources and to supplier disclosures where applicable. Publish a changelog for methodology updates so readers can track why numbers moved between reports. Offer both an executive summary and a technical appendix so different audiences can find what they need quickly.
Frequently asked questions that your page should answer
How were digital emissions calculated. Who verified the data. What is included in the scope. How often will figures be updated. What is the pathway to reach stated targets. How privacy was preserved. Each of these questions should be answered directly on the page or linked to a detailed section.
Common pitfalls to avoid
Omitting methodology details while presenting precise numbers. Using inconsistent boundaries between reporting periods without explanation. Making strong claims without documented evidence or assurance. Burying critical assumptions in inaccessible documents. Failing to address user privacy when using real user measurement.
Publishing a sustainability page for digital properties is an exercise in transparency and reproducibility. A good page makes it straightforward for a technically minded reader to understand and reproduce the numbers and for a non technical reader to grasp the organisation’s commitments and progress. Prioritise clear boundaries, documented methods, downloadable data and an explicit statement about assurance so stakeholders can trust what is published.