Assess whether to non-renew a deteriorating book segment (9bcd32)

SITUATION After a reserve increase that blows the account's loss ratio, D&O claims-made notice and prior-acts history is what cyber underwriter can touch in a law firm buying cyber after a peer's ransom event. Insurance Underwriting will live with Bind versus Restrict on this Treaty and Excess file.

DECISION Cyber underwriter in a law firm buying cyber after a peer's ransom event must choose Bind / Restrict / Decline / Hold using D&O claims-made notice and prior-acts history after a reserve increase that blows the account's loss ratio.

HYPOTHESES TO TEST 1. A reserve increase that blows the account's loss ratio is noise around an already-controlled Treaty and Excess process in a law firm buying cyber after a peer's ransom event, given D&O claims-made notice and prior-acts history. 2. A reserve increase that blows the account's loss ratio is the event in D&O claims-made notice and prior-acts history that forces Bind for cyber underwriter under Insurance Underwriting. 3. D&O claims-made notice and prior-acts history shows a one-file miss after a reserve increase that blows the account's loss ratio, not a Treaty and Excess program failure. 4. D&O claims-made notice and prior-acts history cannot decide to non-renew a deteriorating yet after a reserve increase that blows the account's loss ratio; hold is the only Insurance Underwriting close a law firm buying cyber after a peer's ransom event can defend.

ANALYSIS REQUIRED 1. Flag any accumulation fact D&O claims-made notice and prior-acts history 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 D&O claims-made notice and prior-acts history 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 (D&O claims-made notice and prior-acts history after a reserve increase that blows the account's loss ratio). The follow-on Treaty and Excess action is what cyber underwriter does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line Insurance Underwriting option on to non-renew a deteriorating, then the evidence in D&O claims-made notice and prior-acts history, then the action for cyber underwriter - Hypothesis scorecard against D&O claims-made notice and prior-acts history: supported / rejected / untestable - Treaty and Excess finding in D&O claims-made notice and prior-acts history that a second reviewer can re-perform - Missing page in D&O claims-made notice and prior-acts history after a reserve increase that blows the account's loss ratio, if any