# First notice of loss triage > First notice of loss triage: Claim type, severity, fast track or adjuster Checked: cross-checked. Produces routed claims. Source: https://www.sumarity.ai/library/first-notice-of-loss-triage/ Insurance # First notice of loss triage Reads notifications of loss, the policy. Produces routed claims. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person. Cross-checkedClaims, disputes and exceptions Start from this workflowMore for insurance What it decides ## Narrow questions, each with a check behind it. Claim type, severity, fast track or adjuster Cross-checked: policy in force, cover. A second source has to agree: a register, a contract, a list. When it does the judgement settles; when it doesn't, a person decides. | Reads | Notifications of loss, the policy | Produces | Routed claims | Who signs | A person on your team, with every figure traced to its document and every call on record | Process | Claims, disputes and exceptions | Industry | Insurance See it run ## Every line, decided where it's safest. An example run. Each stage lights up as a line is decided there; pick a stage to see its lines. ReadsNotifications of loss, the policyCodeReads, matches, ties out and works out every figure.JudgementClaim type, severity, fast track or adjuster. Settles only when it clears the cutoff and a second source agrees.A personGets whatever stays uncertain, with the evidence. Their ruling tunes the next run.ProducesRouted claims First notice of loss triage · example run Example run | Ref | Item | Value | Decided by | FN-301 | Windscreen chip, motorFast track: glass cover, under the excess limit | 320.00 | Code · fast track | FN-302 | Water damage, kitchenCovered peril · 0.94 · policy in force | 4,800.00 | Engine · cross-checked | FN-303 | Theft from carPolice report attached · 0.91 | 1,200.00 | Engine · cross-checked | FN-304 | Fire, commercial premisesLarge loss: adjuster | 250,000.00 | To a person | FN-305 | Policy lapsed 01.09No cover on the loss date | | Code · declined | Settled 4 To a person 1 Settled wrong 0 Illustrative lines. Amber rows are the Judgement Engine's calls; each settles only above its cutoff and when its check agrees. What it could save ## Your volumes in. Your hours out. In our tests, between 24% and 42% of items still went to a person after tuning. Set your own share; a pilot measures it on your data. Items per run Runs per month Minutes per item by hand Cost per hour Share of items that still need a person: 30% By hand today80 ha month With Sumarity24 ha month, for the items people decide Saved56 hCHF 53,760 a year Related ## Start from what's closest. ### Claims, disputes and exceptions in other work Finance ### Customer deductions and short-pay disputes Valid deduction (promotion, damage) or not Proven by codeBanking ### Payment exceptions and investigations Why a payment failed or is queried; the action Proven by codeBanking ### Card disputes and chargebacks Network reason code; evidence enough to fight Cross-checked ### More for insurance ### Claim coverage check against policy wording Covered, excluded, limits Cross-checked ### Delegated authority bordereaux reconciliation Each risk and claim line against the binder Proven by code ### Broker premium statement reconciliation Which policies a statement covers Proven by code Questions ## What buyers ask What happens when Sumarity isn't sure? Nothing settles below the cutoff, or when the check disagrees. The item goes to a person in the inbox with what the engine saw, its best answer and the runner-up. The person's ruling is kept and tunes the next run. How are its judgements checked? A second source has to agree: a register, a contract, a list. When it does the judgement settles; when it doesn't, a person decides. Can we change it to fit how we work? Yes. Start from this workflow and describe your differences in plain words. The design assistant revises it, the validator checks it, your expert reviews it on the canvas, and your admin publishes it. Does it read our files as they are? Yes: spreadsheets and CSV in any layout, PDFs, bank formats and e-mail attachments. Sumarity suggests how each column maps, proves the mapping on a sample and remembers it once a person confirms it. Where does our data go? Sumarity runs in Zurich. Your data, backups and logs are stored in Switzerland. How does it get better? Your team's rulings become an answer key. Better questions and cutoffs are proposed, tested on data they haven't seen, and published only when your admin approves. It improves itself, with permission. ## Start from this workflow. Run it on your data. A pilot runs alongside your own process for a few weeks, at our cost, and ends in a line-by-line comparison. Talk to usBack to the library