Control exceptions without hiding them in email.
Referral logic can be driven by product, premium, hazard, state, class, limit, underwriting answer or any combination of risk attributes — and every referral keeps its reason attached.
Discuss authority designDetect the exception
Rules identify conditions outside standard appetite or beyond individual authority as soon as the data supports it.
Assemble the context
Risk facts, pricing impact, documents and the exact referral reason travel together to the reviewer.
Route by authority
Send the case to the appropriate role or authority level based on product and exception type.
Record the outcome
Approval, conditions, notes and overrides stay part of the risk history rather than a mailbox.