Flood claim review software

Flood trainers teach adjusters how to assess a loss, support an estimate, and explain a claim. During a storm deployment, they can also spend much of the day checking trainee files for recurring omissions and inconsistencies.

King Tide grew out of Joseph Koenig's own review process. A flood adjuster, trainer, and Daedalus partner, he knew the small issues that repeatedly sent files back for correction. We used his experience to build a first review that an adjuster could run before sending a claim to the trainer.

The tool takes a claim-package PDF, applies its configured checks, and returns an annotated copy with a summary of findings. The person reviewing the claim can go straight to the flagged page and decide what needs to change.

Overview

Input

Claim-package PDF

Output

Annotated findings

Final judgment

The adjuster

Manual review

A claim package contains information spread across estimates, narratives, summaries, and photographs. A missing caption or inconsistent entry can require another exchange between trainee and trainer before the file moves on.

The trainer handled those checks alongside their own claims. We moved a defined set of checks earlier in the process, so trainees could inspect the findings and correct straightforward issues before asking for expert review.

Audit checks

We built checks for the recurring issues Joseph identified. The engine examines the PDF for supported issues such as missing information, inconsistent summaries, depreciation entries, labor minimums, and baseboard quantities that may need a closer look.

Each finding has a category, a page reference, and an annotation in the returned document. A summary cover page lists the findings so the adjuster can find each issue in the claim package.

The checks have a defined scope. A file with no detected findings still needs professional review. Coverage interpretation, damage assessment, estimating decisions, and approval remain with the people responsible for the claim.

Workflow

1. 01 Upload

   The adjuster submits the claim-package PDF through the web interface.

2. 02 Checks

   The engine applies its supported detectors and groups the findings by category.

3. 03 Findings

   The adjuster receives a summary and an annotated PDF with the relevant pages marked.

4. 04 Expert review

   Straightforward corrections can be made before the trainer reviews the estimate, narrative, and decisions that need their expertise.

Team access

We built a web application around the audit engine, with individual accounts, trainee seats, audit history, and a trainer's team view. This makes the first review available to the people preparing the files, rather than requiring the trainer to run a script for everyone.

The application also handles uploads, annotated downloads, account access, and subscriptions. These features support team use; wider industry adoption has not yet been established.

Results

King Tide makes a defined set of checks available for the team to run before trainer review. The aim is to reduce avoidable correction rounds and leave trainers more time for work that needs their judgment when claim volume surges.

The same configured checks are available to each adjuster, and the findings travel with the document. A trainer can review the flagged issue in context and use it to explain a correction. Any time saved will depend on the files and the team's use of the tool during a deployment.

Scope

We began with a limited set of repeatable checks drawn from Joseph's review process. Linking each finding to the relevant page lets the reviewer inspect it and decide whether a correction is needed. The trainer still reviews the claim and the decisions behind it.