Reinsurance

Treaty Quote Revision Tracking: A Stale-Quote Timeline

On this page

Last reviewed: November 2026

The slip carried the lowest price you offered. It did not carry the flood sublimit that came with that price.

Nobody lied. Four quote versions crossed in three weeks, and one of them never reached the tracker.

Treaty quote revision tracking is the controlled log of every version of a reinsurer's treaty quote, with status, validity, terms and changes.

It matters because a slip assembled from two versions binds a price you never offered on terms you never priced.

This guide gives you a dated v1 to v4 timeline, root causes with the control for each, a version log schema and validity rules.

Key Takeaways

  • Number every version. A quote without a version ID cannot be checked.
  • Price and terms travel together. Never accept one version's rate with another's terms.
  • Validity is a hard stop. Expired firm quotes need a new version.
  • Check slips against the log. Not against memory or the last email you remember.

What Is Treaty Quote Revision Tracking?

Treaty quote revision tracking is the record of each quote version a reinsurer issues on one treaty, from indication to firm order.

Deadline control is a separate task; see quote deadline tracking for reinsurers. Brokers track the other side in reinsurer quote tracking for brokers.

What is the difference between an indicative and a firm treaty quote?

The difference between an indicative and a firm treaty quote is whether the cedent can accept it as stated.

An indicative quote guides negotiation. A firm quote binds you if accepted within its validity, so each firm version needs its own clean record.

How Did One Cat Layer Get Bound on a Stale Quote Version?

One cat layer got bound on a stale quote version through the dated sequence below.

The case is illustrative: a USD 50m xs 50m property cat layer at the 1 January 2025 renewal. ROL means rate on line.

Date and timeEventVersion statusTracker showsRunning position
Mon 18 Nov 2024, 10:00v1 sent: ROL 12.0%, 1 reinstatement at 100%v1 indicativev1Negotiating
Wed 27 Nov 2024, 15:20New exposure file; v2: ROL 11.0%, flood sublimit USD 25mv2 indicativev2Negotiating
Wed 4 Dec 2024, 12:00v3: ROL 11.5%, no flood sublimit, valid to Wed 11 Dec 17:00v3 firmv3Firm offer open
Tue 10 Dec 2024, 18:40v4 emailed from a phone: ROL 11.0% with USD 25m flood sublimit, valid to Fri 13 Dec 17:00v4 firm, v3 supersededv3Tracker stale
Wed 11 Dec 2024, 17:00v3 validity endsv3 expiredv3Tracker stale
Fri 13 Dec 2024, 11:30Firm order "per your firm quote": ROL 11.0%, wording drafted from v3, no sublimitMixed v3/v4v3Reviewer sees v3 terms match
Thu 19 Dec 2024Line stamped at 15%Boundv3Bound on mixed terms
Wed 8 Jan 2025Post-bind review finds missing flood sublimitExceptionv3Unpriced flood exposure

At a 15% line, the missing sublimit leaves 15% × (50m − 25m) = USD 3.75m of flood limit that v4 never priced.

What Root Causes Lead Reinsurers to Quote or Bind on a Stale Version?

Root causes that lead reinsurers to quote or bind on a stale version sit in the process, not in one person's error.

Each root cause below has a control that would have caught it.

Root cause in the timelineControl that would have caught it
v4 sent from a phone, outside the logQuotes go out only from the version log, or sent mail is auto-logged
Quote documents carried no version IDEvery quote states "Q-ID v[n]"; firm orders must cite it
v3 used after its validity endedAutomatic "expired" status; acceptance blocked without a new version
Reviewer compared slip to the tracker, not the last sent quoteSlip check against the latest firm version in the log, field by field
Price and terms checked separatelyPrice and terms locked as one version record

The field-by-field slip check is set out in quoted vs bound terms reconciliation.

Which Fields Should a Treaty Quote Version Log Record?

A treaty quote version log should record one row per version, with these fields.

QUOTE VERSION LOG
Quote ID / version   : [Q-2025-0412] / [v4]
Treaty / layer       : [cedent] [programme] [layer] [period]
Status               : [indicative | firm | superseded | expired | withdrawn | accepted]
Sent at / valid to   : [date, time] / [date, time, time zone]
Sent to / channel    : [broker contact] / [log | email | phone note]
Data basis           : [exposure file name and date]
Price                : [ROL or rate %] [premium at 100%]
Key terms            : [reinstatements] [sublimits] [exclusions] [hours clause]
Subjectivities       : [list]
Line offered         : [written line %]
Changed vs prior     : [fields changed from v(n-1)]
Author / approver    : [underwriter] / [authority holder]
Document ref         : [file name and hash]

The "changed vs prior" line is what lets a reviewer spot a sublimit that came and went.

How should validity dates on firm treaty quotes be enforced?

