Underwriters renew on loss experience. In most carriers that experience reaches them as a loss run pulled before the renewal meeting — weeks old, missing the suit filed last month and the reserve that moved last week. InsightCW and InsightUW share the claim as it happens, in both directions.
Two directions
UW to CW: the policy as it stood on the loss date. CW never owns policies; it asks UW and keeps the answer dated. CW to UW: eleven claim events, signed, each with an event id so a redelivery is ignored.
What the underwriter sees because of it
- Claims experience that is current. UW keeps a twin of each claim on the account, updated by every reserve movement, payment and recovery, so the account view and the renewal read today's incurred.
- Alerts that matter to a renewal. A large loss, a suit and an SIU referral are events UW receives the moment CW records them.
- The net loss. Recoveries reach UW as they land, so the carrier's net loss on the account is right before the renewal, not after.
- Deductible billing. On large-deductible programmes, each deductible bill is kept beside the claim in UW and included in the renewal's experience. A bill carries no claim position, so it never resets the claim's status or loss date in UW.
How the events are made safe
- Outbox. CW writes each event to an outbox in the same transaction as the change, and a worker publishes it. A change without its event, or an event without its change, cannot happen.
- Signed and idempotent. Each delivery is signed with a shared secret; UW refuses a bad signature and ignores an event id it has already applied.
- A written contract. The event types, their fields and the destinations are a versioned contract file that CW, UW, InsightCede and InsightPulse each keep an identical copy of, checked by their tests.
- Demo rows never leave. Illustrative and seeded events are recorded as such and never sent.
The late-notice use case shows the policy lookup in action, and the auto subrogation use case shows a recovery reaching UW.