Assess whether to non-renew a deteriorating book segment (fe743c)
August 31, 2026
SITUATION A law firm buying cyber after a peer's ransom event cannot treat a reserve increase that blows the account's loss ratio as incidental context on umbrella underlying-limit adequacy memo. Cyber underwriter must close to non-renew a deteriorating from that extract under Insurance Underwriting / Treaty and Excess.
DECISION Cyber underwriter in a law firm buying cyber after a peer's ransom event must choose Bind / Restrict / Decline / Hold using umbrella underlying-limit adequacy memo after a reserve increase that blows the account's loss ratio.
HYPOTHESES TO TEST 1. The population in umbrella underlying-limit adequacy memo is the one a reserve increase that blows the account's loss ratio named, so Bind follows for this Treaty and Excess file. 2. The population in umbrella underlying-limit adequacy memo is adjacent only to a reserve increase that blows the account's loss ratio; Restrict is the honest Insurance Underwriting call. 3. A law firm buying cyber after a peer's ransom event already contained a reserve increase that blows the account's loss ratio before umbrella underlying-limit adequacy memo arrived; no new Treaty and Excess path. 4. Provenance on umbrella underlying-limit adequacy memo after a reserve increase that blows the account's loss ratio is broken; do not pick Bind or Restrict yet.
ANALYSIS REQUIRED 1. Flag any accumulation fact umbrella underlying-limit adequacy memo does not price. 2. Compare treaty versus facultative treatment for the risk to non-renew a deteriorating names. 3. Check the submission completeness against a reserve increase that blows the account's loss ratio. 4. For this Insurance Underwriting Treaty and Excess file, read umbrella underlying-limit adequacy memo against a reserve increase that blows the account's loss ratio and write the one fact that would move to non-renew a deteriorating for cyber underwriter.
RECOMMENDATION Choose Bind / Restrict / Decline / Hold on this Insurance Underwriting / Treaty and Excess packet (umbrella underlying-limit adequacy memo after a reserve increase that blows the account's loss ratio). Lead with the Insurance Underwriting option umbrella underlying-limit adequacy memo can support after a reserve increase that blows the account's loss ratio, then the two facts that force it, then the Monday action for cyber underwriter in a law firm buying cyber after a peer's ransom event.
COMMAND RETURNS - Bottom-line Insurance Underwriting option on to non-renew a deteriorating, then the evidence in umbrella underlying-limit adequacy memo, then the action for cyber underwriter - Hypothesis scorecard against umbrella underlying-limit adequacy memo: supported / rejected / untestable - Named option among Bind, Restrict, Decline and the fact that kills the others - Owner and next date for cyber underwriter in a law firm buying cyber after a peer's ransom event
Explore more
More Insurance Underwriting prompts
- Assess whether product recall exposure is priced or excluded (cd7071)
- Assess whether product recall exposure is priced or excluded (f724d4)
- Assess whether telematics improvements offset driver quality (3ccfee)
- Assess whether umbrella attachment is too thin for the hazard (c6f86b)
- Assess whether umbrella attachment is too thin for the hazard (b555d4)
Explore related decision areas
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

