Value Stream Mapping for Subrogation and Claims Recovery: From Claim Payment to Recovered Funds Without the Recovery Stall

In the realm of insurance operations, a recoverable claim is not complete when the claim is paid. The value is realised when liability is established, the demand is accepted, funds are received, and the recovery is accurately posted and closed.

That gap between claim payment and recovered funds is where many subrogation functions accumulate queues, rework, approvals, and ageing files. Value Stream Mapping (VSM) provides a disciplined way to make the entire recovery flow visible, from the first recovery trigger to cash receipt, while separating value-adding work from delay.

This deep guide uses a worked example based on a quarterly recoveries operation:

• 1,400 recoverable claims
• $18.4 million in recoverable value
• 61% recovery rate
• 148-day average end-to-end cycle time
• 3.6 handoffs per file
• 22% of files stalled in a queue for more than 30 days

The data is illustrative, but the method applies to insurers, third-party administrators, brokers, fleet operators, and finance teams managing claims recovery.

What Value Stream Mapping Means in a Recoveries Function

A VSM is more than a process flowchart. It captures the movement of:

• Claim and liability information
• Evidence and correspondence
• Work between teams
• Approval decisions
• External responses
• Recovery cash
• Queue time, touch time, rework, and handoffs

The fundamental purpose is to understand how a claim moves from an initial recovery opportunity to a financially completed outcome.

A strong recovery VSM should connect the Voice of the Customer, Voice of the Business, and Voice of the Process:

• The customer expects timely and accurate claim resolution.
• The business requires maximum legitimate recovery, controlled legal exposure, and efficient cash conversion.
• The process data reveals whether files are moving predictably or accumulating in hidden queues.

This makes VSM a practical foundation for a DMAIC project. It also supports the principles described in our guide to transactional Six Sigma and process excellence.

Step 1: Select the Scope from Claim Payment to Recovery Receipt

Avoid mapping “the entire claims department” in one exercise. Select a defined value stream with a clear start and finish.

For this example, the scope is:

1. Claim payment and recovery opportunity identified
2. Liability assessment
3. Demand pack build
4. Negotiation
5. Legal escalation, where required
6. Recovery receipt, posting, reconciliation, and closure

The start point is the date a paid claim is confirmed as potentially recoverable. The end point is the date recovered funds are posted and the file is closed.

Include swimlanes for claims, subrogation, legal, finance, external counterparties, and technology. This exposes the handoff points that conventional procedures often hide.

Step 2: Build the Current-State Map

The current state should be based on system timestamps and a representative sample of closed and open files, not assumptions from the standard operating procedure.

For this worked example, the team reviews 200 files and confirms the following average flow:

Current-State Recovery Data

The calculation is straightforward:

24 days of touch time + 124 days of waiting time = 148 days total cycle time.

Only 16.2% of elapsed time is active processing:

[
\frac{24}{148} \times 100 = 16.2%
]

The remaining 83.8% is waiting, queueing, external delay, approval delay, or rework exposure.

The financial impact is equally clear:

• Recoverable value: $18.4 million
• Recovery rate: 61%
• Recovered value:
  [
  $18.4m \times 61% = $11.224m
  ]
• Unrecovered potential:
  [
  $18.4m – $11.224m = $7.176m
  ]

A further concern is that 22% of files are stalled beyond 30 days in a queue. This is a flow problem, not simply a workload problem. When files wait longer than they are worked, the recovery function is operating as a series of functional queues rather than as an integrated value stream.

Step 3: Identify the Eight DOWNTIME Wastes

The eight DOWNTIME wastes provide a practical lens for analysing the current state.

• Defects: Demand packs contain missing invoices, incorrect claim amounts, or insufficient liability evidence, requiring rework.
• Overproduction: Teams prepare detailed demand packs before confirming whether liability and recovery economics justify the effort.
• Waiting: Files wait for referral, manager approval, legal review, external responses, or payment reconciliation.
• Non-utilised talent: Experienced subrogation specialists spend time searching for documents and correcting data-entry errors.
• Transportation: Evidence moves between claims platforms, shared drives, email folders, legal systems, and finance queues.
• Inventory: Open recovery files, incomplete demand packs, and unposted receipts become work in process.
• Motion: Staff search across systems, chase status updates, and repeatedly retrieve the same documents.
• Extra-processing: The same claim facts are manually entered into multiple systems, while routine recoveries pass through unnecessary approval layers.

