AI LunchroomPractice AI. Do real work.
AI prompts by job

AI prompts for insurance underwriting assistants

You prep submissions for the underwriter, chase brokers for the missing application page, and write the declination or request-for-information letters that underwriters decide but rarely have time to write. These prompts are written for that work — copy one into ChatGPT, Claude, Copilot, or Gemini, or practice it with step-by-step feedback and keep the ones you reuse.

What AI is actually good for in this job

Not everything — but these four come up every week, and they are all writing tasks, which is where today's tools are strongest.

Before you paste anything

What never goes into a chatbot in this job

Never paste applicant names tied to loss history, financial statements, medical or claim details, policy numbers, producer commission information, or the underwriting guidelines themselves. Describe the situation generically — 'a submission is missing loss runs' — and keep guidelines and files out of any outside tool.

Which tool: Carriers often have in-house underwriting workbenches with their own approved AI features and strict rules against outside tools, because guidelines and applicant data are confidential. Check with your underwriting manager before using anything else for even routine email wording.

Write the request-for-information email to a broker for a missing submission item

The rough version you start from
Submission came in for a small manufacturer. Missing: the signed application's last page, loss runs for the last five years from the prior carrier, a current list of locations with square footage, and a description of operations that explains the new product line. Underwriter wants these before even looking at pricing.
Copy this prompt
I work in insurance underwriting support. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: Insurance Underwriting Assistant
- Work context: You prep submissions for the underwriter, chase brokers for the missing application page, and write the declination or request-for-information letters that underwriters decide but rarely have time to write.

Task:
Write the request-for-information email to a broker for a missing submission item

Source material:
Submission came in for a small manufacturer. Missing: the signed application's last page, loss runs for the last five years from the prior carrier, a current list of locations with square footage, and a description of operations that explains the new product line. Underwriter wants these before even looking at pricing.

What to give me:
Write a concise email to the broker that lists the missing items, states the underwriter can't proceed without them, and gives a response date.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Compare the list with the underwriter's actual request, and confirm that the response date is the one they gave you.

Summarize a long submission into a one-page brief for the underwriter

The rough version you start from
Submission packet is forty pages: application, loss runs showing two claims, financials, safety program description, and a broker cover letter. Underwriter wants a one-page brief: what the business does, locations, claims in plain words, what's unusual, and what's missing. Do not include opinion on whether to write it.
Copy this prompt
I work in insurance underwriting support. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: Insurance Underwriting Assistant
- Work context: You prep submissions for the underwriter, chase brokers for the missing application page, and write the declination or request-for-information letters that underwriters decide but rarely have time to write.

Task:
Summarize a long submission into a one-page brief for the underwriter

Source material:
Submission packet is forty pages: application, loss runs showing two claims, financials, safety program description, and a broker cover letter. Underwriter wants a one-page brief: what the business does, locations, claims in plain words, what's unusual, and what's missing. Do not include opinion on whether to write it.

What to give me:
Create a one-page structured brief using those headings and neutral language, marking any item that the packet doesn't clearly provide.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Read the brief against the original packet, because summaries often drop an exception or misstate a claim, and remove any opinion.

Draft the explanation to a broker of why a submission is being declined

The rough version you start from
Underwriter's decision: decline. Reason given in the file note: the operations include an activity outside appetite, and loss history showed repeated similar claims. Broker has been helpful and sends good business. Wants it respectful, specific on appetite, and open to future submissions of other types.
Copy this prompt
I work in insurance underwriting support. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: Insurance Underwriting Assistant
- Work context: You prep submissions for the underwriter, chase brokers for the missing application page, and write the declination or request-for-information letters that underwriters decide but rarely have time to write.

Task:
Draft the explanation to a broker of why a submission is being declined

Source material:
Underwriter's decision: decline. Reason given in the file note: the operations include an activity outside appetite, and loss history showed repeated similar claims. Broker has been helpful and sends good business. Wants it respectful, specific on appetite, and open to future submissions of other types.

What to give me:
Draft a respectful declination note to the broker that states the reason as the underwriter gave it and keeps the door open.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Confirm the stated reasons match the underwriter's file note exactly, with no added reasons, and that your carrier's required decline wording is present.

Turn the underwriter's notes into a clean file note for the record

The rough version you start from
Call notes: broker said the building was updated, wiring replaced recently, sprinklers added last year. Underwriter said okay but wants proof, and said hold the quote till the roof inspection arrives. Next follow-up Thursday. Pending: roof report, sprinkler certificate.
Copy this prompt
I work in insurance underwriting support. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: Insurance Underwriting Assistant
- Work context: You prep submissions for the underwriter, chase brokers for the missing application page, and write the declination or request-for-information letters that underwriters decide but rarely have time to write.

Task:
Turn the underwriter's notes into a clean file note for the record

Source material:
Call notes: broker said the building was updated, wiring replaced recently, sprinklers added last year. Underwriter said okay but wants proof, and said hold the quote till the roof inspection arrives. Next follow-up Thursday. Pending: roof report, sprinkler certificate.

What to give me:
Turn these notes into a clean, dated file note with the facts the broker stated, what the underwriter decided, and what's pending.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Make sure the note keeps statements marked as broker claims and not verified facts, and adds no dates or conclusions the call lacked.

More prompts for this job

