Assess whether prior-acts and notice issues make D&O unbindable as submitted
August 31, 2026
SITUATION The working file is D&O claims-made notice and prior-acts history after a ransomware questionnaire that still lists SMS MFA. Treaty pricing actuary in a law firm buying cyber after a peer's ransom event has to name Bind or Restrict for this Insurance Underwriting Specialty Liability file.
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 a ransomware questionnaire that still lists SMS MFA.
HYPOTHESES TO TEST 1. The population in D&O claims-made notice and prior-acts history is the one a ransomware questionnaire that still lists SMS MFA named, so Bind follows for this Specialty Liability file. 2. The population in D&O claims-made notice and prior-acts history is adjacent only to a ransomware questionnaire that still lists SMS MFA; Restrict is the honest Insurance Underwriting call. 3. A law firm buying cyber after a peer's ransom event already contained a ransomware questionnaire that still lists SMS MFA before D&O claims-made notice and prior-acts history arrived; no new Specialty Liability path. 4. Provenance on D&O claims-made notice and prior-acts history after a ransomware questionnaire that still lists SMS MFA is broken; do not pick Bind or Restrict yet.
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 a ransomware questionnaire that still lists SMS MFA. 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 a ransomware questionnaire that still lists SMS MFA and write the one fact that would move prior-acts and notice issues 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 a ransomware questionnaire that still lists SMS MFA). 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 prior-acts and notice issues, 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 - What changes prior-acts and notice issues if a ransomware questionnaire that still lists SMS MFA is later withdrawn - Named option among Bind, Restrict, Decline and the fact that kills the others
Explore more
More Insurance Underwriting prompts
- Assess whether the treaty is adequate or needs a cut (4b91f5)
- Assess whether telematics improvements offset driver quality (2908cf)
- Assess whether telematics improvements offset driver quality (f9876b)
- Assess whether pollution coverage should be site-specific or blanket (dcb12e)
- Assess whether CAT pricing is defensible given SOV quality (bcd565)
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.

