Back to the prompt
Step by step

Analyze whether a claim is covered

This page lists three turns, the messages you send to the AI one after another in the same chat, and then a check of the answer. Keep it open next to your chat. Each turn shows the next thing to paste, with the values you entered already filled in. Nothing is sent from this page, and your conversation stays in the AI tool you are using.

Declarations, insuring agreement, definitions, exclusions, conditions, and every endorsement. Paste as much as you have.

What happened, what is alleged, and every date that matters: loss, claim, first knowledge, notice.

Whose law governs the policy and where a coverage dispute would be filed.

Which policy is being analyzed.

Your side, which sets whose burden you should stress-test hardest.

Limits, SIR or deductible, whether defense erodes limits, and the size of the demand.

Watch for these throughout

  • The model sees only what you paste. A single endorsement can reverse the entire analysis. Paste the declarations and the full endorsement schedule, not just the form.
  • Whether a court looks past the complaint to extrinsic facts in deciding the duty to defend, and whether late notice requires prejudice, both vary sharply by state. Confirm the rule where the coverage suit would be filed before relying on any conclusion here.
  • Claims-made analysis fails quietly. Retroactive dates, prior-knowledge wording, and the difference between claims-made and claims-made-and-reported all turn on exact policy language. Read it yourself.
  • Allocation across policy periods, exhaustion of underlying limits, and other-insurance clauses are recurring blind spots for the model in long-tail and tower claims.
  • Do not paste an insured's confidential claim file or privileged investigation material unless your firm's AI policy and the client's engagement terms permit it.