Treaty Contacts Register for Reinsurers: Who to Call
On this page
- Key Takeaways
- What Is a Treaty Contacts Register for Reinsurers?
- Who Should a Reinsurer Contact for Each Treaty Scenario?
- How Should a Treaty Contacts Register Be Maintained Stage by Stage?
- Where Do Treaty Contact Handoffs Fail?
- Does Data Protection Law Require a Treaty Contacts Register to Be Accurate?
- How Does Insurnest Fit Around a Treaty Contacts Register?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
A large loss notice lands on a Friday afternoon. The cedent's claims manager on file left in March, and the address bounces.
The broker's account executive moved firms last year. By Monday, the notice period on the treaty is two days shorter.
A treaty contacts register for reinsurers is a list of named people at each cedent, broker and internal team, mapped to treaties and scenarios.
It matters because notice periods, cash calls and sanctions queries run on the clock, and a wrong address stops the clock for nobody.
This guide gives you a who-to-call matrix, register fields, a stage-by-stage maintenance workflow and an escalation path.
Key Takeaways
- Map people to scenarios. One contact per treaty is not enough.
- Verify by call-back. Bank changes are confirmed on a number you already hold.
- Review on a cadence. Renewal plus quarterly checks catch most leavers.
- Log the source. Every record shows where it came from and when it was checked.
What Is a Treaty Contacts Register for Reinsurers?
A treaty contacts register for reinsurers maps each treaty to the people who act on it, by scenario, at the cedent, the broker and your own firm.
It is narrower than a CRM for reinsurers, which manages relationships. The register answers one question fast: who acts on this treaty, now?
Which fields should each treaty contact record hold?
Each treaty contact record should hold the fields below, keyed to the treaty ID in your reinsurance treaty register.
| Field | Example (illustrative) | Rule |
|---|---|---|
| Treaty ID | PROP-QS-2025-014 | Must exist in the treaty register |
| Organisation and role | Cedent, claims | Cedent, broker or internal |
| Scenario | Claim notice | From the matrix list only |
| Name and job title | Named person | No "TBC" at bind |
| Mailbox | Personal plus team mailbox | Both, where available |
| Verified phone | Main switchboard + direct line | Taken from a trusted source |
| Backup | Second named person | Required for claims and cash |
| Source and verified date | Broker closing, 12 Jan 2025 | Never blank |
| Next review date | Renewal or quarter end | Auto-set |
Who Should a Reinsurer Contact for Each Treaty Scenario?
A reinsurer should contact a different named person for each treaty scenario. Time limits come from the treaty wording or your own service targets.
| Scenario | Cedent contact | Broker contact | Internal owner | Time limit |
|---|---|---|---|---|
| Claim notice / large loss advice | Claims manager | Claims broker | Treaty claims handler | Per treaty notification clause |
| Cash call | Reinsurance finance | Claims broker | Technical accounting | Per cash loss clause |
| Accounts and statements | Reinsurance accounting | Technical accounting broker | Technical accounting | Per accounting clause |
| Wording query | Head of reinsurance | Placing broker | Treaty underwriter | Internal target: 5 working days |
| Dispute or arbitration | Legal / head of reinsurance | Account executive | Legal counsel | Per disputes clause |
| Sanctions query | Compliance officer | Broker compliance | Compliance | Internal target: same day |
Send a sanctions hit to compliance, not the underwriter. Our sanctions screening for reinsurance guide covers the screening itself.
How Should a Treaty Contacts Register Be Maintained Stage by Stage?
A treaty contacts register should be maintained stage by stage, with an owner, an approver and evidence for every change.
| Stage | Trigger | Action | Owner | Approver | Evidence | Time limit |
|---|---|---|---|---|---|---|
| 1. Load | Treaty bound | Add all scenario contacts | Treaty admin | Underwriter | Closing, broker email | Before first account |
| 2. Renewal refresh | Renewal bound | Confirm or replace each contact | Treaty admin | Underwriter | Renewal pack | 10 working days |
| 3. Change notice | Email or letter | Update record, keep old one dated | Treaty admin | Team lead | Notice on file | 2 working days |
| 4. Bank change | Request received | Call-back, then update | Technical accounting | Finance head | Call note | Before next payment |
| 5. Quarterly review | Quarter end | Test bounces, confirm leavers | Treaty admin | Ops head | Review log | 15 working days |
| 6. Re-screen | Contact or entity change | Sanctions screen new names | Compliance | Compliance head | Screen result | Before update goes live |
Time limits here are illustrative internal targets. Set your own and measure them.
A workable review cadence is renewal plus each quarter end, with an extra check after any merger or broker change.
How should a reinsurer verify a change of bank details from a cedent contact?
A reinsurer should verify a change of bank details from a cedent contact by calling a number already on the register.
Never use a phone number from the change request itself. Record who confirmed, on what number, and when.
Where Do Treaty Contact Handoffs Fail?
Treaty contact handoffs fail at the moments when people or firms change and nobody owns the update.
- Leaver at the cedent. The mailbox still accepts mail for weeks, then bounces.
- Broker merger or move. The account executive moves; the placing broker changes.
- Internal leaver. Notices route to a closed inbox; see treaty portfolio handover for reinsurers.
- Out-of-office forever. An auto-reply hides that nobody reads the address.
- Single contact. One person holds claims, cash and accounts, with no backup.
What escalation path applies when a treaty contact cannot be reached?
When a treaty contact cannot be reached, the escalation path should be fixed in advance and logged.
- Backup contact. Same scenario, same day.
- Broker account executive. If no reply within your internal target.
- Cedent head of reinsurance. For time-critical notices and cash calls.
- Internal escalation. Your head of operations decides on formal notice routes.
Log every attempt with time and channel. That log is your evidence if timing is later disputed.
Does Data Protection Law Require a Treaty Contacts Register to Be Accurate?
Data protection law requires a treaty contacts register to be accurate where it holds named people, because their details are personal data.
UK GDPR Article 5(1)(d) requires personal data to be "accurate and, where necessary, kept up to date". See the ICO guidance on the accuracy principle.
The ICO's checklist also expects a process to identify when data needs updating, and a record of its source.
The source, verified date and next review date fields above do both.
For sanctions, OFSI's reporting guidance says relevant firms must report suspected designated persons as soon as practicable.
How Does Insurnest Fit Around a Treaty Contacts Register?
Reinsurance Treaty Management does not store or manage contacts. Keep the register in your CRM or a controlled sheet.
What it holds is the other half of the matrix: each treaty's structure, terms and conditions, shares, limits and settlement conditions.
Amendments become controlled versions with an audit trail.
Key the register to the same treaty IDs. Then the person you call and the terms you quote come from the same reference.
Key Terms
- Who-to-call matrix: A table mapping each treaty scenario to named contacts and an owner.
- Call-back: Confirming a request by phoning a number already held, not one supplied in the request.
- Accuracy principle: The UK GDPR rule that personal data be accurate and, where necessary, up to date.
Sources
- ICO: Principle (d): Accuracy
- GOV.UK (OFSI): Reporting information to OFSI: what to do
- Insurnest: Reinsurance Treaty Management
Frequently Asked Questions
What is a treaty contacts register for reinsurers?
A treaty contacts register for reinsurers is a list of named people at each cedent, broker and internal team, mapped to treaties and to the scenarios each person handles.
Which fields should each treaty contact record hold?
Each treaty contact record should hold treaty ID, organisation, role, scenario, name, mailbox, verified phone, backup, source, verification date and next review date.
Who should a reinsurer contact for each treaty scenario?
A reinsurer should contact a named person per treaty scenario: cedent claims for claim notices, cedent finance for cash calls and accounts, broker for wording, compliance for sanctions.
How should a treaty contacts register be maintained stage by stage?
A treaty contacts register should be maintained stage by stage: load at bind, refresh at renewal, update on change notice, call back on bank changes, review quarterly and re-screen.
How should a reinsurer verify a change of bank details from a cedent contact?
A reinsurer should verify a change of bank details from a cedent contact by calling back a number already held on the register, never one supplied in the change email.
Where do treaty contact handoffs fail?
Treaty contact handoffs fail when people leave, brokers merge, shared mailboxes close or out-of-office replies hide a dead address, so notices reach nobody who can act.
What escalation path applies when a treaty contact cannot be reached?
When a treaty contact cannot be reached, escalate to the named backup, then the broker's account executive, then the cedent's head of reinsurance, logging each attempt with a time.
Does data protection law require a treaty contacts register to be accurate?
Data protection law requires a treaty contacts register to be accurate where it holds named people. UK GDPR Article 5(1)(d) requires personal data to be accurate and, where necessary, up to date.

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 →