Enter workspace

Workflow · Evidence & Compliance · Compliance

Compliance

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

Start — not yet availableAbout this capability
Foundation — in development

Who it is for — and what you will need

Suppliers preparing for a market or buyer; buyers checking a counterparty against requirements.

  • The requirement set (framework, regulation, market or buyer requirements)
  • The subject company/facility/product
  • The destination market where relevant

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

    Company, product/facility, destination market and requirement set selected; known context prefilled.

    in development
    Stage details
    What OrenAtlas already knows
    Subject context from originating workflow; known markets
    What you provide
    Market / requirement set (required) — OrenAtlas explains WHY each requirement set applies before mapping starts
    Evidence used
    No evidence collected at this stage.
    What happens
    Requirement set carries its framework/regulation version
    If something is missing
    Unknown requirement sets stated as unknown.
    Done when
    Subject + versioned requirement set fixed, with applicability explained.
    What comes next
    Compliance case scope.

  2. Evidence mapping

    Every requirement shows: subject → evidence → source → freshness → state → gap.

    in development
    Stage details
    What OrenAtlas already knows
    Per requirement: subject → evidence → source → freshness → state → gap → action (e.g. source-backed/no action · missing/request evidence · pending review/review)
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    All existing evidence records. Reuse: Reuse validates subject/market/freshness; requirement-engine internals never exposed to the user.
    What happens
    Every requirement row has an explicit state and an action or no-action
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Full requirement-evidence map rendered.
    What comes next
    Requirement coverage map.

  3. Actions

    Per-gap next actions: request document, renew credential, resolve mismatch, obtain specialist review.

    in development
    Stage details
    What OrenAtlas already knows
    Per-gap suggested actions: request document, renew credential, resolve identity mismatch, obtain specialist review, collect product information
    What you provide
    Action assignments (required) — WHAT/WHO/WHEN per gap
    Evidence used
    Responses to requests. Reuse: Responses attach to their requirement.
    What happens
    Every open gap has an owner or an explicit accepted-open state
    If something is missing
    Unanswered actions stay visible as waiting.
    Done when
    Actions resolved, accepted open, or escalated.
    What comes next
    Updated coverage + action trail.

  4. Specialist review

    Human review of coverage and unresolved items.

    in development
    Stage details
    What OrenAtlas already knows
    Items flagged for specialist attention
    What you provide
    Specialist assessment (if applicable) — Regulatory ambiguity and material interpretation only — trivial steps need no approval
    Evidence used
    No evidence collected at this stage.
    What happens
    Specialist items resolved or explicitly open
    If something is missing
    Unresolved specialist questions stay open in the report.
    Done when
    Specialist review complete where needed.
    What comes next
    Reviewed coverage state.

  5. Coverage Report

    Compliance Evidence Coverage Report — never "certified compliant" or "approved by OrenAtlas".

    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; never "certified compliant"/"approved by OrenAtlas"; requirement versions retained; next actions present
    If something is missing
    Open gaps listed with owners.
    Done when
    Versioned Compliance Evidence Coverage Report generated.
    What comes next
    Compliance Evidence Coverage Report (versioned) → Feasibility / Trade Rescue / Market Entry.

What you receive: Compliance Evidence Coverage Report

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

requirement-by-requirement coverageevidence with sources and freshnessgapsrequired next actionsspecialist reviewunresolved items

Current state

Foundation — in development.

Requirement templates and evidence coverage computation exist in the engine; the compliance case workspace is specified but not yet built.

Where this hands off next

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

Partially live

Feasibility Study

Can this specific company × product × target market opportunity realistically move forward on available evidence, requirements and practical constraints?

View workflow →Foundation — in development

Trade Rescue

Unblock a stalled case: turn its blockers into an owned, dated action plan, resolve what can be resolved, and return the result to the originating case.

View workflow →Foundation — in development

Market Entry Readiness

For a selected market: what appears ready, what is missing and what remains unresolved — based on available evidence and the market’s known requirements.

View workflow →