Core capabilities

• Carbon scope management (Scope 1, Scope 2, Scope 3) with configurable categories.
• Emission factor lifecycle with versioning and validity windows.
• CO2e calculation on emission records using selected factors and quantities.
• Governance workflow with clear statuses: Draft, Submitted, In Review, Approved, Rejected.
• Policy-driven assignment of reviewer and manager responsibilities.
• Emission reduction targets with period-based progress tracking.
• Operational reporting through list, search, pivot, and graph views.

Designed for governance and auditability

• Maintains traceable master data for scopes, categories, and factors.
• Enforces review/approval flow before records are treated as final.
• Supports threshold-based governance decisions through policy rules.
• Provides consistent monitoring of actual approved emissions versus targets.

Business outcomes

• Standardized carbon data management across teams and companies.
• Better data quality through structured validation and approvals.
• Faster preparation for internal sustainability reporting and external disclosure.
• Stronger readiness for phased integrations with operational modules (purchase, fleet, manufacturing, projects, and more).

Configuration

Use the setup sequence below to ensure stable calculation logic and predictable governance behavior.

Baseline company setup

1. Open the Settings > Users & Companies > Users menus with a user that has administration rights.
2. Confirm company context (for multi-company environments).
3. Define responsible users for governance roles (reviewer and manager).

Configure carbon master data

1. Create or review carbon scopes (Scope 1, Scope 2, Scope 3): menu Carbon Governance > Configuration > Carbon Scopes
2. Define categories under each scope according to your reporting model: menu Carbon Governance > Configuration > Carbon Categories.
3. Keep naming conventions consistent (for example: Energy, Fuel, Transport, Purchased Goods).

Configure factor versions and factors

1. Create factor versions by methodology and effective period.
2. Set validity dates carefully to avoid overlap between versions.
3. Add emission factors with appropriate units and CO2e values.
4. Validate that factors reflect the required accounting period and data source.

Configure governance policies

1. Create policies with reviewer and manager assignment.
2. Set policy priority using sequence (lower number means higher priority).
3. Configure optional reviewer thresholds where stricter review is needed.
4. Add scoped policies first (scope/category specific), then fallback policies.

Configure target tracking

1. Create reduction targets by period, scope, and/or category.
2. Confirm target baselines and target values with business stakeholders.
3. Ensure targets are aligned with the same scope/category taxonomy used by records.

Recommended controls

• Restrict approval rights to designated governance users.
• Keep a documented convention for factor version updates.
• Avoid editing approved records directly; prefer a controlled correction process.
• Review unmatched or rejected records periodically to improve policy quality.

Demo note

In demo mode, a global fallback policy is available (Demo Policy - Global Default). It has no scope/category and lowest priority (sequence 999), so it applies only when no more specific policy matches.

Usage

Typical usage flow

Follow this process to run emissions governance from data entry to approved reporting.

Prepare the governance model

1. Confirm scopes, categories, factor versions, and factors are active and valid for the reporting period.
2. Confirm governance policies are correctly prioritized and assigned.
3. Confirm reduction targets are defined for the same period.

Create emission records

1. Create a new emission record.
2. Select the appropriate scope and category.
3. Enter activity quantity and select the applicable emission factor.
4. Review computed CO2e and source context before submission.
5. Save in Draft while data is incomplete; submit when ready for review.

Review and decision process

1. Reviewer opens Submitted records and verifies data completeness and factor relevance.
2. Reviewer moves record to In Review and either:
   • Approves for manager decision, or
   • Rejects with comments for correction.
3. Manager performs final governance decision based on policy and thresholds.
4. Approved records become the trusted dataset for KPI and target tracking.

Correct rejected records

1. Data owner reviews rejection reason.
2. Update quantity, scope/category, or factor selection as needed.
3. Resubmit record into workflow.

Monitor performance

1. Use list and search views for operational queues (draft, review, approved, rejected).
2. Use pivot and graph views to analyze approved emissions by period, scope, and category.
3. Compare approved actuals with configured targets to track progress.

Role guidance

• Data owner: creates and submits records with complete business context.
• Reviewer: validates methodological correctness and policy alignment.
• Manager: provides final approval decision and governance accountability.

Demo note

In demo mode, a global fallback policy is available (Demo Policy - Global Default). It has no scope/category and lowest priority (sequence 999), so it is used only when no more specific policy matches.

Credits