SystemPolicy Administration & Servicing

Policy Servicing Analytics

Policy servicing analytics that shows which work will miss its promise, and how accurate every finished transaction really is

See which work will miss its promise, and how accurate finished work is.

See one case, screen by screen ↓
demo731itemsforecast to miss their promise by Thu 15 Oct, out of 6,842 open — seen three days ahead
demo95.7%accuracy measured on every Harrowfield transaction, against the 99.2% the outsourcer reports
demo614itemsof in-house work caused by one outsourcer’s wrong transactions, moved to the stream that caused them
demo46missesHarrowfield endorsements still forecast to miss after the suggested rebalance, down from 418
In short

What is Policy Servicing Analytics?

It is the view of all policy service work — endorsements, certificates, cancellations and reinstatements, billing and refunds, mortgagee changes — across in-house teams and outsourcers: what is open, what will miss its promise and how accurate the finished work is. Policy Servicing Analytics builds that view from your queues every 15 minutes instead of from weekly spreadsheets.

How to choose AI solutions for insurance →

Updated

The problem

Why service leaders find out about backlog and bad keying too late

Endorsements, certificates, cancellations and reinstatements, billing and refunds and mortgagee changes are split across in-house teams and outsourcers. Each team reports its own backlog and its own accuracy, in its own spreadsheet, once a week — so by the time the sheet shows a backlog, the promise is already missed.

Accuracy is checked on small samples, and the outsourcer samples its own work. Meanwhile your own people quietly redo the vendor’s wrong transactions — re-issue the endorsement, take the customer’s call, reprint documents, fix the bill, notify the lienholder — and that work is counted as in-house backlog. The in-house team looks slow, the vendor looks accurate, and a new car keyed with the wrong effective date turns up at claim time.

demo3.5pointsbetween Harrowfield’s own sample and every transaction checked
demo220endorsementsin Harrowfield’s own monthly sample, which found 2 errors
demo27ha claim was held because a new car was keyed with the wrong effective date
Where a week of service oversight goes (hours)estimated
By hand28 days
With the solution4.5 days
  • Collecting and merging each team’s backlog sheet6 → 0.5 d
  • Sampling finished transactions by hand10 → 2 d
  • Tracing in-house rework back to the vendor5 → 0.5 d
  • Preparing the vendor review and service credit4 → 1 d
  • Writing the weekly service report3 → 0.5 d

Estimated split for a head of policy services and a quality analyst over one week, by hand and with the solution.

How it works

How the picture is made

Six agents read every queue, check every finished transaction and trace every rework; the head of policy services decides and signs.

What comes in
Work in5 sources · queues, transactions, requests, rosters, contracts
Agents at work
Queue readerevery 15 minutes
Then
Source checkerevery transaction
Rework finderwhere it started
Then
Promise forecaster3 days ahead
Then
Correction drafter
Report writerreport + credits
A person decides
Head of policy servicesmoves work, signs
What comes out
Service river
Corrections sent back
Weekly report
One case, step by step

One Monday morning, from the river to a signed report

