Make Scope 1/2/3 and boundaries approachable — so your reporting doesn't collapse
By the end of this resource you will:
Usually in real estate operations:
Beginner rule: Track kWh (and billing dates) first. Cost is secondary.
Scope 3 is "other indirect emissions" — mainly:
Beginner rule: Scope 3 is not a single project. It's a system: screen → focus → improve.
Before you calculate anything, you must define what's in your inventory.
There are two types of boundaries you need to understand:
Common approaches (pick one and be consistent for the reporting year):
You don't need to master these on day one, but you do need to choose an approach and write it down.
This is where Scopes 1/2/3 live. Operational boundaries define which activities are Scope 1 vs Scope 2 vs Scope 3.
Real estate often has:
So the same building can produce different reporting treatment depending on:
Beginner rule: Don't try to "perfect" leased assets on day one. Build data access + method disclosure and improve over time.
This avoids the most common failure mode: starting Scope 3 while Scope 2 is chaos.
Run the Operation stage
Carbon Basics stage
Carbon Basics stage
Scope 3, Made Practical stage
Scope 2 is often reported two ways:
Beginner rule: Always calculate location-based. Only publish market-based if you can list and defend the instruments and method.
(You'll implement details in the Scope 2 methods resource.)
Scope 3 is a set of categories (15 in the GHG standard). You do not need all categories perfectly to start.
The right approach is:
Use spend and basic activity proxies to find what matters most.
Pick the top 2–4 categories (and the top suppliers driving them).
Upgrade data quality over time (supplier activity data, then supplier-specific methods).
Beginner rule: Your first Scope 3 deliverable is a prioritized shortlist, not "perfect emissions."
Examples:
Fix: Track measured vs allocated vs proxy. Reconcile totals. Keep an explicit method note.
Examples:
Fix: Write your boundary statement. Use leased assets guidance and disclose limitations.
Examples:
Fix: Evidence link requirement for each period and site (bill/export/service log).
Examples:
Fix: Follow the sequence in this resource.
For reporting year [YYYY], Alpaka's organizational boundary uses [operational control / financial control / equity share]. Our operational boundary includes Scope 1 emissions from [on-site fuels + refrigerants under our control], Scope 2 emissions from purchased [electricity/steam/heat/cooling] where we consume energy, and Scope 3 emissions from value chain activities prioritized through a screening process. Where activity data is not available, we use documented estimates and disclose assumptions. We will improve data quality over time by expanding measured data coverage and supplier engagement.
| Source | Scope | Where it shows up | Minimum data needed | Evidence |
|---|---|---|---|---|
| Boiler/generator fuel | Scope 1 | fuel bills, tank logs | quantity + dates + unit | invoice/log |
| Refrigerants (if controlled) | Scope 1 | HVAC service logs | refrigerant type + qty + date | service log |
| Electricity | Scope 2 | utility bills/portal | kWh + billing period | bill/export |
| Natural gas | Scope 1 (if controlled) or tenant | bills/portal/tenant | therms/ccf + dates | bill/export |
| Service vendors | Scope 3 Cat 1 | AP/vendor list | spend + vendor category | invoices/AP |
| Capex projects | Scope 3 Cat 2 | capex ledger | spend + project type | capex docs |
| Waste | Scope 3 Cat 5 | hauler reports | tons by stream + method | vendor report |
| Leased assets | Cat 8/13 | leases + utilities | role + lease type + kWh method | lease + bills |
Measured = direct reading or bill/export for the specific source Allocated = derived from a known total using a documented allocation rule Proxy = estimated using typical intensity/spend factors (temporary only)
Confidence: High (definitions + sequencing align with common GHG reporting practice)
Assumptions: You want operationally defensible reporting, not perfect theory.
Where this can fail: If boundaries and methods change mid-year without a change log, or if evidence links are missing.
v1.0 (2026-01): Latest release