21RISK keeps insurance claims tracking on the site where the loss happened: every payment as it moves, the root cause of each loss, and the loss history ready before the underwriter asks.
Claims run for months. Estimates change, interim payments arrive, and the figures drift away from what actually happened.
Someone types in what was paid and what is still outstanding. After a few interim payments, nobody is sure the totals match what actually moved.
Why it happened stays in the adjuster’s report. The claim closes, and the same cause hits another site the year after.
The underwriter wants claims per year, paid and outstanding. Every year the table is built again by hand.
Claims is its own board in 21RISK, next to your values, COPE and risk improvements. One per organization, with the same access and sites as the rest.
Claims line, damage type, date of loss, the worst case estimate and the deductible. The site is the one that already holds your values and COPE.
A dated ledger of payments by the insurer and by you. What has been paid, by whom, and what is still outstanding are calculated from it, so they always agree.
A root cause per claim, from suspected on day one to confirmed when the adjuster’s report is in. Analytics show which causes cost the most, and where they repeat.
Every claim sits on a claims line, with damage types you set per line: fire, windstorm and water damage, or recall and warranty.
Three facts are stored: the estimate, the deductible and the payments. Gross and net, paid and outstanding are all calculated from them.
A claim is registered on a site, so the loss sits next to that site's insurance values, risk profile and open recommendations.
The formulas and a worked example are in the docs: claim financials.
Gross incurred split into paid and outstanding, the insurer's share and your own, damage types, statuses and claims per year of loss. The overview uses the same filters as the claim list, so the two always agree on which claims count.
Root cause categories ranked by gross incurred, and the vital few that explain 80% of your losses. The hotspot grid puts every site against every cause. A number in a cell means the same cause hit that site more than once: the clearest sign that a fix there will pay off. Click any category or cell to open its claims.
A group owner switches it on under Settings › Account › Claims. That creates the Claims board with Open and Closed statuses and a starting list of damage types and root causes for each line. Your group owners become the board owners, and the board uses the same access, sites, statuses and activity log as your other boards.
Property claims for damage to your own buildings, machinery and stock, and liability claims where a third party holds you responsible, such as product liability or recall. Each line has its own damage types, and you can add or remove them to match the words you already use with your broker and insurer.
Each claim stores three things: the worst case estimate, the deductible and the payments. Gross paid is the sum of the payments, gross outstanding is the estimate minus what has been paid, and net incurred is the estimate minus the deductible. The deductible is capped at the estimate, so net incurred is never negative. Nothing is typed twice, so no figure can contradict another.
Every claim has a root cause status: Not known yet, Suspected, Confirmed or Undetermined. Record a suspicion early, for example from the first notice of loss, and confirm it when the investigation is done. Claims whose cause is not known yet or only suspected stand out in the list, so open questions don’t get lost.
Each claims line starts with a list in two levels, drawn from fire-investigation, insurer and product-recall cause codes: for example Electrical › Loose or faulty connection for property, or Procedures and training › Procedure not followed for liability. Group owners can add and remove categories and sub-categories to match your own language.
Yes. A loss you paid yourself still counts in your claims frequency, still shows per site, damage type and root cause, and is still part of the loss history you bring to the renewal, even though the insurer paid nothing.
Update the worst case estimate whenever you know more. Incurred and outstanding follow at once, and every change is kept, so you can see what was estimated when and who changed it. A payment entered wrongly is corrected with a negative row, so the ledger keeps its history.
Yes. The claim list, root causes included, exports to Excel or CSV and supports saved views. Claims are also in Advanced Analytics, the REST API and the MCP server, so an analytics team or an AI assistant can read the same claims you see.
Talk to us about the claims list you keep today, and we will show you the same book in 21RISK.