Ashcombe Mutual runs its service work across two in-house teams and two outsourcers. It is Mon 12 Oct 2026, 08:10. Here is what the head of policy services sees and decides, screen by screen, in the working solution.

  1. 0108:10

    All service work, as one river

    Dana Whitcombe · Head of Policy Services

    Dana opens the service river: one stream per team, ten working days back and three forecast days ahead. 6,842 items are open — Selwyn 1,454, Harrowfield 2,618, Columbus 1,964, Dayton 806 — and 731 will miss their promise by Thu 15 Oct. Harrowfield’s stream carries 418 of them. The side rail shows how this morning’s picture was made, from 06:00.

    “Source checker · 1,912 weekend transactions checked — 1,889 match their request · 23 differ”

  2. 02One switch

    Count rework where it started

    Dana Whitcombe · Head of Policy Services

    Dana turns on “Count rework where it started”. Every in-house item that exists only because a vendor’s transaction was wrong moves to that vendor’s stream. Harrowfield swells by 614 items: 181 transactions redone in Columbus in 10 working days, and 433 more items they caused — customer calls, reprints, billing fixes and lienholder notices. Its badge turns from 99.2% reported to 95.7% measured.

    “Columbus’s own work is 1,232 open items, not 1,964.”

  3. 03One click

    Harrowfield, on one strip

    Dana Whitcombe · Head of Policy Services

    Clicking the stream opens the team beneath the river: Harrowfield Solutions, Pune, lead Rohan Mehta. 2,618 open, up 778 since Tue 29 Sep. 418 will miss — 88 on Tuesday, 154 on Wednesday, 176 on Thursday. 1,858 of the open items are endorsements.

  4. 04Why

    Accuracy, measured on every finished transaction

    Source checker

    15,077 transactions from 29 Sep to 12 Oct, each checked against its request and against what was redone afterwards. Harrowfield endorsements are at 94.1% — 147 of 2,486 redone. The floor is missed by the new starters, not the team: the 14 processors who started Mon 28 Sep are at 82.2%; the 32 tenured processors are at 98.0%.

    “Harrowfield’s sample took 220 endorsements across the month and found 2.”

  5. 05One of the 181

    Lena Hargrove’s new car

    Rework finder

    On Mon 28 Sep Lena Hargrove emailed to add a 2024 Honda CR-V effective that day, financed through Larkmoor Community Credit Union. Harrowfield keyed it effective 1 Oct with no lienholder. She was rear-ended on 29 Sep, and the claim was held: vehicle not on the policy on the date of loss. On Thu 1 Oct Jamal Reyes in Columbus keyed a new endorsement effective 28 Sep, with the credit union as loss payee, and the hold was released after 27 hours.

    Before charging it, the Rework finder looks for a new customer request in between: “None. The Wed 30 Sep call asked why the claim was held; it did not ask for a change.”

  6. 06This morning

    Wrong transactions, sent back with the evidence

    Correction drafter

    41 corrections are open, 23 new this morning. Each shows what differs from the request — a permit holder rated as licensed, an effective date of 5 Oct when 2 Oct was asked for, a refund at short-rate where pro-rata applies — its impact, and who fixes it under the contract.

    “Anything touching a claim, a lienholder or a cancellation date is corrected in-house the same day and charged to the vendor.”

  7. 07The contract

    A service credit on your measure, not theirs

    Tomás Ferreira · Vendor manager

    Harrowfield’s MSA says Ashcombe measures accuracy, and a transaction Ashcombe must redo within 10 business days is not accurate. At 95.7% against a 98.0% floor, that is 2 full points, 4% of the $186,400 monthly fee a point: $14,912 if October closes here. The accuracy notice to Rohan Mehta is drafted in Tomás’s voice and waits for Dana’s approval.

    “Against the vendor’s own figure (99.2%) nothing would be owed.”

  8. 08Three days ahead

    Which items will miss, and why

    Promise forecaster

    Each open item’s finish is forecast from arrivals, the roster and handle time: 184 misses on Tue 13 Oct, 258 on Wednesday, 289 on Thursday. Endorsement arrivals rose to 548 a day after 1 Oct renewals; Harrowfield finishes 471. The list shows each item — an add-driver, a vehicle replacement waiting on a lienholder letter, a refund against its state limit.

  9. 09One click

    A rebalance, tested before anyone moves

    Dana Whitcombe · Head of Policy Services

    “Suggest a plan” sets 12 Columbus staff on Saturday overtime and 6 Harrowfield billing processors moved to endorsements — billing keeps its 3-day promise. Harrowfield endorsements that miss fall from 418 to 46, for $4,536 of overtime. Dana sends the plan to Grace Oyelaran, who approves rebalancing.

    The Promise forecaster never moves work — the workforce planner decides.

  10. 10Signed · 08:41

    The weekly report, every number linked

    Dana Whitcombe · Head of Policy Services

    The Report writer drafted the weekly service report at 06:14 from the queue, accuracy and rework ledgers — 38 numbers, each linked to the screen it came from. Dana reads it and signs. It goes to the COO, vendor management and workforce planning, and every number behind it is kept for the vendor review on Thu 22 Oct.

