# How a commercial carrier runs submissions from inbox to bind (https://riska.io/blog/commercial-carrier-inbox-to-bind)

_2026-10-12 · Riska · use-case_

A commercial lines carrier writing over $100M runs intake, clearance, appetite, pricing and bind on one record in Riska. Submissions are read, matched to the account and scored before an underwriter opens them, so the day starts at the decision. People still decide every split match, every referral and every change to the book.

## Key takeaways

- A carrier this size loses most of its underwriting hours before the decision: sorting mail, finding the account and reading attachments.
- In Riska every submission is read, cleared against the accounts already on the book and scored for appetite the moment it lands.
- Extracted values arrive as a proposed change with the page and box they came from, and the book only moves when someone applies it.
- Pricing and bind happen on the same record the submission landed on, so nothing is rekeyed between systems.
- Split evidence, referrals and out-of-appetite risks still go to a person. The platform routes them; it does not guess.

> **NOTE: An illustrative use case**
> This post describes how a team of this shape runs the workflow on Riska. It is a composite example, not a report from a named customer, and it quotes no results. Where a number appears, it describes the example, not a measured outcome.

## What inbox to bind looks like at a commercial carrier

Picture a commercial lines carrier with a book north of $100M in written premium. Submissions come from a shared broker mailbox, a producer portal and a couple of agency platforms. A renewal for a trucking account arrives as a reply on a thread from last year, with a fresh loss run and an updated vehicle schedule attached.

Before anyone can decide on it, someone has to work out whether it is new business or a renewal, which account it belongs to, and whether a colleague is already quoting the same insured through another broker. Then someone reads the attachments and keys the values into the policy system. Then someone opens the rating spreadsheet.

None of that is underwriting. All of it happens before the underwriting starts.

### The same submission, two ways of working

Each row is a step every submission goes through, whoever does it.

|  | Today | With Riska |
| --- | --- | --- |
| Intake | someone sorts the shared mailbox | read and filed as it lands |
| Clearance | search the policy system by name | matched on the number in the mail |
| Appetite | the underwriter reads the guide | scored against the rules you set |
| Reading the file | values keyed in by hand | proposed with the page they came from |
| Pricing | a spreadsheet beside the system | a workbook on the same record |
| Bind | rekeyed into another screen | one event on the record |

_Illustrative. The steps are the same; what changes is who does the sorting._

## A submission from arrival to bind

Following the trucking renewal from the broker reply to the bound term.

1. **Land it on the right account** The reply joins the thread it belongs to, and the policy number quoted in it ties the submission to the account the carrier already holds. A message already seen never opens a second submission. If the evidence points two ways, the submission waits for a person instead of picking one.
2. **Read the attachments** Each file is classified against the document types the carrier defined, split into sections and read against the fields mapped to them. The queue shows which documents arrived and which did not, so a missing schedule is asked for on day one.
3. **Clear it and score it** The insured is checked against the accounts and submissions already on the book, and knockout rules run as soon as the data lands. The submission is scored against the appetite the carrier configured and lands in appetite, referred or out, with the rule that put it there attached.
4. **Review the proposed changes** The new vehicle schedule arrives as staged edits in plain language. The underwriter clicks any value, lands on the box it was read from, and applies the changes together or one at a time. Low-confidence fields are the ones shown first.
5. **Price it and bind it** The workbook prices the record it is pointed at, using rate tables from an effective-dated book, so the quote can be reconstructed later. The next event is a button on the record, and when the underwriter is ready that button says Bind.

## Where the underwriter still decides

A platform that guessed through the hard cases would be faster on paper and worse in practice. So the hard cases stop.

When the sender matches two brokers, a person routes it. When a stage cannot resolve something, it opens a task for the owner of the inbox and waits. A referral carries the note written on the rule that raised it. And extracted values never reach the book on their own: they arrive as a proposal, and someone applies them.

What changes is where that person spends the morning. The submissions that need judgement are kept apart from the ones still moving, so the queue is a list of decisions rather than a list of emails.

## One record from intake through bind

Most carriers get here by connecting tools: an intake product, a clearance search, a rating spreadsheet, a policy system. Every hand-off is a place where a value is rekeyed or a submission is matched twice.

Riska is built the other way round. [Submission triage](/platform/submission-triage) (which reads every attachment) and [appetite scoring](/platform/appetite) all write to the same record the underwriter prices and binds in the [underwriting workbench](/platform/workbench). The evidence an extracted value came from, the rule that referred the risk and the version of the rate book that priced it all stay attached to that record, which is what lets a carrier explain a decision months after it was made.

## Questions we get asked

### Is this a real customer?

No. This is an illustrative use case describing how a commercial lines carrier with more than $100M in written premium would run submissions on Riska. It names no customer and reports no results.

### Do brokers have to change how they send submissions?

No. Riska connects to the mailbox submissions already go to, and also accepts submissions from a producer portal or straight from other systems. Every channel joins the same queue and gets the same checks.

### What happens when Riska cannot tell which account a submission belongs to?

It does not guess. A submission whose evidence points to more than one account waits for a person to decide, and the candidates considered and who resolved it are kept on the record.

### Can extracted data change a policy without review?

Not by default. Extracted values arrive as a proposed change that a person applies, and each value keeps the page and box it was read from so it can be checked in one click.