Against the documents in the file
Attach the schedule, the wording, endorsements and reports, and each statement in the summary is checked against them.
Coming soon
Coming soon · For insurers and brokers
The endorsement that replaced the schedule.
A claim summary quotes the deductible from the schedule, the waiting period from the wording and the amount from the adjuster’s estimate. Each was overtaken by another document in the same file. Velydian for insurance is built to read a claim file in the order its documents prevail.
- First run with you. Done together with your team, free of charge.
- Any document today. The general check already works on any text.
- Swiss and private. Data residency in Switzerland, processing in Switzerland and the EU, GDPR compliant.
VerdictIllustration
CLAIM IN YOUR CLAIM FILENeeds Revision
“The deductible is CHF 5,000, as set out in the policy schedule.”
What the source says
“With effect from 1 January, the deductible is increased to CHF 10,000.”
Endorsement 2, in the same claim file
The schedule says CHF 5,000, but a later endorsement raised it to CHF 10,000. The endorsement prevails.
The stakes
What an unsupported claim costs.
$308.6bn
Estimated yearly cost of insurance fraud in the United States, across all lines.
Coalition Against Insurance Fraud (2022), The Impact of Insurance Fraud on the U.S. Economy~10%
Share of total claims spending in Europe estimated to go to fraud, detected and undetected.
Insurance Europe (2024), Breaking boundaries£90.7M
FCA fine over home-insurance renewal letters whose “competitive price” wording the insurer had not checked. Nearly 9 million letters were affected.
UK Financial Conduct Authority, Lloyds Bank General Insurance (Jul 2021)What it catches
Six things that go wrong in claim files.
Each one with the claim, the passage Velydian reads, and the verdict. Examples for illustration.
A schedule overtaken by an endorsement
“The deductible is CHF 5,000.”
Endorsement 2: “the deductible is increased to CHF 10,000”.Needs Revision
The later document prevails.
A waiting period from the wrong document
“Cover starts after 30 days.”
Policy wording: “a waiting period of 90 days applies”.Not Supported
The wording sets 90 days.
An amount from a superseded estimate
“The accepted loss is CHF 184,000.”
Final adjuster report: “accepted loss CHF 162,500”.Needs Revision
An earlier estimate, quoted after the final report.
An exclusion left out
“Water damage is covered.”
Wording: “…except damage from rising groundwater”.Needs Revision
The exclusion may apply to this claim.
A notification date that does not match
“The loss was notified within 48 hours.”
Notification form dated five days after the loss.Not Supported
The file contradicts the summary.
A broker note with nothing behind it
“The broker confirmed cover by phone.”
No document in the file records this.Unverifiable
Flagged so the handler can find the record or remove the line.
Not another fact checker
Not just right or wrong. Supported or not.
Velydian checks the amounts and dates. It also weighs what a summary does with them: which document it relies on and how strongly it states the cover. A limit can be right and the summary can still mislead.
One claim, three levels · illustration
“The policy covers the loss in full, up to CHF 500,000.”Needs RevisionSource: the documents in the claim file. Example for illustration.
- Level 1
Facts
Limits, deductibles, dates and amounts, checked against the documents in the file.
Does the schedule say 500,000 or 50,000?
Velydian findsSupportedThe CHF 500,000 limit is in the schedule.A citation check stops here: true. - Level 2
Interpretation
Whether the statement still holds once every document in the file is read.
Does another document in the file change it?
Velydian findsStretchedAn endorsement in the same file lowers the limit for flood damage to CHF 200,000. - Level 3
Judgement
Whether the statement is as strong as its evidence, and what was left out.
Is this the whole picture the claims manager should see?
Velydian findsOverstatedThe adjuster’s report identifies rising groundwater as the cause, which the wording excludes. The summary leaves it out.Verdict: Needs Revision. The limit is in the schedule; the summary ignores the documents that change it.
How it works
Attach the claim file. Every statement comes back with its evidence.
Attach the documents and Velydian checks each statement in the summary in one of three ways.
Against public texts
When a summary cites a law, a regulation or a published wording, Velydian opens it and checks the statement against it.
Statements nothing backs
Where no document in the file settles a statement, it is marked Unverifiable, so the handler can find the record or remove the line.
Three layers of checking
Surface tools check that a source exists. Velydian reads it.
Layer 1
Distortions and inaccuracies
Amounts that drift, dates that do not match, an earlier document read as current.
An estimate quoted after the final adjuster’s report.
Layer 2
Bias and fabrication
Cover the wording does not give, a document that says something else, and what was left out.
An exclusion in the wording left out of a coverage statement.
Layer 3
Stronger sources
When a statement rests on a note, Velydian looks for the document that settles it.
A broker note is flagged, with the policy wording offered instead.
One verdict per claim
Four verdicts, each with its evidence.
Supported
The documents checked back the statement as written.
Needs Revision
Close, but an amount, a date or a limit does not match the document.
Not Supported
The documents do not back the statement, or say something different.
Unverifiable
No document in the file settles it, for example a phone call nobody recorded.
Open any verdict to see the passage and the reasoning behind it. Correct a line or swap a source and it is checked again. Velydian weighs the evidence; the handler decides.
- Attach the filePDF, DOCX, TXT, MD or pasted text.
- Every statement is checkedAgainst the documents in the file or the texts it cites.
- Review and correctFix a statement or add a document; it re-checks.
- Take the resultAnnotated summary, file audit trail, executive summary, CSV/JSON exports.
How we test it
Test it with us on your own file.
Our published test results so far are on company reports: see Velydian for Finance. For every other kind of document, the best test is one of your own.
Every verdict, open to inspectionSource + reasonEach verdict shows the passage it rests on and why, so you can check Velydian itself.In every result
When the sources cannot settle itUnverifiableThe claim is marked Unverifiable, with the reason, for a person to check.One of four verdicts
Your own testFirst run with youWe run your first claim file with you, and you judge the result before going further.Early access
Review the verdict and the reasoning yourself: every one shows its evidence.
Today and with Velydian
From hours of checking to minutes.
Manual file review
Hours per file, risk in the settlement
- Each document read and cross-referenced by hand
- A later endorsement is easy to miss
- Superseded figures survive into the summary
- No record of which document each statement relied on
Velydian on claim files
Each statement tied to its document
- A full summary checked in minutes
- Every statement checked against the documents you attach
- Statements the file contradicts flagged
- The quoted passage behind every verdict, kept for the file
What it checks
The documents your team signs.
- Claim files and summaries
- Policy schedules and wordings
- Endorsements
- Adjuster and loss reports
- Broker notes and submissions
- Coverage opinions
- Underwriting memos
- Reinsurance submissions
Who uses it
Across the team.
- Claims handlersSee which document backs each statement in a summary.
- Claims managersReview files with the evidence laid out.
- UnderwritersCheck submissions against the documents behind them.
- BrokersCheck a coverage summary before the client relies on it.
What you get back
A record you can keep.
- The annotated summaryEvery statement marked with its verdict, in place.
- A file audit trailFor each statement, the document and the passage relied on.
- Missing recordsWhere nothing in the file backs a statement, it is flagged so the handler can find the record.
- ExportsExecutive summary, CSV and JSON.
Early access
We run your first claim file with you.
The insurance layer is built and not yet switched on. Early-access firms send one claim file; we run it with them and they decide whether to go further. Nothing is charged for that first run.
The general engine works on any document today: every claim checked against the sources it cites, sources it finds, or your own files.
Questions
Before your first claim file.
What works today?
The general engine checks any document against its sources or your own files today, including a claim summary against the documents you attach. The insurance layer, which reads a claim file in the order its documents prevail, is built and not yet switched on.
How do we get early access?
Request early access below. We run your first claim file with you, and you decide whether to go further.
Does it decide the claim?
No. It shows which document each statement relies on and whether it holds. The decision stays with the handler.
Where do the sources come from?
Three places. The sources your document cites; sources Velydian finds on official websites, research databases and the wider web for claims without a citation; or your own files, if you attach them.
What happens to my document?
When you run a check, your document’s text is sent over an encrypted connection to our servers and AI services in Switzerland and the EU. To find evidence, short search queries built from your claims are sent to web and scholarly search services. Your document’s content and results are deleted automatically about 24 hours after your check; source links and summary data are kept.
Which languages does it check?
English is measured and in daily use. German and French are in validation.
Can I rely on Velydian as my only check?
Velydian supports human review. It shows the evidence behind every verdict so you can decide. In high-stakes work, expert judgement stays essential.
A Swiss company
Data in Switzerland. Processing in Switzerland and the EU.
- Data residency in Switzerland, processing in Switzerland and the EUGDPR and Swiss data protection terms are covered by our Data Processing Agreement.
- A Swiss companyVelydian is built by MindtheGap Sàrl in Geneva.
Be among the first to check a claim file this way.
Also for: AI answersMediaFinanceLegalResearchComplianceConsultingInvestmentHRSustainability