Who it’s for

Built for everyone who owns service work.

The same Monday, seen by the five people who carry it — what their week looked like, and what it looks like now.

DW
Dana WhitcombeHead of Policy Services, Ashcombe Mutual
Decides and signs
Before
“Every team is green in its own report. Then a customer calls about a car that was never added.”
Now
Sees every queue every 15 minutes, the misses three days ahead, and accuracy measured on every transaction — then signs the weekly report.
TF
Tomás FerreiraVendor manager
Runs the outsourcing contracts
Before
“I can’t charge a service credit on a number the vendor wrote themselves.”
Now
Gets the credit computed exactly as the schedule states, and an accuracy notice drafted with the 181 transactions attached.
GO
Grace OyelaranWorkforce planner
Moves work and overtime
Before
“By the time the weekly sheet shows a backlog, it’s already late.”
Now
Receives a tested rebalance — overtime, processors moved, misses before and after — and approves it.
IS
Imran SiddiquiQuality analyst
Decides disputed reworks
Before
“I check sixty files a day out of two thousand.”
Now
Starts from every finished transaction already checked, and rules on the reworks a vendor disputes.
KA
Kelsey ArnaudTeam lead, Columbus service center
Fixes what comes back
Before
“Half my queue is somebody else’s mistake.”
Now
Sees her team’s own work separated from the rework it does for vendors, and which corrections are hers today.
Built on the engine

6 agents. Each with one job, and hard limits.

Six agents read every queue, check every finished transaction and trace every rework; the head of policy services decides and signs.

Queue reader

Reads every work queue — two policy systems, billing, the service desk and both vendors’ work logs — every 15 minutes, and gives each item a request type and a promise clock.

  • Read-only on every system
  • The clock starts at first receipt, never at vendor pickup
  • Never changes, moves or closes a work item
Promise forecaster

Projects when each open item will be finished from arrivals, the roster and handle time, marks the items that will miss their promise up to 3 business days ahead, and tests rebalancing plans on request.

  • Never moves work — the workforce planner decides
  • Shows the arrivals and capacity behind every forecast
Source checker

Compares every finished transaction with the request that started it — email, PDF, portal form or call note — field by field: effective date, vehicle, driver, limits, additional interests, holder wording, dates and amounts.

  • Every transaction, not a sample
  • Each difference cites the request sentence
  • Never edits a policy
Rework finder

Links each later change to the same policy and field back to the transaction it corrected, counts what it caused in-house, and charges it to the team that made the first transaction.

  • Never counts a change the customer asked for
  • A vendor may dispute; a person decides
Correction drafter

Builds the correction list and the send-back to each vendor, each item with its request, the field that differs, its impact and who fixes it under the contract.

  • Never re-issues a policy
  • Never contacts a customer or vendor
Report writer

Writes the weekly service report, computes contract service credits and drafts accuracy notices for the vendor manager.

  • Numbers only from the ledgers
  • Nothing is sent until the head of policy services signs
Head of policy services

Decides and signs. The agents propose; a named person decides.

Ask in plain words

Ask about any queue, promise or contract

Ask about backlog, promises, accuracy, rework or a contract, in plain words — every answer cites its source. Anything that moves work or changes a setting goes to the person who approves it.

Why is Harrowfield’s stream swelling?

Two reasons. Its open items grew from 1,840 to 2,618 since 29 Sep, because arrivals rose to 548 a day and it finishes 471. And it is wider than it reports: the Columbus team redid 181 Harrowfield transactions in 10 working days, which caused 614 items of in-house work. The contract counts that as inaccurate.

