Use case
Compare expiring and renewal treaty wording, clause by clause.
For reinsurance underwriters, brokers and contract teams preparing a renewal. Upload the expiring and renewal bundle (treaty wording, endorsements, I&Ls and schedules) and Ultrassure produces a “what changed” report grouped by clause, with every change linked to the page and section it came from. You need both versions of the documents, as native PDFs, Word files or scans.
- Who it’s for
- Treaty underwriters, brokers, contract and legal teams
- What you need
- Expiring and renewal bundles: wordings, endorsements, I&Ls, schedules
- What you get
- A cited change map, clause summaries and a CSV export
- Typical result
- Renewals in ~2–4 business days, down from ~10–15 (case study)
The finished result
Sample “what changed” report
Sample data for illustration. Not from a real contract.
| Clause | Expiring | Renewal | Change | Source |
|---|---|---|---|---|
| Loss occurrence (windstorm hours) | 168 consecutive hours | 144 consecutive hours | Narrower | Art. 7, p. 15 |
| Retention | USD 25,000,000 | USD 30,000,000 | Higher | Schedule A, p. 2 |
| Reinstatements | One at 100% | One at 100% additional premium | Terms changed | Art. 9, p. 18 |
| Communicable disease exclusion | Not present | Added | New exclusion | Endorsement 2, p. 1 |
| Territory | Worldwide excl. USA | Worldwide excl. USA | No change | Art. 3, p. 6 |
Step by step
One complete example.
- 01
Gather the renewal bundle
Collect the expiring and renewal treaty wordings with their endorsements or addenda, I&L schedules and exhibits. Native PDFs, Word files and scanned PDFs can all go in.
- 02
Upload and label the versions
Upload the files, or bring them in from SharePoint, a virtual data room or S3. Ultrassure groups them into one renewal bundle and labels each document as expiring or renewal.
- 03
Extract the critical terms with citations
Limits, retentions, reinstatements, premium, commissions, territory, exclusions and special conditions are pulled into a standard set of fields. Each value is tied to the page and section it came from.
- 04
Generate the clause comparison
Ultrassure produces a “what changed” report grouped by clause category. It shows changes in meaning, such as a limit raised or an exclusion added, not just edited words.
- 05
Review anything flagged
Ambiguous or scan-degraded sections go to a review queue for a person to confirm instead of being guessed.
- 06
Export and sign off
Share the change map, the cited clause summaries and a CSV export with counsel and underwriting for sign-off, from one source of truth.
Questions that could stop you
Does it work on scanned PDFs?
Yes. The treaty-renewal case study used a mix of native PDFs, scanned PDFs of varying OCR quality and table-heavy schedules. Sections that are hard to read are routed to review rather than guessed.
What happens when a clause is ambiguous?
It is flagged for human review instead of being given a confident answer. In the case study, ambiguous items were explicitly flagged and confirmed by the team before sign-off.
Does this replace our counsel’s review?
No. It gives counsel and underwriters a cited starting point so they spend their time on the changes that matter, not on finding them.
How long does it take?
In the case study, the full renewal cycle went from about 10–15 business days to about 2–4 for the same scope and team. Extraction and comparison happened the same day; the rest was review and sign-off.
Is our contract wording used to train AI models?
No. Customer contracts, prompts, outputs and embeddings derived from customer data are not used to train, retrain or fine-tune generally available or third-party foundation models.
Who can see the documents?
Access is controlled with role-based permissions and every action is recorded in audit logs. Ultrassure can support SSO, including Microsoft Entra ID, and is SOC 2 Type II certified. See the Trust Center.
Do we need a paid plan to try this?
You can try Ultrassure free with no credit card, or book a demo and see this workflow run on your own documents. Plans for production use are scoped with you on the demo.
Other use cases
Building the tools we wish we had as underwriters.
Make every promise provable.
No credit card required · Typically live in 10 business days