Intake sets your expense ratio. Quietly, it sets part of your loss ratio too.
A submission that gets rekeyed by hand costs the hours it takes. It also carries whatever was mistyped into the rating engine, where nothing surfaces it until a claim. SnapLine reads what the broker actually sent and returns a structured record in which every field traces back to the page it came from.
- Covering email
- MRC slip.pdf
- schedule_of_values_v3.xlsx
- schedule_of_values_FINAL.xlsx
- survey_scan.pdf
- IMG_4471.jpeg
- named_insuredRavensholme Estates LimitedTraced to source
- total_insured_valueGBP 24,850,000Two sources disagree. Both are on the record.
- locations14Traced to source
- construction_classMasonry, non-combustibleTraced to source
- year_builtNot in submissionSent to outreach, not inferred.
Four things move, and they are all on the same invoice
None of these is a number we are asking you to accept. Each one is a mechanism you can check against your own operation, and then measure on your own submissions before you commit to anything.
Reading a pack, finding the fields that matter and keying them into three systems is work that scales with volume and nothing else. It is also the work people are doing at seven in the evening in renewal season.
A transposed figure in a declared value does not announce itself. It prices, it binds, and it is discovered at the claim. Cross-document checks raise the disagreement while someone can still do something about it.
Brokers place with the market that answers. When intake is a queue, the quote is late for reasons that have nothing to do with appetite or capacity.
Exposure management, rating and the data warehouse inherit whatever intake produced. Structured at the front means those systems stop being fed by hand, and the numbers in them start agreeing with the documents.
Not only the submissions that are new
Most of the documents an underwriting operation handles are not first submissions. They are the same risk coming back a year later, a change part-way through, or a return from a coverholder.
The submission pack as it arrives: email, slip, schedule, loss runs, whatever else the broker attached.
The expiring policy read against the renewal submission, so what changed since last year is the first thing visible rather than something to be found.
A mid-term change read and applied against the policy as it currently stands, instead of against the version someone remembers.
Coverholder returns ingested and checked against the binder, with what does not reconcile raised as a list rather than discovered at the quarterly review.
In the product
The add-in works inside the underwriter's own inbox, so a submission doesn't have to be forwarded into another system before anything can read it.
The Market Reform Contract defeats general-purpose document AI because of how it is structured. SnapLine reads a slip as a slip.
Valuation adequacy flags raise the question at submission stage, which is a considerably cheaper place to answer it than a claim.
Requires Atlas, which is licensed separately.
Run it across the book and vacancy surfaces where the occupancy data and the risk have quietly stopped agreeing.
Requires Atlas, which is licensed separately.
Provenance
Why any of the above is worth believing
Extraction is the easy half. The harder half is the question any underwriter asks of a number they didn’t key themselves: where did that come from, and is it right? A record nobody trusts gets checked by hand, and then the hours never came out in the first place.
Hover or select a field in the structured record and SnapLine shows you the region of the source document it was read from. You confirm it, correct it, or send it back to the broker. The record carries that decision with it, and the next person to open the file can see who decided what.
Risk code PD
Inception 01.11.2026
- Insured
- Ravensholme Estates Limited
- Interest
- Commercial property portfolio, 14 locations
- Construction
- Masonry, non-combustible
- Year built
- not stated
| Loc | Address | Occupancy | Building | Contents |
|---|---|---|---|---|
| 001 | Ravensholme Works, Leeds | Warehouse | 4,120,000 | 980,000 |
| 002 | Carlisle Road, Bradford | Light industrial | 2,340,000 | 610,000 |
| 003 | Eastgate Retail, Wakefield | Retail | 3,880,000 | 1,240,000 |
| … 11 further locations | ||||
| Total insured value | cited24,850,000 | |||
Illustrative. Broker, insured and all figures are fictional.
From attachment to quote-ready record
- 01Arrives
An email lands in the underwriting inbox with a stack of attachments, several of which are versions of the same schedule and one of which is a photograph of a roof.
- 02Triaged
SnapLine sorts it where it sits.
- 03Extracted
Fields are read across the whole bundle, including the scans and the spreadsheet tabs nobody opens, and disagreements between documents are preserved rather than resolved quietly in the background.
- 04Validated
An underwriter checks what matters and corrects what doesn't look right.
- 05Quote-ready
The structured record goes downstream with its provenance and every correction attached, so the audit trail exists without anyone having to assemble one afterwards.
In production, not in pilot
SnapLine runs on live submissions inside a working US specialty underwriting operation, under a commercial contract, and has been delivering against it. Not a proof of concept kept alive on goodwill, and not a sandbox.
We will not name them on a web page, and you would not want us naming you on one either. At the right stage we will put you in front of people who use it, and you can ask them what you would ask us.
What is not yet true is a Lloyd’s syndicate running it in production. That conversation is on the London Market page, where it belongs, rather than left for you to discover at reference stage.
Independently audited
Lloyd's Lab Cohort 15 FinalistA selection. Not an accreditation, not a deployment, and not an endorsement by any syndicate.
What an engagement looks like
Three shapes, and which one fits depends on the volume, the lines, and what sits downstream of intake. Scope is agreed in writing before anything starts.
Atlas property intelligence is licensed separately and is not part of any of the three.
A demo, then a fixed-scope Proof of Value measured on your own live submissions.
- A demo with five sample submissions already loaded
- Up to three of your own submissions, uploaded and processed in the session
- A Proof of Value run across twenty of your live submissions
- Scope agreed in writing before anything starts
- A written report at the end, yours to circulate internally
SnapLine in the underwriting workflow for a defined team and a defined set of lines.
- The Outlook add-in in your underwriters' own inboxes
- Submission queue and submission detail views
- Provenance on every extracted field
- Outreach for missing information, back to the broker
- Quote-ready structured output
More than one underwriting team, more than one entity, or a group-wide rollout.
- Everything in Deployment, across multiple teams or legal entities
- Security review support, with SOC 2 Type 2, ISO/IEC 27001 and ISO/IEC 42001 documentation
Bring three of your own submissions
A demo on our sample data tells you what the software does. A demo on your own slips tells you whether it survives contact with the way your brokers actually send things. The second is the one worth your half hour.
SnapLine was built for Lloyd’s and the London Market, and is now being taken into US specialty insurance.