Liability or damages in dispute
One method for every file in dispute —and one place the evaluation lives.
Every evaluation follows the same structure — liability, damages, and expected value — configured once to your company's guidelines. The work stays in the system, so you can see how the book is actually being valued, and export any file's evaluation when you need it.
Built for carriers, TPAs, and self-insured programs. Pre-suit or in suit, property damage or bodily injury — wherever liability or damages are in dispute.
Already provisioned? Sign in.
Most shops do not have a method. They have habits.
Some files get a spreadsheet. Some get a counsel letter. Some get a number from the last round table. The reasoning, when it exists, is in the claim file, an email, a shared drive, or a personal drive. There is nothing to compare, and nothing to stand on later.
A record that holds up when the file is questioned.
When an extra-contractual claim arrives, the question is whether the file was evaluated on a consistent method, with the assumptions recorded. This is that record. It does not value the claim for you. It holds the evaluation your people already make, in a form leadership can review.
What you get
A method you can require
Same liability questions, same damages elements, same scenario structure on every file — built to your guidelines, not ours.
A home for the evaluation
The decision tree, damages worksheet, expected value, and rationale all live in one record. Export a copy whenever the file needs one.
Visibility into the book
See which files have a completed evaluation, what each one concludes, and where values have moved.
Why not spreadsheets and counsel letters?
Spreadsheets hide silent errors and die when the author leaves. Counsel letters are not comparable across the book. Shared drives are not a method. This stores your scoring weights in one place, calculates expected value the same way every time, and leaves a reviewable analysis on every file.
For panel counsel
Counsel works in the same evaluation your adjusters use — same method, same numbers, same rationale — instead of sending a separate letter that never gets back into a comparable record.
Who built it
Built by someone who has valued files this way in practice. The method came first; the software holds it in one place.
See it on a real file
We'll walk through a sample file — liability, damages, and expected value — and show what leadership sees across the book.
Already provisioned? Sign in.