Every claims operation runs on rules: which claims are high severity, who gets which line, which clocks start, which payments need a second look, when a fraud indicator fires. In most organisations those rules are buried in vendor configuration or live in a supervisor's head. The Rules Studio puts them where a claims manager can read them, test them and change them.

The claims rule types

TypeWhat it decidesWhen it runs
SeverityLow, medium, high or criticalClaim opened
Fraud indicatorRaises an indicator with a weightClaim opened, Analyze
AssignmentThe role or team a claim goes toClaim opened
SLA selectionWhich clocks startClaim opened
DiaryOpens a diary with a due dateClaim opened
Coverage referralRefers the coverage position, or requires an approvalClaim opened, Analyze
Payment controlHolds a payment, or requires an approvalPayment requested, issued
RecoveryRaises a subrogation, salvage or deductible opportunityAnalyze, liability recorded
Bill reviewCuts a legal or vendor bill line with a reasonBill received
Large lossIssues the large-loss report and reinsurers' noticeIncurred crosses a threshold

Line rules sit in the same Studio, predicated on the line: claims-made checks for management liability, sanctions and sublimit checks for cyber, coinsurance and ALE for property, long TTD for workers' comp, rental over limit for auto.

A rule is a sentence

Each rule reads as English — “When line is workers' comp → assign to the Workers Comp team” — built from the catalogue's labels, never a field key. Underneath it is declarative JSON that the same shared engine evaluates in every Insight product.

flowchart LR A["Draft a change"] --> B["Test against
one real claim"] B --> C["Impact: which open
claims would change"] C --> D{"Publish?"} D -->|"yes"| E["New version;
the next Analyze
uses it"] D -->|"no"| A E --> F["Roll back from
the history"] style D fill:#e8f8f4,stroke:#22c1a4,stroke-width:2px

Saving keeps a draft. Testing runs it against a real claim and shows which conditions held, with the claim's actual values. Impact shows what the unsaved draft would change across open claims, by line and stage, with examples. Only publishing changes what the pipeline does, and decisions already made do not change.

The Rules Studio with the claims rule types, rule counts and hits, on demo data
The Rules Studio on demo data: ten claims rule types with their rules and 30-day hits.

Who owns which rules

  • Claims operations: severity, assignment, clocks and diaries.
  • Coverage leads: coverage referrals and the line checks.
  • SIU: the fraud indicator catalogue and its weights.
  • Compliance and finance: payment controls.
  • Litigation and vendor management: bill review guidelines.
  • Leadership and reinsurance: large-loss thresholds.

Every rule fire is logged with the claim and the facts, and lands on the decision record. That is how a rule owner learns whether a rule earns its place.

Keep reading