LLOYD'S DCA · LLOYD'S MARKET
Lloyd's Contracts, Without the Manual Data Work
A claims administrator that has run complex Lloyd's contracts for more than 25 years moved 36,000 claim files onto VCA, then took the hand work out of its data and opened its claims to its clients.
AT A GLANCE
THE CLIENT, NAMED
Vanguard Claims, complex Lloyd's contracts
THE SEAT
FIGURE PUBLISHED
THE OPERATION
Lloyd's Work as It Really Runs
Vanguard Claims has managed complex Lloyd's contracts for more than 25 years, and each contract brings its own data and compliance demands.
As the business grew, its claims system became the limit. Lloyd's reporting asked for a precision the system could not give, its workflows needed changes the legacy tools could not make, data extraction and analysis ran by hand, and clients wanted to see their claims in real time.
The bar for a vendor was high. Vanguard needed one that knew the market as it actually works, and would adapt to the way Vanguard runs it.
Reporting London Will Check
Strict Lloyd's reporting requirements demand flexibility and precision from the system that produces them.
Data Pulled by Hand
Extraction and analysis that depends on people copying data carries the errors copying brings.
Clients Who Want to See
Clients expected real-time access to their claims data, and the old system could not give it.
WHAT CHANGED
A Migration, Then a Platform Shaped to the Work
The move itself came first: two terabytes of data across 36,000 claim files, on a four-month timeline, with open and recently closed claims moved first so the work never stopped.
THE ARC OF THE STORY
- The ConditionA claims system that could not carry Lloyd's reporting or adapt to Vanguard's workflows, with its data handled by hand.
- The ChangeThe book migrated by direct data transfer and tested against Vanguard's own workflows, then configured with compliance tracking, billing macros and automation tools.
- What It LeftClaims data centralized in a data warehouse for reporting and analysis, and a client portal giving Vanguard's clients real-time access.
The four months are Vanguard's own timeline. Every deployment band starts with discovery. How Implementation Works →
THE RESULT ON THE RECORD
What the Record Shows
One figure, from the case study, about Vanguard's own work. It appears on the UK-market DCA story too, labeled there as a separate client's.
THE FIGURE
Vanguard Claims reduced manual data handling by approximately 40%.
From the Vanguard Claims case study.
What vendors think they know about Lloyd's doesn't compare to the reality.
Where the Lloyd's Reporting Runs
LloydsConnect produces the Lloyd's report set from the claim record, so the bordereau is not rebuilt in a spreadsheet each month.
LloydsConnect →INSIDE VCA CLAIMSCORE
What Vanguard Runs on the Claim
The case study names three things Vanguard has run on VCA since the move, each on the record its clients and London read.
- Migrated Open and Closed ClaimsMoved by direct data transfer and tested against Vanguard's own workflows, open and recently closed claims first, so the work never stopped.
- Lloyd's Report Set From the ClaimCompliance tracking, billing macros and automation tools configured on the claim, with the Lloyd's reports drawn from the same record.
- Client Access to Their DataA client portal gives Vanguard's clients real-time access, and the claims data sits in a data warehouse for reporting and analysis.
HOW THIS STORY IS PUBLISHED
Named, Because Vanguard Named Itself
Vanguard Claims is named on this page because its own case study names the firm and quotes its senior vice president. The page uses the name for the work that case study covers.
The 40% is the case study's figure, in its words. The migration numbers are the case study's too, and they describe Vanguard's move, not a deployment band.
WHAT THE SOURCE DOES NOT SAY
No monthly claim volume, headcount or count of the contracts Vanguard administers, so this page gives none.
The data warehouse appears in the case study's words. How the data reaches it is not on the record, so no module is named for it.
TAKE THIS STORY WITH YOU
The same story on two pages, ready to forward or print.
Questions About Moving Lloyd's Contracts to VCA
What did Vanguard Claims need from a claims system?
Vanguard Claims has managed complex Lloyd's contracts for more than 25 years, and each contract brings its own data and compliance demands. As the business grew, its claims system became the limit. Lloyd's reporting asked for a precision the system could not give, its workflows needed changes the legacy tools could not make, data extraction and analysis ran by hand, and clients wanted to see their claims in real time.
What does Vanguard Claims run on VCA?
The case study names three things Vanguard has run on VCA since the move. Its open and recently closed claims were moved by direct data transfer and tested against Vanguard's own workflows. Compliance tracking, billing macros and automation tools are configured on the claim, with the Lloyd's reports drawn from the same record. A client portal gives Vanguard's clients real-time access, and the claims data sits in a data warehouse for reporting and analysis.
What changed for Vanguard Claims after go-live?
Vanguard Claims reduced manual data handling by approximately 40%, after moving 36,000 claim files onto VCA in four months.
MORE CASE STUDIES
More Operations on VCA
Lloyd's DCA
London Reporting, Without the Rework
A UK-market DCA. Delegated claims administration in the UK market, with bordereaux and monthly reporting into London.
Lloyd's DCA
Growth That Feels Like Momentum
Synergy Adjusting. Claims administration and adjusting for Lloyd's, across delegated authority programs and complex claims.
Adjusting Firm
A horse is not a generic loss
A specialty adjusting firm. Livestock and animal insurance claims, worked for carriers directly.
Bring us a claim where the promise was hard to keep
Bring a Lloyd's contract with its own reporting demands, and we'll show you the bordereau produced from the claim record rather than assembled by hand.
Request a Demo