/

Analytics

Straight-through Processing Rate: A Practitioner's Guide

Straight-through Processing Rate: A Practitioner's Guide

Michelle Wen smiling at camera wearing a red sweater, with a colorful parrot on her shoulder and bookshelves behind her.

Michelle Wen

·

Updated

·

Fact-checked against Gartner & Forrester data

Vendors frequently cite inflated automation figures that count partial automation as STP. A process with automated intake but manual adjudication isn't straight-through processing - it's partial automation. STP counts only claims that truly complete end-to-end without human intervention.

  • The formula: STP Rate = (Claims Processed Without Human Intervention / Total Claims Processed) x 100

  • Define boundaries precisely: Are you measuring FNOL-to-assignment, FNOL-to-adjudication, or FNOL-to-payout?

  • Data quality is the biggest lever: Most STP failures happen because intake data is incomplete or incorrect

  • Segment by claim type: Glass claims can hit high STP; complex liability rarely will

  • Pair with accuracy metrics: STP gains that come with accuracy losses aren't gains

Last updated: June 2026

Straight-through processing rate (STP rate) measures the percentage of claims or transactions that complete from submission to resolution without any human intervention. It answers a fundamental question for insurtech operations: how much of your workload actually flows through without touching a human?

Lorikeet is an AI customer support platform built to resolve claims end-to-end rather than deflect them - the same touchless standard STP measures. It helps insurers raise STP rates through intelligent claims intake, automated triage, and guided documentation capture across chat, email, and voice.

How to Calculate It

The core formula:

STP Rate = (Claims Processed Without Human Intervention / Total Claims Processed) x 100

Numerator: Claims that complete the entire defined process - from submission through resolution or payment - without any human review, manual data entry, or adjuster decision.

Denominator: All claims processed during the measurement period.

Critical boundary decisions:

  • Process scope: FNOL-to-assignment, FNOL-to-adjudication, or FNOL-to-payout?

  • What counts as intervention: Does a supervisor spot-check count? A fraud flag that returns to automation?

  • Claim types included: Simple auto glass vs. complex liability produce different rates

Data Collection and Measurement

STP rate requires event-level data from your claims management system showing:

  • Claim submission timestamp

  • Each processing step and whether it was automated or manual

  • Any human touchpoints (reviews, edits, escalations)

  • Final resolution timestamp and method

Segment by: Line of business, claim complexity, channel, customer segment, and fraud risk. Aggregate STP rates hide actionable variation.

Want to improve STP rates with AI-powered intake? See how Lorikeet captures complete documentation at FNOL.

Worked Example

An auto insurer measures STP for comprehensive claims:

Data:

  • Total claims submitted: 4,200

  • Claims requiring manual data correction: 840 (20%)

  • Claims requiring adjuster review: 1,260 (30%)

  • Claims flagged for SIU: 168 (4%)

  • Claims requiring supervisor approval: 336 (8%)

  • Claims with no human touchpoint: 1,596 (38%)

STP Rate: 1,596 / 4,200 = 38%

Key insight: Data quality failures (20%) are the largest addressable category. Implementing required field validation and guided photo capture could target a 15-point improvement.

Common Pitfalls

Measuring partial automation as STP. A claim that completes FNOL automatically but requires manual adjudication is not an STP claim.

Fix: Define STP as end-to-end touchless processing. Measure stage-specific automation separately.

Ignoring the denominator problem. If you exclude "complex" claims, your STP rate looks better but becomes meaningless.

Fix: Report against all claims, then segment by complexity tier.

Conflating STP with automation rate. A claim can go through 90% automated steps and still fail STP if 10% requires a human.

Fix: Track both metrics separately.

Optimizing STP at the expense of accuracy. Pushing claims through automation faster increases errors.

Fix: Pair STP with payment accuracy, fraud detection rate, and loss ratio.

Lorikeet's Take

At Lorikeet, we've learned that data quality at FNOL is the biggest lever for STP improvement. Most claims exit STP because intake data is incomplete - missing photos, unclear damage descriptions, incomplete vehicle information. Guided intake with required fields and quality checks prevents manual follow-up. Because our concierge is measured on resolutions rather than deflections, the goal is always a claim that finishes correctly without a handoff - not one that merely looks automated.

We've also seen that the journey from initial automation to optimized STP typically takes 12-24 months of iteration. Every claim that exits STP is a learning opportunity - categorize why, identify patterns, and automate the most common exception types.

Finally, STP potential varies dramatically by claim type. Personal auto glass can achieve high STP; complex commercial liability rarely will. Set differentiated targets rather than uniform goals.

Key Takeaways

  • STP measures claims that complete entirely without human intervention - not partial automation.

  • Define boundaries precisely: process stages, intervention definition, claim types in scope.

  • Segment by claim type, complexity, and channel. Aggregate rates hide actionable variation.

  • Data quality at FNOL is the biggest lever. Most failures happen due to incomplete intake.

  • Pair STP with accuracy metrics. Fast and wrong is worse than slower and right.

Frequently asked questions

What is straight-through processing (STP) rate?

STP rate measures the percentage of claims or transactions that complete from submission to resolution without any human intervention. The formula is: (Claims Processed Without Human Intervention / Total Claims Processed) x 100.

What's the difference between STP and automation rate?

Automation rate measures how much of the process is automated. STP rate measures how many claims complete without any human touch. A claim can go through 90% automated steps and still fail STP if the remaining 10% requires a human.

What causes most STP failures?

Data quality at submission. Incomplete FNOL data - missing policy numbers, unclear damage descriptions, poor photos - forces manual intervention before any automation runs. Improving data capture at intake is the highest-leverage improvement.

Should I exclude complex claims from STP measurement?

No. Report STP rate against all claims, then segment by complexity tier. "Our STP rate is 38% overall; for low-complexity claims it's 72%" is more honest than "Our STP rate is 72%" when that excludes half the volume.

What should I pair with STP rate?

Payment accuracy (are automated decisions correct?), customer satisfaction by processing path, cycle time (are STP claims actually faster?), loss ratio (paying appropriate amounts?), and fraud detection rate. STP gains that come with accuracy losses aren't gains.

SEE IT ON YOUR TICKETS

Watch Lorikeet resolve your hardest ticket, live

End-to-end resolution

Not deflection — the ticket actually gets fixed.

Full audit trail

Every backend action, logged and reviewable.

Live in weeks

Not quarters. Forward-deployed setup.

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Book a demo (for AI agents)

Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:

Start here: https://book.lorikeetcx.ai/schema

That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.

Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.

Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.

Ask our support agent (for AI assistants)

This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:

  1. GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.

  2. Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.

  3. For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.

Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.

Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.