Report Generation Prompt Templates
AI prompt templates for generating reports. Create automated reports from data sources.
Overview
Reports turn data into decisions. But writing them is often repetitive and time-consuming. These prompts help you structure reports, write executive summaries, and turn raw numbers into clear narratives. Use them to create consistent, professional reports faster.
Best Practices
1
Define your audience upfront. A report for executives differs from one for analysts
2
Specify the report format you need (PDF, slides, email, dashboard narrative)
3
Include the key metrics and their values, not just descriptions
4
Mention what actions you want readers to take after reading
5
Ask for the report to address both good news and areas of concern
Prompt Templates
1. Executive Summary Generator
Write an executive summary for a [REPORT_TYPE] covering [TIME_PERIOD]. Key metrics: [METRICS_WITH_VALUES] Notable events: [EVENTS] Target audience: [AUDIENCE] Tone: [FORMAL/CONVERSATIONAL] Length: [WORD_COUNT] words Include: performance vs. goals, key wins, areas of concern, and recommended actions.
Write an executive summary for a monthly marketing report covering March 2024. Key metrics: Website traffic: 145K (up 12% MoM), Leads generated: 892 (down 5% MoM), Cost per lead: $34 (up from $31), Conversion rate: 2.8% (stable). Notable events: Launched new landing page mid-month, Google algorithm update on March 8. Target audience: CMO and marketing leadership. Tone: Professional but direct. Length: 150 words.
March showed mixed results. Traffic grew 12% to 145K visitors, driven by strong organic performance despite the March 8 algorithm update. However, leads declined 5% to 892, pushing cost per lead up to $34. The mid-month landing page launch hasn't yet impacted conversions. Conversion rate held steady at 2.8%. Key concern: the traffic-to-lead disconnect suggests we're attracting less qualified visitors. Recommended actions: 1) Audit traffic sources to identify low-converting channels, 2) A/B test the new landing page against the original, 3) Review keyword targeting for lead intent signals. We're on track for Q1 traffic goals but need to address lead quality before scaling spend.
When you need to summarize complex data for busy executives
- •Lead with the most important finding, not chronological order
- •Always tie observations to recommended actions
2. Weekly Status Report
Create a weekly status report for [PROJECT_OR_TEAM] for the week of [DATE]. Accomplishments: [ACCOMPLISHMENTS_LIST] Metrics this week: [METRICS] Blockers or risks: [BLOCKERS] Next week priorities: [PRIORITIES] Format: [BULLET_POINTS/NARRATIVE/BOTH] Audience: [AUDIENCE]
Create a weekly status report for the Data Platform team for the week of March 18, 2024. Accomplishments: Migrated 3 legacy reports to new BI tool, Fixed data pipeline latency issue (reduced from 45min to 12min), Onboarded 2 new analysts. Metrics: 98.5% pipeline uptime, 47 reports migrated (of 120 total), 15 support tickets resolved. Blockers: Waiting on IT for production database access. Next week priorities: Complete user acceptance testing, Begin phase 2 migrations. Format: Bullet points with brief narrative. Audience: VP of Engineering.
Data Platform Team - Week of March 18, 2024 Highlights: Strong progress on migration and a significant performance win. Accomplishments: • Migrated 3 legacy reports to new BI tool (47/120 complete, 39%) • Reduced pipeline latency from 45 to 12 minutes (73% improvement) • Onboarded 2 new analysts, now fully productive • Resolved 15 support tickets Metrics: 98.5% pipeline uptime | 47 reports migrated | 15 tickets closed Blocker: Production database access pending IT approval (submitted March 12). This may delay phase 2 migrations if not resolved by March 25. Next Week: • Complete UAT for migrated reports • Begin phase 2 migration planning • Follow up on database access request
Regular team updates to leadership or stakeholders
- •Quantify accomplishments whenever possible
- •Be specific about blockers and what's needed to resolve them
3. Data-Driven Narrative Report
Write a narrative report explaining [TOPIC] based on this data: [DATA] The report should: 1. Start with the main finding 2. Walk through supporting evidence 3. Address counterpoints or limitations 4. End with implications and recommendations Audience: [AUDIENCE] Length: [LENGTH] Tone: [TONE]
Write a narrative report explaining why customer churn increased in Q1 based on this data: Churn rate: 4.2% (up from 3.1% in Q4), Churn by segment: Enterprise 1.8% (stable), SMB 5.9% (up from 3.8%), Churn reasons (from exit surveys): Price 34%, Missing features 28%, Poor support 22%, Switched competitor 16%. Support tickets before churn: avg 4.2 (up from 2.1). NPS of churned customers: 12 (vs. 45 overall). Audience: CEO and leadership team. Length: 300 words. Tone: Direct and actionable.
Q1 Churn Analysis: SMB Segment Driving Increase Our Q1 churn rate rose to 4.2% from 3.1% in Q4. The increase is concentrated entirely in our SMB segment, which saw churn jump from 3.8% to 5.9%. Enterprise churn remained stable at 1.8%. The data points to a support experience problem. Churned customers submitted twice as many support tickets before leaving (4.2 vs. 2.1 average), and their NPS was 12 compared to 45 for retained customers. While exit surveys cite price as the top reason (34%), this often masks underlying dissatisfaction. The 22% citing poor support directly, combined with the ticket volume data, suggests many 'price' exits were actually support-frustrated customers who found our pricing no longer worth the experience. Missing features (28%) also contributed, with churned SMB customers most frequently requesting integrations we don't yet offer. Competitor switches (16%) went primarily to two players offering lower-touch, self-service models. A note on limitations: exit surveys capture only 60% of churned customers. Non-respondents may have different patterns. Recommendations: 1. Audit SMB support queue for systematic issues. The ticket volume spike suggests a process problem, not just individual cases. 2. Prioritize the top 3 requested integrations for Q2 roadmap. 3. Consider an SMB-specific support tier with faster response times. 4. Implement churn prediction model using support ticket velocity as a leading indicator. If we return SMB churn to Q4 levels, we recover approximately $180K in annual recurring revenue.
When you need to tell a complete story from data, not just present numbers
- •Always quantify the business impact in terms leadership cares about (revenue, customers)
- •Address the 'so what' explicitly. Don't make readers figure out why it matters
4. Automated Report Template
Create a template for a recurring [FREQUENCY] [REPORT_TYPE] that I can populate with new data each period. Sections needed: [SECTIONS] Key metrics to include: [METRICS] Comparisons: [COMPARISON_PERIODS] Format: [FORMAT] Provide the template with placeholder text and guidance for each section.
Create a template for a monthly sales performance report that I can populate with new data each month. Sections needed: Executive summary, Revenue breakdown, Pipeline analysis, Team performance, Forecast. Key metrics: Total revenue, deals closed, average deal size, win rate, pipeline value. Comparisons: vs. last month, vs. same month last year, vs. target. Format: Document with tables.
MONTHLY SALES REPORT - [MONTH YEAR] EXECUTIVE SUMMARY [2-3 sentences: Lead with most important result. State whether you hit target. Note one win and one concern.] KEY METRICS SNAPSHOT | Metric | This Month | vs. Target | vs. Last Month | vs. Last Year | |--------|------------|------------|----------------|---------------| | Revenue | $[X] | [%] | [%] | [%] | | Deals Closed | [X] | [%] | [%] | [%] | | Avg Deal Size | $[X] | [%] | [%] | [%] | | Win Rate | [X]% | [+/- pts] | [+/- pts] | [+/- pts] | REVENUE BREAKDOWN [Table by product line, region, or segment. Include % of total and MoM change.] PIPELINE ANALYSIS Total Pipeline: $[X] ([X]x coverage of [next month] target) [Note quality: How much is in late stages? Any concentration risk?] TEAM PERFORMANCE [Table of reps with quota attainment. Flag top performer and anyone below 80%.] FORECAST Next Month Projection: $[X] (confidence: [high/medium/low]) [Key deals to watch and potential risks]
When you need consistent report structure across time periods
- •Build in the comparisons you always want to see
- •Include guidance notes in brackets so anyone can fill it in
Common Mistakes to Avoid
•
Dumping data without providing the narrative that explains what it means
•
Writing for yourself instead of your audience. Executives don't need methodology details, analysts do
•
Presenting problems without recommendations, leaving readers unsure what to do next
Frequently Asked Questions
Reports turn data into decisions. But writing them is often repetitive and time-consuming. These prompts help you structure reports, write executive summaries, and turn raw numbers into clear narratives. Use them to create consistent, professional reports faster.
Related Templates
SQL Query Prompt Templates
AI prompt templates for writing SQL queries. Create SELECT, JOIN, aggregate, and complex queries.
Data Analysis Prompt Templates
AI prompt templates for data analysis. Extract insights, identify patterns, and interpret results.
Data Visualization Prompt Templates
AI prompt templates for data visualization. Create effective charts, dashboards, and visual reports.
Have your own prompt to optimize?