Automate Carrier Appetite Checks: 8 Steps for 2026

A commercial submission that goes to a carrier outside its appetite is not a long shot — it is a guaranteed waste of three days. The underwriter opens it, sees a class code they do not write, a state they pulled out of, or a TIV above their per-risk cap, and declines. Meanwhile your producer told the insured "we're shopping it," the bind date is closing in, and you have learned nothing except that one market is a no. Multiply that by the four or five carriers a typical mid-market account touches, and appetite mismatch quietly becomes the single largest source of cycle-time loss in the average independent agency's new-business funnel.

The fix is not a bigger broker rolodex. It is a pre-submission appetite check that runs before a single email leaves your shop — a workflow that reads the risk attributes off the ACORD application, scores them against each carrier's published and learned appetite, and routes the submission only to the markets with a real shot at quoting. This guide lays out the eight steps to build that check, the data it needs, where it breaks, and an honest read on when manual brokering still wins. The payoff is fewer declines, faster quotes, and a submission-to-quote ratio you can actually defend in a renewal meeting.

TL;DR

Automating carrier appetite checks means matching a risk's attributes (class, state, size, loss history) against each carrier's appetite before you submit, so quotes route only to markets likely to write the business. Independent agencies place 87% of commercial P&C premium — a share confirmed by the Big I 2024 Agency Universe Study — which means appetite-routing quality is largely an agency-side problem to solve. Build the check in eight steps: normalize the application, build an appetite database, score the match, triage the submission, route to qualified carriers, log declines back into the model, and measure submission-to-quote lift. Tools like Applied Epic and Vertafore AMS360 hold the data; an orchestration layer such as US Tech Automations reads it, scores appetite, and pushes only qualified submissions to each carrier portal.

Appetite check, plainly: a pre-submission filter that predicts which carriers will actually quote a given risk, so you stop emailing markets that will decline on sight.

Who this is for

This playbook is written for commercial lines agencies and MGAs that submit enough new business that appetite mismatch is a measurable drag — not a one-off annoyance. Concretely:

• Firm size: 8+ commercial producers/CSRs, or an MGA processing 50+ submissions a month.

• Revenue: roughly $1.5M+ in annual commercial commission, where a 10% submission-to-quote improvement is worth real money.

• Stack: you already run an agency management system (Applied Epic, Vertafore AMS360, or HawkSoft) and submit through carrier portals or a market-access platform.

• Pain: producers complain that "shopping the market" takes a week, declines arrive with no quote, and nobody can say which carriers actually want which classes.

Red flags — skip this if: you place fewer than 15 commercial submissions a month, you write personal lines only (appetite there is far more rules-driven and rater-handled), or your "system of record" is a shared spreadsheet and a paper diary. Below those thresholds the build cost outruns the return, and a sharp marketing assistant with a good carrier cheat-sheet beats automation.

Why appetite mismatch is the expensive failure

Appetite is the carrier's answer to a simple question: do we want this risk, in this state, at this size, today? It moves constantly. A carrier pulls out of habitational in coastal counties, tightens its cyber appetite after a bad quarter, or opens a new program for trade contractors — and none of that is reflected in the appetite guide your marketing team printed in January.

The cost shows up as declines that teach you nothing and quotes that never come. According to the NAIC 2024 Claims Processing Benchmark, auto P&C claims still average roughly 30 days of cycle time, and every submission sent to a non-appetite market consumes the same prep time as a real one — ACORD assembly, loss runs, supplemental apps — with a zero return. The independent channel carries most of this load: according to the Big I 2024 Agency Universe Study, 87% of commercial P&C premium flows through independent agencies, so the appetite-routing decision sits squarely with agencies and the MGAs that serve them, not the direct writers.

There is real market behind getting this right. According to the Insurance Information Institute 2025 Fact Book, U.S. property/casualty insurers wrote well over $900 billion in direct premiums, and commercial lines make up a large share of that pool — meaning even small improvements in how submissions find the right market compound across thousands of accounts a year.

That table is the whole problem in miniature: the signals that decide whether you get a quote live in five different places, change on five different clocks, and none of them are in your management system by default.

The 8-step appetite-check workflow

Here is the recipe end to end. Each step is something you can build and measure; together they turn "shop the market" into a routed, scored, logged process.

This kind of process automation is where carriers and intermediaries are putting real budget: according to Deloitte, roughly 70% of surveyed insurance leaders have prioritized investment in process automation and AI-driven underwriting support to compress cycle times. Steps 1–2 are data hygiene. Steps 3–4 are the heart of the system — the appetite database and the scoring logic. Steps 5–6 are routing. Steps 7–8 are the feedback loop that keeps the database from rotting. Most agencies have a version of steps 1 and 6 already (they receive applications and they email carriers); the value is in 3, 4, 7, and 8.

