The review view
A real scan of our own test policy (Meridian Mutual). Illustration, not a claim.
We turn a US declarations page into structured rows: every coverage, limit, deductible and premium, each one with the line and page it came from — so your reviewer verifies in seconds instead of re-reading the PDF.
You keep control. The machine drafts, you approve — and the approval is recorded. Nothing is exported before you sign off. (Extraction runs on an external AI service — see Privacy.)
A PDF or a photo of the declarations page. Text layer or scanned — both go through.
Coverages, limits, deductibles, premiums — each value with its page and line, plus a traffic-light that flags what to look at first.
Review the flagged rows, fix if needed, confirm. Your name and timestamp are recorded before the export.
If a coverage limit is copied wrong, it lands on your desk, not on the machine's. That is the point of the review step.
One row per coverage, limit and deductible side by side — ready to paste into your system, not a paragraph to re-parse.
Limits, deductibles, premiums and policy identifiers link to their page and line. If a value can't be traced back, it says so — in red, not in the fine print. No silent guesses.
Records who approved what and when, before anything is exported. It's a record of the sign-off — a proof, not a shield.
Green = mechanically clean, not proofed. Amber = worth a look. Red = a rule was violated or a required field is missing. You decide; the machine flags.
One product, one price — for independent agents and small agencies.