Enter workspace

Workflow · Evidence & Compliance · Due Diligence

Due Diligence

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

Start a Due Diligence case →About this capability
Partially live

Who it is for — and what you will need

Buyers and diligence teams before a commercial commitment.

  • Why the due diligence is being conducted
  • The counterparty
  • Relevant products, facilities and market
  • Any documents you already hold

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. Scope

    Define the purpose and select the counterparty; identity confirmed from the registry.

    Start a Due Diligence case → (live today)
    Stage details
    What OrenAtlas already knows
    Company identity + everything already known (shown compactly, not re-asked)
    What you provide
    Review purpose (required) — Supplier onboarding / transaction / buyer request / market entry / enhanced review — tailors required depth (progressive, never one giant questionnaire)
    Evidence used
    No evidence collected at this stage.
    What happens
    Purpose selected; identity confirmed
    If something is missing
    Unconfirmed identity blocks deeper stages with an explicit resolution task.
    Done when
    Purpose + counterparty fixed; case created.
    What comes next
    Due-diligence case (case_id) with tailored review areas.

  2. Evidence

    Required evidence assembled; credentials, sanctions and risk evidence reviewed.

    Request a due-diligence pack → (live today)
    Stage details
    What OrenAtlas already knows
    Existing evidence, credentials, sanctions/risk evidence for the counterparty
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    Evidence Core inventory, Credential records, Sanctions/watchlist evidence. Reuse: Reuses Evidence Core — known documents never recollected; reuse re-validates freshness and subject.
    What happens
    Required review areas derive from the stated purpose
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Purpose-required evidence assembled or gap-listed.
    What comes next
    Assembled evidence + risk findings.

  3. Issues

    Missing, conflicting and stale evidence identified as concrete follow-ups.

    in development
    Stage details
    What OrenAtlas already knows
    Detected missing/conflicting/stale items and risk findings, each with source, date, subject and what it does NOT prove
    What you provide
    Escalation decisions (if applicable) — Escalations must have a recorded reason — no automatic universal risk score
    Evidence used
    No evidence collected at this stage.
    What happens
    Every escalation has a reason
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Issue list finalized with owners.
    What comes next
    Issue list.

  4. Remediation

    Evidence requests and actions created; responses received and reviewed.

    in development
    Stage details
    What OrenAtlas already knows
    Evidence requests drafted per issue
    What you provide
    Responses/documents (if applicable) — Close specific issues
    Evidence used
    Supplier responses, Source lookups. Reuse: Responses attach to their issue; prior submissions and return reasons preserved.
    What happens
    Each response reviewed against its issue
    If something is missing
    Unanswered requests remain visible as waiting-on-supplier.
    Done when
    Each issue resolved, accepted open, or escalated.
    What comes next
    Remediation trail.

  5. Human review

    A person reviews the assembled case — arithmetic and uploads are never verification.

    in development
    Stage details
    What OrenAtlas already knows
    Final-review screen: inputs, source-backed facts, statements, evidence, missing, conflicts, assumptions, unresolved questions
    What you provide
    Reviewer judgment (required) — Material interpretation and conditional conclusion — evidence-safe language, never certification
    Evidence used
    No evidence collected at this stage.
    What happens
    Explicit confirmation step before report generation
    If something is missing
    Open items must be acknowledged in the judgment.
    Done when
    Human review recorded.
    What comes next
    Reviewed case state.

  6. DD Report

    Versioned Due Diligence Report in evidence-safe language — never certification.

    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; evidence-safe language; next actions present
    If something is missing
    Open conditions listed.
    Done when
    Versioned Due Diligence Report generated.
    What comes next
    Due Diligence Report (versioned) → Compliance / Trade Secure / Carbon Credit Review.

What you receive: Due Diligence Report

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

purpose/scopeidentityevidence with provenancecredential statesrisk evidencegaps and conflictsremediation trailhuman reviewevidence-safe conclusionconditionsnext actions

Current state

Partially live.

The operational case workflow is live for eligible signed-in buyer members: canonical counterparty scope, reused evidence/credential pictures (sanctions honestly not connected), evidence-safe findings with owners and real remediation requests, authorized operator review and a versioned Due Diligence Report (/workspace/due-diligence/new; requires the case runtime to be provisioned). No universal risk score and no safe-supplier verdict exist or will.

Where this hands off next

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

Foundation — in development

Compliance

Understand whether available evidence covers a defined requirement set — and exactly what to do about every gap.

View workflow →Foundation — in development

Trade Secure

Review the counterparty and transaction evidence before a commitment.

View workflow →Foundation — in development

Carbon Credit Evidence Review

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

View workflow →