The same information moves forward without being rebuilt at every step.
01 · Operation
All context starts together
Client, product, supplier, country and regulation are connected before documents are reviewed.
One operation can contain several regulatory case files without duplicating the context.
Case files in the operation
State
Risk
02 · Requirements
Every case file knows what it needs
The regulation defines the data and evidence required before a decision can be made.
It is not a generic checklist: it responds to the product and operation.
Regulatory data
Risk per axis
Calculated risk
03 · Evidence
Every document stays tied to its requirement
You can see what has been provided, what is under review and what remains pending.
The history preserves who submitted or reviewed every item.
Case-file documents
Client file
Provided by the client
04 · Portal
The client sees what they need to do
Actions, pending documents and deliverables appear without the technical noise of the backoffice.
Team and client work on the same case file, with the access each side needs.
Client portal
Pending actions
Who does what
We automate order, not judgement
The separation is deliberate: it prevents presenting a contextual regulatory decision as automatic.
The engine proposes
A person chooses
The signature is immutable
The options depend on the actual state of the case file: with 3 of 8 requirements satisfied, the favourable conclusion is not available yet. The system does not decide for you — it only tells you when you can.
Borderline case
With regulatory basis
Stays auditable
When a case does not fit the general rule, the team can document a justified exception. It is written down, frozen once the case file concludes, and shown in the report — not a silent shortcut.
The platform
Structures case files by regulation and operation.
Contrasts requirements with data and documents.
Flags gaps and inconsistencies.
Preserves evidence, activity and progress.
The expert
Interprets how the rule applies to the case.
Validates the information behind the decision.
Resolves exceptions and judgement calls.
Approves the conclusion and deliverable.
Two views, one case file
What the team sees and what the client sees
Not two systems, and not two copies of the case. The same case file with the access each side needs.
Team view
Client view
The team works on requirements, evidence and decisions, with the full operational detail.
The client sees what is theirs to do and what is already resolved, without the backoffice noise.
When the team moves, the client sees it: nobody has to forward a status by email.
Security and data
Information is handled as evidence
Access and preservation are part of the case-file design.
01Data hosted on European Union infrastructure.
02Documents in private storage separated by organisation.
03Temporary download links.
04Each client only accesses their own case files.
05Audit log protected against modification.
How it is contracted
Per case file, not per licence
You tell us the operation, we define the scope and send a proposal before starting.
The price depends on the regulation, complexity and work required. Platform management and the portal are part of the contracted case file.
You do not need to deploy software or configure an internal system.
