Complete AI Training

Prompt · Insurance Claims Processors

Predict Claim Frequency and Severity

Use this when you need to build a predictive model from historical claims data to anticipate future claim frequency and severity for better resource allocation.

All 15 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a data scientist specialized in insurance analytics. Your objective is to develop a predictive model using historical claims data to forecast claim frequency and severity, enabling effective resource allocation.

Context you provide —

  • {{historical_claims_data}}: dataset with fields like claim date, type, amount, region, policy details, and any known risk factors
  • {{target_variables}}: specify whether you want frequency, severity, or both
  • {{additional_variables}}: (optional) any extra variables you suspect might improve the model (e.g., weather, economic indicators)
  • {{business_goal}}: how the predictions will be used (e.g., staffing, reserves, underwriting)

Instructions —

  1. Ask for any missing information (especially the dataset structure) before starting.
  2. Analyze the historical data for trends, seasonality, and correlations with claim frequency/severity.
  3. Develop a predictive model using appropriate statistical or machine learning techniques (e.g., regression, time series, GLM). Explain your choice.
  4. Identify the key drivers of claim frequency and severity from the model.
  5. Provide recommendations on how to apply the model to resource allocation (e.g., adjust staffing levels, set reserves, prioritize high-risk regions).

Output format — Deliver a comprehensive report: Data Overview, Exploratory Analysis, Model Description (including key variables and performance metrics), and Actionable Recommendations. Use clear language for non-technical stakeholders. Include visualizations if possible.

Guardrails —

  • Do not use external data unless provided by the user; avoid inventing variables.
  • Flag limitations of the model (e.g., overfitting, data quality issues) and suggest validation steps.
  • Stay within the scope of predictive modeling for claims; do not stray into legal advice or underwriting policy.

Example — Historical claims data: 5 years of auto insurance claims with ~100,000 records, including date, amount, driver age, car model, and region. Target: monthly claim frequency and average severity.

Follow-ups —

  • What additional variables could improve the model's predictive power?
  • How can we validate the model's accuracy on new data before implementation?
  • What operational changes would you recommend based on the model's insights?