Code bordereau loss descriptions to your cause-of-loss list
Each loss description in a bordereau gets a cause code from your list, named events, weather and injury flags, and a flag for risks outside the binder.
Try it on this example
Class of business from the bordereau: Property owners
Loss description from the bordereau
- What caused the loss, as the loss description tells it?Storm: wind100%
- Does the loss description name one of the events listed in the context?No named event100%
- Does the loss description say or suggest that weather caused the loss?Yes97%
- Does the loss description say that anyone was hurt in this incident, even slightly?No92%
- Does the loss description show a risk or activity the binder does not authorise?Yes98%
- Does the loss description say enough to assign a cause-of-loss code?Yes92%
These are real answers stored from one run on this example.
The prism behind it
Code bordereau loss descriptions to your cause-of-loss list
Fields
- Class of business from the bordereau
- Loss description from the bordereau
Context
We are a London MGA and Lloyd's coverholder writing UK commercial property and casualty under binding authority agreements. Our claims administrator sends a monthly claims bordereau, one row per claim, with a free-text loss description and the class of business. The file is read here once a month, one row per call, to code the cause of loss for our capacity providers, to record any named event the description cites, and to flag risks the binder does not let us write. A data analyst works every row the answers are unsure about. Code reads the loss date, the location, the amounts and the policy details from the other bordereau columns. Code attributes a claim to a named event by its date and region; the event question here records only what the description itself says. Nothing here decides cover or any payment. Classes the binder authorises: property owners (commercial, mixed-use and residential blocks); commercial combined for offices, shops and light industrial units; contractors' liability for building trades. The binder does not authorise, in any class: - premises with a nightclub, or where food is fried in deep-fat fryers, such as a fish and chip shop or a takeaway; - waste, recycling or scrap businesses; - buildings that were empty or unoccupied at the time of the loss; - thatched buildings; - contractors doing demolition, asbestos removal, or work on railways, airports or offshore. Named events of the period: - The January freeze: 5 to 11 January 2026, a long hard frost across Great Britain. - Storm Hedda: 22 to 23 January 2026, severe gales in Scotland, northern England and Northern Ireland. - Storm Ivo: 14 February 2026, gales and heavy rain in Wales and south-west England. - The Severn floods: 16 to 19 February 2026, river flooding along the River Severn.
Questions
What caused the loss, as the loss description tells it? Choice
Choose the code from our list that fits the cause of the damage or injury, not the cover the insured may think applies. When one event leads to another, such as wind that lifts a roof covering and lets rain in, choose the first cause. Use the class of business to tell a property claim from a liability claim. Bordereau descriptions are often in capitals and abbreviated: INSD is the insured, TP a third party, O/N overnight, EOW escape of water.
Does the loss description name one of the events listed in the context? Choice
Choose an event only when the description names it, such as "Storm Hedda" or "the Severn floods". Weather words or a date that would fit an event are not enough; code attributes claims by date and region.
Does the loss description say or suggest that weather caused the loss? Yes / No
Count wind, gales, storms, heavy rain, hail, snow, frost, freezing and lightning, whether or not an event is named. Flooding from a river or the sea counts. Yes: The description puts the loss down to weather, or describes weather at the time as part of the cause. No: The description gives a cause that is not weather, or mentions no weather.
Does the loss description say that anyone was hurt in this incident, even slightly? Yes / No
Count anyone: an employee, a tenant, a visitor or a member of the public. Yes: The description says someone was hurt, needed medical help, or claims for an injury. No: The description says nobody was hurt, such as "NO INJ", or mentions no injury. An illness or injury unrelated to the incident is No.
Does the loss description show a risk or activity the binder does not authorise? Yes / No
Use the classes and the list of what the binder does not authorise in the context. Judge only what the description says about the premises, the occupiers or the work. This flags the row for our delegated authority auditor; it is not a finding on cover. Yes: The description shows premises, an occupier, a trade or work on the list, or a risk outside the authorised classes. No: Nothing in the description falls outside what the binder authorises.
Does the loss description say enough to assign a cause-of-loss code? Yes / No
Abbreviations and capitals are normal and do not make a description too short. Yes: The description says what happened clearly enough to choose one code from the list. No: The description gives only a label or a vague phrase, such as "EOW", "DAMAGE TO PREMISES" or "TP CLAIM", so no code can be chosen with confidence.
Lens columns
loss_cause, loss_cause_probability, event_named, event_named_probability, weather_implied, weather_implied_probability, injury_reported, injury_reported_probability, outside_binder, outside_binder_probability, enough_information, enough_information_probability
Run it on your own text
Add this prism in the app, change any question, and test it on a file of your own.