Assess whether the treaty is adequate or needs a cut (d27287)
August 31, 2026
SITUATION A fleet with a new ELD vendor and rising frequency cannot treat a product that just got an FDA warning letter as incidental context on umbrella underlying-limit adequacy memo. Cyber underwriter must close the treaty is adequate from that extract under Insurance Underwriting / Specialty Liability.
DECISION Cyber underwriter in a fleet with a new ELD vendor and rising frequency must choose The treaty is adequate / Needs a cut using umbrella underlying-limit adequacy memo after a product that just got an FDA warning letter.
HYPOTHESES TO TEST 1. Authorize The treaty is adequate now; umbrella underlying-limit adequacy memo already has the discriminator after a product that just got an FDA warning letter. 2. Keep Needs a cut in force until umbrella underlying-limit adequacy memo is completed after a product that just got an FDA warning letter for cyber underwriter. 3. Treat umbrella underlying-limit adequacy memo as The treaty is adequate because both readings appear after a product that just got an FDA warning letter. 4. Refuse a Insurance Underwriting close: cyber underwriter does not have the decision the treaty is adequate turns on in umbrella underlying-limit adequacy memo.
ANALYSIS REQUIRED 1. Say whether a fleet with a new ELD vendor and rising frequency can bind, restrict, or decline from the file as it stands. 2. Test exposure, limits, and endorsement language in umbrella underlying-limit adequacy memo after a product that just got an FDA warning letter. 3. Flag any accumulation fact umbrella underlying-limit adequacy memo does not price. 4. For this Insurance Underwriting Specialty Liability file, read umbrella underlying-limit adequacy memo against a product that just got an FDA warning letter and write the one fact that would move the treaty is adequate for cyber underwriter.
RECOMMENDATION Choose The treaty is adequate / Needs a cut on this Insurance Underwriting / Specialty Liability packet (umbrella underlying-limit adequacy memo after a product that just got an FDA warning letter). If umbrella underlying-limit adequacy memo cannot force a Insurance Underwriting label under Specialty Liability, stop. Do not invent missing evidence a fleet with a new ELD vendor and rising frequency does not have.
COMMAND RETURNS - Bottom-line Insurance Underwriting option on the treaty is adequate, 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 - Specialty Liability finding in umbrella underlying-limit adequacy memo that a second reviewer can re-perform - Missing page in umbrella underlying-limit adequacy memo after a product that just got an FDA warning letter, if any
Explore more
More Insurance Underwriting prompts
- Assess whether prior-acts and notice issues make D&O unbindable as submitted
- Assess whether CAT pricing is defensible given SOV quality (65c9d8)
- Fleet auto renewal underwriter must resolve whether to non-renew
- Assess whether a warranty should be converted to a condition precedent
- Assess whether the treaty is adequate or needs a cut (b60dff)
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.

