The playbook
Appetite you can version.
Your rules, written down. Tested before they go live. Changed only when a person publishes.
Day one
We start by writing down your best underwriter.
A Lore engineer sits with your chief underwriter and turns how they actually decide into version one of your playbook.
A Lore FDE is the engineer in the room: they sit with your underwriter, hear how the desk decides, and write it into the playbook.
Soft factors
The things you look for in a risk.
Hard fields are not the whole call. On day one we write down the instincts too. Then Lore pulls them out of every pack that arrives.
Lore noticed
Single claim represents 36% of incurred losses (£4,422)
CL-23-4759 for third-party wing damage accounts for £4,422 of £12,315 total five-year incurred, well above the median claim of £1,605.
Operations extend into cross-border EU transport
Predominantly UK mainland with occasional journeys to France and Belgium representing under 5% of total mileage.
Claims frequency showing clear improvement
Volume dropped from 6 claims in 2023 to 1 claim in 2024, a downward trend in loss experience.
Cargo profile typical for food distribution haulage
Chilled and frozen foodstuffs transported for retail and wholesale customers.
Numbers from the pack. Framing from your own playbook's soft factors.
How it stays current
You change it. Or Lore proposes it.
Either way you see what it would do to your book. A person publishes.
Shadow-replay
Edit a rule. Lore replays it across every submission you have already decided. You see what would change, and which calls get stricter, before anything goes live.
Lore Suggests
When the desk keeps overriding a rule, Lore drafts the change, with evidence, already tested on your book. Nothing publishes itself.