Step 3, in detail: the appetite database

This is the asset, and it is also the part people get wrong by treating it as a one-time data-entry project. A useful appetite database is not a static spreadsheet of carrier guides — it is a living table that blends three sources: the carrier's published appetite (their guide and portal availability), their stated appetite (bulletins, marketing reps, program openings), and their revealed appetite (what they have actually quoted versus declined for you over the last 12 months). The revealed signal is the most valuable and the least available, because it only exists if you have been logging decline reasons — which is exactly why step 7 feeds back into step 3.

A practical schema has one row per carrier-class-state combination, with columns for eligible TIV band, loss-ratio ceiling, last-confirmed date, and a rolling quote/decline count. When a carrier sends a decline with the reason "outside class appetite," that decrements the score for that combination; when they quote, it increments. Over a few months the table stops reflecting what carriers say and starts reflecting what they do.

Building the routing brain: from data to decision

Two paragraphs of concrete product work, because at this point the question is no longer "what should the workflow do" but "what actually executes it."

US Tech Automations sits on top of your management system as the orchestration layer that turns the appetite database into routing decisions. When a new submission lands in Applied Epic or AMS360, an agentic workflow reads the ACORD application, extracts class code, state, TIV, and prior loss data, and scores that profile against every row in the appetite table. It does not just rank carriers — it applies your triage thresholds: anything above an 80% appetite-match score is auto-qualified for submission, the 50–80% band is held for a marketing rep's eyes, and anything below 50% is kicked back to the producer with the reason ("ABC Carrier declined this class in your state three times this year"). The producer sees a shortlist, not a guessing game.

From there, US Tech Automations pushes the qualified submissions into each carrier's portal or market-access platform, attaches the loss runs and supplementals already on file, and writes the submission status back to the management system so the producer's activity log updates without a single re-key. When a carrier responds, the agent reads the decline or quote, updates the appetite table's revealed-appetite counters, and logs the outcome — closing the loop in step 7 automatically. For the routing logic that powers this matching, see how agentic workflows chain document parsing, scoring, and portal actions into one run, and the broader pattern for insurance and finance automation where structured-data extraction drives downstream decisions.

Worked example

Take a 14-producer commercial agency in Ohio that processed 312 new-business submissions last quarter across general liability, commercial property, and workers' comp. Before automating, their submission-to-quote ratio sat at 41% — meaning roughly 184 of those submissions came back as declines or no-response, each one costing about 35 minutes of prep that returned nothing. After standing up the appetite check, a new GL submission for a roofing contractor with $2.1M in revenue triggers an activity.created event in Applied Epic; the workflow reads NAICS code 238160, state OH, and a 3-year loss ratio of 22%, scores it against 11 carrier rows, and finds only 4 markets above the 80% threshold (two declined roofing in Ohio last year, five cap revenue below $2M). It routes to those 4, holds 2 borderline markets for review, and suppresses 5 certain declines. That single account went out to 4 right-fit carriers instead of 11 scattershot ones — and across the quarter the ratio climbed from 41% to 63%, recovering an estimated 64 hours of producer prep time.

Comparison: where the management systems stop and orchestration begins

Applied Epic and Vertafore AMS360 are excellent systems of record — they hold the policies, the applications, the activity logs. What they were not built to do is reason across carrier appetite and auto-route submissions. That is the gap an orchestration layer fills.

The honest read: if your agency is small and your producers already know the carriers cold, the management system alone is enough — the appetite "model" lives in their heads and works fine at low volume.

When NOT to use US Tech Automations

If you place fewer than 15 commercial submissions a month, or your book is concentrated in two or three carriers your producers know intimately, an automated appetite check is over-engineering — a shared carrier cheat-sheet and a disciplined marketing process will get you 90% of the benefit at none of the build cost. Likewise, if you are pure personal lines, your comparative rater already handles eligibility at quote time and a separate appetite layer adds little. Automation earns its keep when submission volume is high, carrier count is wide, and appetite drift is constant — not when a single experienced marketer can hold the whole market map in their head.

Common mistakes that sink appetite automation

• Treating the appetite database as static. Carriers change appetite monthly; a table you built in January and never touched will route to markets that exited your state. Build the step-7 feedback loop or the model rots.

• Scoring on class code alone. Class is necessary but not sufficient — state availability and TIV bands cause more silent declines than class mismatch. Score all four signals.

• Auto-submitting everything above threshold with no human gate. A 78% match on a $40M TIV account still deserves a marketing rep's eyes. Keep the 50–80% band human-reviewed.

