Workflow · Trade Readiness · Trade Secure

Trade Secure

Review the counterparty and transaction evidence before a commitment.

Start — not yet availableAbout this capability
Foundation — in development

Who it is for — and what you will need

Parties about to commit to a transaction.

  • The transaction/opportunity
  • Buyer and supplier identities
  • Product and destination
  • Trade-related documents you 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. Transaction

    Transaction, parties, product and destination captured.

    in development
    Stage details
    What OrenAtlas already knows
    Known parties, product, destination from the originating case
    What you provide
    Transaction description + terms context (required) — This is a checkpoint before commitment, not a static brochure
    Evidence used
    No evidence collected at this stage.
    What happens
    Transaction bound to canonical parties/product
    If something is missing
    Unknown terms recorded as open.
    Done when
    Transaction captured.
    What comes next
    Trade Secure case.
  2. Risk checks

    Identity, sanctions/watchlist evidence, licences and credentials for both sides.

    in development
    Stage details
    What OrenAtlas already knows
    Identity, sanctions/watchlist evidence, credential/licence states for both sides
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    Identity records, Sanctions evidence, Credential records. Reuse: Reused with freshness re-checked at checkpoint time.
    What happens
    Both parties screened; freshness stated
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Party checks assembled.
    What comes next
    Party check findings.
  3. Documents

    Trade-related documents with provenance, expiry and freshness.

    in development
    Stage details
    What OrenAtlas already knows
    Trade-related documents on file with provenance, expiry and freshness
    What you provide
    Transaction documents (if applicable) — Close specific document gaps
    Evidence used
    Trade documents with provenance. Reuse: Documents attach to the transaction; expiry visible.
    What happens
    Each document bound to the transaction with expiry state
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Document set assembled (gaps explicit).
    What comes next
    Document inventory.
  4. Gaps

    Open questions and evidence gaps as explicit findings.

    in development
    Stage details
    What OrenAtlas already knows
    Open questions and evidence gaps
    What you provide
    Nothing — OrenAtlas assembles this stage.
    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
    Gap list finalized.
    What comes next
    Pre-commitment gap list.
  5. Review

    Human review. States: clear on available evidence · conditions outstanding · further evidence required · specialist review required · unresolved.

    in development
    Stage details
    What OrenAtlas already knows
    Full checkpoint picture
    What you provide
    Checkpoint state (required) — Clear on available evidence · conditions outstanding · further evidence required · specialist review required · unresolved
    Evidence used
    No evidence collected at this stage.
    What happens
    State uses the five checkpoint states only
    If something is missing
    Open items acknowledged in the state.
    Done when
    Checkpoint state recorded.
    What comes next
    Checkpoint judgment.
  6. Trade Secure Report

    Versioned review. Not cybersecurity, not insurance, not a payment guarantee, not regulatory approval.

    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; explicitly NOT insurance/cybersecurity/payment-guarantee/approval; monitored until commitment
    If something is missing
    Outstanding conditions listed.
    Done when
    Versioned Trade Secure Review generated; monitoring active until commitment.
    What comes next
    Trade Secure Review (versioned) → Trade Rescue / Sourcing decision.

What you receive: Trade Secure Review

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

transaction contextparty identity findingssanctions/credential evidencedocument provenancegapsreview stateconditions

Current state

Foundation — in development.

An evidence-review discipline specified end to end — not yet implemented; no transaction tables exist.

Where this hands off next

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