← All articles Use case

Use case: commercial insurance submissions, from broker email to underwriter decision

How a made-up specialty insurer combines Insight Extract and Insight UW: broker emails and attachments become validated data, each submission is assessed against guidelines and appetite, and the underwriter decides with the evidence in front of them.

Example · a made-up specialty insurer

Cobalt Ridge Specialty and the submission queue

Cobalt Ridge Specialty (made up) writes commercial property and casualty through brokers. Submissions arrive as emails with a mix of ACORD forms, statements of values, loss runs and free-text notes. Underwriters spend much of their day re-keying data and hunting for the facts that decide whether a risk is in appetite. This is how the Insight products fit that process. The company and its numbers are fictional.

The problem in one sentence

The underwriting decision needs a few dozen facts, and those facts are spread across five documents in four formats that arrive by email.

1. From email to validated data: Insight Extract

Insight Extract runs agentic pipelines rather than single-step OCR: classify each document, extract it to a schema, run business rules, cross-check against systems of record, and escalate when something doesn't fit. Extraction is layout-aware across structured forms, semi-structured loss runs and free-text emails, with a confidence score for every field. Its out-of-the-box pipelines include submission intake, claims first notice of loss, renewal data refresh and bordereaux processing.

Whether a submission goes straight through or to a person is configured per line of business, per document type and per confidence threshold. Reviewers correct fields and classifications with a reason, and accumulated corrections are turned into suggested changes to prompts, rules and class descriptions, for a reviewer to approve.

2. Assessment: Insight UW

Insight UW reads each submission, checks it against the carrier's guidelines, appetite and existing book, and gives the underwriter a recommendation with the signals behind it, before they open the file. How much it does on its own is a setting, line by line; humans hold the authority, and the underwriter can override every recommendation. It covers the underwriting workflow from submission and triage through research, rating, quote and bind, with integrations to the policy administration system and enrichment sources.

3. The evidence trail

Each step is recorded: which agent version extracted which field from which page, what UW recommended and why, and what the underwriter decided. For carriers that also run Insight Lense, agent runs and authority decisions sit in the same kind of thread as everywhere else in the programme.

What changes for the team

RoleBeforeWith Extract + UW
Underwriting assistantRe-keys every formReviews only low-confidence fields
UnderwriterHunts for appetite signalsStarts from a recommendation with cited signals
Underwriting managerSamples files for consistencySees overrides and their reasons
ComplianceReconstructs decisions after the factReads them from the audit trail

How Cobalt Ridge starts

  1. One line of business (commercial property) and one broker channel.
  2. Extract on submission intake, with a high confidence threshold so most fields get reviewed at first.
  3. UW recommendations shown to underwriters, with no automatic actions.
  4. Lower the threshold and widen the scope as review data shows where extraction is reliable.

Regulation and model risk. Use of AI in underwriting is subject to insurance regulation and model-risk expectations that vary by jurisdiction. This example is general information; confirm requirements with your compliance and legal teams.

Questions to ask in the first working session

  • Which lines and document types? Extraction agents are built per line of business; start with the one with the most volume.
  • Where is the truth? Which system of record each extracted field should be cross-checked against.
  • What are the guidelines? Appetite and referral rules written down clearly enough to check a submission against.
  • Who reviews exceptions? And how quickly, so low-confidence submissions don't become a new queue.
  • What must the audit show? For underwriting, model-risk and compliance sign-off.

The UW site suggests seeing it run against a real broker email, a real submission and your own lines and policy system; that's also the fastest way to find which of these questions need more work.

Related: running AI inside your environment.

See the right Insight products in your environment

Tell us what you're trying to build, and we'll walk you through the products that fit, with your data, where it lives.

Request a demo

Keep reading

Guide
Ask + RAG + LenseCatalog + PromptsDLM

Guide: a phased adoption plan for the Insight platform

Where to start and what to add next: a first phase with Ask, RAG and Lense, a second with Catalog and Prompts, and a third with domain models and domain solutions, with the questions that decide when to move on.

November 17, 2026 · 8 min read
Use case
Insight CatalogAutomation HubInsightKafkaInsight Dataflow

Use case: moving a data platform without losing track of what depends on what

A made-up retailer's data team migrates warehouses and Kafka clusters with Insight Catalog for lineage and impact analysis, Insight Automation Hub for validated migration runs, InsightKafka for cluster health, and Insight Dataflow for the new pipelines.

November 15, 2026 · 8 min read
Use case
Insight AskInsight RAGInsight Lense

Use case: one search box for IT operations, across tickets, wikis and code

How a made-up manufacturer's IT operations team uses Insight Ask on top of Insight RAG: connect ServiceNow, Confluence, Jira, Slack and Git, keep permissions intact, and trace every answer with Insight Lense.

November 13, 2026 · 7 min read