Extract data from accident reports
Unstract reads police crash reports and motor accident report forms, scanned, faxed or handwritten, and returns every driver, vehicle, insurer and named company as checked data in your claims system.
U2 driver to Hardin Memorial — RH
SHP CRASH REPORT · PAGE 1 OF 4
{ "report_number": "2026-0418837", "crash_date": "10/29/2026", "location": "I-65 NB Mile 92.4, Elizabethtown", "motor_carrier": "Ridgeline Freight LLC", "usdot_number": "3184402", "unit1_driver": "Okafor, Daniel J", "unit1_policy": "CTM-AL-7730415", "unit2_driver": "Mercer, Lauren A", "unit2_insurer": "Blue Hollow Casualty", "confidence": 0.94}
Trusted by insurance teams around the globe
Every police department files its own crash report
A crash report requested from the records unit is the easy one. The rest reach the claims desk as faxes, photos and forms filled in at the roadside.
Faxed from a county records office, four pages a little crooked
One crash, on the police report, the motor claim form and the fleet's own incident report
Filled in at the roadside, the plate number struck out and rewritten
Crash report, photos, claim form and condition report in one email
Passenger supplements and condition reports in no fixed layout
An adjuster reads four pages of codes to find which driver, which insurer and which company owned the truck, and liability waits until someone does.
Unstract reads each crash report and motor claim form, pulls out every unit, person and company on it, checks them against the policy, and opens the claim in your claims system.
From a faxed crash report to a claim with every party named
Three products that work alone or together: one reads the report, one turns it into data, one runs the claim from there. Start with whichever your team needs first.
Read every accident report, unit boxes and narrative included
Capture the text of a state police crash report, a motor accident report form or a fleet's vehicle incident report with each box still beside its label. Unit 1 stays apart from Unit 2, the injury code stays with the person it describes, and the officer's handwritten narrative comes out as text, not as a picture.
The same reading covers motor insurance claim OCR for the claim form that arrives with the report, so both land in one claim file.
Learn more about LLMWhispererTurn accident reports into one record per vehicle, driver and company
Name the fields you need once, and every accident report comes back in the same JSON shape, whichever state drew the form. Each unit becomes its own record with driver, owner, VIN, plate, insurer and policy, and the motor carrier and USDOT number sit beside the truck they belong to. A policy number that doesn't match your insured, or a crash date outside the policy term, arrives flagged with the reason.
Call it as an API from your FNOL portal, run it as an ETL pipeline on the records inbox, or make it one step in a full claims run.
Learn more about Document StudioRun the motor claim from the crash report onward
Describe your accident report intake in plain English and Flow's agents build the workflow. Reports and claim forms are collected from the records inbox, web forms and agent uploads, each page is sorted, and every unit and person is read. Your insured's policy is checked for the crash date and the vehicle on the report, and the claim opens in your claims system, such as Guidewire ClaimCenter or Duck Creek Claims, with the other driver's insurer ready for subrogation. You approve the workflow once and it runs the same way on every report.
Decide in advance where a person steps in: an injury on the report, a VIN that isn't on the policy, an amount above an adjuster's authority, a smudged box. Only those reports pause, routed to an adjuster or the special investigations unit with the reason written on them.
Learn more about FlowExtract from crash reports today. Automate motor claims when you're ready.
Start for free to parse and extract your own accident reports now. Automating the claim around them starts with a consultation.
Crash reports and the motor claim paperwork around them
Documents
- State police crash reports
- City and county police accident reports
- Motor vehicle accident reports filed by drivers
- Motor accident report forms
- Motor insurance claim forms
- ACORD 2 Automobile loss notices
- Vehicle condition reports
- Vehicle incident reports
- Fleet and driver incident reports
- Passenger and witness supplements
- Damage photos and repair estimates
- Towing and storage invoices
Fields captured
For everyone who has to work out who was in the crash
Both drivers, both insurers and the injury codes already on the claim when the adjuster first opens it, so liability and subrogation start on day one.
Crash reports from any state read into the same fields, so a desk adjuster handling five carriers' files isn't learning five layouts.
Every crash involving a company vehicle logged with the driver, unit, citation and USDOT number, ready for the accident register and the next safety review.
The other driver, their insurer, the employer or motor carrier and every injured passenger pulled from the report at intake, before the demand letter is drafted.
Motor claims opened with every party already named
Built for reports that name strangers
One crash report carries the home addresses, birth dates and driver's license numbers of people who never bought your policy, the VINs and plates of their cars, and an officer's account of who was hurt and how badly. That is enough to steal an identity or build a fake injury claim.
- Encrypted in transit and at rest.
- Crash reports are never used to train any model.
- Role-based access, so injury details reach only the adjusters handling bodily injury, and every correction is logged against the claim.
- Retention on your terms: reports and the data read from them are deleted on the schedule you set.
- Self-hosted deployment for insurers and law firms that keep claim and case files inside their own network.
What claims and safety teams ask about crash reports
Unstract does it in three layers. LLMWhisperer reads the report as text with its boxes and codes kept in place, Document Studio uses LLMs to turn that text into named fields, and Flow decides what happens to the claim next. Code tables differ by state, so a "4" in a severity box is returned as the injury it stands for on that state's form.
Crash report data extraction in Document Studio returns one record per unit, with the driver, owner, VIN, plate and insurer inside it, and a list of every passenger and injured person tied to the unit they rode in. A three-car pile-up comes back as three unit records, not one long block of text.
Most state forms have a commercial vehicle section for trucks and buses. The motor carrier name, its address and the USDOT number are read from that box and attached to the unit they describe, so Ridgeline Freight LLC lands on Unit 1 and not on the car it hit. The USDOT number is the reliable key for matching the carrier to its insurer.
Yes. On a car or van crash the company usually appears as the registered owner, a lessor, or an employer named in the narrative ("driving for Northfield Plumbing"). Each of those is read and labelled by role, owner, lessor or employer, so you can tell a rental company apart from the business the driver was working for.
Police crash reports from state highway patrols, city and county departments, such as the Texas CR-3 and the New York MV-104, plus drivers' own motor vehicle accident reports and insurers' motor accident report forms. Fields are read by what they mean, so a state it hasn't seen before still comes back in your schema.
Yes. Handwriting is read alongside the typed boxes, and the narrative comes back as text you can search. The page location of every value stays attached, so an adjuster can see exactly which line a field came from.
Yes. The claimant's motor claim form, the vehicle condition report from a rental or fleet return, and a company's vehicle incident report are read into the same claim as the police report, so the dates, VINs and damage descriptions can be compared across all of them.
Yes. Your insured's policy is checked as in force on the crash date, the VIN on the report against the vehicles on the policy, and the claimant against earlier claims. A mismatch stops the claim for an adjuster with both values side by side.
Many records units mask license numbers and VINs before release. A masked value comes back exactly as printed, never filled in by guess, and a box that can't be read with confidence goes to an adjuster with the page image.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Reports are encrypted in transit and at rest, never used to train models, and kept only as long as you decide. A self-hosted option is available, and the Trust Center has the details.
We set up the intake in a consultation around your state mix, your coverage checks and your claims system, and most teams run their first live reports within days. To test the extraction now, start for free and upload one crash report.
Bring a month of crash reports to the consultation
Reports from several states, the faxed copies, the roadside forms and a truck crash or two. We run them live and show every unit, every named company and why any report stopped.