The wording that applied
The policy wording and endorsements in force when the policy was bound, not the version on file today.
A claim can be reopened, litigated or audited years after it is paid. Tabellix keeps the claim file, the wording that applied and every reserve decision on a verifiable record, then destroys it lawfully when its time comes.
The policy wording and endorsements in force when the policy was bound, not the version on file today.
Who changed a reserve, from what to what, and the reason given at the time.
Every notice, estimate, photo, report and letter, in order, unchanged since it was filed.
What the loss adjuster, the claimant's lawyer or the reinsurer received, which version, and when.
Whether the retention period has passed, whether a hold applies, and who approved the destruction.
Which steps an AI agent took on a claim, for which handler, and which decisions a person made.
Wordings are controlled documents with versions and scheduled effective dates. A link from a policy record pins the version it refers to, and that link never moves.
Each reserve change is its own event record, locked at capture. A correction is an amendment that states a reason, and the original value stays visible.
A claim file is a case record that binds its members in order. Holds, retention triggers and access flow from the claim to every document in it.
Adjusters, lawyers and reinsurers get expiring, watermarked shares or a data room, with an agreement before content. The accounting of disclosures lists every version each one received.
The system proposes what is due and records administrators approve each disposal. Destruction crypto-shreds the content, an active hold blocks it, and the ledger still verifies afterward.
Under the flexible preset you open individual agent permissions one by one, and an agent's signature always says it was the agent's. Every tool call carries the handler and the agent session.
| Record | Kind | What it holds |
|---|---|---|
| Policy wording HW-12 | document | Versions with scheduled effective dates; endorsements as their own documents; superseded wordings kept with their history. |
| Claim CL-55120 | case record | First notice, estimates, photos, reports and correspondence as ordered members; retention counted from the day the claim closes. |
| Reserve change | event record | Previous and new amount, the handler, the reason and the time, linked to the claim and locked at capture. |
| Underwriting referral | case record | The referral, the underwriter's decision signed with its meaning, and the guideline version that applied. |
| Independent adjuster report | document | Received through the claim, scanned for malware before anyone opens it, and versioned if a revised report follows. |
Where the deployment allows early destruction, records can be crypto-shredded under a legal order with two distinct approvers. An active hold refuses the order. The record's identity and history remain, and the ledger still verifies.
Yes. A disclosure is a signed, deterministic bundle checked offline, and a data room reports what each recipient fetched.
Every file is scanned for malware and served only after the scanner answers clean. A file that is not what it claims to be is refused, and downloads are served with active content blocked.
Your claims system keeps its screens, rules and payments. It files each document and event into the claim case through one contract over gRPC or REST, and outside parties need no seat. Your brand appears on every customer-visible surface Tabellix provides.
Tell us what you build and who audits it. We'll show you how Tabellix fits into your product and how it answers your auditors' most common questions.