[Use case]

How a property carrier automates appetite decisions on submissions, referrals and renewals

Written by
RiskaProduct
Published
Length
4 min read

What appetite decisions look like at a middle-market property carrier

Picture a carrier writing commercial property for middle-market accounts: a handful of locations each, a schedule of values that runs to a few pages, a loss run and an ACORD 140 attached to the broker's email. On Monday morning one of those arrives for a fourteen-location light manufacturing account.

The appetite guide is a PDF on a shared drive, last revised in the spring. Two underwriters read its line on frame construction near the coast differently. The point at which a risk needs the property manager's sign-off lives in people's heads. And a renewal bound three years ago is about to be quoted again because it renewed last year, even though the carrier pulled back on that county in the meantime.

None of these decisions is hard. Each one is made by hand, one file at a time, by whoever happened to open it.

How a submission is scored and routed

Following the light manufacturing account from arrival to a decision.

  1. 01

    Write the guide as rules

    The carrier groups its rules the way its underwriters already think: property risk, occupancy, loss experience and catastrophe exposure. Protection class and broker quality sit alongside as modifiers, which nudge the score inside a narrow range rather than set it.

    Each rule picks how a value becomes a score. Tiers for a five-year loss ratio. A curve for total insured value, so a million dollars more moves the score smoothly instead of over a cliff. A fixed score for sprinklered. A pass-through for a wildfire rating that already runs 0 to 100. And every rule says what a blank is worth, so a missing value never passes by accident.

  2. 02

    Score it the moment it lands

    When the submission enters the lifecycle, every appetite model in scope for that product runs against it. Total insured value comes from the schedule of values and the loss ratio from the loss run. The result is a score, an outcome, and how much each group of rules contributed to it.

  3. 03

    Let knockouts decide first

    A knockout overrides the score. In this carrier's model, a five-year loss ratio at or above 100% puts the risk out of appetite whatever else it scores. When more than one knockout fires, the most severe one wins, and every one that fired is recorded with the value it saw and the bound it crossed.

  4. 04

    Route on the outcome

    The screening step in the product's lifecycle carries guards in priority order. In this example a score of 70 or above with no knockout routes to quoting, 40 to 69 routes to referral, and anything below 40 or knocked out routes to decline. Nobody picks the branch by hand.

  5. 05

    Send the referral to the desk that can sign it

    Entering the referral status starts a workflow that creates a task for the underwriter who holds authority for that kind of risk, linked to the submission. The task opens on the score breakdown and the rule that referred it, not on the inbox.

Where the underwriter still decides

A referral is not a soft decline, and the platform does not treat it as one. It stops the submission in a status of its own and waits for a person.

What the person gets is the reasoning. The note the underwriting manager wrote on the rule travels with the result, so "refer anything over 40 years old without a roof update" arrives as that sentence, next to the year built it read. If the year built was wrong on the schedule, the underwriter corrects it and the model scores the submission again.

A rule can also raise a requirement: an inspection report, a signed loss control letter. That requirement blocks the quote until someone satisfies it, or waives it with a written reason that stays on the file. Nothing gets skipped quietly.

Three outcomes, and what each one carries

What happens to a submission in this carrier's setup once its appetite model has run.

OutcomeWhat puts it thereWhat happens nextWhat the underwriter sees
In appetiteScore of 70 or above, no knockout firedRouted straight to quoting in the workbenchThe score and each rule group's contribution
ReferScore of 40 to 69, or a referral rule firedStops in referral, with a task for the desk that holds authorityThe rule that referred it, its note and the values it read
Out of appetiteScore below 40, or a knockout firedRouted to decline, with the reason ready for the brokerThe knockout that fired, the value it saw and the bound it crossed
Illustrative configuration. The bands, thresholds and routes are the carrier's own choices, not defaults.

Re-scoring renewals against today's appetite

Appetite moves. This carrier tightened on coastal frame construction in the spring, and accounts bound before that still sit on the book.

So renewals open on their own, 90 days before expiry in this example, as a new term on the same policy. The renewal re-enters the same lifecycle and is scored like a new submission: against the appetite model in force today, with the facts on the renewal. Last year's result does not carry over. An account that bound when the carrier wrote coastal frame freely meets the same knockouts and referral rules as a new one would.

The renewal queue filters on the appetite outcome like any other column. The renewals that now refer or fall out of appetite are a saved view three months ahead, not a surprise on the broker's call two weeks before expiry. A carrier that wants different rules for renewals can apply a model only to renewal terms, for example to go easier on an account with five clean years.

Appetite on the same record as the decision

Most carriers keep appetite in a guide, the referral in an email thread and the renewal in a diary. Each hand-off is a place where the reason for a decision gets lost.

Riska is built so that appetite is a model that scores the record the underwriter works, and its outcome is something the lifecycle can route on. Submission triage lands the submission on that record, workflows carry the referral to the right desk, and every run keeps the rules, the values and the version of the model that produced it. That is what lets a carrier change its appetite on Monday and still explain last October's decline.

Questions we get asked

Is this a real customer?
No. This is an illustrative use case describing how a middle-market commercial property carrier would run appetite decisions on Riska. It names no customer and reports no results.
Can Riska decline a submission without a person?
It can route a submission to a decline status the moment a knockout fires, if the carrier draws its lifecycle that way. Carriers that want a person on every decline route knockouts to a review status instead; either way the knockout and the value that fired it stay on the record.
What happens when a submission is missing data the appetite model needs?
Each rule declares what a blank is worth: the worst score, a fixed score the carrier chooses, or skipped with the other rules reweighted. A missing value is never treated as a pass by accident.
Do renewals keep last year's appetite score?
No. A renewal is scored again when it opens, against the appetite model in force at that moment and the facts on the renewal term, so a change in appetite reaches the renewal book before it comes due.
Can one product run more than one appetite model?
Yes. Every model in scope runs and keeps its own score and outcome, so a property model and a catastrophe model can score the same submission without one overwriting the other.
Can we see why a submission was referred months later?
Yes. Every run records each rule's score, every knockout that fired with the value it saw, and the version of the model that ran, so a referral or decline can be explained after the model has changed.

Keep reading

[Use case]Oct '26

How an MGA rates, reprices and quotes commercial property by asking

A commercial property and crime MGA gives its underwriters, assistant underwriters and account managers one way to rate, reprice and quote: they ask Ask Riska in plain language. It reads the actual record, prices it through the MGA's own rate book and workbook, and shows the premium line by line with the factor behind each one. Nothing on the record changes, and no quote goes out, until a person approves it.

RiskaProduct
[Use case]Oct '26

How a program administrator tracks loss ratio and premium against plan

A program administrator writing commercial property, crime and auto runs its annual plan as portfolio metrics in Riska: written premium, loss ratio, bind ratio and mix, each split by line and program and read against the target in the plan. Every number opens onto the policies and claims behind it, so a ratio that drifts in week three becomes a list of accounts to review, not a surprise at the carrier meeting.

RiskaProduct
[Use case]Oct '26

How an E&S carrier ranks its submission queue by expected value

An E&S carrier writing property and crime uses Riska to score every submission, renewal and task on expected value: premium size, appetite fit and likelihood to bind, lifted by how close the effective date is. The queue is ordered by that score with the reasons beside each rank, so underwriters start on the accounts most worth winning and decline the rest on the first read. People still make every quote, referral and decline.

RiskaProduct

See it on your own submissions.

Bring a real ACORD form and a real appetite guide. We will run them through Riska on the call.