Operations

Straight-Through Processing in Commercial Lines: What It Actually Takes to Make STP Work

Straight-Through Processing in Commercial Lines: What It Actually Takes to Make STP Work

Straight-through processing in commercial P&C underwriting means binding a policy without manual underwriter review — the submission comes in, the automated system evaluates it against documented appetite criteria, and the policy issues. For carriers that get the configuration right, STP rates of 25-40% on commercial submissions are achievable. That represents a material reduction in underwriting labor per bound policy and a meaningful improvement in the broker experience for routine accounts.

Getting there requires careful thinking about which submissions belong in the STP path and which do not. The operational efficiency argument is straightforward; the risk management argument requires more precision.

What STP Is Appropriate For

STP works well for a specific profile of commercial submission: clean business, standard occupancy, peril exposure within carrier appetite, requested limits below a defined threshold, no adverse prior loss indicators, and no flags from the automated data enrichment process.

Think about the commercial submissions your underwriting team processes in a typical week. A subset of those — often larger than carriers initially estimate — are accounts your underwriters bind without significant deliberation after reviewing the data. A retail store in a low-hazard location, a professional services firm with standard GL requirements, a light manufacturing operation with a clean loss history. The underwriter's review of those accounts confirms that the data is as expected; it does not generate new risk insight.

Those are the submissions STP is designed for. The automated system does the same confirmation the underwriter was doing, runs it against documented appetite criteria, and routes to the bind queue when all checks pass.

What STP Is Not Appropriate For

Elevated peril exposure is the clearest exclusion. Any submission with a multi-peril score above the carrier's defined moderate threshold warrants underwriter review, regardless of how routine the occupancy appears. Peril exposure is the variable most likely to produce unexpected claims, and it is also the variable most likely to have changed since the last time the carrier evaluated a similar risk in the same location.

High-limit requests belong in the underwriter review queue. The practical loss exposure on a $5M commercial property policy is qualitatively different from a $500K policy even if the risk profiles appear similar. STP is appropriately limited to limits below a threshold that your underwriting leadership defines based on your reinsurance structure and risk appetite.

Unusual business structures — subsidiaries with complex ownership chains, businesses with SIC codes that don't match their described operations, new businesses with less than two years of operating history — should route to the underwriter review queue. These are exactly the situations where business intelligence enrichment is most likely to surface something the submission data does not show.

Prior loss flags are a hard stop. Any submission with adverse loss history signals routes to the underwriter review queue without exception.

The Configuration Work That Precedes STP

Carriers that attempt STP without completing the appetite documentation work first get one of two outcomes: an STP rate so conservative it produces no operational benefit, or an STP path with gaps that binds risks the underwriting team would have declined manually.

The configuration work requires your underwriting leadership to document appetite criteria with enough precision that a rule engine can apply them consistently. This means specifying:

This documentation often surfaces appetite ambiguities that have existed in informal form for years. Different underwriters in the same commercial lines team sometimes apply different standards to identical submissions because the standards were never explicitly written down. The STP configuration process forces that documentation.

The Auditability Requirement

Every automated binding decision in the STP path needs a complete audit trail: the input data, the scoring outputs, the appetite rules applied, and the routing determination. This is not optional — it is a compliance requirement in most states for any automated underwriting decision, and it is essential for your own post-binding review capability.

When a claim comes in on an STP-bound policy and the claims team asks why the account was bound without underwriter review, you need to be able to answer that question with specifics. The audit trail should show exactly which criteria the submission met and which rules produced the routing decision.

Carriers that cannot produce that trail have an exposure they may not recognize until a regulatory examination or a coverage dispute puts the binding decision under scrutiny.

Expanding STP Incrementally

The carriers that implement STP most successfully treat the initial configuration as a starting point, not a final state. Start with a narrow STP eligibility profile — low-hazard occupancies, modest limits, clean losses, standard territories — and run it for a full quarter before evaluating expansion.

After the first quarter, pull the data on everything the STP path processed: the actual bind rate, the post-bind claim rate on STP-processed policies versus manually reviewed policies, and the exception rate — how often the automated system flagged something the underwriter review would have caught and how often it missed something only visible to a human reviewer.

Use that data to inform the first expansion of STP eligibility criteria. The goal is a system where STP handles the genuinely routine accounts efficiently and routes genuinely complex accounts to the underwriting team. Getting there requires the calibration data that comes from running the initial configuration against real production volume.

The Impact on Underwriter Roles

One concern carriers consistently raise is whether STP reduces underwriter headcount. The honest answer is that STP reduces the number of routine submissions underwriters need to review, which creates capacity that can be deployed toward more complex accounts, larger submission volumes, or a reduced growth rate in headcount as the book expands.

The underwriters at carriers that have deployed STP effectively report that the quality of their work day improves. They spend more time on the accounts where their judgment actually matters and less time on confirmation reviews that produced no insight. The routine confirmation work that STP handles is not what experienced commercial lines underwriters want to be doing — removing it from their queue is a retention factor, not a threat.

See Perilarc in action for your submissions

We’ll show you what 90-second dossier assembly looks like for your commercial lines.