Transactional Liability

Underwriting software for transactional liability teams.

From broker submission materials to quoting and the non-binding indication letter, through underwriting, purchase agreement review, binding, and claims. One underwriting record with the source behind every value.

How a transactional liability submission moves through Lexcel

Quoting comes first, underwriting goes deep after, and every stage works off the same record.

  1. 01

    Start with the broker submission

    The broker's submission email arrives as it is: deal overview, confidential information memorandum, financial statements, and whatever else came with it. The workbench structures the record from the materials, cites every value, and holds what the documents do not support rather than guessing.

  2. 02

    Quoting and the indication letter

    The team-built workflow drafts the quote or non-binding indication letter in your template: limit, retention, policy period, indicative premium or rate on line, and the exclusions already visible. The underwriter reviews it and sets what goes back to the broker.

  3. 03

    Underwriting

    The purchase agreement is worked section by section against your playbook: exclusions, deemed edits, and follow-up questions, each pointing back to the language it came from. Underwriting call preparation gets a cited issues list, separated into what looks material and what is only a question.

  4. 04

    Binding

    The bound package is assembled from the underwriting record, so the issued terms match the record the team reviewed.

  5. 05

    Claims on the same record

    When a claim notice arrives, the claims workflow starts from the bound policy and underwriting record. Nobody rebuilds on the claims side what underwriting already verified.

Built for the whole transactional risk family

Representations and warranties

The deepest work sits here today: intake, quoting, underwriting, purchase agreement review, binding, and claims on one cited record.

Transactional tax

Identified tax positions: eligibility, amount, transferability. The same record and the same workflow discipline, applied to tax submissions.

Contingent liability

Known, quantified exposures: pending litigation, successor liability, disputed ownership. Underwritten on the documents that define them.

Secondary transactions

Secondary transaction coverage, underwritten off the materials the sponsor sends, on the same record the rest of the book runs on.

Built for specialty insurance teams

Lexcel starts with transactional liability because it is the hardest proving ground: the submissions, the policy language, and the underwriting judgment have to stay connected on every deal. The same approach extends to other specialty lines. Each desk's fields, criteria, and review sequence are built with that team rather than copied from another line, and practitioners in D&O, employment practices, management liability, cyber, and E&O have asked whether the same submission workflow could run on their desks.

For brokers placing the risk

Carrier comparison, built from the quotes you hold

Lexcel tracks the carrier quotes and indication letters you hold, extracts the terms into one comparison, and drafts the carrier selection report for your client.

Purchase agreement and policy review

The draft purchase agreement and the carrier's policy both get reviewed with citations: issues in the agreement your client should know about, and policy terms checked against what was quoted before anything binds.

How it fits

Works with your stack. Leaves judgment with the underwriter.

Syncs with systems you already run

Verified fields update the system of record, and the workbench reads from and files to the document system over API. Salesforce and SharePoint are examples. No double keying.

The underwriter keeps the final say

Cited fields and drafts only. Nothing binds or goes outbound until the underwriter reviews and confirms.

Read: How to start without replacing your system of record in the Journal

Questions underwriters and brokers ask

What does an underwriter need in a representations and warranties (R&W) insurance submission?

What reliably arrives is the broker's submission email: a deal overview with the basic parameters, plus the confidential information memorandum and financial statements as attachments. The draft purchase agreement and the buyer advisors' diligence reports may or may not come with it, and even a requested retention is sometimes missing, so underwriters routinely quote off a partial package and use the gaps to drive their questions.

Format varies widely broker to broker, with some putting every detail in the email body and others attaching a submission document and leaving the email nearly empty.

What makes specialty underwriting different from standard lines when applying AI?

In standard lines the form is largely common and pricing leans actuarial. Specialty exists precisely because the exposures are not readily available from standard market insurers, so coverage is written bespoke, and in management liability alone there are a great many carriers each carrying their own definition of a claim.

That is why the data-driven, actuarial approach practitioners describe using in other lines does not transfer cleanly: the terms shift year to year and the judgment lives in reading documents rather than scoring a form. AI that is useful here has to run a desk's own criteria against its own documents, which is a different exercise from applying a packaged model of the line.

Which specialty lines does this work for?

Specialty lines where the work runs on documents rather than a rating engine, which is most of the specialty market: submissions arrive as email with attachments, someone pulls the fields out by hand, and the judgment that follows comes from reading rather than scoring. Transactional liability is where the deepest work sits today, and it is a demanding proving ground precisely because the terms move deal to deal.

What does not travel between lines is the criteria, so workflows are built to the desk in question rather than ported from somewhere else. Teams that own several lines usually start with whichever one repeats most often, which is also the fastest way to learn whether the rest of the book is worth doing.

What is a non-binding indication letter in R&W insurance, and how does quoting work?

The indication letter sets out indicative terms after a first read of the submission materials: limit, retention, policy period, indicative premium or rate on line, the underwriting fee, and the exclusions already visible. In practice a junior team member or analyst assembles the first draft off a prior precedent or template, the team works through it together with the senior underwriter, and it goes back to the broker before formal underwriting begins.

Lexcel works with a team to build the workflow that produces that draft, and the underwriter still sets the terms.

What happens between the indication letter and binding in R&W insurance?

This is the underwriting stage, and practitioners describe it as the most time-intensive part of the process: working the purchase agreement rep by rep and section by section, tax, material contracts, regulatory, then deciding what becomes an exclusion, what becomes a deemed edit, and what is only a follow-up question. Not every flag becomes an exclusion; some get traded, and some get comfort and go away, which is exactly why the work resists a rules engine.

Lexcel runs the same passes the team runs, section by section against its own playbook, with each position pointing back to the language behind it, so the underwriter spends the time deciding rather than re-reading.

How does AI review of a purchase agreement work?

Purchase agreement review is usually a later-stage workstream, since the draft agreement often is not in the submission and requests for comments frequently arrive as a second-stage ask. The work runs section by section against the team's own playbook: exclusions where a carve-out demands one, deemed edits where the language reaches something like a forward-looking projection, provisions that are not insurable, and the definitional mechanics that move coverage.

Every comment points back to the language it came from, and the underwriter decides what actually goes to the broker.

What is transactional tax insurance?

It covers an identified tax position rather than the unknown breaches an R&W policy covers: whether a tax credit is eligible, in the claimed amount, and transferable, or whether an uncertain position already on a balance sheet will hold up on challenge. Buyers use it to take a known tax risk off the table so a deal can close or a reserve can come off the financials.

What is contingent liability insurance?

It covers a specific, identified exposure that is already known and quantifiable, most often pending or threatened litigation, a successor liability question, or a disputed ownership or title issue holding up a transaction. Where R&W responds to breaches nobody knew about at signing, contingent liability responds to the one risk everyone has already found and priced.

More questions answered in the FAQ

Connects everywhere you work

Works with your existing systems.

Google Drive iconSharePoint iconBox iconSalesforce icon
Excel iconEmail iconOutlook iconWord iconPowerPoint icon

Security & Compliance

Built for enterprise security.

SOC 2 Type II

AICPA SOC for Service Organizations