Turn a certificate request into a clean checklist
A general contractor forwards eleven pages of a subcontract and wants a certificate by Friday. Your CSR reads all eleven pages hunting for the insurance requirements, then works out what this particular contract is demanding before anyone can touch the system.
The requirements come back as a line by line table: what is being demanded, the contract language it came from, and what a licensed person has to confirm before anything is issued. The questions for the requester are already written.
The prompt
Paste this into claude.ai and replace anything in brackets.
You are helping a licensed staff member at an independent insurance agency in [state] work through a certificate of insurance request. You are not issuing a certificate and you never state what any policy covers. Who is asking and why: [for example the general contractor on a job our insured just won] The insurance requirements language from the contract, plus the request as it came in: [paste the insurance requirements section and the request email] Produce four things. 1. A requirements table, one row per demand. Columns: what is being required (limit, coverage line, endorsement, or wording such as additional insured, waiver of subrogation, primary and non contributory, notice of cancellation), the exact contract language it comes from in quotation marks, and the specific document or system record our team must check to confirm whether we can meet it. 2. A verification checklist written as tasks for a licensed person, in the order they should happen. Never state or assume that a policy already meets a requirement. 3. Every requirement that is vague, internally contradictory, or that our team should raise with the carrier or the requester before we promise anything. Say plainly what is unclear. 4. A short reply email to the requester that confirms receipt, gives [date] as when we expect to have an answer for them, and asks the questions from item 3. This email confirms no coverage and no wording. Quote the contract exactly wherever you quote it. If something I need is not in the text above, write "not stated in the request" rather than filling it in.
What to skip in insurance agencies
- Never let Claude tell anyone what a policy covers. Coverage comes from the form, the endorsements, and the schedule on that specific policy, and a confident wrong answer in an email is how an errors and omissions claim starts. The same line holds for the harder documents: no coverage opinions, no coverage position or reservation of rights letters, and no claim denial language. Those belong to the carrier, the adjuster, and counsel. Claude drafts what you already know and what you can point to; the policy answers what is covered.
- Client nonpublic information and policy documents stay out of a consumer chat window. No Social Security numbers, dates of birth, driver's license numbers, EINs, VINs attached to a name, medical detail, loss runs carrying claimant names, or full declarations pages. Many states have adopted a version of the NAIC Insurance Data Security Model Law, which requires licensees to maintain a written information security program and to oversee the third parties who touch nonpublic information, so an account nobody approved is a compliance question before it is a privacy question. On Free, Pro, and Max plans whether your chats are used to improve Claude is a setting you control in Privacy Settings, so check where yours sits, and Anthropic does not use Team, Enterprise, or Claude for Work inputs to train its models by default. Redact first, work at a summary level, and get your agency's own sign off before live client material goes in.
- Anything that reaches a client or the public without a licensed person reading it. Advertising rules, disclosure requirements, and what a licensed person must personally do vary by state, and your carrier appointment agreements add terms of their own. Claude holds no license: it cannot quote premium, bind or cancel coverage, issue a certificate, or answer a prospect's coverage question on your website. Use it to get to a first draft faster, then let the licensed person who is accountable for the file put their name on it.
Want all 4 workflows for insurance agencies in your inbox?
Every prompt on this page plus the rest, so you still have them on Monday. One email, then four short ones on making it stick. Unsubscribe any time.
Or answer four questions and Claude writes three workflows for your specific business rather than the industry generally.
Before you try it
More for insurance agencies
- Draft the renewal letter before the crunch month
- Send the claim status update the same day
- Write the submission summary an underwriter reads