The policy as it stood on the date of loss
Endorsements, amendments, renewals and cancellations resolved as one timeline. Cover is read on the date of the claim, not on today’s.
Policies, endorsements, claims, submissions and underwriting rules live in different systems and different versions. Strattum resolves that as one governed context, in the version in force on the date, and serves it to the AI your teams already use.
Endorsements, amendments, renewals and cancellations resolved as one timeline. Cover is read on the date of the claim, not on today’s.
Submission, policy, claim, broker and billing resolved as one customer. The history stops depending on which line of business opened the query.
Acceptance, loading, exclusion and authority applied in the version in force on the submission date, with the clause cited. What passes and what stops becomes explicit.
Today each one ends in a policy PDF, an email to underwriting, or someone rebuilding by hand which endorsement applied when.
Policy, endorsements and general conditions resolved on the date of the claim. The handler stops reassembling the policy version from four PDFs to work out what was covered.
The submission read against the acceptance rule in force, with the loading and the exception that profile opens. The underwriter sees the rule and the deviation on one screen instead of emailing the technical team.
What the policy covers, what the endorsement changed and what is missing to issue, written from the general conditions and the manual itself. The broker stops depending on an underwriter being available.
Premium, claims and endorsements read together. When the loss ratio rises, the reason surfaces tied to the product, the broker or the cover change that produced it.
The policy is treated as a timeline rather than a document. The original, the endorsements, the amendments and the renewals all enter versioned, each with the date it took effect and what it changed. When the question carries a date, the answer is built from the version on that date and cites the endorsement that produced it, so it can be opened and checked.
Same mechanism. The manual is versioned context, so a February submission is judged by the February rule even if the rule changed in April. The answer carries the clause applied, its version and what it replaced, which is what holds up an acceptance decision when someone revisits it months later.
They see the context their permissions reach, and no more. The filter is applied before ranking, so a document that profile may not see never enters the material the answer is built from, and does not appear as a citation either. The walls the insurer already keeps between channel, underwriting and claims continue to hold.
No. Strattum is the layer between those systems and the AI. They remain the system of record. What changes is that the policy, the endorsement and the claim get resolved as one thing, on the right date, when someone asks.
A generic assistant answers from whatever it can search, and in an archive where the same policy exists in five versions that means citing the wrong clause with confidence. What is missing is not the model, it is the context: which endorsement applied on the date, which manual judged that submission, what that user is entitled to see.
Inside your cloud. The entire platform is deployed in your infrastructure: AWS, Azure, GCP, OCI or on-prem. Strattum has no runtime access to the data, and your records, credentials, keys and network access never leave it.
Strattum