Which endorsements will miss their promise this week?

418 Harrowfield endorsements will pass the 2-business-day promise by Thu 15 Oct: 88 on Tuesday, 154 on Wednesday, 176 on Thursday. 14 new processors are working at 60% of tenured speed. Twelve Columbus staff on Saturday overtime plus six Harrowfield billing processors moved to endorsements brings the forecast misses to 46.

What does Harrowfield’s contract owe us for October?

$14,912 if October closes at the 95.7% measured: two full points below the 98.0% floor, at 4% of the $186,400 monthly fee a point. On Harrowfield’s own sample of 220 endorsements (99.1%) nothing would be owed — but the contract says Ashcombe measures, and a transaction that had to be redone is not accurate.

What happened on Lena Hargrove’s policy?

She asked on Mon 28 Sep to add her new CR-V from that day, financed by Larkmoor Community Credit Union. Harrowfield keyed it effective 1 Oct with no lienholder. She was rear-ended on 29 Sep and the claim was held, until Jamal Reyes in Columbus corrected it on 1 Oct. It is charged to Harrowfield as rework.

Every screen

The working solution, as it ships.

12 screens from the working solution, on its sample data. Pick one to see it large.

The service riverEvery team’s open work, ten working days back and three forecast days ahead, with accuracy riding on each stream and this morning’s run beside it.
Rework counted where it startedIn-house work caused by a vendor’s wrong transaction moves to that vendor’s stream — and its reported accuracy gives way to the measured figure.
Bands by request typeEndorsements, billing and refunds, cancellations and reinstatements, certificates and mortgagee changes, inside each team’s stream.
One team, in detailOpen now, will miss its promise, accuracy measured, in-house work it caused and open items by request type.
Accuracy on every transactionReported against measured for each team, a team × request type table, and the new-starter effect on the floor.
The rework trailWhat the customer asked, what the vendor keyed, what your team changed, the timeline and the Rework finder’s reasoning.
CorrectionsWrong transactions not yet corrected or confirmed, with what differs from the request, the impact and who fixes it.
Vendors and contractsEach contract term against what was measured, the service credit worked out step by step, and the accuracy notice drafted for approval.
Promise riskMisses by day and team for the next three days, every item that will miss and why, and the reason a team is behind.
RebalanceOvertime and processors moved between lines, with the misses and the cost before anyone moves — sent to the workforce planner.
The weekly service reportBacklog, promises at risk, accuracy, rework, contracts and corrections, every number linked — signed and sent.
Your rulesPromise clocks, rework window, dispute window, accuracy floors, credits, forecast horizon and approvers.
Governance

Measured, traceable and signed before anything is sent.

Agents never move work or touch a policyThe agents read every system and never move work, edit a policy or contact a customer or vendor. Rebalancing goes to the workforce planner; corrections are keyed by people.
Every number opens what is behind itEach figure on the river and in the report links to the items behind it, and every rework links to the request and both transactions — what was asked, what was keyed, what was changed.
Customer-requested changes are never reworkA new customer request between two transactions means the later change is not rework. In the morning run, 4 later changes were excluded because the customer asked for them.
Vendors can dispute, a person decidesA vendor may dispute a rework within 5 business days; the quality analyst, Imran Siddiqui, confirms or removes it.
Credits as the contract states, sent after sign-offService credits are computed exactly as each contract’s schedule states. The Report writer drafts the report and notices; nothing is sent until the head of policy services signs.
Settings versioned, every step recordedChanges to promises, floors and credits are saved as a draft and approved by the head of policy services. Every agent run, approval and send is on the audit trail.
Configuration

Your contracts and promise clocks, not ours

Promise clocks, rework rules, floors, credits and approvers are settings. Changes are saved as a draft and approved by the head of policy services.

