Rules turn your underwriting guidelines and your binding authority into something the engine applies on every submission, before a human looks at it. A rule is a condition on an answer or a standard input, and an outcome.
Building blocks
- Outcomes
- Auto-accept (quote without a human), Refer (an underwriter decides) or Decline (the engine says no, with the reason recorded).
- Inputs
- Any of the product's questions (dates can be used as an age), plus the standard inputs sum insured, age, duration in months and premium.
- Operators
- greater than, at least, less than, at most, equals, not equal, in a list, contains.
- Conditions
- A rule tests one thing or several. With several you choose whether all of them must be true or one of them is enough. For a choice or yes/no question you tick the answers instead of typing them.
- Order
- The list shows decline rules first, then refer, then auto-accept. Within one outcome the first rule that applies is the reason shown on the submission; the order does not change the outcome.
Add a rule with Add rule, change one with the pencil next to it. A question that a rate or a rule still uses cannot be removed from the Questions tab until that rate or rule is changed, so a rule never silently stops firing.
How the outcome is decided
- All active rules are evaluated. If any decline rule matches, the result is Decline.
- Otherwise, if any refer rule matches, the result is Refer.
- Otherwise, if an auto-accept rule matches, the result is Auto-accept.
- If no rule matches at all, the engine refers. A product without rules therefore never binds unattended, which is the safe default.
Examples
- Decline when sum insured is greater than the binder limit.
- Refer when age is at least 70, or when 'previous claims' is yes.
- Auto-accept when sum insured is at most 250,000 and occupation class is in Office, Light manual.