Back to Blog
.6 min read.Prompts by Profession

10 ChatGPT Prompts for Data Analysts

10 copy-paste ChatGPT prompts for data analysts - KPI definitions, dashboard commentary, QA summaries, stakeholder briefs, and experiment readouts.

Important note: Use AI to draft analysis outputs, not to invent facts. Always validate numbers, SQL logic, definitions, and conclusions before sharing.

Most analysts do not lose time on the analysis itself. They lose time on the layer around it: turning requests into scoped work, documenting KPI definitions, writing dashboard takeaways, and packaging findings for busy stakeholders.

These prompts are built for that communication and documentation layer. They help data analysts move from raw notes to clear deliverables faster, while keeping the final review where it belongs: with the analyst who knows the business context and the data quality realities.

Every prompt uses [BRACKETS] for your context. Copy, customize, and review before anything goes to a client, stakeholder, or team.

Prompts 1-3: Free to Use

Stakeholder intake, KPI definitions, and dashboard insight summaries.

1. Stakeholder Analytics Request Intake

Turn a vague ask into a concrete analytics brief before the work starts.

Scoping
Write an analytics request intake brief for [REQUESTER / TEAM]. Their request: [PASTE REQUEST]. Business goal behind the request: [GOAL]. Known data sources: [LIST]. Deadline: [DATE]. Write a structured intake brief with: (1) clarified business question, (2) success metric or output needed, (3) assumptions or missing information, (4) recommended analysis approach, and (5) follow-up questions required before work begins.

2. KPI Definition Sheet

Write metric definitions clearly enough that teams stop arguing over the numbers.

Documentation
Create a KPI definition sheet for [METRIC NAME] at [COMPANY NAME]. Business context: [WHAT THIS METRIC IS USED FOR]. Data source(s): [LIST]. Current confusion or inconsistency: [DESCRIBE IT]. Write a definition document with: (1) metric definition in plain English, (2) exact formula, (3) inclusion and exclusion rules, (4) reporting cadence, (5) owner, and (6) common ways this metric gets misread. Format so product, finance, and marketing can all use the same source of truth.

3. Dashboard Commentary for Leadership

Add the narrative that explains what the charts mean and what deserves attention.

Executive Communication
Write dashboard commentary for [DASHBOARD NAME]. Audience: [EXECUTIVE TEAM / FUNCTIONAL LEADS]. Reporting period: [DATE RANGE]. Key metrics and current values: [LIST]. Biggest changes versus prior period: [LIST]. Known context: [CAMPAIGNS / PRODUCT CHANGES / SEASONALITY / DATA ISSUES]. Write a short narrative with: (1) overall read on performance, (2) top 3 insights, (3) one risk or anomaly to watch, and (4) one recommended next step. Avoid repeating the chart labels back to the reader.

Prompts 4-10: QA, Experiment Readouts, and Executive Synthesis

Dataset QA summaries, experiment recaps, decision memos, and recurring reporting workflows.

4. Dataset QA Summary

Summarize data quality issues in business language, not just technical notes.

Quality Control
Write a dataset QA summary for [DATASET NAME]. Checks performed: [LIST]. Issues found: [LIST]. Severity of each issue: [DETAILS]. Downstream reports or decisions affected: [LIST]. Write a QA summary with: (1) scope of checks, (2) issues found with severity, (3) business impact, (4) recommended fixes, and (5) whether the dataset is safe to use now, safe with caveats, or blocked.

5. Experiment Readout Memo

Turn test results into a recommendation stakeholders can act on immediately.

Analysis Communication
Write an experiment readout memo for [EXPERIMENT NAME]. Hypothesis: [HYPOTHESIS]. Test period: [DATE RANGE]. Primary metric: [METRIC]. Secondary metrics: [LIST]. Result summary: [NUMBERS / DIRECTIONAL RESULT]. Caveats: [SAMPLE SIZE / DATA LIMITATIONS / SEGMENT BIAS]. Write a memo with: (1) experiment goal, (2) result summary, (3) interpretation, (4) caveats, and (5) recommendation: roll out, iterate, or stop.

6. Recurring Weekly Performance Update

Produce the same weekly update faster without rewriting the structure every Monday.

Reporting
Write a weekly performance update for [TEAM / FUNCTION]. Reporting period: [DATE RANGE]. Metrics to cover: [LIST]. Biggest wins: [LIST]. Biggest misses: [LIST]. Relevant context: [DETAILS]. Create a structured update with: (1) headline summary, (2) wins, (3) concerns, (4) context behind changes, and (5) actions for the coming week.

7. Metric Change Investigation Brief

Explain a sudden KPI movement with a clean hypothesis-led structure.

Investigation
Write a metric change investigation brief for [METRIC NAME]. Change observed: [WHAT CHANGED]. Date or period: [DATE RANGE]. Segments checked: [LIST]. Early hypotheses: [LIST]. Confirmed findings so far: [LIST]. Write a brief with: (1) what changed, (2) likely drivers, (3) open questions, (4) confidence level in the current explanation, and (5) recommended next analysis steps.

8. SQL Handoff Note for Engineering or BI

Hand off logic or data needs cleanly so implementation does not get lost in chat threads.

Cross-Functional Handoff
Write a SQL or data handoff note for [TEAM / PERSON]. Request: [WHAT NEEDS TO BE BUILT OR CHANGED]. Relevant tables or sources: [LIST]. Business rules: [LIST]. Edge cases: [LIST]. Deadline: [DATE]. Write a handoff note with: (1) business objective, (2) logic requirements, (3) source tables or dependencies, (4) edge cases or exclusions, and (5) acceptance criteria.

9. Executive Decision Memo from Analysis

Translate an analysis into a recommendation instead of leaving leaders with a pile of charts.

Decision Support
Write an executive decision memo based on this analysis: [PASTE NOTES]. Business decision at stake: [DECISION]. Options being considered: [LIST]. Most important findings: [LIST]. Risks or limitations: [LIST]. Write a memo with: (1) recommendation up front, (2) supporting evidence, (3) limitations or uncertainty, (4) tradeoffs, and (5) next actions required.

10. Self-Serve Dashboard Launch Announcement

Launch a new dashboard with enough context that people actually use it correctly.

Enablement
Write a launch announcement for a new self-serve dashboard called [DASHBOARD NAME]. Audience: [TEAM / COMPANY]. What the dashboard covers: [DETAILS]. Why it matters: [DETAILS]. Key definitions or guardrails: [LIST]. Where to find help: [LINK OR CONTACT]. Write an announcement with: (1) what is new, (2) who should use it, (3) how to interpret it correctly, and (4) how to request follow-up analysis if needed.

Get all 10 prompts

Unlock the full list — plus 54 automation templates plus more analyst-ready workflows for reporting, handoffs, and recurring ops — for just $29

Unlock Now — $29

Instant download · Digital product — no shipping or physical delivery.

Get the ChatGPT Automation Templates ->

The ChatGPT Automation Templates pack helps analysts standardize recurring updates, reporting memos, handoffs, and operational documentation so the work around the analysis stops eating the week.

Get the ChatGPT Automation Templates - $29 ->

Digital product — no shipping or physical delivery.

Strong analysts are valued for judgment, not just query output. These prompts speed up the packaging, explanation, and follow-through so your insight lands faster and with less back-and-forth.

Keep exploring: ChatGPT prompts for product managers and ChatGPT prompts for marketers.