Data analysts spend enormous time doing the work that surrounds the analysis — writing executive summaries, explaining anomalies, responding to stakeholder requests, and translating SQL into plain English. ChatGPT doesn't replace analytical judgment, but it eliminates the blank-page friction on every report, memo, and explanation you have to write.
These 10 prompts cover the three writing jobs data analysts do every week: summarizing and reporting data, communicating with stakeholders, and explaining queries and methodology. Copy them, fill in the brackets, and communicate your findings faster.
Data Summaries & Reporting
The hardest part of data work is often the last mile — turning a spreadsheet of findings into something executives will read and act on. These four prompts give you a structured starting point for every report, update, and issue doc you need to write.
1. Executive Summary of Data Findings
The Prompt
You are a data analyst. Summarize the following findings for a non-technical executive audience in 3–5 bullet points. Focus on what changed, why it matters, and what action it implies: [paste findings]
Why it works: Executives don't want to read data — they want to know what to do. This prompt forces the output into the three questions every leader actually asks: what changed, why it matters, and what's next.
2. Weekly Metrics Narrative
The Prompt
Write a short weekly metrics update for a product/marketing team. Tone: clear, direct, no jargon. Include: what went up, what went down, one hypothesis for each, and one recommended action. Data: [paste]
Why it works: Weekly updates fail when they just list numbers. This prompt structures the narrative around hypotheses and actions — turning a data dump into something the team can actually use on Monday morning.
3. Anomaly Explanation
The Prompt
An unusual spike/drop appeared in our data: [describe]. Write a plain-English explanation of 3 possible causes and what additional data would confirm or rule out each.
Why it works: When something unexpected happens in the data, stakeholders want a story, not a shrug. This prompt structures a rigorous response — three hypotheses, each with a clear path to validation — so you look prepared instead of reactive.
4. Data Quality Issue Report
The Prompt
Write a brief report documenting a data quality issue for stakeholders. Include: what the issue is, what data is affected, business impact, and recommended fix. Details: [paste]
Why it works: Data quality issues are uncomfortable to communicate. A structured report with business impact and a clear recommended fix turns a problem into a project — and gives stakeholders something to approve, not just absorb.
Stakeholder Communication
Analysis only creates value when it changes decisions. These three prompts handle the communication work that turns data into action — dashboard walkthroughs, scoping responses, and recommendation memos that actually get read.
5. Dashboard Walkthrough Script
The Prompt
Write a 3-minute spoken walkthrough script for a dashboard presentation. Audience: [role]. Data shown: [describe charts/metrics]. Make it story-driven — lead with the insight, not the chart.
Why it works: Most dashboard walkthroughs narrate what's on screen instead of what it means. This prompt flips the structure — insight first, chart second — which is how the most effective analysts present data.
6. Analysis Request Response
The Prompt
A stakeholder sent this analysis request: [paste]. Write a response that: clarifies what they're actually asking for, confirms the scope and timeline, and flags any data limitations upfront.
Why it works: Vague analysis requests are the #1 cause of wasted analytical work. This prompt gives you a professional, thorough response that sets scope and surfaces limitations before you spend a week on the wrong question.
7. Insight → Recommendation Memo
The Prompt
Turn this data insight into a 1-page recommendation memo for a business decision. Insight: [paste]. Include: context, what the data shows, recommended action, expected outcome, and risks.
Why it works: Data insights don't drive decisions — recommendations do. This prompt bridges the gap between what you found and what should happen next, in the format that business leaders actually read.
Get 50+ prompts like these, ready to copy and use.
Get the full Prompt Pack — 50+ ready-to-use prompts for every role and workflow. $19, instant download. →Query & Code Explanation
Technical work becomes invisible if no one understands it. Explaining a SQL query to a non-technical stakeholder, writing a methodology note that holds up to scrutiny, or defining a metric clearly enough that people stop measuring it wrong — these three prompts make the technical side of your work legible to the rest of the business.
8. SQL Query Explainer
The Prompt
Explain this SQL query in plain English so a non-technical stakeholder can understand what it does and why: [paste query]
Why it works: Stakeholders who don't trust the data will keep asking for re-runs. A plain-English explanation of how the query works builds confidence in the methodology — and fewer follow-up questions.
9. Analysis Methodology Note
The Prompt
Write a short methodology note explaining how this analysis was done, what assumptions were made, and what the limitations are. For: [audience]. Analysis: [describe]
Why it works: Methodology notes protect you and educate your audience. A clear note about assumptions and limitations prevents the analysis from being misapplied — and positions you as rigorous, not defensive.
10. Metric Definition
The Prompt
Write a clear, jargon-free definition of the following business metric for a company wiki: [metric name]. Include: what it measures, how it's calculated, why it matters, and common misinterpretations.
Why it works: Metric confusion is expensive — teams optimize for the wrong thing when definitions drift. A well-written wiki entry that includes common misinterpretations stops the argument before it starts.
Data analysts who use ChatGPT for the writing overhead reclaim hours every week for the actual analysis work — building models, exploring data, and making the judgment calls that AI can't make. The prompts above cover the documents that matter most; start with the one that's sitting in your drafts right now.
Ultimate ChatGPT Prompt Pack
$19
50+ prompts for data reporting, stakeholder communication, query explanation, and more. Copy, paste, ship.
No-Code Automation Starter Kit
$27
No-code automation templates to handle the repetitive parts of your workflow. No coding required.