The policy and every endorsement
- Pulled out
- Coverages, limits, deductibles, exclusions, endorsement wording and the policy period.
- Checked against
- The date of loss, and each estimate line, coverage by coverage.
ClaimVision digitizes and extracts the data from every document in a US property claim file, then reads the file as a whole, so your adjuster starts with findings instead of fields.
That means the adjuster and inspection reports, the estimate, the policy and its endorsements, proof of loss, correspondence and photos, scanned and handwritten pages included. The AI recommends; a licensed adjuster or TPA handler agrees with or changes every recommendation.

01A worked example
This is the fictitious Sykes example claim from our walkthrough: a wind and hail loss in Oklahoma. The figures are invented demo data. What happens to them is what ClaimVision does on a real file.
An illustration, not a product screen. A page from the Sykes example claim, with what is read from it numbered.
Peril observed: wind and hail
Roof covering: asphalt shingle, installed 2009
Granule loss on N + W slopes, see photos 14-22
Location: Oklahoma
Then the fields meet the rest of the file:
An extraction tool would stop at the four fields. The finding comes from reading the inspection report, the policy and the estimate together, and it arrives with the clause and the dollar impact attached. The adjuster reads it, agrees or changes it, and decides.
02Document by document
Every page of a US property claim file becomes structured data, whether it arrived as a digital PDF, a scan or a page written by hand. Nobody rekeys a thing.
03The money
Financial figures carry a quality label, or are withheld until they can be confirmed. A number that two documents agree on reads differently from one that appears once in a scan, and the adjuster can see which is which.
Every recommendation also shows how confident the system was, and the adjuster's note when they disagree is kept with the claim.
See the audit trail

04Beyond the fields
A property claim is decided in the connections between documents. Because ClaimVision reads the documents and the photos together, the same reading also gives the adjuster:
If all you need is clean data at intake, an extraction-only tool may be enough. Our guide to AI claims tools by job names several.
05Getting the data out
{ }Structured JSONFor your systems and your data team.#MarkdownEasy for a person to read, and easy to drop into notes, reports or other tools.APIAPI accessSo your own systems can request the data.↓Data exportsTo load into your claims system or data warehouse.How the data reaches your systems is agreed with your team.
06How it fits
ClaimVision recommends; it never decides, pays or denies. A licensed adjuster or TPA handler agrees with or changes every recommendation, and every source and note stays on the record.
See the audit trailNo need to replace Guidewire ClaimCenter, Duck Creek, Sapiens or an in-house system. ClaimVision reads the documents the claim file already holds.
See how it fits your stackClaimVision runs entirely on Microsoft Azure, using Azure's built-in security, and client data stays in the client's region: US data stays in the US.
Read the security detailsWhat we can show todayA full day's reconciliation work on a real large-loss claim, done exactly, in under a minute.
FAQ
Two kinds. General document-extraction tools pull fields such as policy numbers, dates and totals out of PDFs and scans, across many industries. Property claims tools such as ClaimVision digitize the same documents, including scanned and handwritten pages, and then read the whole file in context, so the adjuster gets a summary, flagged issues and a recommendation rather than a spreadsheet. A licensed adjuster or TPA handler agrees with or changes every recommendation.
The whole claim file: adjuster and inspection reports, estimates, the policy and every endorsement, proof of loss, correspondence, and photos with their captions. They are read together, so a line in the estimate can be checked against the policy and the photos.
Yes. ClaimVision reads scanned documents as well as digital PDFs, and it reads handwriting. A scanned proof of loss or a handwritten note in a field report is read with the rest of the file, not set aside for someone to type up.
In the format your team needs. ClaimVision exports structured JSON and Markdown, offers API access, and provides data exports you can load into your claims system or data warehouse. How the data reaches your systems is agreed with your team.
Extraction turns pages into fields. Claims intelligence uses those fields and the full documents to answer the questions a claim is decided on: do the photos match the report, is there subrogation or salvage potential, what does the policy say about this loss. ClaimVision does both, and the decision stays with the adjuster. More on AI claims intelligence.
Yes. ClaimVision looks at every photo in the file, reads its caption and label, and checks whether the adjuster's report matches what the photos show. Photos are grouped by the report they came from, so inspection photos and loss photos can be compared side by side. Anything that does not line up is flagged for a person.
No. You do not need to replace Guidewire ClaimCenter, Duck Creek, Sapiens or a system built in-house. ClaimVision reads the documents the claim file already holds and hands back findings. The system of record stays the system of record.