Automate policy checking
Unstract reads each issued policy as it arrives from the carrier, compares it with the binder, the quote and the expiring term, and records the result in your AMS, rater or policy system.
Trusted by insurance teams around the globe
The policy arrives weeks late, and nobody has time to read it
The binder told the insured what they bought. The issued policy, often a hundred pages or more, decides what a claim will pay, and an account manager is expected to read it against the binder between new business and service calls. Insurance policy review slips to the bottom of the pile.
A renewal checked page by page, weeks after it took effect
Declarations, forms and endorsements in one 142-page file
A deductible bound at one figure and issued at another
ISO forms, a carrier's own forms and manuscript wording
The quote and binder in autumn, the policy after the term began
An unread policy is an errors and omissions claim waiting for a loss to reveal it.
Unstract reads every issued policy, compares it line by line with what was quoted and bound, and puts only the differences in front of an account manager, with the policy page and the binder side by side.
From the carrier's issued policy to a checked account, without the keying
Five steps, run on their own for every policy. Parsing by LLMWhisperer, extraction by Document Studio, the whole run by Flow.
Pick up the issued policy wherever it lands
Carriers send issued policies through their portals, by email or by download, and the quote, the binder and the application already sit in the account file. At renewal the expiring policy joins them. Each document is picked up where it arrives and tied to the policy it belongs to, one record per policy.
Nobody has to notice that a policy came in. The check starts when the carrier sends it.
Read every page of the policy, then pull the terms that matter
LLMWhisperer reads the declarations, the forms schedule, the endorsements and the location schedules with the layout kept, so a limit stays tied to the coverage line it sits on. Document Studio then extracts the terms you defined from each document: named insureds, policy period, forms and editions, endorsements, limits, deductibles, premium, locations and scheduled items.
The same definitions run on ISO forms, a carrier's own forms and manuscript wording, without a template per carrier.
Check the policy against the binder before anyone files it
Every term on the issued policy is compared with the binder and the quote, and at renewal with the expiring policy. Named insureds, limits, deductibles, forms and editions, endorsements and premium are matched line by line. Each difference is listed with both values and the page each one came from.
Set the tolerance once (a premium within a few dollars, say) and only real differences hold the policy.
Put only the differences in front of an account manager
A policy that matches is marked checked without anyone opening it. A policy with a difference in named insured, limits, forms, endorsements or premium beyond tolerance goes to the account manager or CSR on the account. They see the difference, the policy page and the binder together, and decide whether to accept it or ask the carrier to correct it.
Account managers spend their time on the one deductible that changed, not the 140 pages that didn't.
Record the check where your account managers already work
The checked status and an activity note land on the account in your AMS, rater or policy system, such as Applied Epic or Vertafore AMS360. A discrepancy goes back to the carrier as a correction request, with the policy page and the binder attached as evidence. Each decision is recorded against the policy.
The E&O file builds itself, and the carrier gets a request it can act on without a phone call.
See it check a month of your own renewals.
Bring the issued policies and binders from one carrier. We run them live and show every term compared and every difference held.
Everything a policy is checked against
Documents
- Issued policies and declarations pages
- Binders
- Quotes and proposals
- ACORD forms
- Expiring policies at renewal
- Endorsements and policy change requests
- Certificates of insurance
- Schedules of locations and vehicles
- Statements of values
- Premium audit statements
- Cancellation and nonrenewal notices
- Coverage requests from the account file
Fields captured
Our agents are extroverts.
Cloud storage like S3, Google Drive, Dropbox and Box. Databases and warehouses like Snowflake, BigQuery, Postgres and SQL Server. Accounting, ERP and CRM systems like QuickBooks, Xero, SAP, NetSuite, Salesforce and HubSpot. Project trackers like Jira, Asana, ClickUp and Linear. And anything with an API.
Live on one carrier's renewals first
Nothing for your IT team to build, and no change to how policies reach you. The check is set up on your own binders and policies and proven on one carrier before it covers the book.
Book a consultation
We go through a month of issued policies with you: which carriers send them, how they arrive, and what your account managers compare today.
Built on your binders and policies
The terms to extract, the tolerances, the comparison rules and the connection to your agency system are set up on your carriers' real policies, not samples.
Start with one carrier's renewals
One carrier's renewals run live within days. When the results hold, the other carriers and new business follow, with the same tolerances.
Built for the people who answer for what the policy says
Every renewal and new policy checked against the binder before it goes to the insured, so an unread policy stops being an E&O exposure.
Policies issued under your binding authority checked against what was bound for each retail agent, before the documents leave your desk.
Issued policies compared with the quoted and bound terms before mailing, so a form or limit keyed wrong at issuance is caught in-house.
The policy the company paid for checked against what it was promised, with every difference listed before the renewal is signed off.
Policies checked in minutes, discrepancies caught before a claim finds them
Keep your book of business to yourself
A policy file carries the insured's FEIN, payroll, revenue, property values, driver lists and premium: everything a competing agency needs to quote the account away from you at the next renewal.
- Encrypted in transit and at rest.
- Policies and binders are never used to train models.
- Access by role, carrier and account, with every accepted difference and correction request recorded against the policy.
- Retention you set: processed policy files are deleted on the schedule you choose.
- Self-hosted deployment for carriers and MGAs whose controls keep policy data inside their own environment.
Questions account managers raise about policy checking
Insurance policy checking is comparing the policy a carrier issues with what was quoted and bound: named insureds, policy period, limits, deductibles, forms, endorsements and premium. Agencies do it to catch carrier errors before a claim does, and because an unchecked policy is a common source of errors and omissions claims.
Read the policy with its layout kept, then extract the terms you need into a fixed set of fields. LLMWhisperer reads declarations, forms schedules and endorsements as text with their tables intact, and Document Studio pulls named insureds, limits, deductibles, forms and premium into the same fields for every carrier.
Look for a tool that reads the whole policy, not only the declarations page, handles each carrier's layout without a template, and shows where on the page every value came from. Unstract does that and then goes a step further: it compares the policy with the binder and the quote, so digitized policies arrive already checked.
Yes. LLMWhisperer reads declarations pages, location and vehicle schedules, and statements of values with the columns kept, including scanned and mailed copies. Every value can be traced back to its spot on the page, which is what an account manager needs when the carrier asks where a difference came from.
Outsourced insurance policy checking services return results in days and charge per policy, so many agencies check only their larger accounts. Policy checking automation runs on every policy the moment it arrives, at the same cost for a small account as a large one, and your own account managers decide on each difference.
No. It does the reading and the comparing. The account manager decides what a difference means: whether a changed deductible was agreed with the insured or is a carrier error. Policies that match need no one; policies that differ stop for the person who knows the account.
The binder, the quote and the application, and at renewal the expiring policy. Named insureds, policy period, every limit and deductible, forms and their editions, endorsements, premium, locations and scheduled items are compared line by line, and any difference beyond the tolerance you set is listed with both values.
The policy stops in a review screen with the term, the value on the policy, the value on the binder and both pages side by side. The account manager accepts the difference or sends a correction request to the carrier with the evidence attached, and the decision is recorded against the policy.
Into your AMS, rater or policy system, such as Applied Epic or Vertafore AMS360: a checked status and an activity note on the account. Correction requests go to the carrier as part of the same run, so nothing is printed, marked up and keyed again.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Policy files are encrypted in transit and at rest, never used to train models, and kept only as long as you choose. Self-hosted deployment keeps policy data inside your own environment; see the Trust Center.
We build it with you in a consultation, around your own binders, policies, tolerances and agency system. Most teams run one carrier's renewals live within days, then add the rest of the book once the results hold.
Bring last month's renewals and their binders
The issued policies from one carrier, with the binders and expiring terms beside them. You watch each one get compared, and every held policy shows the exact line that differs.