Tools for working a property claim from first notice of loss to the finished packet. ClaimFlow is the system of record — a claim starts and ends there — and the other tools connect through its API. Two also ship as standalone Windows apps.
Not a chain of seven apps — one system of record with tools attached. The claim never leaves ClaimFlow; the tools do their piece of the work against it.
The claim opens here — the notice of loss is parsed on intake, built in. Status is tracked through the file's life, and the finished packet is filed here to close. Every tool below reads and writes against ClaimFlow — the single source of true information for the claim. Runs local.
The tools that reach the internet carry only the limited, non-personal fields their job needs — the jurisdiction detail behind a tax lookup, for instance. The claim file itself stays in ClaimFlow.
Two tools ship as standalone Windows apps, linked below.
The claims management layer, with its own API. The single source of true information for the claim. Tracks status across the file and gives the rest of the suite one place to read from and write to. Notice-of-loss parsing is built in.
Takes an assignment email or PDF and extracts the claim fields — insured, loss type, date of loss, policy and claim numbers, carrier contacts. Built into ClaimFlow, and also available as an independent Windows app that runs on its own.
Download for Windows — NoticeOfLossParser.exe (9 MB)Fills carrier and state forms from the parsed claim data. One source of truth for the claim fields means the same values land on every form, without transcription errors.
Voice assistant for the truck. Captures inspection notes, next steps, and route details hands-free, and files them to the correct claim.
Imports and labels loss photos at volume, then organizes them into the structure the packet expects.
Merges reports, forms, photo sheets, and correspondence into one ordered, consistently paginated packet. Works against ClaimFlow, and also available as an independent Windows app.
Download for Windows — ClaimPDF_Stacker.exe (19 MB)Returns the jurisdiction and tax detail a settlement needs from a single lookup, replacing manual county-site searches.
A short survey emailed to the policyholder from ClaimFlow; their answers file straight back onto the claim. The email itself carries no personal information — PII stays reserved to ClaimFlow.
Captures what neither the loss notice nor the survey covers — the details gathered on site — and feeds the preliminary report and the proof of loss. Same rule as the survey: PII stays reserved to ClaimFlow.
Extends PhotoTag into contents work: tags contents items for the labeled photo report, then builds a full contents estimate — RCV, ACV, depreciation, line notes referencing the photos — without a trip through Xact Contents.
Turns RouteBook's drive and site captures into per-claim mileage and time records, ready for the fee bill. Nothing extra to track — the log is a byproduct of the day's work.
Carrier guidelines, price list notes, SOPs, and manuals live in an Obsidian vault with AnythingLLM on top, searchable and answerable in plain language. Runs locally; consulted at any stage rather than being a stage itself.
Claim files are sensitive. These rules apply to every tool in the suite.
Every demonstration runs on a synthetic claim packet — invented insured, invented address, photos with nothing identifying in frame. This includes demos requested against your own files.
ClaimFlow and the claim file live on your machine. The tools that do reach the internet — RouteBook, PhotoTag, Tax Info Lookup — carry only the limited, non-personal fields their job needs. No PII leaves the machine.
On completion of an engagement, source and assets transfer to the client. No lock-in and no licensing terms beyond that — the same as every other Hale Group engagement.
A walkthrough runs one synthetic claim through the full system, start to finish, and takes about fifteen minutes.