Enter workspace

Workflow · Evidence & Compliance · Evidence Core

Evidence Core

Understand exactly what evidence exists for a subject and what it supports.

Start an Evidence Core case →About this capability
Partially live

Who it is for — and what you will need

Anyone who must judge a company, facility, product, credential, case or requirement on evidence.

  • The subject (company, facility, product, credential, case or requirement)
  • The purpose of the review
  • Any evidence you hold that OrenAtlas does not

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

How it works

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

  1. Scope

    Select the subject and purpose; existing evidence loads automatically — nothing already known is re-asked.

    Start an Evidence Core case → (live today)
    Stage details
    What OrenAtlas already knows
    Subject context from the originating workflow (never re-selected) · All existing evidence for the subject loads automatically
    What you provide
    Purpose of the review (required) — Determines which claims/requirements evidence is organized against
    Evidence used
    No evidence collected at this stage.
    What happens
    Subject resolves to a canonical record
    If something is missing
    No generic document-upload-first: subject selection is required before any collection.
    Done when
    Subject + purpose fixed.
    What comes next
    Scoped evidence case.

  2. Inventory

    Evidence grouped by requirement/claim with source, issuer, subject, effective date, expiry and retrieval date.

    in development
    Stage details
    What OrenAtlas already knows
    Evidence grouped by claim/requirement: what we have, what it supports, who/what it belongs to, source, freshness, state
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    All existing evidence records for the subject. Reuse: Reuse validates subject, purpose, market, freshness, expiry, source, review and conflict state — collect once ≠ blindly trust everywhere.
    What happens
    Every item bound to the exact subject it names
    If something is missing
    Unmatched claims appear as gaps.
    Done when
    Inventory organized by claim/requirement.
    What comes next
    Organized evidence inventory.

  3. Gaps

    Missing, stale and conflicting evidence detected and listed as specific requests.

    Request a supplier check → (live today)
    Stage details
    What OrenAtlas already knows
    Detected missing/stale/conflicting items
    What you provide
    Which gaps to action (required) — Convert gaps into specific evidence requests with owners
    Evidence used
    No evidence collected at this stage.
    What happens
    Every actioned gap has WHAT/WHO/WHEN/STATUS — no ownerless "missing document"
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Each meaningful gap is actioned, accepted as an open condition, escalated, or explicitly unresolved.
    What comes next
    Evidence request tasks (→ supplier) with tracked lifecycle.

  4. Review

    New evidence reviewed against the exact subject it claims to support; unresolved conflicts recorded.

    in development
    Stage details
    What OrenAtlas already knows
    Submission bound to its gap, with submitter, date and source type
    What you provide
    Review decision per submission (required) — Accept for use / return for correction / mark conflicting / require further verification
    Evidence used
    Supplier submissions, Source-backed records. Reuse: Prior submissions and return reasons preserved — history is never deleted.
    What happens
    Review binds evidence to the exact subject · No generic "Verified" state exists
    If something is missing
    Unanswered requests stay visible as waiting-on-supplier.
    Done when
    All received submissions reviewed (accepted / returned / conflicting / further verification required).
    What comes next
    Reviewed evidence states.

  5. Evidence Pack

    Versioned pack: inventory, provenance, coverage, gaps, pending and human-reviewed items — never a generic "Verified" verdict.

    in development
    Stage details
    What OrenAtlas already knows
    Full inventory + states + follow-ups
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    No evidence collected at this stage.
    What happens
    Pack is versioned; never a company-level "Verified" verdict; next actions present
    If something is missing
    Open requests listed in the pack.
    Done when
    Versioned Evidence Pack generated.
    What comes next
    Evidence Pack (versioned) → feeds Due Diligence / Compliance / Credentials.

What you receive: Evidence Pack

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

evidence inventorysource/provenancecoveragemissingexpiredconflictingpending reviewhuman-reviewed itemsrequested follow-up

Current state

Partially live.

The operational case workflow is live for eligible signed-in buyer members: subject-first scope (company/product), canonical inventory, gap actions through the existing evidence-request lifecycle, authorized operator review and a versioned Evidence Pack (/workspace/evidence-core/new; requires the case runtime to be provisioned). Review never converts evidence into source-backed provenance.

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 →Foundation — in development

Compliance

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

View workflow →Partially live

Credentials & Licences

Confirm which certificates, licences and authorisations exist for the exact entity, facility or product — and which are current.

View workflow →