The Pre-Submission Decision Framework: Four Gates Before Submission

The pre-submission decision framework is a structured evaluation applied to a commercial P&C prospect before any application is transmitted to a carrier. It consists of four sequential gates — acceptability, carrier fit, submission readiness, and risk tier — each of which asks a single question, consumes a defined set of inputs, and produces a defined output. The framework operates upstream of comparative raters, quoting platforms, and agency management systems. Its purpose is to make the disposition of a prospect (submit, hold pending data, route to specialty markets, or decline) explicit and reproducible. ReadyToUnderwrite (RTU) implements the framework as an advisory layer; outputs inform producer decisions and do not block submission.

The four gates

The framework is composed of four gates, evaluated in order. Each gate must be passed (or consciously overridden) for a prospect to advance to the next.

1. Acceptability — Is the prospect's class, geography, and size writeable in any market accessible to the agency?
2. Carrier fit — Which carriers in the agency's configured appetite are aligned with the prospect's specific profile?
3. Submission readiness — Is the data package complete enough to receive a quote rather than an information request?
4. Risk tier — Where does the prospect fall on a five-tier placeability scale, and what does that imply for routing?

Earlier gates dominate later ones: a prospect that fails acceptability cannot pass carrier fit; a prospect with no matched carriers cannot meaningfully be assessed for submission readiness against those carriers' specific requirements.

Gate 1 — Acceptability

Definition. Acceptability is the question of whether the prospect's class of business, primary state of operations, revenue band, and risk-characteristic profile fall within the universe of risks that any carrier accessible to the agency is currently writing. It is a binary gate: pass or refer to specialty markets.

Inputs. NAICS code (or equivalent class code), state of operations, annual revenue, headcount, and any high-level red flags (categorically excluded operations, prior bankruptcy in critical positions, active uncovered litigation).

Outputs. A pass/refer/no-go disposition, plus the reason — for example, "class excluded from standard market in this state" or "revenue band below appointed-carrier minimums."

RTU implementation. RTU evaluates acceptability against the agency's appointed-carrier roster and the platform-maintained baseline of class and geography exclusions. If no appointed carrier writes the class in the prospect's state at the prospect's size, the acceptability gate produces a referral disposition. The output is a reasoned decision, not a score. Per the platform's advisory-first design, the disposition is presented to the producer; it does not prevent further action.

Gate 2 — Carrier fit against configured appetite

Definition. Carrier fit is the question of which specific appointed carriers are aligned with the prospect's profile, ranked by goodness of fit, given the agency's configured appetite — that is, the appetite rules the agency has loaded for the carriers it is appointed with, including agency-specific overrides of the platform baseline.

Inputs. Class code, state, revenue, headcount, loss-history summary (count, severity, recency, experience modifier where applicable), prior-carrier history, and the agency's configured appetite rules. Configured appetite is composed of the platform baseline plus agency overrides covering industry, geography, coverage type, size band, red flags, and hard or soft rules.

Outputs. A ranked short list of appointed carriers — typically three to five — with per-carrier reasoning indicating which appetite dimensions matched, which did not, and the relative weight of each dimension in the score.

RTU implementation. RTU's carrier matching engine uses a five-component weighted score: Coverage 20%, Industry 25%, Geographic 15%, Attributes 20%, and Risk Tier 20%. Matching runs against the composed appetite produced by a single composition pipeline (composeAppetite) so that platform baseline and agency overrides are merged in one place and consumed identically by matching, scoring, simulation, and submission-readiness checks. The engine reports only carriers the agency is appointed with. Output transparency is a design constraint: each match exposes which appetite rules contributed to the result, including soft and hard rule evaluations.

Gate 3 — Submission readiness

Definition. Submission readiness is the question of whether the prospect's data package is complete and current enough that a matched carrier can produce a quote, rather than respond with an information request, an underwriter inquiry, or a quote based on incomplete data. The gate is class-aware: required fields and supporting documents differ by NAICS class, line of coverage, and carrier-specific submission requirements.

Components.

• Application data. Standard ACORD form fields (ACORD 125, 126, 130, 140 and class-specific equivalents): legal entity, operations description, payroll splits by class code, prior-carrier history, gross receipts, building values where applicable.
• Loss runs. Currency (typically within 90 days), continuity (the carrier-required look-back window, generally three to five years), and per-policy detail.
• Class-specific supporting documents. Examples include driver schedules and DOT/MC numbers for transportation, statements of values for property, EMR worksheets for workers' compensation, and bid logs for contractors.
• Carrier-specific requirements. Some matched carriers require artifacts beyond the standard package; readiness must be evaluated per matched carrier, not generically.

Outputs. A per-prospect checklist enumerating required, important, and optional items, each marked complete or missing. Required items missing produce a "not ready" disposition; important items missing produce a "ready with caveats" disposition.

