Adjuster tools · Reference

The adjuster tool suite

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.

Maintained by Daniel Hale Updated July 2026 daniel@halegroup.ai
The system

ClaimFlow in the middle

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.

Start and end · System of record

ClaimFlow

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.

Form Wizard
Fills carrier and state forms from the claim fields
RUNS LOCAL
RouteBook
Scheduling assistant — distance between claims on a visual map; drives log mileage and time
INTERNET · NO PII
PhotoTag
Labels and organizes the loss photos
INTERNET · NO PII
PDF Stacker
Assembles the ordered packet for the file
RUNS LOCAL
Tax Info Lookup
Jurisdiction and tax detail at settlement
INTERNET · NO PII
Reference Layer
AnythingLLM + Obsidian — guidelines and SOPs, answerable in plain language
RUNS LOCAL
Field Survey
Emailed to the policyholder; answers file back to the claim
IN DEVELOPMENT
Field App
All the information needed for narrative, preliminary, and proof of loss reporting
IN DEVELOPMENT
Contents Estimating
Photo tagging for contents with a full estimating suite — RCV, ACV, price verification
IN DEVELOPMENT
Activity Log
Emails, calls, tasks, milestones — a complete activity record and itemized time worksheet
IN DEVELOPMENT

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.

INTERACTIVE DEMO · SYNTHETIC CLAIM · RUNS IN YOUR BROWSERWatch a claim file build itself — loss notice in, finished documents out
Tools

Notes, demos, downloads

Several tools can be tried right now — the demos run on synthetic data, entirely in your browser. Standalone Windows downloads are linked where available.

Notice of Loss Parser

In productionIntake

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) Unsigned app — Windows will ask you to confirm before running.

Form Wizard

In productionDocumentation

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.

RouteBook

In productionField capture

Scheduling assistant for the field. Maps the distance between claims, builds the day’s route, and shows it all on a visual map — stops ordered, miles and drive time totaled. In development: drives becoming the per-claim mileage and time record for the fee bill.

Visual demo — the RouteBook interface

Tax Info Lookup

In productionSettlement

Returns the jurisdiction and tax detail a settlement needs from a single lookup, replacing manual county-site searches.

In development

Field Survey

In developmentClaimFlow · Policyholder

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.

Field App

In developmentClaimFlow · On site

Captures what neither the loss notice nor the survey covers — all the information needed for narrative, preliminary, and proof of loss reporting, gathered on site. Same rule as the survey: PII stays reserved to ClaimFlow.

Activity Log

In developmentClaimFlow · Activity

Every touch on the claim — emails, phone calls, completed tasks, milestones — recorded as it happens. Together they build a complete activity log for the file, or an itemized time worksheet when billing needs one.

Reference layer — AnythingLLM + Obsidian

In productionReference

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.

Data handling

Operating rules

Claim files are sensitive. These rules apply to every tool in the suite.

RULE 01

Demos are synthetic only

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.

RULE 02

The claim file stays local

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.

RULE 03

You own the result

When the work is done, the source code and every asset transfer to you. No subscription keeping it alive, no license to renew, no dependency on me — the tools are yours to run, change, or hand to whoever comes next.

Contact

Questions or a walkthrough

A walkthrough runs one synthetic claim through the full system, start to finish, and takes about fifteen minutes.

daniel@halegroup.ai