AI-SEARCH-INSURANCE-CLAIM-DOCUMENTATION-READY
Why this deserves a source card
Insurance-related wording is easy for AI to overstate. A model can turn a customer photo into a conclusion, treat an old invoice as proof, imply a repair is covered, promise reimbursement, or summarize an adjuster note without context. For AI search, the risk is worse: unsupported wording can be copied into snippets, chat answers, directories, review replies, and sales conversations.
STOP PUBLISHING: do not let AI state or imply coverage, claim approval, denial, liability, reimbursement, repair necessity, safety, warranty eligibility, legal rights, adjuster findings, damage cause, or insurer deadlines unless the exact source and approved wording have been reviewed by the owner or qualified professional. This checklist is operational documentation, not legal, insurance, or financial advice.
Copy/paste insurance-claim source card
Business / page / claim context: [company, URL, product/service, customer-facing surface]
Claim-sensitive topic: [coverage / reimbursement / damage / warranty / replacement / liability / claim status / proof photos / adjuster / insurer deadline / other]
Exact source record: [policy excerpt / insurer email / adjuster note / invoice / photo log / inspection / warranty doc / owner-approved SOP]
Source owner and date: [person/team + last verified date]
Approved public wording: [paste the exact wording that may appear publicly]
Wording that must NOT be used: [coverage guarantee / approval / denial / fault / safety / deadline / reimbursement / diagnosis / legal conclusion]
Customer-safe fallback answer: [we can help gather documentation / check your policy or insurer / route for review]
Evidence limits: [what the photos, invoices, messages, or inspection do and do not prove]
Human reviewer required: [owner / licensed professional / legal / insurance agent / adjuster / warranty team]
Review cadence / expiration: [date or trigger]
AI-search audit query: [what to ask ChatGPT/Perplexity/Google AI to see if wrong claim wording appears]
STOP PUBLISHING until: [source verified + wording approved + reviewer assigned]Customer-safe wording starters
Thanks for sending the documentation. We can help gather and organize the available records, but coverage, reimbursement, claim approval, and policy decisions must be confirmed by the insurer or the appropriate reviewer.We are reviewing the source records before publishing or sending a final answer. We do not want to guess about coverage, liability, warranty status, reimbursement, repair cause, or timelines.Internal note: Insurance-sensitive wording. Source records checked: [list]. Missing: [list]. Do not publish AI-generated language about coverage, approval, denial, liability, reimbursement, safety, damage cause, or legal rights until reviewed.AI audit prompt
You are auditing insurance-claim, coverage, damage, reimbursement, warranty, or liability-sensitive wording for a small business website or customer-answer system. Use only the source card below. Do not invent coverage, claim status, reimbursement, legal rights, liability, safety, warranty eligibility, adjuster findings, or damage cause.
Return: 1) unsupported claims, 2) missing source fields, 3) safer wording, 4) reviewer/escalation owner, 5) AI-search queries to test for wrong answers, and 6) STOP PUBLISHING triggers.
Source card:
[Paste source card]Fast QA before publishing or training AI
- Does every insurance-related statement tie to a current source record?
- Does the wording avoid promising claim approval, reimbursement, deadlines, liability, legal rights, warranty coverage, or safety outcomes?
- Are photo, invoice, inspection, warranty, policy, and adjuster records described as evidence to review rather than conclusions?
- Is there an owner/professional reviewer for edge cases, disputes, threats, injuries, regulated advice, or customer escalation?
- Are public pages, FAQs, chatbots, macros, PDFs, and AI snippets using the same approved wording?
How this connects to the paid system
This checklist is a narrow example of the source-of-truth controls inside SEO After AI. The full playbook helps small businesses make pages, policies, proof, schema, and support answers easier for AI search tools to quote without inventing risky promises.