Back to guide/Research & Analysis

Report Narrative Writer

Requiring a 'so what' for each finding transforms a data dump into actionable insight. The ban on vague language forces specificity that executives can act on.

chatgpt-prompts-for-data-analysisanalysis_topicaudiencetechnical_level
Edit View
Prompt
Write an executive summary and narrative for a data analysis report. Context:

Analysis topic: {{analysis_topic}}
Audience: {{audience}} ({{technical_level}} technical level)
Key findings:
{{key_findings}}

Business impact: {{business_impact}}
Recommended actions: {{recommendations}}

Structure:
1. Executive summary (3-4 sentences, lead with the most important finding)
2. Context paragraph (why this analysis was done)
3. Key findings section (use bullet points, each finding should have a data point and a "so what")
4. Implications and recommended actions
5. Methodology note (1-2 sentences, what data, what timeframe, what method)
6. Caveats and limitations

Tone: {{tone}}. Use specific numbers from the findings — no vague language like "significant improvement" without the actual percentage. Total length: 400-500 words.

Variables to customize

{{analysis_topic}}{{audience}}{{technical_level}}{{key_findings}}{{business_impact}}{{recommendations}}{{tone}}

Why this prompt works

Requiring a 'so what' for each finding transforms a data dump into actionable insight. The ban on vague language forces specificity that executives can act on.

Save this prompt to your library

Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.

Related prompts

SQL Query Writer

Providing the full schema and relationships eliminates guesswork. Asking for comments and assumption flags makes the output reviewable and trustworthy before running against production.

Data Cleaning Script

Requiring before/after logging and a summary report turns a cleaning script into an auditable process. Flagging rows for manual review prevents silent data loss.

Visualization Recommendation

Starting from the insight rather than the chart type ensures the visualization serves the story. Asking for common mistakes prevents the most frequent data viz errors.

Statistical Analysis Guide

Listing confounders and asking for assumption checks prevents the common mistake of running a test on data that violates its assumptions. The plain-English interpretation ensures you understand the results.