Skip to main content
Your progress
0 of 6 complete0%
T5 / M5.8 / L5 OF 5 / Architect LEVEL / 9 min

Reporting carbon to leadership

Outcome

By the end of this lesson, you will be able to build a carbon report leadership can use for ESG and strategy, adapt the message for different audiences (CEO, sustainability team, investors), and avoid common reporting pitfalls.


PrerequisitesM5.8.L1-L4 (carbon fundamentals + scheduling)
Time9 minutes

1. Concept

A carbon report is built the same way as a cost report: the trend, the breakdown, the per-unit figure, a comparison, and what to do about it.

The audience shifts a little. The structure does not. Done properly it turns sustainability from something in the annual report into a number somebody owns.

Terminal window
SECTIONS:
ANNUAL CARBON TREND (this year vs prior years)
PER-WORKLOAD BREAKDOWN (where the carbon comes from)
INTENSITY METRICS (kg CO2 per unit of business value)
COMPARISON TO PEERS (industry context)
INITIATIVES + DECISIONS (what was done, what's planned)

Sample carbon report

A canonical annual report:

Terminal window
ANNUAL CARBON FOOTPRINT: 2025
TOTAL: 580 tons CO2 equivalent (-13% vs 2024's 665 tons)
INTENSITY METRICS:
Per MAU: 48 kg CO2/MAU (down from 67 kg in 2024; -28%)
Per order: 0.045 kg CO2/order
Per $1M rev: 12 tons CO2 per $1M revenue (down from 15)
BREAKDOWN BY SOURCE:
Compute: 380 tons (66%)
Storage: 90 tons (16%)
Network: 75 tons (13%)
Other: 35 tons (6%)
GEOGRAPHIC BREAKDOWN:
us-east-1 (high intensity): 380 tons
eu-west-1 (lower intensity): 130 tons
ap-southeast-2 (high): 70 tons
INITIATIVES TAKEN in 2025:
Q3 schedule rollout non-prod (-45 tons in 2025)
Q4 ML training moved to eu-north-1 (-25 tons in 2025)
Graviton migration eligible workloads (-15 tons in 2025)
Combined: -85 tons (665 → 580)
2026 TARGET: 435 tons (-25%)
Required initiatives:
Expand scheduling to remaining non-prod
Region migration for batch data pipelines
Continue Graviton migration

Audiences and their needs

Terminal window
LEADERSHIP (CEO, COO):
Headline trend (am I getting better or worse?)
Target + progress (am I on track?)
Drivers (what changed, why)
Decisions needed (investments, prioritization)
ESG / SUSTAINABILITY TEAM:
Detailed methodology
Scope boundary definition
Initiative tracking
Comparable metrics across business units
Audit-trail for verification
INVESTORS / BOARD:
Trend vs prior year
Industry comparison
Sustainability commitments (do we meet our public goals?)
Public-facing carbon scope (what's reported externally)
CUSTOMERS (some require sustainability disclosure):
Vendor-supplied numbers
Methodology + scope
Reduction commitments
INTERNAL ENGINEERING:
Per-workload attribution (who's responsible)
Optimization opportunities
Trend per team

Each audience gets a different lens on the same data.

Per-workload attribution

Carbon flows like cost: you can attribute by team, by cost-center, by service, by environment:

Terminal window
SIMILAR TO COST ATTRIBUTION:
Compute carbon = compute_hours × power_draw × grid_intensity
Storage carbon = stored_bytes × power_per_byte (rough)
Network carbon = traffic × power_per_gigabyte (rough)
ATTRIBUTE TO:
Team (by tag)
Cost-center (by tag)
Workload (by service)
Environment (by tag)
Product line (by tag)
SAME tagging discipline as cost. Carbon flows the same way.

Per-team carbon reporting drives accountability the way per-team cost reporting drives ownership.

Annual targets

Setting carbon reduction targets:

Terminal window
TYPICAL TARGETS:
Year 1: -10% (achievable with quick wins like scheduling)
Year 2: -20% (compounding gains)
Year 3: -30% (region migrations + Graviton)
Long-term: net-zero by the year your corporate sustainability
commitment names
SETTING TARGETS:
Baseline: current annual carbon (measured)
Industry benchmarks: where peers are
Net-zero commitments: organization-wide goals
Trajectory: gradual reduction; realistic per year

Targets should be measurable (clear baseline, clear method), time-bound (year-by-year, not vague), and achievable (don’t promise what you can’t deliver).

Carbon intensity metrics

Terminal window
CARBON PER UNIT OF BUSINESS VALUE:
kg CO2 per MAU
kg CO2 per order
kg CO2 per $1M revenue
kg CO2 per active tenant
SIMILAR TO unit economics (M5.3).
Track over time as the efficiency metric.
EFFICIENCY IMPROVEMENT = lower kg CO2 per unit (similar to cost-per-MAU).

The intensity metric matters more than the absolute. A company growing 50% YoY with a 20% increase in total carbon is improving (carbon per unit is dropping); a flat company with the same 20% increase is getting worse.

Comparison to peers

Terminal window
ILLUSTRATIVE RANGES (not a published standard):
SaaS: 30-100 kg CO2/MAU
E-commerce: 0.01-0.05 kg CO2/order
Media / streaming: ~0.04 kg CO2/streaming-hour (IEA, 2020)
Cloud platform vendors: per-vCPU-hour comparisons
USE FOR:
Investor narrative (we're at the favorable end of the range)
Customer comparison (procurement scoring)
Industry recognition
Self-benchmarking (are we improving relative to peers?)

Industry benchmarks are imperfect, methodology varies, but they provide context. Use them sparingly and honestly.

Carbon vs cost reporting cadence

Terminal window
COST: CARBON:
─────────────────────────────────────────────────────
Daily Cost Trend dashboard Quarterly review
Monthly variance review Annual with leadership
Quarterly with finance Annual with ESG team
Annual planning Annual with board / investors

Carbon moves slower than cost:

  • Grid intensity changes slowly (mostly seasonal)
  • Compute pattern stays consistent
  • Reporting overhead is higher (more data sources)

Don’t try to track carbon daily; quarterly is the right cadence.

Common reporting mistakes

Terminal window
MISTAKE FIX
──────────────────────────────────────────────────────────────────
Total only (no per-team breakdown) Attribution drives action
Total only (no intensity metric) Per-unit metric shows
efficiency vs raw size
Vague initiatives without numbers Quantify each initiative's
impact (tons CO2)
Methodology not documented ESG audits require it;
document the scope clearly
Over-claiming reductions Use conservative estimates;
audit annually
Hiding bad data (no comparison to peers) Be honest about where you
stand; transparency builds
credibility
One-time report; no ongoing tracking Quarterly cadence; tracker
in dashboard

Presenting carbon to leadership

A canonical 5-minute presentation:

Terminal window
SLIDE 1: Trend headline
"2025 cloud carbon: 580 tons CO2 (-13% vs 2024)"
SLIDE 2: Per-MAU intensity (the efficiency story)
"2024: 67 kg/MAU
2025: 48 kg/MAU
Trajectory: -28% year-over-year"
SLIDE 3: Drivers of improvement (what worked)
"Schedule rollout: -45 tons
Region migration: -25 tons
Graviton migration: -15 tons
Combined: -85 tons in 2025"
SLIDE 4: 2026 plan (commitment + ask)
"Target: 435 tons (-25%)
Required initiatives: scheduling expansion (+ROI),
region migrations, Graviton continuation
Estimated investment: 1-2 engineering quarters"
SLIDE 5: ESG narrative
"On track for our -25%/year reduction target
Peers: favourable end of the illustrative 30-100 kg/MAU SaaS range
Investor reporting: SOC 2 sustainability addendum"

Crisp. Trend-led. Investment-aware. Audience-appropriate.


2. Demo

A team presents to leadership:

Terminal window
QUARTERLY EXEC PRESENTATION (CFO + CTO + CEO):
SLIDE 1: 2025 CARBON FOOTPRINT: HEADLINE
Total: 580 tons CO2
-13% vs 2024
CONTEXT: 48 kg/MAU, low in the illustrative SaaS range (30-100)
SLIDE 2: DRIVERS OF IMPROVEMENT (one chart)
Schedule rollout: -45 tons (Q3 2025)
Region migration: -25 tons (Q4 2025)
Compute efficiency (Graviton): -15 tons (rolling)
TOTAL achieved: -85 tons in 2025
SLIDE 3: EFFICIENCY METRIC (per-MAU)
2024: 67 kg/MAU
2025: 48 kg/MAU
-28% improvement in carbon intensity
SLIDE 4: 2026 PLAN
Target: 435 tons (-25%)
Required:
Expand scheduling to remaining non-prod
Region migration for batch data
Graviton coverage to 50% of x86 eligible
Estimated effort: 2 engineering quarters
SLIDE 5: SUSTAINABILITY NARRATIVE
Net-zero commitment: 2030
Current trajectory: -25%/year leaves ~140 tons in 2030; residual needs PPAs or offsets
Peer context: low in the illustrative SaaS range per-MAU
LEADERSHIP DISCUSSION:
CEO: "What's the cost of the 2026 initiatives?"
FINOPS: "Net cost neutral. Scheduling saves cost; region migration
is neutral; Graviton saves cost. All three improve carbon."
CTO: "Can we accelerate?"
FINOPS: "Maybe. The region migration is the longest pole; trying
to do that in one quarter would compress engineering."
OUTCOME: 2026 plan approved; ESG report prepared with these figures;
investor narrative aligned.

The presentation took 5 minutes. The work to build it took ~10 hours per quarter. Worth it.


3. Hands-on (5 min)

Sketch your org’s carbon report:

Terminal window
HEADLINE:
Total annual carbon: __________ tons CO2
Trend vs prior year: ____% (improving / worsening / flat)
INTENSITY METRIC:
Per MAU (or per orders / per $rev): __________ kg CO2/unit
Trend: __________ (improving / worsening / flat)
BREAKDOWN BY:
Compute: __________ tons (____%)
Storage: __________ tons (____%)
Network: __________ tons (____%)
Other: __________ tons (____%)
GEOGRAPHIC distribution (top 3 regions):
__________ __________ tons
__________ __________ tons
__________ __________ tons
INITIATIVES taken (past year):
__________ Impact: __________ tons reduction
__________ Impact: __________ tons reduction
TARGET FOR NEXT YEAR: -____% reduction
PLANNED INITIATIVES:
__________
__________
__________
AUDIENCE for this report:
□ Leadership (5-min version)
□ ESG team (detailed methodology)
□ Investors (industry-comparison version)
□ Internal engineering (per-team attribution)

If you can’t fill in even rough numbers, that’s the first thing to fix: measure before you report.


4. Knowledge check

Q1

A carbon report should include:

A. Multiple lenses: total + breakdown + intensity per unit + comparison to peers + initiatives + decisions
B. Just the total
C. Only the year-on-year comparison figure, which is the only number that the leadership ever reads
D. Just numbers, no context

Show answer

Correct: A. Different audiences need different views. Leadership wants the headline trend; ESG wants methodology; investors want industry comparison; engineering wants per-team attribution. One report can serve all if structured layered.

Q2

Carbon intensity metric (kg CO2/MAU):

A. Vanity metric: not actionable
B. Same as cost-per-MAU
C. Important: it shows efficiency
D. Useful only for regulatory filing

Show answer

Correct: C. Track over time; lower is better. A company growing 50% YoY with a 20% increase in total carbon is improving (carbon per unit is dropping); a flat company with the same 20% increase is getting worse.

Q3

Carbon report frequency vs cost report:

A. Same: daily for both
B. Quarterly typical for carbon (vs monthly/daily for cost)
C. Monthly for both, in the same pack
D. Daily for the carbon, and monthly for the cost figures

Show answer

Correct: B. Grid intensity changes slowly; compute patterns stay consistent; data sources are heavier. Don’t try to track carbon daily: quarterly is the right cadence with annual deep-dive.


5. Apply

Build quarterly carbon reports. Use the canonical 5-slide format for leadership; expand to per-team attribution for engineering audiences. Pair with industry benchmarks for context.

For ESG reporting, ensure methodology is documented and auditable.


Glossary terms touched

Carbon intensity


Module quiz

Complete M5.8 → 10-question module quiz. Track 5 complete.


Start with the bill.

Foundations takes about five hours. The first lesson is nine minutes.

Free curriculum. No paywall. 290 lessons across 7 courses, plus an optional 24-lesson beginner course. Browse every course without an account; a free account opens the lessons, saves your progress and opens the exams for three publicly verifiable credentials. Read it on the train, take the exam on a Saturday, list the credential on your résumé Monday.

5h median time to finish Foundations
free account, every course, no paywall
3 certifications, each with a public verifier
Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·