Assess whether umbrella attachment is too thin for the hazard (bcf7fe)
August 31, 2026
SITUATION Treaty pricing actuary in a law firm buying cyber after a peer's ransom event has one working extract — D&O claims-made notice and prior-acts history — after an umbrella competitor offering limits you will not match. If D&O claims-made notice and prior-acts history cannot support umbrella attachment is too thin, the only defensible Insurance Underwriting output is hold.
DECISION Treaty pricing actuary 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 an umbrella competitor offering limits you will not match.
HYPOTHESES TO TEST 1. An umbrella competitor offering limits you will not match is noise around an already-controlled Specialty Liability process in a law firm buying cyber after a peer's ransom event, given D&O claims-made notice and prior-acts history. 2. An umbrella competitor offering limits you will not match is the event in D&O claims-made notice and prior-acts history that forces Bind for treaty pricing actuary under Insurance Underwriting. 3. D&O claims-made notice and prior-acts history shows a one-file miss after an umbrella competitor offering limits you will not match, not a Specialty Liability program failure. 4. D&O claims-made notice and prior-acts history cannot decide umbrella attachment is too thin yet after an umbrella competitor offering limits you will not match; hold is the only Insurance Underwriting close a law firm buying cyber after a peer's ransom event can defend.
ANALYSIS REQUIRED 1. Say whether a law firm buying cyber after a peer's ransom event can bind, restrict, or decline from the file as it stands. 2. Test exposure, limits, and endorsement language in D&O claims-made notice and prior-acts history after an umbrella competitor offering limits you will not match. 3. Flag any accumulation fact D&O claims-made notice and prior-acts history does not price. 4. For this Insurance Underwriting Specialty Liability file, read D&O claims-made notice and prior-acts history against an umbrella competitor offering limits you will not match and write the one fact that would move umbrella attachment is too thin for treaty pricing actuary.
RECOMMENDATION Choose Bind / Restrict / Decline / Hold on this Insurance Underwriting / Specialty Liability packet (D&O claims-made notice and prior-acts history after an umbrella competitor offering limits you will not match). The follow-on Specialty Liability action is what treaty pricing actuary does next: implement the option, assign an owner, and log the missing fact.
COMMAND RETURNS - Bottom-line Insurance Underwriting option on umbrella attachment is too thin, then the evidence in D&O claims-made notice and prior-acts history, then the action for treaty pricing actuary - Hypothesis scorecard against D&O claims-made notice and prior-acts history: supported / rejected / untestable - Specialty Liability 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 an umbrella competitor offering limits you will not match, if any
Explore more
More Insurance Underwriting prompts
- Assess whether the treaty is adequate or needs a cut (1bc99b)
- Assess whether cyber controls claimed are actually in force (5aa0bc)
- Assess whether the treaty is adequate or needs a cut (4bba39)
- Assess whether to non-renew a deteriorating book segment (f1ec38)
- Assess whether telematics improvements offset driver quality (4a1ec2)
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.

