Enter workspace

Workflow · Evidence & Compliance · Due Diligence

Carbon Credit Evidence Review

Review the documentation supporting a carbon-credit case: completeness, traceability, cross-checks and gaps — prepared for specialist review.

Start — not yet availableAbout this capability
Foundation — in development

Who it is for — and what you will need

Buyers and teams evaluating carbon-credit documentation before relying on it.

  • The project/provider/credit context
  • The documents submitted so far
  • The intended use of the credits

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. Case scope

    Project, provider and credit context captured; required document checklist derived.

    in development
    Stage details
    What OrenAtlas already knows
    Known counterparty context from the DD case
    What you provide
    Project / provider / credit context (required) — Determines the required document set · Intended use (required) — Frames what the review must and must not conclude
    Evidence used
    No evidence collected at this stage.
    What happens
    Required document checklist derived from context
    If something is missing
    Unknown context fields become explicit open questions.
    Done when
    Case scope + required document set fixed.
    What comes next
    Scoped carbon-credit review case with document checklist.

  2. Documents

    Submitted documents inventoried; registry/source cross-checks where supported.

    in development
    Stage details
    What OrenAtlas already knows
    Submitted documents inventoried against the checklist
    What you provide
    Documents (if applicable) — Project records, registry entries, issuance/retirement statements, methodologies, attestations
    Evidence used
    Project documents, Registry records, Issuance/retirement statements, Methodology documents, Attestations. Reuse: Documents attach to their checklist item; provenance per record.
    What happens
    Every document mapped to a checklist item
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Inventory complete against checklist (gaps explicit).
    What comes next
    Document inventory with completeness states.

  3. Traceability

    Issuance, retirement and methodology evidence; provenance per record.

    in development
    Stage details
    What OrenAtlas already knows
    Registry/source cross-checks where supported; issuance/retirement/methodology evidence chains
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    Registry cross-checks, Source confirmations. Reuse: Cross-check results carry retrieval dates; what could NOT be cross-checked is stated.
    What happens
    Cross-checks state what they establish AND what they do not
    If something is missing
    "Source not confirmed" is an explicit state — never silently passed.
    Done when
    Traceability findings recorded per document.
    What comes next
    Traceability findings.

  4. Gaps

    Missing, conflicting and stale records; further-document requests.

    in development
    Stage details
    What OrenAtlas already knows
    Gap/conflict list with per-item further-document requests
    What you provide
    Further-document requests (if applicable) — Close specific documentation gaps
    Evidence used
    No evidence collected at this stage.
    What happens
    Each gap has an owner and action
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Gaps actioned or accepted open.
    What comes next
    Gap/request list.

  5. Specialist review

    Human/specialist review of the assembled evidence.

    in development
    Stage details
    What OrenAtlas already knows
    Full case: inventory, traceability, gaps — with what requires specialist interpretation flagged
    What you provide
    Specialist judgment (required) — Interpretation of completeness and traceability — never a rating, certification, authenticity guarantee, approval or trading recommendation
    Evidence used
    No evidence collected at this stage.
    What happens
    Judgment uses evidence-state vocabulary only
    If something is missing
    Open items acknowledged in the judgment.
    Done when
    Specialist review recorded.
    What comes next
    Specialist-reviewed case state.

  6. Evidence Pack

    Versioned pack. OrenAtlas never certifies credits, guarantees authenticity or acts as a registry.

    in development
    Stage details
    What OrenAtlas already knows
    Everything above
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    No evidence collected at this stage.
    What happens
    Versioned; explicit no-certification framing; next actions present
    If something is missing
    Outstanding requests listed.
    Done when
    Versioned Carbon Credit Evidence Pack generated.
    What comes next
    Carbon Credit Evidence Pack (versioned) → back to the owning Due Diligence case.

What you receive: Carbon Credit Evidence Pack

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

case scopedocument inventorycompleteness statestraceability findingscross-check resultsgapsspecialist reviewfollow-up requests

Current state

Foundation — in development.

A specialized due-diligence use case built on the Evidence Core — specified, honest checklist structure defined, workspace not yet built.

Where this hands off next

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

Partially live

Due Diligence

Review a counterparty or case for a specific business purpose, with evidence, gaps and human review.

View workflow →