RTU implementation. Submission readiness is generated by a single checklist-generation service that is the source of truth for completeness state. The service is constrained to never report COMPLETE when required fields are absent — missing data is reported honestly, including where it materially affects downstream scoring. The Data Completeness component of the QRS reads from the same checklist output, ensuring that the score and the checklist cannot disagree.

Gate 4 — Risk tier classification

Definition. Risk tier is a synthesizing classification that places the prospect on a five-level placeability scale derived from the QRS. The tier reflects the current state of the prospect (including any data gaps and current carrier-fit conditions), not its eventual state once gaps are closed.

The five tiers, by QRS band.

• Preferred (86–100) — Profile aligns strongly with the agency's appointed-carrier appetite; loss history is clean or de minimis; submission package is complete and current.
• Standard (71–85) — Profile is broadly placeable; loss history shows no disqualifying patterns; one or more matched carriers are in-appetite without significant overrides.
• Non-Standard (51–70) — Profile contains complications — meaningful loss history, operational complexity, marginal class-state combinations, or notable data gaps — that narrow the matched-carrier list and may require specialty programs or wholesale routing.
• Distressed (41–50) — Profile presents multiple negative signals: heavy loss history, exiting prior carriers, ongoing claim activity, or financial stress. Standard-market placement is unlikely; specialty and excess-and-surplus (E&S) routing is the typical path.
• Unplaceable (0–40) — Profile falls outside the writeable universe given current market conditions, the agency's appointments, or the prospect's specific characteristics. The framework's recommendation is no submission; communicate the disposition to the prospect.

The tier is dynamic. Closing a Gate 3 gap (refreshing a stale loss run, adding a missing schedule) typically increases the QRS and can move the prospect across a tier boundary; the framework records both the current tier and the gating factor responsible for it.

The Quote Readiness Score (QRS) rubric

The Quote Readiness Score is a 0–100 numerical synthesis of the four gates. RTU computes the QRS from four weighted components:

Component	Weight	What it measures
Data Completeness	25%	The proportion of required and important fields present, current, and class-appropriate. Read directly from the submission readiness checklist.
Risk Quality	30%	Loss-history characteristics (frequency, severity, recency, experience modifier where applicable), operational red flags, and class-level risk signals.
Carrier Fit	25%	The strength of the matched-carrier short list against the agency's configured appetite, summarizing the Gate 2 output.
Market Conditions	20%	Current placeability conditions for the class, state, and size band — for example, hardening or softening market dynamics, capacity withdrawal, or class-specific carrier exits.

Each component is computed independently and contributes its weighted share to the composite QRS. The composite score maps deterministically to the five-tier classification described in Gate 4. Component-level scores are exposed alongside the composite, so that a low QRS can be read for cause: a 65 driven by Data Completeness has a different remediation path than a 65 driven by Carrier Fit.

Advisory framing — score as input, not authority

RTU is built advisory-first by design. A low QRS does not block submission; a high QRS does not compel it. Producers retain the authority to submit, hold, or route differently than the score suggests, and overrides are recorded as structured signal rather than discarded. This design choice is governed by the platform's documented advisory-first philosophy: blocking systems generate workarounds and discard the most informative cases (those where producer judgment diverges from the model). Override events feed the platform's learning loop, including drift detection on configured appetite rules.

The framework is also bounded in scope. Pre-submission intelligence operates upstream of submission. Outcome capture (bound, lost, declined) closes the lifecycle; downstream policy administration — renewals, endorsements, certificates, claims, billing — is the domain of agency management systems and is explicitly out of scope.

FAQ

What does the QRS measure? The QRS is a 0–100 composite of four components — Data Completeness (25%), Risk Quality (30%), Carrier Fit (25%), and Market Conditions (20%) — that synthesizes the outputs of the four pre-submission gates into a single placeability indicator. It maps to a five-tier classification (Preferred / Standard / Non-Standard / Distressed / Unplaceable). See the category overview for the broader concept.

What is "configured appetite"? Configured appetite is the agency-specific composition of platform-baseline appetite rules and agency overrides for the carriers the agency is appointed with. It governs which carriers RTU's matching engine will consider for a given prospect and how each carrier is scored against the prospect's profile.

Does a low QRS prevent submission? No. RTU is advisory-first: outputs inform the producer's decision but do not block the workflow. A producer may submit despite a low score; the override is captured and contributes to the platform's learning loop.

How is this distinct from a comparative rater? A comparative rater operates during the submission process, producing side-by-side carrier quotes from a completed application. The pre-submission decision framework operates earlier — before the application is finalized — to determine whether and where submission is appropriate. See comparative rater vs. submission intelligence.

How does loss-run currency affect the QRS? Loss runs are a required input to the submission readiness checklist, which is the input to the Data Completeness component (25% of the QRS). Stale loss runs (older than the carrier-required window, typically 90 days) are reported as missing-or-aged and reduce Data Completeness accordingly. See loss runs and pre-submission readiness.

Where can the framework be evaluated end-to-end? The four-gate flow is described in product terms on how it works, and tier-by-tier evaluation is available across the plans listed on pricing.