Report Copilot: Prompting Patterns and Scenarios

14. Report Copilot: Prompting Patterns and Scenarios

Good prompts are clear, specific, and include business context. Here are common patterns:

Prompt: "Count active claims by peril type. Group by peril. Include only open claims."

Why it works: Specifies the grouping field, the grain (one row per peril), and the filter (open claims).

Prompt: "For each policy, show the policy number, insured name, and total premium. Include only in-force policies."

Why it works: Names the output columns, the anchor table (policies), and implies a join to insureds for readable names.

Prompt: "Top 10 insureds by total claims count. Sort from highest to lowest."

Why it works: Specifies rank, metric, sort order, and the entity of interest.

Prompt: "Count new claims by month for the last 12 months. Group by month."

Why it works: Specifies the time grain, date range, and the metric.

Prompt: "Show all claims with loss amount greater than $50,000, claim status = Open, and loss date in 2024."

Why it works: Lists all conditions explicitly and avoids ambiguous phrasing like "big claims."

Be explicit about columns - Name which fields should appear in the output.
Specify aggregations - "Count," "Sum," "Average" are clearer than "analyze."
Mention filters upfront - "Only active policies" is better than relying on defaults.
Use domain terminology - "Policies," "claims," "premiums," etc., are recognized terms.