Validity dates on firm treaty quotes should be enforced by the log itself, not by memory.

  1. Mandatory field. No firm version saves without a valid-to time and time zone.
  2. Auto-expiry. Status flips to "expired" at that time.
  3. Superseding. A new firm version marks the prior one superseded at once.
  4. Acceptance check. A firm order against an expired or superseded version is blocked until a new version is issued.

How Should Reinsurers Track Treaty Quote Revisions Through Negotiation?

Reinsurers should track treaty quote revisions through negotiation with a short, enforced routine.

  • Issue from the log. Phone agreements are written up as a version within the hour.
  • Ask brokers to cite versions. Firm orders quote the Q-ID and version number.
  • Compare like with like. Each version records the data basis it priced.
  • Review the slip against one version. Price, terms and line from the same record.
  • Keep the history. Superseded versions stay readable for audit.

Why does contract certainty depend on tracking quote versions?

Contract certainty depends on tracking quote versions because you cannot show agreed terms without knowing which version was agreed.

Lloyd's describes contract certainty as complete and final agreement of all terms by the time the contract is entered into.

The HMRC Lloyd's Manual glossary treats the written line as the maximum an insurer agreed when initialling a slip.

Your version log proves which terms that line was agreed on.

How Does Insurnest Fit With Treaty Quote Revision Tracking?

Reinsurance Treaty Management does not manage quotes, negotiation or broker placement. Keep the quote version log in your underwriting workflow.

Once bound, it holds the treaty's structure, terms, share, retention and limits as a controlled record.

Later amendments become new versions with an audit trail.

That gives the post-bind review one agreed version to test the slip against.

Key Terms

  • Firm quote: A quote the cedent can accept as stated within its validity period.
  • Superseded version: A quote version replaced by a later one; it stays on file but cannot be accepted.
  • Firm order: The broker's instruction to bind on stated terms.

Sources

Frequently Asked Questions

What is treaty quote revision tracking?

Treaty quote revision tracking is the controlled log of every version of a reinsurer's quote on a treaty, with its status, validity, terms and changes, from first indication to binding.

What is the difference between an indicative and a firm treaty quote?

The difference between an indicative and a firm treaty quote is commitment. An indicative quote guides negotiation; a firm quote can be accepted as stated until its validity date.

How did one cat layer get bound on a stale quote version?

One cat layer got bound on a stale quote version when a v4 price was sent outside the tracker and the slip combined it with v3 terms, dropping a USD 25m flood sublimit.

What root causes lead reinsurers to quote or bind on a stale version?

Root causes that lead reinsurers to bind on a stale version are quotes sent outside the log, unnumbered quote documents, unenforced validity dates and slips checked against the wrong version.

Which fields should a treaty quote version log record?

A treaty quote version log should record quote ID, version, status, sent and valid-until times, data basis, price, key terms, line offered, changes from the prior version and approver.

How should validity dates on firm treaty quotes be enforced?

Validity dates on firm treaty quotes should be enforced by marking expired versions automatically and requiring a new version number before any expired quote is accepted.

How should reinsurers track treaty quote revisions through negotiation?

Reinsurers should track treaty quote revisions by numbering every version, sending quotes only from the log, requiring the version on firm orders and checking slips against it.

Why does contract certainty depend on tracking quote versions?

Contract certainty depends on tracking quote versions because Lloyd's defines it as complete and final agreement of all terms when the contract is entered into.

Hitul Mistry

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 →
ShareLinkedInX

Read our latest blogs and research

Featured Resources

Reinsurance

Quoted vs Bound Terms Reconciliation for Reinsurers

Quoted vs bound terms reconciliation catches changes made between quote and final slip. See a field-by-field cat XL example with premium impact.

Read more
Reinsurance

Quote Deadline Tracking for Reinsurers: Never Miss Quote-By

Quote deadline tracking for reinsurers: a renewal timeline from receipt to bind with owners, a worked back-plan for a 1 January treaty and escalation triggers.

Read more
Reinsurance

Reinsurer Quote Tracking for Brokers: Every Market Response

Reinsurer quote tracking for brokers compared: spreadsheets, broking systems, placing platforms and email capture, plus decision rules and a quote template.

Read more

Meet Our Innovators:

We aim to revolutionize how businesses operate through digital technology driving industry growth and positioning ourselves as global leaders.

circle basecircle base
Pioneering Digital Solutions in Insurance

Insurnest

Empowering insurers, re-insurers, and brokers to excel with innovative technology.

Insurnest specializes in digital solutions for the insurance sector, helping insurers, re-insurers, and brokers enhance operations and customer experiences with cutting-edge technology. Our deep industry expertise enables us to address unique challenges and drive competitiveness in a dynamic market.

Get in Touch with us

Ready to transform your business? Contact us now!

We respond within one business day.