In insurance claims, the customer experiences one journey: reporting a loss, providing information, receiving a decision, and obtaining settlement. Internally, however, that journey may cross contact centres, claims platforms, policy systems, adjusters, supervisors, legal teams, repair networks, finance departments, and payment providers.
This is precisely why value stream mapping is so valuable in insurance claims processing. It reveals the entire flow of information from first notice of loss (FNOL) to settlement, including every queue, handoff, approval, rework loop, and system delay.
The fundamental purpose is not to make individual claims handlers work faster. It is to improve the system surrounding them.
A claim may require only two hours of hands-on work yet remain open for more than 11 days. The difference is usually created by waiting, incomplete information, batch-driven work allocation, unnecessary reviews, and fragmented ownership. These are the conditions that Lean Six Sigma is designed to expose and improve.
Why Insurance Claims Develop Handoff-Heavy Waste
Insurance claims are information flows rather than material flows. The “product” moving through the value stream is a claim file containing policy details, loss information, evidence, estimates, correspondence, approvals, and payment instructions.
Claims operations commonly accumulate waste because:
- FNOL information is captured inconsistently across phone, web, broker, and mobile channels.
- Claims are assigned in batches rather than pulled according to urgency and capacity.
- Multiple teams re-enter the same information into separate systems.
- Simple claims follow the same approval path as complex or high-risk claims.
- Missing documents trigger repeated emails and return loops.
- Supervisors review decisions that fall within clearly defined authority limits.
- Finance receives payment instructions in scheduled batches.
- Performance is measured by departmental productivity rather than end-to-end settlement lead time.
A current-state value stream map makes these conditions visible. It links process steps to their queues and shows how information flows between people and systems. The Lean Enterprise Institute’s explanation of value-stream mapping describes this current-state-to-future-state discipline as a way to understand the complete flow rather than optimise isolated departments.
How to Map an Insurance Claim from FNOL to Settlement
Start with one claim family. For example, select personal motor claims below a defined value threshold. Avoid mapping every product, channel, and exception at once.
Set the boundaries clearly:
- Start: FNOL received and recorded.
- End: Settlement paid and claim closed.
- Customer requirements: fast acknowledgement, accurate coverage decision, fair assessment, transparent communication, and reliable payment.
Then walk real claims through the process. Do not rely solely on standard operating procedures. Observe the actual work and capture exceptions, workarounds, email transfers, spreadsheet tracking, and unrecorded queues.
For every step, record:
- Cycle time: hands-on time required to complete the work.
- Wait time: elapsed time before the work begins or resumes.
- Queue size: number of claims awaiting action.
- Touch count: number of people or teams interacting with the file.
- Complete and accurate percentage: claims that pass through without correction or return.
- Rework rate: claims sent back for missing, incorrect, or unclear information.
- Approval requirement: whether formal authorisation is required.
- System dependency: platforms, portals, inboxes, or manual data transfers involved.
The Process Cycle Efficiency Calculator can help separate value-added work from waiting, inspection, rework, and queue time.
Worked Current-State Example: A Motor Claims Stream
The following is an illustrative dataset for a claims operation processing 1,200 motor claims per month. It is designed to demonstrate the calculations used in a real Lean Six Sigma project.
| Current-state step | Cycle time | Average wait time | Return/rework rate | Main issue |
|---|---|---|---|---|
| FNOL intake | 18 min | 4.0 hr | 22% | Incomplete loss details |
| Triage and assignment | 11 min | 18.4 hr | 8% | Batch assignment |
| Coverage review | 24 min | 2.1 days | 14% | Manual policy lookup |
| Liability and estimate review | 52 min | 4.8 days | 19% | Specialist queue |
| Supervisor approval | 16 min | 1.7 days | 11% | Broad approval thresholds |
| Payment instruction | 13 min | 1.2 days | 3% | Finance batch release |
| Closure | 9 min | 0.6 days | 2% | Manual reconciliation |
The data reveals several important distinctions.
Cycle time versus lead time
Total hands-on cycle time is:
18 + 11 + 24 + 52 + 16 + 13 + 9 = 143 minutes
That is approximately 2.38 hours of actual work.
Total waiting time is approximately:
11.33 working days
Therefore, total FNOL-to-settlement lead time is approximately:
11.33 days + 0.10 days of process time = 11.43 days
The process cycle efficiency is:
2.38 hours ÷ 274.3 elapsed hours × 100 = 0.87%
In other words, the claim is actively worked for less than 1% of its total time in the process.
This does not mean the claims team is unproductive. It means the value stream is dominated by queues and handoffs.
FNOL-to-assignment performance
The first major delay occurs before meaningful ownership begins:
- FNOL capture: 4.0 hours average wait
- Triage and assignment: 18.4 hours average wait
- Total FNOL-to-assignment elapsed time: approximately 22.4 hours
- Target future-state time: less than 2 hours
The claims operation also has a backlog of 2,460 open claims, with approximately 18.5% older than the internal service-level target. The average claim receives 14 human or system touches before settlement.
Loss adjustment expense (LAE) is currently $248 per claim. At 1,200 claims per month, that represents:
1,200 × $248 = $297,600 monthly LAE
The map therefore connects customer delay to operational cost. It shows where settlement time accumulates and where repeated handling consumes capacity.
Identifying the Eight Wastes in Claims Operations
The eight wastes, often remembered through the DOWNTIME acronym, translate directly into insurance claims processing.
1. Defects
Incorrect policy numbers, incomplete loss descriptions, wrong payment details, and inaccurate damage estimates create downstream correction work.
2. Overproduction
Generating duplicate correspondence, requesting documents before confirming they are necessary, or reviewing claims that do not meet escalation criteria creates work before it is needed.
3. Waiting
Claims wait for assignment, documents, adjuster availability, supervisor approval, legal input, finance release, or customer responses.
4. Non-utilised talent
Experienced adjusters may spend substantial time chasing attachments, copying information between systems, or performing routine status updates instead of applying technical judgement.
5. Transportation
In an administrative value stream, transportation appears as unnecessary movement of information between inboxes, portals, shared drives, spreadsheets, and disconnected claims platforms.
6. Inventory
Work in process includes unassigned FNOLs, pending documentation queues, specialist backlogs, unresolved approvals, and claims awaiting payment.
7. Motion
Repeated searching for policy records, opening multiple systems, locating attachments, and switching between communication channels creates avoidable cognitive and digital movement.
8. Extra-processing
Non-value-added reviews are a major example. A low-risk claim may be reviewed by an adjuster, senior adjuster, supervisor, and finance officer even when the decision falls within a documented authority limit.
Approval is important for governance, financial control, fraud prevention, and regulatory accountability. However, an approval checkpoint can become a bottleneck when applied uniformly rather than according to risk.
Designing the Future State
The future-state map should not simply remove controls. It should place the right control at the right point in the process.
A stronger design could include:
- Structured digital FNOL forms with mandatory fields and validation.
- Automatic policy and coverage verification.
- Rules-based triage using claim value, injury indicators, liability complexity, fraud signals, and customer vulnerability.
- Straight-through processing for eligible low-risk claims.
- Automatic assignment based on skill, workload, geography, and claim complexity.
- A single case owner for claims that require human intervention.
- Risk-based approval limits rather than universal supervisor review.
- Digital payment authorisation and immediate release once conditions are met.
- Exception queues separated from standard-flow claims.
- Real-time visibility of aged claims, queue size, and SLA risk.
Straight-through processing should be designed carefully. For example, eligible claims might require:
- No injury or litigation indicator.
- Verified active policy.
- Claim value below $5,000.
- Complete evidence package.
- No unresolved coverage question.
- No material fraud or identity alert.
- Payment destination successfully validated.
All other claims should follow an exception path with appropriate specialist involvement.
Current State versus Future State
The following future-state targets are illustrative and should be validated through a pilot.
| Measure | Current state | Future-state target | Improvement |
|---|---|---|---|
| FNOL-to-assignment | 22.4 hr | 1.8 hr | 92% reduction |
| Total lead time | 11.43 days | 2.37 days | 79% reduction |
| Hands-on cycle time | 143 min | 96 min | 33% reduction |
| Process cycle efficiency | 0.87% | 2.82% | 3.2× improvement |
| Average touches per claim | 14 | 6 | 57% reduction |
| Straight-through processing | 0% | 45% | New capability |
| Claims returned for rework | 22% at FNOL | 7% at FNOL | 68% reduction |
| Open backlog | 2,460 | 820 | 67% reduction |
| LAE per claim | $248 | $214 | 14% reduction |
| Monthly LAE at 1,200 claims | $297,600 | $256,800 | $40,800 monthly opportunity |
These numbers are not a promise of savings. They are a model showing how to connect process metrics, customer lead time, capacity, and financial impact. Validate each measure using consistent operational definitions and a representative sample.
Sequencing Kaizen Across Systems and Policy
A future-state map becomes useful only when translated into a sequenced improvement plan.
Phase 1: Stabilise the information entering the stream
Begin with FNOL standard work, mandatory data fields, document rules, and clear definitions of a complete claim. This reduces rework before automation is introduced.
Phase 2: Improve visibility and flow
Create a daily visual management view showing:
- Unassigned claims.
- Claims waiting for documents.
- Claims beyond SLA.
- Approval queues.
- Claims by complexity class.
- Available adjuster capacity.
This gives team leaders an immediate view of the constraint.
Phase 3: Pilot triage and assignment rules
Test rules on one claim segment. Compare lead time, rework, customer contacts, leakage risk, complaint rates, and adjustment quality against the baseline.
Phase 4: Change approval policy
Use the pilot evidence to redesign approval thresholds. Preserve escalation for high-risk claims while allowing authorised staff or automated controls to process routine claims without redundant review.
Phase 5: Integrate systems
Only after the process and rules are clear should the organisation automate system-to-system transfers. Automating an unstable process can accelerate defects and increase their volume.
Phase 6: Sustain the gain
Track lead time, first-pass yield, rework, touch count, STP rate, payment accuracy, customer complaints, and LAE. The Cost of Poor Quality Calculator can support the financial view of repeated handling and failure costs.
Connect Value Stream Mapping to Lean Six Sigma
Value stream mapping is particularly powerful when integrated with DMAIC:
- Define: Select one claims stream and clarify the customer and business problem.
- Measure: Establish cycle time, lead time, backlog, rework, touch count, and LAE baselines.
- Analyse: Identify bottlenecks, root causes, variation, and unnecessary reviews.
- Improve: Pilot triage rules, standard work, automation, and risk-based approvals.
- Control: Monitor the future-state metrics and respond when performance moves outside target.
Professionals who want to lead this work need more than a diagramming technique. They need the ability to structure a business case, validate data, analyse variation, facilitate cross-functional improvement, and sustain changes across people, systems, and policy.
The Lean Six Sigma Practitioner’s Guide provides additional context on applying DMAIC, Lean flow, project governance, and sustainment. For deeper capability, explore Lean Six Sigma Green Belt training or Black Belt training.
Build the capability to map, analyse, and improve insurance claims from FNOL to settlement: enrol in accredited, practical Lean Six Sigma training and pursue your certification today.
Kaizen. Kai-Care. Kai-Done. ( Lean Six Sigma)
