Enter workspace

Workflow · Evidence & Compliance · Credentials & Licences

Credentials & Licences

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

Start a Credentials case →About this capability
Partially live

Who it is for — and what you will need

Compliance and sourcing teams checking credentials before relying on them.

  • The exact legal entity (and facility/product where applicable)
  • Which credential or licence types matter
  • The relevant market/jurisdiction

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

    Resolve the exact legal entity, facility or product — credentials never transfer across group companies.

    Start a Credentials case → (live today)
    Stage details
    What OrenAtlas already knows
    Exact legal entity, facilities and products from canonical records
    What you provide
    Subject selection (entity / facility / product) (required) — Credentials bind to the exact subject the issuer names — never transferred across group companies
    Evidence used
    No evidence collected at this stage.
    What happens
    Subject resolves to one canonical record
    If something is missing
    Missing subject records create a data task, not a guess.
    Done when
    Subject fixed.
    What comes next
    Credential case subject.

  2. Requirements

    Which credentials/licences the purpose or market requires.

    in development
    Stage details
    What OrenAtlas already knows
    Requirement sets known for the market/purpose
    What you provide
    Market / purpose (required) — Scopes which credential requirements apply
    Evidence used
    No evidence collected at this stage.
    What happens
    Requirement set carries its version
    If something is missing
    Unknown requirement sets are stated as unknown — never invented.
    Done when
    Applicable credential requirements listed.
    What comes next
    Credential requirement list.

  3. Records

    Issuer, identifier, source, issue/expiry dates and jurisdiction per record.

    in development
    Stage details
    What OrenAtlas already knows
    Existing credential records: issuer, identifier, source, issue/expiry dates, jurisdiction
    What you provide
    Additional credential documents (if applicable) — Fill gaps the connected sources do not cover
    Evidence used
    Official register lookups, Issuer databases, Supplier-submitted certificates (labelled). Reuse: Existing credential evidence reused with validity re-checked; supplier submissions never overwrite authoritative states.
    What happens
    Each record bound to the exact named subject
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Records matched to requirements.
    What comes next
    Credential record inventory.

  4. Validity

    Current? Source-confirmable? Conflicting? Renewal needed? Explicit states, no generic verified.

    in development
    Stage details
    What OrenAtlas already knows
    Per-record: current/expiring/expired, source-check state, conflicts; expiry made obvious (e.g. "expires in 28 days → renewal action")
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    Source confirmations. Reuse: Source-check results carry their retrieval date; stale checks shown as stale.
    What happens
    Explicit per-item states — no generic verified
    If something is missing
    Unconfirmable sources → "source not confirmed", an explicit state.
    Done when
    Every record has an explicit validity state; expiring items have renewal actions.
    What comes next
    Validity assessment with renewal/request actions.

  5. Credential Report

    Versioned Credential & Licence Evidence Report with per-item states and gaps.

    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 report; per-item states; monitoring triggers registered
    If something is missing
    Gaps appear as owned actions in the report.
    Done when
    Versioned Credential & Licence Evidence Report generated.
    What comes next
    Credential & Licence Evidence Report (versioned) → Compliance / Due Diligence; monitored for expiry/renewal/revocation.

What you receive: Credential & Licence Evidence Report

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

per-credential stateissuer + identifiersubject bindingvalidity windowssource confirmation stateconflictsrenewal needs

Current state

Partially live.

The operational case workflow is live for eligible signed-in buyer members: canonical company subject, requirement picture (honest not-connected market rows), canonical records from certifications/evidence documents/supplier submissions, multi-dimensional validity with real renewal tasks, and a versioned Credential & Licence Report (/workspace/credentials/new; requires the case runtime to be provisioned). Human review never establishes issuer/source provenance.

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 →Partially live

Due Diligence

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

View workflow →