Assess whether to quote, refer, or decline (baafc5)
August 31, 2026
SITUATION A law firm buying cyber after a peer's ransom event cannot treat a product that just got an FDA warning letter as incidental context on product-liability claim frequency by SKU. Treaty pricing actuary must close to quote, refer, or decline from that extract under Insurance Underwriting / Specialty Liability.
DECISION Treaty pricing actuary in a law firm buying cyber after a peer's ransom event must choose To quote, refer, / Decline using product-liability claim frequency by SKU after a product that just got an FDA warning letter.
HYPOTHESES TO TEST 1. Product-liability claim frequency by SKU reads as To quote, refer, once a product that just got an FDA warning letter is lined up to the same Insurance Underwriting population. 2. Product-liability claim frequency by SKU is closer to Decline after a product that just got an FDA warning letter; To quote, refer, would over-claim this Specialty Liability extract. 3. A dual reading is still live in product-liability claim frequency by SKU for treaty pricing actuary in a law firm buying cyber after a peer's ransom event. 4. Product-liability claim frequency by SKU is missing the fact treaty pricing actuary needs after a product that just got an FDA warning letter; stop this Insurance Underwriting close.
ANALYSIS REQUIRED 1. Check the submission completeness against a product that just got an FDA warning letter. 2. Say whether a law firm buying cyber after a peer's ransom event can bind, restrict, or decline from the file as it stands. 3. Test exposure, limits, and endorsement language in product-liability claim frequency by SKU after a product that just got an FDA warning letter. 4. For this Insurance Underwriting Specialty Liability file, read product-liability claim frequency by SKU against a product that just got an FDA warning letter and write the one fact that would move to quote, refer, or decline for treaty pricing actuary.
RECOMMENDATION Choose To quote, refer, / Decline on this Insurance Underwriting / Specialty Liability packet (product-liability claim frequency by SKU after a product that just got an FDA warning letter). If product-liability claim frequency by SKU cannot force a Insurance Underwriting label under Specialty Liability, stop. If product-liability claim frequency by SKU after a product that just got an FDA warning letter cannot support To quote, refer, versus Decline on this Insurance Underwriting Specialty Liability close, treaty pricing actuary must do not bind, restrict, or decline beyond what the submission actually prices.
COMMAND RETURNS - Bottom-line Insurance Underwriting option on to quote, refer, or decline, then the evidence in product-liability claim frequency by SKU, then the action for treaty pricing actuary - Hypothesis scorecard against product-liability claim frequency by SKU: supported / rejected / untestable - Named option among To quote, refer,, Decline and the fact that kills the others - Owner and next date for treaty pricing actuary in a law firm buying cyber after a peer's ransom event
Explore more
More Insurance Underwriting prompts
- Assess whether prior-acts and notice issues make D&O unbindable as submitted
- Assess whether pollution coverage should be site-specific or blanket (a21aa4)
- Assess whether umbrella attachment is too thin for the hazard (01f1ad)
- Assess whether cyber controls claimed are actually in force (67ed31)
- Assess whether to quote, refer, or decline (da0a70)
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.

