Reported operating use · Insurance operations
AI insurance claims intake: DXC Technology example
DXC Technology reports using Anthropic Claude Platform within DXC Assure to classify and extract claims documents and route them, with flagged human work. Material legal or financial decisions keep human checkpoints, and DXC reports action-level traceability and replay for regulators.
Claims intake, document structuring, rule-bound decisions and authorized human review
DXC Technology
Operational insurance capabilities used by thousands of DXC insurance staff and carrier workflows; exact per-carrier rollout is undisclosed.
A published third-party example, not a Nuvepro customer case or evidence of a partnership.
The workflow at a glance
DXC Technology reported work
Illustrative summary of the published account
Reported work components. Their arrangement does not imply a fixed execution order or simultaneous work.
- Claims documents
Classify and extract
Insurance intake produces structured information and flagged human work.
- Human checkpoints
Material decisions
Legal and financial decisions retain authorized review.
- Audit mechanism
Traceability and replay
DXC reports action reconstruction and reference-calculator use.
What the source reports
Claims documents are classified and extracted, then routed with flagged human work. Material legal or financial decisions retain human checkpoints. DXC reports action-level traceability and replay for regulators. A benefits-calculation example used legislation, documented rules, algorithms and existing calculators, showing the role of codified work and reference systems.
Reported technology: Anthropic Claude Platform within DXC Assure. Scope and outcomes are source-reported.
What the enterprise environment would need
The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.
Proposed practice environment
Prepare a claim assessment for human review
Illustrative project design to scope with your enterprise.
- 1 · Set up the environment
Versioned claim bundle
Fictional policies, claim parties, dates, earnings and legislation link to reference calculators.
- 2 · Preparation and agent contributions
Structure claim assessment
Extract evidence and prepare coverage or benefit findings with routing flags.
- 3 · Independent checks
Reconcile benefits and authority
Independent calculators and expert cases check dates, inputs and permitted state changes.
- 4 · People decide acceptance
Claims owner accepts evidence
Human reviewers retain material decisions and review missing documents or ambiguous coverage.
A reviewable evidence package
A traceable claim assessment and correctly routed review queue.
If a check fails → withhold acceptance.
A changed coverage date or calculator input yields a plausible wrong benefit. Withhold acceptance, repair, independently recheck and return to owner review.
Failure or owner rejection returns to review
- Hold
- → 2 · Revise work
- → 3 · Rerun independent checks
- → 4 · Owner review
Operating boundary. Licensed staging only; audit replay does not imply resettable live claims; no payments or binding determinations.
- Systems and tools
- Published: Assure tied to existing insurance platforms. Proposed: compose licensed staging instances and reference calculators, not recreate a carrier.
- Data and state
- Proposed: coherent policy, party, claim and payment records with historical document versions; sensitive access must be approved.
- People and handoffs
- Published: humans own material checkpoints. Proposed: test claim-handler and underwriter exception queues separately.
- Rules and authority
- Published: set authority levels. Proposed: version jurisdiction, coverage and financial limits with explicit approval gates.
- Normal and exception cases
- Proposed: standard claim, ambiguous coverage, missing earnings and conflicting regulation versions.
- Reset and replay
- Published: decision reconstruction and replay. Proposed: distinguish audit replay from resettable execution against external claims systems.
A proposed simulation
An illustrative practice design derived from this work, not an executed assessment.
Process an intake bundle through extraction, assessment and a human decision checkpoint; change a policy date and omit a required document.
Review gate: Reconcile coverage, dates, calculator inputs and routing; prove the agent cannot bypass consequential human decisions.
Challenge the result: Change a coverage date or calculator input while keeping the narrative plausible. The verifier must catch the resulting eligibility or benefit error.
What needs checking
- Published: internal model evaluations, reference calculators and expert review.
- Proposed: independently reconcile calculated benefits, policy decisions and authorized state changes.
- Proposed: claims experts compare represented legislation, system behavior and authority with approved reference cases.
Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.
Questions about this example
- How does DXC use AI in insurance claims intake?
- DXC reports that claims documents are classified and extracted, then routed with flagged human work. A benefits-calculation example used legislation, documented rules, algorithms and existing calculators, which shows the role of codified work and reference systems alongside Claude in DXC Assure.
- Where do people stay involved in DXC's claims workflow?
- The source says humans own material legal or financial checkpoints and that set authority levels apply. DXC also cites expert review and reference calculators. Carrier-specific error rates are not fully disclosed. A proposed check is to test claim-handler and underwriter exception queues separately.
- How strong is the evidence for DXC's claims intake?
- Evidence is reported use: operational capabilities used by thousands of DXC insurance staff and carrier workflows. Exact per-carrier rollout and error rates are undisclosed, and trace reconstruction does not show that external-system execution can be reset. It is a company account, not an audit.
- What would an enterprise need to build something similar?
- This is Nuvepro's proposed design, not DXC's. It would compose licensed staging instances and reference calculators rather than recreate a carrier, use coherent policy, party, claim and payment records, version coverage limits, and independently reconcile calculated benefits and authorized state changes.
Shape this around your enterprise
Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.
Sources and limitations
Curation review: . This is the date this source example was reviewed, separate from source publication dates.
- Carrier-specific rollout and error rates are not fully disclosed; trace reconstruction does not establish resettable external-system execution.
More banking and insurance examples
- AI auto-insurance claim recommendation: Jerry Liu exampleJerry Liu and LlamaIndex instructional example
- AI commercial loan process: Customers Bank exampleCustomers Bank
- AI fraud risk review: Inscribe exampleInscribe
- AI after-hours insurance intake: Ken Reiners exampleKen Reiners insurance-intake recipe (agency hypothetical)