Carbon Overview and GHG Scopes
TX1 tracks greenhouse gas emissions alongside cost using the GHG Protocol framework. Every direct cost item, overhead and resource can carry an emission figure; the totals roll up like money does.
GHG Scopes
| Scope | Example |
|---|---|
| Scope 1 | Fuel burned on site, company vehicles, equipment you own. |
| Scope 2 | Purchased electricity, steam, district heating or cooling. |
| Scope 3 | Supplied materials (cement, steel), sub-contracted works, employee travel, waste transport — everything else. |
Resources default to Scope 3 if their scope value is missing or invalid — that's the conservative, usual choice for supplied materials.
What TX1 Tracks
| Entity | Purpose |
|---|---|
EmissionFactor | Standardised kgCO₂e per unit for a material / activity. Can be a system default or custom. |
DirectCostEmission | Emission attached to a direct cost item. |
OverheadEmission | Emission attached to an overhead item. |
CarbonEmissionAllocation | Broader project-level allocation (resource-based, formula, or manual). |
CarbonEmissionSnapshot | Historical record for trend analysis. |
Core Formula
TotalEmissions = Quantity × EmissionFactorFor overheads that work off a dollar amount:
TotalEmissions = Amount × EmissionFactorFor custom allocations:
TotalEmissions = ActivityData × EmissionFactorData Quality
Every emission record carries a DataQuality rating 1–5:
| Rating | Meaning |
|---|---|
| 5 | Supplier-specific EPD / third-party verified. |
| 4 | Industry-standard database (e.g. DEFRA, ICE). |
| 3 | Organisation default factor. |
| 2 | Estimated from a proxy material. |
| 1 | Rough assumption — improve before reporting. |
Verification Workflow
Emissions have a Verified flag plus VerifiedAt / VerifiedByUserId. See 09.5.
Reporting Outputs
- Summary view — totals per scope, and a combined total.
- Dashboard KPI — per project and across the portfolio.
- PDF report — scope breakdown, top emitters, charts.
- Carbon Emissions export — CSV / JSON for external auditors.
- Snapshots — stored historical totals for trend reporting.
Organisation vs Project Factors
EmissionFactor.IsSystemDefault separates organisation-wide factors from project-specific overrides. Users can create custom factors per project without polluting the master library.