Extract data from loss and damage claims
Unstract reads loss notices, damage reports and freight claims, typed, handwritten or photographed, and returns checked, structured data to your claims system.
insd sending plumber invoice + photos — Mark
ACORD 1 (2016/10)
{ "form": "ACORD 1", "policy_number": "GBM-HO-5521807", "carrier": "Granite Bay Mutual", "insured": "Patel, Anika", "date_of_loss": "10/25/2026", "kind_of_loss": "water", "estimated_amount": 18400, "police_report": false, "confidence": 0.95}
Trusted by insurance teams around the globe
Claimants report a loss any way they can
A typed ACORD notice from an agency is the tidy case. On the morning after a storm, the claims inbox looks like this.
Photographed on a phone in a flooded basement, then faxed
One loss, reported on the ACORD form, the carrier's and a freight form
Filled in by hand, the estimate crossed out and raised
Notice, photos, contractor estimate and invoices in one email
Contents inventories and damage reports in no standard layout
Someone retypes every one into the claims system before an adjuster is assigned, while the claimant waits to hear back.
Unstract takes that on — it reads loss notices, damage reports and freight claims, pulls the loss details you name, checks them against the policy, and opens the claim in your claims system.
Read, extract and route every first notice
Three products that work alone and stack: one reads the notice, one turns it into data, one runs the intake. Adopt them in whatever order suits your claims team.
Read every loss notice and damage report, with its layout kept
Capture the full text of an ACORD 1, 2 or 3, a carrier's own loss form, an adjuster's damage report or a notice of loss at delivery, whether it was typed, handwritten in a hurry or photographed on a phone, with the layout intact. The date of loss stays with its label, the kind-of-loss box keeps its tick, and an estimate total is never read as a policy number.
Hand the text to your own LLM, or make parsing the first step of an FNOL workflow.
Learn more about LLMWhispererTurn loss and damage claims into one structured record
Name the claimant, policy, loss and damage fields you want, and every notice comes back as the same JSON record, whether it was an ACORD form, a carrier's own layout, a freight claim or an adjuster's report. A blurry photo or a crossed-out estimate doesn't change the shape. A value that fails a check, such as a loss date outside the policy period, arrives flagged with the reason.
Expose it as an API to your FNOL portal, run it as an ETL pipeline from the claims inbox, or make it one step of an orchestrated claims process.
Learn more about Document StudioFNOL AI that opens the claim, not just reads it
Describe your first notice of loss intake in plain English and Flow's agents build the workflow. Notices are picked up from email, web forms and agent uploads, the claim file is sorted, each document is read, and the policy is checked as in force on the date of loss with the cause covered. Simple claims are fast-tracked, injury and complex ones go to the right adjuster, and the claim opens in your claims system, such as Guidewire ClaimCenter or Duck Creek Claims. You approve the workflow once and AI FNOL claims intake runs the same way every time.
Say once when a person takes over: coverage in question, a fraud flag, an amount above an adjuster's authority, a read that isn't certain. Only those claims wait, sent to an adjuster or the special investigations unit with the reason attached.
Learn more about FlowExtract from loss notices today. Automate FNOL when you're ready.
Start for free lets you parse and extract your own notices now. Automating first notice of loss starts with a consultation.
Every way a loss gets reported, and what follows it
Documents
- ACORD 1 Property loss notices
- ACORD 2 Automobile loss notices
- ACORD 3 Liability notices of occurrence
- Carrier claim notification forms
- Standard claim forms for loss or damage
- Material damage claim forms
- Damage assessment reports
- Physical damage inspections
- Property damage reports
- Equipment damage and loss reports
- Utility damage reports
- Notifications of loss or damage at delivery
- Freight claims and bills of lading
- Contractor estimates and repair invoices
- Contents inventories
- Police and fire department reports
Fields captured
Processes these documents feed
For everyone who handles the first report of a loss
First notices opened with the policy, loss and contact details already in, so the first call to the claimant is about the loss.
Carrier assignments, inspection notes and contractor estimates read into one file, whichever carrier sent them.
Loss notices from insureds sent on to the carrier the same day and logged in the agency's AMS, without retyping them.
Notices of loss at delivery, bills of lading and inspection reports matched into one claim well inside the filing window.
Claims opened sooner, adjusters assigned faster
Safe for claimant details, photos and police reports
A claim file holds a claimant's address and phone number, photos of their home or vehicle, and police reports that may name other people.
- Encrypted in transit and at rest.
- Claim files are never used to train any model.
- Role-based access by team and line of business, and every review or correction logged against the claim.
- Retention on your terms: claim documents are removed on the schedule you set.
- Self-hosted deployment for carriers that keep claims processing inside their own environment. Talk to us about yours.
What claims teams ask before they start
It reads the report so nobody has to retype it. LLMWhisperer turns the notice, photos of forms and estimates into layout-preserved text, and Document Studio uses LLMs to pull out the claimant, policy, loss and amounts. The OCR layer is not an LLM; it is a parser built for LLM pipelines. Flow then runs the checks and routing on rules you approve.
Yes. Send a loss notice or damage report by API, email or a watched folder and the record comes back as JSON, with every field tied to where it was read on the page. Nothing needs a template per carrier or per form.
The ACORD 1 property, ACORD 2 automobile and ACORD 3 liability notices, carriers' own claim notification forms, and the standard loss and damage claim forms used for equipment, utility and material damage. Fields are read by what they are, not where they sit, so a carrier's layout comes out in the same record as an ACORD one.
Yes. Adjuster and inspector reports are long and loosely structured, so the useful parts are pulled out by meaning: the damaged items, the cause, the inspector's estimate and the date of inspection, each checked against the notice that opened the claim.
Yes. Skewed phone photos, faxes and handwritten notices are read with their layout kept, so a ticked box stays with its label. A value that can't be read with confidence goes to an adjuster with the image, not into the claim as a guess.
Yes. The delivery receipt's exceptions, the bill of lading, the inspection report and the claimed amount are read into one claim, so a cargo claim can be filed, or answered, without assembling it by hand.
Most stop at a chatbot or a web form that collects the report. This starts from the documents that actually arrive, in whatever form, and carries the claim through to an open file in your claims system: read, checked against the policy, triaged and routed.
Yes. The policy is checked as in force on the loss date, the kind of loss against what is covered, and deductibles and limits applied. Dates that don't line up, repeat claimants and invoices above the estimate are flagged for review.
The claim stops in a review queue with the reason attached. An adjuster sees the field, where it came from and why it stopped, then approves or corrects it, and the decision is recorded on the claim. Other claims keep moving.
Yes. Describe your FNOL process in plain English and Flow's agents build the workflow: intake, sorting the claim file, reading, coverage and fraud checks, triage and opening the claim. You approve it before it runs, and it then runs identically on every notice.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Claim files are encrypted in transit and at rest, are never used to train models, and are kept only as long as you decide. Self-hosted deployment is available; details are in the Trust Center.
We build the intake in a consultation around your loss notices, your coverage checks and your claims system, and most teams run their first live claims within days. To test the extraction now, start for free and upload a loss notice.
Bring a week of first notices to the consultation
The ACORD notices, carrier forms, photos and estimates, the handwritten ones too. We run them live and show you each field, every check and why any claim stopped.