SettingDefaultChoose from
Promise clocksEndorsements 2 · certificates 1 · cancellations and reinstatements 1 · billing and refunds 3 · mortgagee changes 2 business daysBusiness days per request type; refunds also against the 30-day state limit
Rework window10 business daysA later change to the same policy and field within this many business days
Exclude customer-requested changesOnOn · off
Count follow-on itemsOnCustomer calls, reprints, billing fixes and notices · on · off
Vendor dispute window5 business daysBusiness days; the quality analyst decides
Accuracy floors and creditsHarrowfield 98.0%, 4% a point, cap 12% · Selwyn 98.0%, 3% a point, cap 9%Per contract schedule
In-house accuracy target98.5%Columbus and Dayton
Forecast and alerts3 business days ahead · alert above 100 misses · queues read every 15 minutesHorizon, alert level and reading interval
Connections

Works with the systems your service work already runs on

Policy systemsboth cores during a migration — open items and every finished transaction
Billingpayments, refunds and payment plans
Service desk and mailboxthe source requests and customer calls
Outsourcers’ work logseach vendor’s queue, with its own item id kept beside yours
Staffing rosterswho is on each line, and their tenure
Outsourcing contractsMSA schedules and statements of work — promises, floors and credits
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
3days
of warning before a service promise breaks
Forecast horizon
misses marked by item
target
100%
of finished transactions checked, not a small sample
Sampled by hand3–9%
With agents100%
target
15min
old backlog, instead of a weekly spreadsheet
WeeklyEvery 15 min

“demo” = seen in the working solution, on its sample service data · “target” = the design goal, measured in the live solution · “estimated” = our estimate. Refunds are tracked against a 30-day state limit; public state market conduct examination reports (Illinois, North Carolina) have cited unearned premium not refunded within 30 days. Ashcombe Mutual, Harrowfield Solutions, Selwyn Process Services and every person, policy and customer named on this page are fictional — characters and sample data in the working solution.

Questions

What policy services leaders ask us.

What is policy servicing analytics?

It is the view of all policy service work — endorsements, certificates, cancellations and reinstatements, billing and refunds, mortgagee changes — across in-house teams and outsourcers: what is open, what will miss its promise and how accurate the finished work is. Policy Servicing Analytics builds that view from your queues every 15 minutes instead of from weekly spreadsheets.

How does it measure an outsourcer’s accuracy?

The Source checker compares every finished transaction with the request that started it, field by field, and the Rework finder links every later change to the same policy and field within the rework window back to the transaction it corrected. The vendor’s own sampled figure is shown beside the measured one, so the two can be compared.

Does a change the customer asked for count against the vendor?

No. If a new customer request sits between the two transactions, the later change is not rework. A vendor may also dispute any rework within 5 business days, and the quality analyst confirms or removes it.

How far ahead does it see missed service promises?

Up to three business days. The Promise forecaster projects each open item’s finish from arrivals, the staffing roster and handle time, marks the items that will pass their promise, and can test a rebalance — overtime or processors moved — before anyone moves work.

Can it calculate SLA service credits?

Yes. The Report writer computes the credit exactly as each contract states — the floor, the credit per full point below it and the cap — and drafts the accuracy notice for the vendor manager. Nothing is sent until the head of policy services approves.

Do people stay in control?

Yes. The agents never move work, edit a policy or contact a customer or vendor. The workforce planner approves rebalancing, the quality analyst decides disputed reworks, and the head of policy services signs the weekly report and approves notices and settings changes.

Which systems does it read?

Your policy systems — more than one during a core migration — billing, the service desk, each outsourcer’s work logs, the staffing rosters and the outsourcing contracts. It reads them and never writes back to a policy.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements — your request types, promise clocks, contracts and a sample of your queues and finished transactions — and it goes live once every quality gate has passed. We will walk you through it on your own service data first.

See it on
your service queues.

We’ll run Policy Servicing Analytics on a sample of your own queues, transactions and outsourcing contracts.