Text-only version of https://ultrassure.com/resources/case-study-treaty-renewal-reinsurer for AI assistants, LLM crawlers, search engines, and non-JavaScript clients. The interactive application loads for visitors with JavaScript enabled.
The short answer: Treaty renewals slow down when teams manually reconcile multi-document renewal bundles (treaty wording, endorsements/addenda, I&Ls, schedules) across mixed-quality PDFs and scans. This reinsurer used Ultrassure to generate clause-level 'what changed' analysis with citations, standardize critical terms across renewals, and route ambiguity to review — cutting renewal cycles to days instead of weeks while improving auditability and consistency.
Key Takeaways
- 1. Documents processed: treaties, endorsements/addenda, I&Ls, schedules/exhibits; mix of native PDFs + scanned PDFs
- 2. Renewal cycle reduced from ~10–15 business days to ~2–4 business days (same scope, same team)
- 3. ~99% accuracy on critical structured fields after review pass; 'abstain + review' used for ambiguous clauses
- 4. Outputs: change map + cited summaries + structured exports with page/section citations
Results Snapshot
- Treaties, endorsements/addenda, I&Ls, exhibits
- Native PDFs + scanned PDFs + table-heavy packs
- Accuracy on critical fields
- Abstain + review queues + audit trails
- Change map + cited summaries + structured exports
Accuracy definition: correctness of extracted structured terms with correct source citations, after a human review pass, with ambiguous cases explicitly flagged (not guessed).
What is insurance contract AI? Software that ingests policies, endorsements, and schedules; preserves document structure; reasons across multi-document stacks; and produces auditable answers with citations. This case study shows what happens when that approach is applied to treaty renewals.Learn why generic AI fails →
The Problem: Why Treaty Renewals Took Weeks
The reinsurer's renewal team was losing time to three repeat pain points:
- Fragmented renewal bundles: Treaty wording, addenda/endorsements, I&Ls, and exhibits were scattered across mixed-quality PDFs (including scans).
- Manual comparison burden: The team needed a reliable way to answer "What changed?" across versions (expiring vs renewal) without manual clause-by-clause reading.
- Audit-ready outputs required: Outputs needed to survive internal scrutiny— structured term summaries and audit-ready evidence for counsel, underwriting leadership, and ops.
What documents were in scope (and what formats)?
This pilot focused on real renewal packages representative of their book.
In-scope document types
- Treaty wordings (quota share + XoL formats)
- Endorsements / addenda / amendments
- Interests & Liabilities (I&L) schedules
- Exhibits & reporting schedules
- Side letters where applicable (redacted)
File formats encountered
- Native PDFs (digitally generated)
- Scanned PDFs (mixed OCR quality)
- Schedule-heavy PDFs (multi-page tables)
- Slip-like summary pages embedded in PDF packs
Baseline Workflow (Before Ultrassure)
Their baseline process was typical for sophisticated reinsurers:
- Triage & intake (1–2 days) Gather documents, confirm"complete set," de-duplicate versions
- Manual comparison (4–8 days) Counsel/analysts compare expiring vs renewal, track changes in spreadsheets
- Term summary drafting (2–4 days) Create internal renewal summary, circulate for review
- Sign-off loop (2–4 days) Questions back to analysts; re-check source language; finalize approvals
Baseline cycle time: ~10–15 business days end-to-end (varied by complexity and number of endorsements)
New Workflow (After Ultrassure)
They implemented a repeatable"renewal bundle" workflow:
- Upload & auto-organization (same day) Treaties + endorsements + I&Ls grouped into a renewal bundle with version labels (expiring vs renewal)
- Automated extraction + citations (same day) Critical fields extracted into a standard schema; every field tied to source references
- Clause diff generation (same day) Ultrassure produced a structured"what changed" report highlighting deltas by clause category
- Review queue for edge cases (0.5–1 day) Ambiguous or scan-degraded sections routed for human confirmation rather than guessed
- Export & sign-off (1–2 days) Counsel and underwriting sign-off using a single source of truth: diff + cited summaries + CSV
New cycle time: ~2–4 business days end-to-end (same renewal bundle scope)
What did they measure (methodology you can replicate)?
This case study is intentionally"evidence-forward." Here's the measurement approach the team used:
1) Renewal cycle time (before/after)
- Before: measured from"bundle complete" →"internal sign-off sent"
- After: same definition, same renewal team, same sign-off gate
Result: ~10–15 days → ~2–4 days
2) Accuracy on critical fields
They defined a critical-field checklist and labeled"ground truth" from the final signed set.
Critical fields tested (examples):
- Limits (per risk / per event / aggregate)
- Attachment points / retentions
- Key exclusions (named peril, cyber, war, etc.)
- Reporting requirements (timelines, data fields)
- Claims cooperation / control / notification
- Commutation clauses (presence + mechanics)
Scoring rules:
- Correct: extracted term matches ground truth + correct citation
- Needs review: model abstained or flagged ambiguity
- Incorrect: wrong value or wrong clause reference
Result: ~96–99% accuracy on critical structured fields after the review pass (with abstentions routed to human review rather than guessed)
Outcomes Beyond Speed
Speed was the headline, but three outcomes mattered just as much:
- Consistency: Standardized term summaries reduced"analyst style variance" between teams.
- Auditability: Every key term and conclusion could be traced back to exact source language.
- Renewal governance: Clause diffs created a durable record of what changed and why.
How Changes Were Flagged (Change Map)
Instead of long redlines, the team used a change map that categorized differences and prioritized review.
Change categories tracked
- Limits & structure — limits, attachments, aggregates, reinstatements
- Reporting & bordereaux — frequency, deadlines, required fields
- Claims control — notice windows, cooperation, consent
- Exclusions & carve-backs — new or modified exclusions
- Definitions & interpretation — terms that alter meaning elsewhere
- Conditions & warranties — obligations, remedies, time limits
Impact levels
- High: Likely to change coverage, economics, or obligations
- Medium: Operational or timing change requiring review
- Low: Clarification, cleanup, or formatting
Example: What a change map looks like
- "Within 10 business days"
Critical Terms Checklist
Reinsurers should verify these fields are extracted accurately with correct citations:
Economics & structure
- Limits (per event / per risk / aggregate)
Operational obligations
- Notice triggers and timelines
- Claims control / cooperation
Coverage shaping
- Exclusions added, removed, or modified
- Carve-backs and sub-limits
- Key definitions affecting interpretation
- Conditions, warranties, and remedies
> Buyer-grade rule: A term only counts as extracted if it includes both a normalized value and a citation to the exact source language.
What were the hardest edge cases (and how were they handled)?
No system should pretend every clause is easy. The reinsurer encountered three common edge cases:
- Scan-degraded tables in I&Ls Handling: table-aware extraction + review queue for low-confidence cells
- Manuscript endorsements with dense cross-references Handling: definition linking + cited evidence retrieval
- "Same meaning, different wording" changes Handling: diff categorized as"semantic / potential impact" with human confirmation
> The key is governance: abstain rather than guess and route ambiguous items to review.
What Other Reinsurers Should Copy
If you want similar results, replicate these three principles:
- Treat renewals as bundles with version labels, not individual PDFs.
- Score success on cycle time + citation quality + critical-field accuracy, not"demo accuracy."
- Enforce"no-guessing" rules (abstain + review queues) for high-stakes clauses.
Planning a pilot? See theBuyer's Guide (2026)for evaluation scorecards, RFP questions, and practical pilot blueprints.
Ready to see Ultrassure in action?
Request a 30-minute demo to see how we can help your team process contracts faster with higher accuracy.
FAQ: Treaty Renewal Automation
How are hallucinations prevented?
Does this work on scanned renewal packs?
How long did it take to see results?
What should we measure in our own pilot?
Can this approach handle multi-jurisdictional treaty programs?
How does Ultrassure handle amendments and side letters mid-term?
Related Reading
How to Prepare a Treaty Renewal Faster
The workflow that compresses renewal prep to days.
Insurance Contract AI Software: Buyer's Guide (2026)
The definitive evaluation guide covering use cases, accuracy, scorecards, pilots, and ROI.
Northern Re Expands Its Use of Ultrassure
Reinsurer widens deployment across its contract portfolio.
Disclaimer: This content is provided for informational purposes only and does not constitute legal, financial, or professional advice. Please consult with qualified professionals for advice specific to your situation.
More from Ultrassure
- Ultrassure — Contract Certainty for the Business of Uncertainty — Insurance-native AI contract intelligence for carriers, MGAs, brokers, and reinsurers. Transform contracts into searchable intelligence with AI.
- AI Contract Intelligence Platform for Insurance Teams — Ultrassure turns insurance documents into searchable, structured intelligence for insurers, MGAs, brokers, and reinsurers, with extraction, semantic search, comparison, and governed review.
- Company | Ultrassure Insurance Contract Intelligence — Ultrassure builds AI contract intelligence software for insurers, MGAs, brokers, and reinsurers that need structured, searchable, evidence-linked contract operations.
- Request an Ultrassure Demo — Book a demo of Ultrassure, the insurance contract intelligence platform for insurers, MGAs, brokers, and reinsurers.
- Try Ultrassure Free — Start a free Ultrassure trial for AI-powered insurance document intelligence.
- Ultrassure FAQ — Answers to common questions about Ultrassure accuracy, security, implementation, document support, integrations, and pricing.
- Security at Ultrassure — SOC 2 Type II certified security, AES-256 encryption, TLS 1.3, RBAC, SSO/SAML, audit logging, and enterprise controls.
- Privacy Policy — Ultrassure privacy practices and data protection commitments.
- Terms of Service — Ultrassure terms and legal conditions.
- Ultrassure Trust Center — Security, compliance, privacy, reliability, subprocessors, legal resources, and trust documentation for Ultrassure.
- Trust Center — Compliance — SOC 2 Type II, GDPR, HIPAA readiness, CCPA, audit practices, and compliance resources.
- Trust Center — Privacy — Customer data privacy, model training policy, deletion rights, data residency, and privacy-by-design controls.
- Trust Center — Subprocessors — Third-party subprocessors used by Ultrassure and data processing commitments.
- Trust Center — Reliability — Uptime, SLA, monitoring, incident response, recovery objectives, and platform resilience.
- Trust Center — Legal — Master Services Agreement, DPA, BAA, SCCs, and enterprise legal resources.
- Trust Center FAQ — Security, privacy, compliance, and reliability questions for enterprise insurance buyers.
- Request Trust Center Access — Request access to Ultrassure security and compliance documentation.
- Ultrassure Resources — Buyer guides, case studies, answer pages, and practitioner resources for insurance contract intelligence.
- Insurance Contract Management Buyer Guide — Evaluation framework for AI contract intelligence platforms, pilots, ROI, security, and compliance.
- Treaty Renewal Case Study — How a global reinsurer reduced treaty renewal processing from 10–15 days to 2–4 days with Ultrassure.
- AI in Commercial Insurance Underwriting Guide — Practitioner guide to AI use cases in commercial insurance underwriting and contract certainty.
- Insurance Contract Intelligence Answers — Citation-ready answers for insurance contract intelligence, automation, clause mapping, renewals, compliance, and integrations.
- What Is Insurance Contract Intelligence? — Insurance contract intelligence transforms policies, slips, binders, treaties, endorsements, and schedules into searchable structured data.
- Binder vs Slip vs Policy vs Bordereau — Definitions and differences between common insurance placement and contract documents.
- How Automated Extraction Works — How AI extracts structured data from insurance documents with validation, confidence scoring, and audit trails.
- What Is Clause Mapping? — Clause mapping identifies, normalizes, compares, and tracks clauses across insurance contracts.
- Compare Contract Versions Quickly — How insurance teams compare expiring and renewal contracts, clauses, endorsements, and manuscript changes.
- Prepare Treaty Renewal Faster — How reinsurers and brokers accelerate treaty renewal preparation with contract intelligence.
- Improve Compliance Without Headcount — How automated compliance checks reduce manual review burden for insurance teams.
- Security FAQ for Contract Intelligence — Security questions enterprise buyers ask when evaluating AI contract intelligence platforms.
- Integrations FAQ — How Ultrassure integrates with policy administration, document management, data warehouses, BI tools, and APIs.
- Contract Intelligence vs CLM — How insurance contract intelligence differs from general contract lifecycle management software.
- Quota Share vs Excess of Loss Reinsurance: What's the Difference? — Quota share is proportional reinsurance sharing covered business by an agreed percentage; excess of loss is non-proportional reinsurance responding above a retention up to the treaty limit.
- What Is an I&L in Reinsurance? Interests and Liabilities Agreements Explained — An I&L, or Interests and Liabilities Agreement, records a subscribing reinsurer's participation in a reinsurance contract, including layer shares and its relationship to the underlying treaty.
- Ultrassure Blog — Articles on AI, insurance contract intelligence, underwriting operations, and document automation.
- Why Most AI Fails on Insurance Contracts — Why generic AI struggles with insurance contracts and how insurance-native contract intelligence improves reliability.
- Ultrassure vs Copilot GPT-5.1 Smart — Comparison of Ultrassure and general AI assistants for insurance contract intelligence workflows.
- Ultrassure Joins Creative Destruction Lab’s 2026/27 Risk Stream — Toronto-based insurtech Ultrassure has joined Creative Destruction Lab’s 2026/27 Risk Stream at the University of Wisconsin-Madison. Ultrassure is the AI system of intelligence for insurance, with more than $10 billion of platform premium flowing through the platform.
- Full Stack Engineer at Ultrassure — Career opportunity for a full stack engineer building insurance-native AI contract intelligence.
- Forward Deployed Engineer at Ultrassure — Career opportunity for a forward deployed engineer working with insurance teams and AI workflows.
- AI Engineer at Ultrassure — Career opportunity for an AI engineer building reliable document intelligence for insurance contracts.
- Founding Account Executive at Ultrassure — Career opportunity for a founding account executive helping insurance enterprises adopt Ultrassure.
- Millennium Insurance Selects Ultrassure — Press release: Millennium Insurance Corporation selects Ultrassure for AI contract intelligence.
- Pillar Capital Management Adopts Ultrassure for Contract Review Workflows — Customer announcement: Bermuda-based collateralized reinsurance and ILS manager Pillar Capital Management adopts Ultrassure for contract review and underwriting workflows. Covered by Artemis on September 17, 2026.
- Northern Re Expands Its Ultrassure Partnership — Press release: Northern Re expands its use of Ultrassure for treaty and contract intelligence.
- Ultrassure Support & Help Center — Support contact options, service level targets, and Trust Center resources for Ultrassure customers.
Full plain-text context for AI assistants: /llms-full.txt and /ai/sitemap.md.