Operations
Straight-through processing (STP)
Also called: touchless processing, STP rate
Definition
Straight-through processing is the share of transactions — claims, submissions, endorsements — completed end to end with no human touch.
STP rate is the headline automation metric in insurance and the easiest one to game. Rate rises whenever the routing rules push more cases into the automated path, regardless of whether those cases were decided well, which is why STP is only meaningful when reported next to leakage, reopen rate, and complaint volume. A high STP number with no quality context tells you almost nothing about whether the operation actually improved.
A rate without a quality pair is a vanity metric
Raising STP by widening eligibility looks identical on a dashboard to raising it by improving decisions, and the two produce the same headline chart for very different reasons. The two are distinguished only by what happens downstream — reopens, disputes, and reserve development — which typically shows up weeks or months after the STP number itself was reported and celebrated. A program that reports STP without a lag-adjusted quality metric is reporting a number that cannot be trusted until the downstream evidence catches up with it.
The easy cases go first
Early STP gains come from the simplest work, so the average complexity of what remains rises steadily as the program matures and the routing rules get more aggressive about what qualifies for automation. Capacity plans built on the first year's productivity curve will overstate the second year's, because the team is now handling a residual mix that is systematically harder than the mix it started with. Planning for this shift in advance avoids the awkward conversation about why handling time went up even though the automation program is supposedly succeeding.
Where STP breaks down as a target
Treating STP rate itself as the goal, rather than as one input to a broader outcome, creates pressure to route ambiguous cases into the automated path simply to move the number, which is exactly the failure mode leakage and reopen metrics exist to catch. The healthiest programs set STP as a monitored operating statistic rather than an incentive target for any individual or team, precisely because a metric that determines someone's bonus will eventually be optimized in ways that look good on the dashboard and cost money downstream.
In practice
- Always pair STP rate with reopen rate, leakage, and complaint volume
- Segment STP by case complexity, not just by line of business
- Re-baseline handling time for the residual queue after each automation wave
- Avoid tying individual incentives directly to the STP number itself