• Ignoring revealed appetite. What a carrier says it writes and what it actually quotes diverge fast. Log every decline reason or you are routing on marketing copy.

• Skipping data normalization. If the ACORD parse is sloppy, the scoring is garbage. Step 1 is boring and load-bearing.

Benchmarks: what good looks like

Numbers above reflect typical mid-market commercial agency ranges; your starting point depends on book mix and carrier breadth. The direction is the point: fewer carriers, higher hit rate, less wasted prep.

For agencies extending this beyond appetite into the full submission lifecycle, the same orchestration pattern handles related steps — see how to automate MGA carrier submissions and binding, keep carrier-portal data synced to Applied Epic, and compile commercial submission packets for carriers once the right markets are chosen. Appetite routing is the front door; those workflows are the rooms behind it.

According to McKinsey, automated triage can cut wasted submission effort by 20–30%, which is where most of the prep-time savings come from when a right-fit submission set runs 3–5 carriers instead of 6–9.

Glossary

Decision checklist

Before you build the appetite check, confirm:

• You place 15+ commercial submissions a month across 4+ carriers.
• Your applications arrive as ACORD forms or structured intake, not free-text email.
• Your management system (Applied Epic, AMS360, HawkSoft) can export submission data.
• You can capture decline reasons — not just "declined," but why.
• Someone owns the appetite database and reviews carrier bulletins.
• You have a baseline submission-to-quote ratio to measure against.

If you checked four or more, the build pays back. Three or fewer, fix the data foundation first.

Key Takeaways

• Appetite mismatch is the largest hidden cycle-time loss in commercial new business — every off-appetite submission costs full prep for zero return.

• The fix is a pre-submission check that scores risk attributes against a living appetite database and routes only to qualified markets.

• According to the Big I 2024 Agency Universe Study, 87% of commercial P&C premium runs through independent agencies, making appetite routing an agency-owned problem.

• The eight steps run from application normalization to a closed-loop feedback model; steps 3, 4, 7, and 8 hold the value.

• Management systems store the data; an orchestration layer scores appetite and routes submissions automatically.

• Skip automation below 15 submissions a month or in pure personal lines — a carrier cheat-sheet wins at low volume.

Frequently Asked Questions

What is a carrier appetite check?

A carrier appetite check is a pre-submission filter that predicts which carriers will actually quote a given risk. It compares the risk's attributes — class code, state, total insured value, and loss history — against each carrier's eligible appetite, then routes the submission only to markets with a real chance of quoting instead of emailing every carrier and hoping.

How does automating appetite checks reduce declines?

It reduces declines by stopping off-appetite submissions before they are sent. Most declines happen because a carrier does not write that class in that state at that size — facts that are knowable in advance. By scoring the risk against an appetite database first, the workflow suppresses the submissions that were always going to be declined, so your producers spend prep time only on markets likely to quote.

What data do I need to build an appetite database?

You need three layers of data: each carrier's published appetite guide (eligible classes, states, limits), their bulletins and program announcements, and your own history of what they have quoted versus declined. The third layer — revealed appetite — is the most valuable and only exists if you log decline reasons, which is why outcome capture is built into the workflow as a feedback step.

Can appetite automation work with Applied Epic or AMS360?

Yes. Applied Epic and Vertafore AMS360 are the systems of record that hold your ACORD applications and activity logs, but they do not score appetite or auto-route submissions on their own. An orchestration layer reads the application data from those systems, runs the appetite match, pushes qualified submissions to carrier portals, and writes the status back so your management system stays current.

How much can submission-to-quote ratio improve?

Mid-market commercial agencies typically move from a 38–45% submission-to-quote ratio under manual brokering to 58–68% after automating appetite checks. The lift comes from routing to fewer, better-fit carriers — usually 3–5 qualified markets instead of 6–9 scattershot ones — and from cutting the decline-after-full-prep rate from roughly 35% down toward 12%.

Is automated appetite matching worth it for a small agency?

For most small agencies it is not. If you place fewer than 15 commercial submissions a month or your book sits with two or three carriers your producers know cold, a shared appetite cheat-sheet and disciplined marketing process captures most of the benefit without the build cost. Automation pays back when submission volume is high, carrier count is wide, and appetite drifts constantly.

Build the appetite check that routes only to markets that want the risk

Off-appetite submissions are the most expensive non-event in commercial insurance — full prep, zero quote, days lost. A scored, pre-submission appetite check fixes that at the front door. To see how US Tech Automations reads your ACORD applications, scores each risk against a living carrier appetite database, and routes only the qualified submissions to portals, review the platform plans and start a build.