Policy and premium / Policy administration
A policy that remembers every version of itself
Contracts of insurance held as versioned records: coverages, locations, forms and endorsements, each change preserved rather than overwritten.
The question that decides a coverage dispute is what the policy said on the date of loss — not what it says now. A system that overwrites cannot answer it.
Bring a mid-term changeWhat did this policy say on the day of the loss?
Versioning answers it directly. A policy carries its history: the coverages, limits, deductibles and forms in force at any point, so a claim opened against a two-year-old loss resolves against the terms that actually applied then.
Versioned, not overwritten
What the policy record holds
- 01
Coverages, limits and deductibles
Held per coverage rather than as a flat set of fields, so a policy with different limits per location or per peril is represented as it actually is.
- 02
Every version retained
Endorsements and mid-term changes create versions. The prior terms remain readable, which is what makes a coverage position defensible after the fact.
- 03
Forms attached to the contract
Generated forms belong to the policy version that produced them, so the document set and the terms cannot drift apart.
- 04
Renewal carries the history
A renewed policy is a new term that knows what preceded it, rather than a fresh record with a similar number.
What the claim side reads
One policy record, two portals
The adjuster verifying coverage and the underwriter who bound it read the same record. There is no policy extract, no nightly sync, and therefore no window where the two disagree.
| Element | Behavior |
|---|---|
| Policy resolution at FNOL | The claim resolves to the policy version in force at the loss date |
| Coverage verification | Runs during intake and records its result on the claim |
| Mid-term changes | Create a new version; prior terms stay readable |
| Forms | Bound to the version that generated them |
| Status changes | Pass the single policy transition door, with a reason recorded |
Where configuration is yours
The platform models policies. It does not know your product.
No shipped products
Coverage structures, forms and rules reflect your filings. We ship the model, not a product catalog that guesses at them.
Migration is real work
Bringing history from a legacy PAS means mapping their model to this one. We would rather scope that honestly than call it an import.
Filings remain yours
Nothing here relieves you of the regulatory work of filing and maintaining the product itself.