Enter workspace

Workflow · Sustainability & Product Compliance · ESG

ESG Workspace

Collect, calculate, review and report sustainability information with traceable evidence.

ESG evidence view →About this capability
Partially live

Who it is for — and what you will need

Suppliers building an evidence-backed sustainability record; buyers reading it.

  • Reporting period and boundary
  • Framework or reporting purpose
  • Metric values and their supporting evidence
  • Emissions activity data where applicable

Anything OrenAtlas already knows is prefilled with its evidence state — you are asked only for what is missing or unresolved.

How it works

6 stages. Save and resume at any point; each stage keeps its evidence attached to the exact item it supports.

  1. Program setup

    Company, reporting period, boundary, framework(s) and responsible team.

    in development
    Stage details
    What OrenAtlas already knows
    Company; previous periods and their settings (recurring periods reuse setup)
    What you provide
    Reporting period + boundary (required) — Scopes every metric and calculation · Framework / reporting purpose + responsible team (required) — Determines topics, metrics and reviewers
    Evidence used
    No evidence collected at this stage.
    What happens
    Period well-formed; boundary explicit
    If something is missing
    Setup incomplete blocks collection with a clear checklist.
    Done when
    Program configured.
    What comes next
    ESG program (reporting_period_id).

  2. Collect

    Metrics across Environmental (energy, water, waste, emissions), Social and Governance — known OrenAtlas data prefilled, evidence attached at the value.

    ESG evidence view → (live today)
    Stage details
    What OrenAtlas already knows
    Topics (Environmental: energy/water/waste/emissions · Social · Governance); metric pages with existing OrenAtlas data prefilled; per-metric: unit, period, data provider, reviewer, instructions/why-we-ask, comments, history
    What you provide
    Metric values (required) — Direct entry / document-backed entry; each value may attach invoice, meter statement, policy, report, certificate — evidence stays separate from the number
    Evidence used
    Invoices, Meter statements, Policies, Reports, Certificates, Source records. Reuse: Existing ESG data prefilled — never re-asked; reuse validates period and subject.
    What happens
    Value + unit + period per metric; evidence linked at the value
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Metrics submitted (draft → submit per metric).
    What comes next
    Submitted metric set.

  3. Calculate

    Emissions: activity × approved factor = CO2e via the emissions engine (PR #14) after approved integration. Calculation success never means verified evidence.

    in development
    Stage details
    What OrenAtlas already knows
    Activity records; factor selection/mapping via the approved emissions engine (PR #14) after approved integration — the engine is never duplicated
    What you provide
    Factor mapping confirmations (if applicable) — Explicit factor_key selection where mapping is ambiguous — never silent
    Evidence used
    Activity evidence (bills, meter records). Reuse: Calculation snapshots preserve inputs; factor updates never mutate history.
    What happens
    Every calculation retains factor identity/source/version/validity; calculation success ≠ evidence verification
    If something is missing
    Missing factors/units fail closed as tasks.
    Done when
    Calculations produced with full provenance.
    What comes next
    Emission calculations (review state separate from arithmetic).

  4. Review

    Draft → submitted → pending review → returned/resubmitted → human reviewed.

    in development
    Stage details
    What OrenAtlas already knows
    Per-metric review queue: value, evidence, history
    What you provide
    Review decision per metric (required) — Accept / return with reason — Draft → Submitted → Pending review → Returned → Resubmitted → Human reviewed
    Evidence used
    No evidence collected at this stage.
    What happens
    Return requires a reason; prior submissions preserved
    If something is missing
    Unreviewed values stay pending, visibly.
    Done when
    All submitted metrics reviewed.
    What comes next
    Reviewed metric set.

  5. Gaps

    Missing values, missing evidence, conflicts, expired evidence, framework gaps → remediation tasks.

    in development
    Stage details
    What OrenAtlas already knows
    Missing values, missing evidence, conflicts, expired evidence, unreviewed values, framework gaps
    What you provide
    Task assignments (required) — Gaps become owned tasks, not dead warnings
    Evidence used
    No evidence collected at this stage.
    What happens
    Every gap owned or accepted open
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Gaps actioned or accepted.
    What comes next
    Remediation task set.

  6. ESG Report

    Versioned ESG Report / Evidence Pack with boundary, period, metrics, evidence, calculations, methodology, review states and audit trail.

    in development
    Stage details
    What OrenAtlas already knows
    ESG summary by pillar with evidence states and open gaps
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    No evidence collected at this stage.
    What happens
    Versioned; contains boundary, period, metrics, sources, evidence, calculations, methodology, review states, gaps, audit history; next actions present
    If something is missing
    Open gaps listed in the report.
    Done when
    Versioned ESG Report / Evidence Pack generated.
    What comes next
    ESG Report / Evidence Pack (versioned) → CSRD / VSME / DPP; recurring periods supported conceptually.

What you receive: ESG Report / Evidence Pack

A versioned result — not just a PDF. It preserves:

reporting boundaryperiodmetricsevidenceemissions calculationsmethodologygapsreview statesframework mappinghuman reviewaudit trail

Current state

Partially live.

ESG evidence submission/review and the evidence view are live; the program workspace (periods, metric collection, calculation, report) is specified — the emissions engine exists in PR #14 pending approved integration.

Where this hands off next

Your case context (company, product, market, requirement) travels with you — nothing is re-selected.

Foundation — in development

CSRD Preparation

Prepare the evidence a CSRD-aligned disclosure would rest on — reusing ESG data, showing exactly what is covered and what is missing.

View workflow →Foundation — in development

VSME Preparation

Structure available evidence against the voluntary SME reporting standard — conservatively and progressively.

View workflow →Foundation — in development

DPP Readiness

For one product in one market under one regulation: what does a Digital Product Passport require, what evidence exists, and what is missing?

View workflow →