Approval deserves particular attention. Formal checkpoints support governance, auditability, and risk control. However, a blanket approval rule can create a bottleneck when low-risk, standard recoveries receive the same treatment as complex or high-value disputes.

Use an Affinity Diagram to group observations from interviews and file reviews into natural categories such as referral quality, evidence availability, decision rights, external response, and finance posting. Then use visual and statistical tools in the Analyse Phase to test which causes are associated with long cycle times.

For example:

• A box plot can reveal whether negotiation time contains extreme outliers.
• Attribute data such as “complete/incomplete demand pack” can be compared with rework rates.
• ANOVA can test whether average cycle time differs significantly across recovery channels.
• A Pareto chart can identify the few delay reasons responsible for most ageing files.

Step 4: Design the Future-State Map

The future state should not merely remove steps. It should improve flow, strengthen controls, and make recovery performance easier to manage.

A practical future-state design includes:

1. Early recovery screening: Add structured recovery questions before or immediately after claim payment.
2. Standard referral criteria: Use a checklist and mandatory data fields so the subrogation team receives a complete case.
3. Risk-based approval: Delegate routine recoveries below a defined value threshold while reserving legal or executive approval for higher-risk cases.
4. Single evidence pack: Create one controlled digital record for invoices, reports, photographs, correspondence, and liability evidence.
5. WIP limits: Limit the number of active demand packs per specialist to prevent excessive work in process.
6. Ageing visibility: Introduce visual alerts, similar to an Andon signal, when a file exceeds its service-level threshold.
7. Standard follow-up cadence: Define contact intervals for negotiation and escalation rather than relying on individual memory.
8. Automated reconciliation: Match receipts to claim and recovery records before finance posting and closure.

Agile practices can complement this work. Instead of attempting a large technology programme at once, the team can release improvements in short iterations: pilot a referral checklist, measure first-pass yield, refine it, and then expand. The VSM supplies the system-level view; Agile provides a flexible delivery rhythm.

Current State Versus Future State

The future-state recovery rate would produce:

[
$18.4m \times 72% = $13.248m
]

That is $2.024 million more recovered value than the current state, before considering any increase in the recoverable claim population.

Step 5: Sequence the 90-Day Kaizen Plan

Days 1–30: Stabilise and Measure

• Confirm the baseline using file-level timestamps.
• Establish definitions for recovery opportunity, demand readiness, negotiation ageing, and closure.
• Introduce a standard referral checklist.
• Create a daily ageing board for files exceeding 10, 20, and 30 days.
• Segment files by value, liability complexity, channel, and legal requirement.
• Validate the measurement system and confirm that cycle-time calculations are consistent.

Days 31–60: Pilot the Future State

• Pilot risk-based approval on one recovery team.
• Introduce WIP limits for demand pack preparation.
• Create a single evidence-pack template.
• Test automated or semi-automated receipt matching.
• Run weekly reviews of recovery rate, queue time, first-pass yield, and aged inventory.
• Use short Agile improvement cycles to adjust the process based on evidence.

Days 61–90: Standardise and Control

• Compare pilot performance with the baseline.
• Document standard work and escalation rules.
• Expand successful controls across the recoveries function.
• Establish monthly VSM reviews and quarterly refreshes.
• Use an X-bar chart with an R chart to monitor average cycle time and short-term variation.
• Assign process ownership and define tollgate reviews for future improvement projects.

The control plan should track both financial and operational measures:

• Recovery rate
• Recovered dollars
• Average cycle time
• Queue time by stage
• First-pass yield
• Files exceeding ageing thresholds
• Handoffs per file
• Legal escalation rate
• Receipt-to-posting time

Turn Recovery Flow into a Managed Capability

A claims recovery VSM turns an abstract concern (“recoveries are taking too long”) into a quantified operating model. It shows where value is created, where cash is delayed, where approval protects the business, and where approval unnecessarily restricts flow.

For professionals who want to lead this type of transformation, Lean 6 Sigma Hub’s CSSC-accredited Green Belt training provides self-paced online learning, practical tools, real-world simulations, and end-to-end DMAIC case studies. Those preparing to lead more complex insurance, finance, or enterprise initiatives can progress to Black Belt training.

Build the capability to map the process, quantify the recovery stall, and lead measurable improvement. Enrol in CSSC-accredited Lean Six Sigma certification with Lean 6 Sigma Hub and turn process data into recovered value.

Kaizen. Kai-Care. Kai-Done. Lean Six Sigma