The claim, not the document, is the basic unit.
REGULOGRAPH gives every regulatory-sensitive claim its own record: precise wording, source, owner, approval and validity in time. This page explains how the platform works.
Every claim has its own record
The most important object is not the document. It is the individual claim — because it is the claim that can be true, misleading, outdated or unsupported.
- Claim ID
- A unique identifier of the claim across all documents and versions.
- Exact wording
- The approved sentence and its permitted variants; shorthand and proxy phrases are recorded separately.
- Type
- Claim category: status, licence, partnership, performance, risk, governance, technology or history.
- Entity and product
- The legal entity and the product or service the claim actually concerns.
- Jurisdiction and regime
- The jurisdiction and regulatory regime in which the claim has meaning.
- Audience and channel
- The target audience and the communication channel for which the wording is approved.
- Validity
- Effective from–to, date of last verification and the trigger for the next review.
- Evidence and source authority
- The primary legal source, decision, contract, technical proof or minutes, together with the authority level of the source.
- Owner and approver
- The business owner and the approver (compliance, legal or board); a precise accountability matrix.
- Risk tier
- Risk classification — blocking, high, medium or low — including the reason for the classification.
- Usage
- Where the claim has been published and in which versions of a document or channel.
- State
- Current state: draft, pending approval, approved, published, expired or withdrawn.
From draft to published version
Six steps every claim passes through before it appears on a website, in a PDF or in a pitch deck.
- 01The author submits a URL, PDF, DOCX, PPTX or plain text.
- 02The system creates a snapshot and breaks the content into atomic claims.
- 03The owner confirms the entity, product, jurisdiction, audience and channel.
- 04Deterministic rules flag status words and blocking patterns; the system proposes more precise wording with a cited source.
- 05The business owner confirms factual accuracy; Compliance or Legal decides according to the risk tier.
- 06The published version is archived with a claim manifest and an audit trail.
Same fact, different impression
Two ways to express participation in a regulatory programme. One conflates statuses and creates the impression of a licence; the other is precise and defensible.
“We are approved by the regulator and operate in its sandbox.”
Problem: It may conflate two different statuses, create the impression of a licence and attribute an endorsement to the institution.
“On date D, Company X was admitted to programme Y for purpose Z. Participation in the programme is not a licence or an approval of the product.”
Advantage: It separates the fact of admission from the legal meaning of a licence; every element is verifiable.
Evidence questions
- Which entity?
- Which programme?
- Admission, participation, consultation — or a licence?
- Which date?
- Which document?
Control
The words ‘approved’, ‘regulated’ and ‘in cooperation with’ are blocked without a status object and legal approval.
What the platform does
Core capabilities of the platform under development; availability is detailed to partners.
Claim Registry
A central register of atomic claims, their variants, owners and states across the whole company.
Evidence Cards
Each claim carries a card with the primary source, its authority, jurisdiction and validity in time.
Pre-publication review
Website, PDF, pitch-deck and email content is reviewed before release under a risk-based workflow.
Approvals and four-eyes
Decisions by risk tier: self-service, compliance approval or legal four-eyes approval.
Publication Manifest
Every published version is archived with a manifest of claims, sources and approvals.
Interaction Ledger
A chronology of regulatory inquiries, meetings, participants, replies, commitments and deadlines.
Meeting confirmations
A structured record separating facts, open questions and a request to correct inaccuracies.
Evidence Pack and audit trail
A human- and machine-readable export with an index, sources, versions, timeline and audit trail.
An export anyone can read
The output is not a closed file but a shareable evidence bundle.
- A human-readable PDF accompanied by a machine-readable manifest with an index of claims, sources, versions and the timeline.
- The recipient needs no REGULOGRAPH account; a standard browser or text editor is enough.
- The export documents the available materials and their relationships; it does not determine their legal effect or conclusion.
Five working scenarios
REGULOGRAPH is not a single dashboard. It is a set of precise workflows that switch on at the moment legal risk arises.
- 01The author submits text or works directly in the CMS / Word / PowerPoint.
- 02The system breaks the text into atomic claims and flags regulated words, status shorthand, figures, performance promises and references to institutions.
- 03For each claim it retrieves the current evidence card and verifies jurisdiction, audience and validity date.
- 04Deterministic rules block prohibited wording; AI proposes more precise wording with a cited source.
- 05Depending on the risk tier, the claim goes through self-service, compliance approval or legal four-eyes approval.
- 06The published version is archived and receives a claim manifest.