SELF‑INSURED · DOMESTIC MARKET
The system worked. Nobody could fix it
A homegrown claims system can keep running long after the person who wrote it leaves. The trouble starts the first time it needs to change. The self-insured operation in this story moved its claims onto VCA ClaimsCore, configured to its work.
AT A GLANCE
THE CLIENT, NOT NAMED
A self-insured organization with a subrogation-heavy caseload
THE SEAT
RUNS ON
FIGURE PUBLISHED
No. The move is the result
THE OPERATION
Recovery work changes the job
A self-insured organization carrying its own risk, with a caseload weighted toward subrogation.
Recovery work changes what a claims system has to be good at. The claim stays open past the point most claims close, the record has to support a demand against somebody else, and money comes back in as well as going out.
None of that was the problem. The problem was the software underneath it.
Homegrown and Unsupported
The system did the job it was written to do. What it lacked was anyone behind it.
Nobody Left Who Understood It
The people who wrote it were gone. A request that a supported platform would treat as configuration became a question nobody in the building could answer.
Change as the Requirement
The operation needed a system it could keep changing as its work changed, with nobody writing code to do it.
WHAT CHANGED
Replaced with Something Configurable
Configuration is the relevant word. The work was fitting a platform to how this operation handles recovery claims, rather than writing new software that would eventually need a maintainer of its own.
THE ARC OF THE STORY
- The ConditionA working system that could not be changed, carrying a caseload where claims stay open and recoveries have to be evidenced.
- The ChangeThe homegrown system was replaced with a configured deployment of ClaimsCore. Each loss type gets its own tabs and fields, and fields, rules, workflows and templates change in a no-code admin console.
- What It LeftWhen the work changes, the system changes with it, through configuration rather than a rebuild.
What a replacement involves, phase by phase: How Implementation Works →
THE RESULT ON THE RECORD
The reason for the move is the result
THE RESULT
The operation runs its claims on a supported platform, and change, the one thing the old system could not absorb, is now ordinary configuration work.
RECOVERY WORK IN CLAIMSCORE
Where Recoveries Live
Subrogation is claims work, and VCA goes deep in claims, so a recovery sits on the claim beside the reserve it offsets. ClaimsCore carries recovery work the same way for any operation that runs it.
- Flagged When Worth PursuingA Subrogation Potential flag marks the claims worth pursuing, on the claim where the handler already works.
- Each Recovery on the RecordThe recovery agent, the status, and the dates it was assigned, reviewed, filed and settled, with amounts filed and funds received and disbursed.
- Net Recovery on the ClaimSubrogation and salvage recoveries post against the reserve they offset, and the claim shows the net recovery.
HOW THIS STORY IS PUBLISHED
Described by Its Shape, Not Its Name
No public reference names the operation, so it is described by its shape. The story carries no figure. It describes the operation instead.
TAKE THIS STORY WITH YOU
The same story on two pages, ready to forward or print.
Questions About Replacing a Homegrown Claims System
Can a self-insured organization run its claims on VCA ClaimsCore?
Yes. Self-insured organizations and captives are among the operations VCA serves, and ClaimsCore runs their claims whether their own team handles them or a third-party administrator does. VCA ClaimsCore is complete on its own: add-ons are added for specific jobs, and a client running only ClaimsCore is never at a disadvantage.
How long does it take to replace a homegrown claims system with VCA?
Every VCA implementation starts with discovery, which maps how claims actually move through the operation before anything is configured. On a Standard License, configured to your workflows, ClaimsCore goes live in 3 to 4 weeks; Enterprise License deployments take 8 to 16 weeks, and Carrier License deployments 12 weeks to 6 months.
What happens to the claims already in the old system?
They move in the data migration phase, which follows discovery and configuration and comes before training and go-live. Open and historical claims come across and are checked against the source before anyone relies on them.
MORE CASE STUDIES
More Operations on VCA
Adjusting Firm
A horse is not a generic loss
A specialty adjusting firm. Livestock and animal insurance claims, worked for carriers directly.
TPA
From Field Adjusting to a Full-Service TPA
Peninsula Insurance Bureau (PIB). Third-party administration for carriers, syndicates and coverholders in the E&S market.
TPA
The Administrative Time Hiding in Every Claim
Unity Claims. Claims and accident management for fleet and hire-car clients in Australia.
Bring the change nobody can make
Bring the request your current system cannot absorb, and see what configuring it looks like on one claim.
Request a Demo