Underwriting File Notes Automation: Record Every Decision
On this page
- What Is Underwriting File Notes Automation?
- What Does a Good Underwriting File Note Look Like?
- Which Fields Belong in the Header and Submission Facts?
- Which Fields Capture the Decision and the Rationale?
- Which Governance Fields Make the Note Review-Ready?
- How Do You Keep Underwriting File Notes Current?
- Where Does Insurnest Fit in Underwriting File Notes Automation?
- How Should a CUO Introduce Underwriting File Notes Automation?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
A treaty comes up for renewal, and the only note on file says "Written, terms agreed, good relationship".
The underwriter who wrote it has moved on, and nobody can explain the price.
Underwriting file notes automation pre-fills the facts of each treaty decision from the submission, so underwriters record only the judgement.
The result is a consistent, review-ready note for every treaty written or declined.
What Is Underwriting File Notes Automation?
Underwriting file notes automation is the practice of generating the factual parts of an underwriting file note directly from submission data.
Underwriters then add the decision, rationale and conditions in fixed fields rather than free text.
The goal is a note that is complete by default. Missing rationale becomes visible instead of hidden.
Why do treaty file notes stay thin?
Treaty file notes stay thin because underwriters spend their time retyping facts that already sit in the broker's email and attachments.
By the time the facts are typed, the renewal queue has moved on and the reasoning gets one line.
Lloyd's MS2 Underwriting and Controls expects managing agents to retain placing information.
It also expects them to keep "the rationale for risk acceptance, terms and pricing". A one-line note rarely meets that standard.
What Does a Good Underwriting File Note Look Like?
A good underwriting file note has five sections, and each section has a clear owner and purpose.
The template below is the core artefact, and the next sections break each part down field by field.
| Section | Purpose | Filled by |
|---|---|---|
| 1. Header | Identifies the treaty and the decision-maker | Automation, checked by underwriter |
| 2. Submission facts | Records what the decision was based on | Automation, checked by underwriter |
| 3. Decision | States the outcome, line and price | Underwriter |
| 4. Rationale | Explains why, including risks and trade-offs | Underwriter |
| 5. Governance | Shows authority, referral, review and renewal points | Underwriter and reviewer |
Sections 1 and 2 are where automation saves time. Sections 3 to 5 are where judgement lives.
Which Fields Belong in the Header and Submission Facts?
The header and submission facts should hold every detail the decision relied on, captured from the submission with its source.
| Field | Purpose | Source |
|---|---|---|
| Submission reference | Links the note to emails and documents | Intake |
| Cedent, broker, contact | Identifies the parties | Broker email |
| Treaty structure | Quota share, surplus, per risk or cat XoL | Slip |
| Limit, attachment, period, territory | Defines the cover | Slip |
| Subject premium and ceded premium | Sizes the deal | Submission pack |
| Commission and profit commission | Shows proportional economics | Slip |
| Loss history and loss ratios | Shows experience used in pricing | Loss data |
| Exposure summary and exclusions | Shows what is covered and what is not | Submission pack |
| Information gaps at decision | Shows what was missing | Intake check |
The last field is often skipped. It is also the field reviewers most need.
Why should facts be pre-filled rather than retyped?
Facts should be pre-filled rather than retyped because each manual copy is a chance to mistype a limit, a period or a commission.
Pre-filling also means the note and the submission always agree, which matters in any later dispute.
Which Fields Capture the Decision and the Rationale?
The decision and rationale fields capture what was agreed and why, in the underwriter's own words.
| Field | What to record | Example (hypothetical) |
|---|---|---|
| Outcome | Written, quoted not bound, or declined | Written |
| Line and capacity used | Share or amount written | 7.5% of the layer |
| Price vs technical price | Agreed rate and deviation | 4% below technical |
| Reason for deviation | Why the gap was accepted | Long-standing cedent, improved data |
| Top three reasons | The main drivers of the decision | Clean five-year experience, stable portfolio, adequate rate change |
| Key risks and mitigants | What could go wrong, and why it is acceptable | Growth in new region, capped by sub-limit |
| Data relied on | Which figures drove the price | 2021–2025 large loss listing |
| Conditions and subjectivities | What must happen before or after binding | Updated exposure by 31 January |
Our guide to technical price overrides and accountability explains why the deviation field matters.
How much rationale is enough?
Rationale is enough when a reviewer who was not in the meeting could understand the decision and challenge it from the note alone.
"Good relationship" is not rationale. "Accepted 4% below technical because exposure data improved materially" is.
What should a decline note record?
A decline note should record the main reason, such as appetite, price, data quality or capacity, plus what would change the answer.
That second part turns a decline into a lead for next year.
Our guide to declined reinsurance submissions analysis shows how to reuse decline notes across the book.
Which Governance Fields Make the Note Review-Ready?
The governance fields make the note review-ready by showing that the decision sat within authority and was checked.
| Field | Purpose |
|---|---|
| Authority level used | Shows the decision was within the underwriter's limit |
| Referral and approver | Records who approved anything outside authority |
| Peer review selected | Shows whether the risk was picked for review |
| Reviewer comments and actions | Records findings and how they were resolved |
| Renewal watch points | Lists what to check before next year's terms |
How do file notes support peer review?
File notes support peer review by giving the reviewer a consistent record to test, instead of an inbox to reconstruct.
Lloyd's peer review guidance says findings should be recorded to a consistent standard.
It adds that comments should be "readily available and utilised should the risk be renewed". The renewal watch points field does exactly that.
How Do You Keep Underwriting File Notes Current?
Underwriting file notes stay current when specific events, not memory, trigger an update to the same record.
Which events should trigger a file note update?
The events that should trigger a file note update are any change that would have altered the original decision.
- Endorsement or amendment: record what changed and whether the price was revisited.
- Material claim or loss development: note whether the original assumptions still hold.
- Peer review finding: add the finding and the action taken.
- Change of underwriter: confirm the note is complete before handover.
Our guide to reinsurance knowledge loss explains what disappears when handover notes are thin.
What should change at renewal?
At renewal, the underwriting file note should start from last year's watch points, not from a blank page.
The new note records whether each watch point was resolved, then adds this year's facts and decision.
Where Does Insurnest Fit in Underwriting File Notes Automation?
Insurnest fits at the start of underwriting file notes automation, by turning the broker submission into structured facts.
Reinsurance Email Intelligence for treaty submissions reads broker emails and attachments, including PDFs and spreadsheets.
It extracts cedent, broker, structure, premium, limits, commissions, claims history, loss ratios, exposure, period and territory.
That structured submission view provides the facts needed for sections 1 and 2 of the template. It also surfaces missing information early.
What should never be automated in a file note?
The decision, rationale and conditions should never be automated in a file note, because they record human judgement.
Insurnest does not write rationale or replace underwriting judgement. Underwriters validate the extracted facts.
For a wider view of where AI helps, see our guide to AI in reinsurance underwriting.
How Should a CUO Introduce Underwriting File Notes Automation?
A chief underwriting officer should introduce underwriting file notes automation in stages, starting where review risk is highest.
- Adopt the five-section template for all new business and referred treaties first.
- Make the information gaps, deviation and watch point fields mandatory.
- Pre-fill sections 1 and 2 from submission data so underwriters stop retyping.
- Ask peer reviewers to score notes against the template each quarter.
- Extend to all renewals once the first cycle is complete.
Measure completion within an agreed time after binding or declining, and track reviewer findings about missing rationale.
Key Terms
- Underwriting file note: The record of what was decided on a treaty, on what facts, and why.
- Technical price: The modelled price before commercial adjustments by the underwriter.
- Deviation: The gap between the agreed price and the technical price.
- Peer review: A check by another underwriter that a decision followed policy and authority.
- Renewal watch points: Specific issues recorded for review before the next renewal.
- Subjectivity: A condition that must be met for cover to be confirmed.
Sources
- Lloyd's: Minimum Standards MS2 – Underwriting and Controls (January 2021)
- Lloyd's: Peer Review Guidance (February 2021)
- Insurnest: Reinsurance Email Intelligence
Frequently Asked Questions
What is underwriting file notes automation?
Underwriting file notes automation pre-fills the factual parts of an underwriting file note from the submission, so underwriters only write the judgement. Header details, structure, premium, limits and loss history arrive already captured, while the decision, rationale and conditions stay in the underwriter's own words.
Why do reinsurers need underwriting file notes?
Reinsurers need underwriting file notes because they must be able to show why each treaty was written, priced or declined. Lloyd's MS2 expects managing agents to retain the rationale for risk acceptance, terms and pricing, and file notes are also the starting point for every renewal.
What should an underwriting file note include?
An underwriting file note should include a header, the key submission facts, the decision and line, the price against technical price, the top reasons, key risks and mitigants, conditions, referral and peer review details, and watch points for renewal. Each field should have a clear owner.
Who should write the rationale in an underwriting file note?
The underwriter who made the decision should write the rationale in an underwriting file note. Operations or automation can fill the facts, but only the decision-maker can explain the judgement, the trade-offs accepted and the assumptions relied on when terms were agreed or declined.
How long should an underwriting file note be?
An underwriting file note should be as short as the decision allows, often one page for a routine renewal. Complex, new or referred treaties need more. The test is whether a reviewer who was not in the room could understand and challenge the decision from the note alone.
Can AI write underwriting file notes?
AI can extract submission facts and pre-fill most of an underwriting file note, which removes repetitive typing. AI should not invent the underwriting rationale. Underwriters should validate the pre-filled facts and write the reasons, conditions and deviations from technical price in their own words.
How do automated file notes compare with free-text notes?
Automated, structured file notes differ from free-text notes in consistency and searchability. Free text varies by underwriter and is hard to review. Structured notes put the same fields in the same place, so peer reviewers, auditors and the next underwriter can compare decisions quickly.
How can a CUO measure file note quality?
A chief underwriting officer can measure file note quality by the share of bound and declined treaties with a complete note, notes completed within the agreed time, peer review findings about missing rationale, and renewals where prior watch points were actually reviewed.

Hitul Mistry
CEO, Insurnest
An InsurTech leader with more than a decade of experience across insurance and technology, focused on solving business problems with the help of technology. Has worked with brokers, insurance carriers, and reinsurance firms across the India, UAE, and US markets.
View LinkedIn profile →