Drawn from AI Lunchroom's Finance, Billing & Purchasing practice labs and rewritten for this role. See every Finance, Billing & Purchasing prompt.

Billing question summary

Summarize a billing question into facts, missing information, and a review-ready note.

Copy this prompt
I work in insurance underwriting support. Help me create one billing question summary that I can review and edit before use.

Relevant context:
- Role: Insurance Underwriting Assistant
- Work context: You prep submissions for the underwriter, chase brokers for the missing application page, and write the declination or request-for-information letters that underwriters decide but rarely have time to write.

Task:
Create a billing question summary without making billing decisions.

Source material:
"Hey — got a weird one on invoice 77031 from Coastal Print & Supply. PO 4402 was for 24 toner cartridges at $18.50, but the invoice's billing 40 units, so it's $296 over what we ordered. Coastal's AP contact, Denise, called this morning asking why payment hasn't gone out yet -- she says net-30 is up Friday. I pulled the receiving log and it shows we only signed for 24 units on the loading dock, no partial shipment note. I don't know if this needs Priya's sign-off since it's over the $500 variance threshold, or if the front desk copy of the PO from March even matches what's in the system now. Can you put together something I can hand off that lays out what we know, what's missing, and who needs to look at this?"

Return only the finished work:
billing question summary

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Purchase request cleanup

Turn a rough purchase request into item, quantity, purpose, urgency, and approval questions.

Copy this prompt
I work in insurance underwriting support. Help me create one clean purchase request that I can review and edit before use.

Relevant context:
- Role: Insurance Underwriting Assistant
- Work context: You prep submissions for the underwriter, chase brokers for the missing application page, and write the declination or request-for-information letters that underwriters decide but rarely have time to write.

Task:
Create a clean purchase request for review.

Source material:
Text from Marcus in Ops Training, 6:42pm: "Hey -- need you to get me a purchase request going for tablets before the Sept 14 onboarding cohort starts. We've got 9 people this round and only 5 tablets that still hold a charge, the rest are the 2019 ones that die by lunch. I was thinking 10 to have spares. Alicia mentioned in the budget meeting that training tech was 'probably fine' for this quarter but I never saw a number. Vendor we used last time was Contoso Office Supply, PO was around $3,200 for 8 units back in March if that helps. Can you get something together I can forward to Denise for sign-off?"

Return only the finished work:
clean purchase request

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Expense summary cleanup

Turn messy expense notes into a clear reimbursement summary ready for review.

Copy this prompt
I work in insurance underwriting support. Help me create a set of expense summary with items that I can review and edit before use.

Relevant context:
- Role: Insurance Underwriting Assistant
- Work context: You prep submissions for the underwriter, chase brokers for the missing application page, and write the declination or request-for-information letters that underwriters decide but rarely have time to write.

Task:
Turn the message below into a clean expense summary and flag exactly what still needs a receipt or an approval sign-off before it goes to Sandra.

Source material:
"Hey, can you pull together the expense summary for the Denver trip before Friday? I've got dinner with the Meridian Ridge client on the 12th (about $140, no receipt yet), the rideshare from the airport to the Lakeview Suites hotel ($38, I have that one), and the Northfield Design Cloud renewal finance flagged last month ($52.99/mo, not sure if it's supposed to hit the marketing budget or ours). Sandra in AP said she needs it by end of day Thursday for the reimbursement batch, but I honestly don't remember which of these she can approve versus what needs Marcus to sign off on since it's over the $100 threshold. Can you clean this up and tell me what's missing?"

Return only the finished work:
1. expense summary with items
2. amounts where known
3. missing receipts or approval flags

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

How to use ChatGPT or Copilot for underwriting assistants work

  1. Start from your own rough version. Type or dictate what you would have written anyway, however messy. A prompt built on your real note beats a blank-page request every time.
  2. Say who it is for and how long it should be. "Two sentences for a supervisor" and "a checklist a new hire can follow" produce completely different output from the same facts.
  3. Strip the identifying details first. Applicant names tied to loss history, financial statements, medical or claim details, policy numbers, producer commission information, or the underwriting guidelines themselves. Describe the situation generically — 'a submission is missing loss runs' — and keep guidelines and files out of any outside tool.
  4. Read every specific it produces. AI fills gaps with plausible invention — dates, amounts, names, policy numbers. If you did not supply it, do not trust it.
  5. Keep the ones that work. The value compounds when you stop rewriting the same prompt. Save it with a note about when to use it.
Practice, don't just copy

Get better at these — free

Copying a prompt is a start. AI Lunchroom walks you through the task step by step with your own work, checks what your AI tool gives back, and saves the prompts you will reuse. Free to start, no credit card.

Related jobs in Finance, Billing & Purchasing

Underwriting Assistants AI questions

can ai make underwriting decisions

It shouldn't, and automated decisions about coverage can carry regulatory risk. The underwriter decides using the carrier's guidelines and the full file. AI can help you with the writing around that decision, such as clear information requests, provided you remove identifying details and follow your carrier's rules.

how do i write a decline email brokers don't hate

Say what was reviewed, the reason in the underwriter's own words, and what, if anything, might change the answer. Stay neutral and specific. AI can smooth tone and structure; the stated reason must come from the underwriter, because a vague or invented reason can create fair-treatment and compliance trouble.