Eligibility and auto-settlement rules kept out of the claims monolith, versioned, and explainable per decision.
Underwriting appetite changes faster than the release train
Auto-settlement thresholds are a magic number in a handler class
Disputed claims need a human to reconstruct the decision by hand
Decide whether an applicant can be offered cover based on age, risk score, and claims history.
A **applicant** is eligible for cover
if §applicant.age is valid
and §applicant.risk is valid
and §applicant.history is valid.
applicant.age. A **applicant** passes age_check
if the __age__ of the **applicant** is greater than or equal to 18
and the __age__ of the **applicant** is less than or equal to 70.
applicant.risk. A **applicant** passes risk_check
if the __risk_score__ of the **applicant** is less than 72
and the __occupation_class__ of the **applicant** is in ["A", "B", "C"].
applicant.history. A **applicant** passes history_check
if the __claims_last_3_years__ of the **applicant** is less than 3
and the __cancelled_for_fraud__ of the **applicant** is equal to false.
Change the policy, change the input, evaluate. The same engine your application would call.
Policy
Input
Claim Auto-Approval
InsuranceSettle a small claim without a handler when the policy is active, the claim is recent, and documents are verified.
Age Verification
ComplianceVerify that a user meets the minimum age requirement and is in an allowed region.
Transaction Fraud Flag
FinanceFlag a transaction when the amount is unusually high and the location does not match the account.
We will implement your first policy with you.
Send us a rule you currently keep in application code and we will show you what it looks like as a versioned, traceable policy.
Talk to us