AI Prompts for Business Reporting

Summarize these meeting notes.

Meeting: [MEETING NAME/TYPE]
Date: [DATE]
Attendees: [WHO WAS THERE]

Raw notes:
[PASTE YOUR MEETING NOTES HERE]

Create a summary that includes:
1. Meeting purpose (1 sentence)
2. Key discussion points (bullet points)
3. Decisions made (with who decided)
4. Action items (with owner and due date for each)
5. Open questions or parking lot items
6. Next meeting date/topic (if discussed)

Format for easy scanning. Someone who missed the meeting should be able to get up to speed in 2 minutes.

Write a weekly status update.

Week of: [DATE RANGE]
Project/Team: [NAME]
For: [WHO WILL READ THIS]

What happened this week:
[LIST ACCOMPLISHMENTS AND PROGRESS]

What's planned for next week:
[LIST PLANNED ACTIVITIES]

Blockers or risks:
[ANY ISSUES THAT NEED ATTENTION]

Key metrics (if applicable):
[NUMBERS THAT MATTER]

Help needed:
[ANYTHING YOU NEED FROM READERS]

Create an update that:
- Opens with the most important news
- Uses bullet points for scannability
- Clearly flags anything that needs attention
- Keeps good news proportional (don't pad it)
- Includes specific numbers where relevant

Keep it under 300 words unless there's major news.

Write a summary of data analysis findings.

Analysis topic: [WHAT YOU ANALYZED]
Data source: [WHERE THE DATA CAME FROM]
Time period: [DATE RANGE]
Audience: [WHO WILL READ THIS]

Key findings:
[LIST THE MAIN THINGS YOU DISCOVERED]

Data highlights:
[SPECIFIC NUMBERS OR TRENDS]

Create a summary that includes:
1. Executive summary (3-4 sentences)
2. Background/context
3. Methodology (brief)
4. Key findings with supporting data
5. Implications (so what?)
6. Recommended actions
7. Limitations or caveats
8. Next steps

Write for the audience's level of data literacy. Lead with insights, not methodology. Make it actionable.

Write a quarterly review.

Quarter: [Q1/Q2/Q3/Q4] [YEAR]
Team/Project/Business: [NAME]
Audience: [WHO WILL READ THIS]

Goals for this quarter (what we set out to do):
[LIST THE QUARTER'S GOALS]

Results (what actually happened):
[LIST OUTCOMES AGAINST EACH GOAL]

Key metrics:
[RELEVANT NUMBERS AND COMPARISONS]

Major wins:
[SIGNIFICANT ACCOMPLISHMENTS]

Challenges faced:
[WHAT DIDN'T GO AS PLANNED]

Lessons learned:
[INSIGHTS TO CARRY FORWARD]

Next quarter focus:
[PREVIEW OF UPCOMING PRIORITIES]

Create a review that:
- Honestly assesses performance against goals
- Celebrates wins without over-inflating
- Acknowledges challenges constructively
- Extracts actionable lessons
- Sets up next quarter clearly

Keep it comprehensive but readable (aim for 1-2 pages).

Write an incident report.

Incident type: [WHAT HAPPENED—OUTAGE, SECURITY, ERROR, ETC.]
Date and time: [WHEN IT OCCURRED]
Duration: [HOW LONG IT LASTED]
Severity: [LOW / MEDIUM / HIGH / CRITICAL]
Affected: [WHO OR WHAT WAS IMPACTED]

Timeline of events:
[LIST WHAT HAPPENED IN ORDER]

Root cause:
[WHAT CAUSED THIS TO HAPPEN]

Resolution:
[HOW IT WAS FIXED]

Impact:
[WHAT WAS THE EFFECT]

Create a report that includes:
1. Executive summary (3-4 sentences)
2. Timeline of events (with timestamps)
3. Root cause analysis
4. Impact assessment
5. Resolution steps taken
6. Preventive measures for the future
7. Action items with owners
8. Lessons learned

Write factually, not defensively. The goal is learning, not blame.

Write a performance summary.

Employee name: [NAME]
Role: [JOB TITLE]
Review period: [DATE RANGE]
Reviewer: [YOUR NAME/ROLE]

Goals from this period:
[LIST THEIR GOALS]

Performance against goals:
[HOW DID THEY DO ON EACH]

Key accomplishments:
[NOTABLE ACHIEVEMENTS]

Areas for development:
[CONSTRUCTIVE FEEDBACK]

Feedback from others (if available):
[PEER OR STAKEHOLDER INPUT]

Create a summary that:
- Provides specific examples for all feedback
- Balances recognition with constructive growth areas
- Focuses on behaviors and outcomes, not personality
- Gives actionable development suggestions
- Aligns with their career goals

Write as if they'll read this—because they will. Be honest, specific, and constructive.

Write a client-facing project report.

Client: [CLIENT NAME]
Project / engagement: [WHAT YOU ARE DELIVERING FOR THEM]
Reporting period: [DATE RANGE — e.g. May 2026 / Q2 2026]
Audience: [WHO READS THIS — owner, marketing lead, ops manager, etc.]

What we did this period:
[LIST THE WORK YOU COMPLETED — DELIVERABLES, CALLS, EXPERIMENTS, FIXES]

Results / outcomes:
[NUMBERS, BEFORE-AND-AFTERS, OR QUALITATIVE CHANGES THE CLIENT CARES ABOUT]

What's planned for next period:
[NEXT MILESTONES, EXPERIMENTS, OR WORKSTREAMS]

Risks, blockers, or decisions we need from the client:
[ANYTHING THAT NEEDS THEIR INPUT]

Write a report that:
1. Opens with a 3-sentence executive summary — what we did, what changed, what's next
2. Reports results against the goals we agreed on, not vanity metrics
3. Translates jargon into the client's language (a roofer doesn't care about "MQLs")
4. Explicitly flags decisions we need from them, with a deadline
5. Closes with the 2-3 things they should do or approve this week

Keep it under one page when printed. The client should be able to skim it in 90 seconds and know whether the engagement is on track.

Write a marketing performance report.

Period: [DATE RANGE]
Audience: [OWNER / LEADERSHIP / CLIENT]
Goal of the period: [WHAT WE WERE TRYING TO ACHIEVE — LEADS, BOOKINGS, BRAND, ETC.]

Channels and raw numbers:
[PASTE METRICS BY CHANNEL — e.g. email opens, social impressions, ad spend, conversions, paid CPL, organic clicks]

What changed this period:
[NEW CAMPAIGNS, BUDGET SHIFTS, CREATIVE CHANGES]

Known external factors:
[SEASONALITY, PRESS, COMPETITOR MOVES, OUTAGES]

Create a report that:
1. Opens with one sentence on whether the period hit the goal
2. Shows period-over-period change on the 3-4 metrics that actually map to revenue
3. Calls out the single best- and worst-performing channel and explains why
4. Notes what we'll keep, kill, or change next period (be specific)
5. Lists 2-3 experiments to run next period with a hypothesis for each

Don't include every metric you have access to. Cut anything that doesn't lead to a decision. Round numbers to 2 significant figures.

Synthesize raw customer feedback into a report leadership can act on.

Source of feedback: [REVIEWS / NPS / POST-PROJECT SURVEY / SUPPORT TICKETS]
Period: [DATE RANGE]
Number of responses: [HOW MANY]
Customer segment(s): [WHO THESE CUSTOMERS ARE]

Raw feedback:
[PASTE THE FEEDBACK — VERBATIM IS BEST]

Known context:
[ANY PRODUCT/SERVICE CHANGES, INCIDENTS, OR CAMPAIGNS DURING THIS PERIOD]

Produce a report that includes:
1. Executive summary (3-4 sentences) — overall sentiment and the single biggest signal
2. The 3-5 themes that show up most often, ranked by frequency, with a representative quote for each
3. Sentiment split — what % praised what, what % complained about what
4. The "watch list" — themes that appeared 2-3 times that might be early signals
5. Direct quotes worth sharing internally (mark which are praise vs. constructive)
6. Recommended actions — what to fix, what to double down on, what needs more research

Be honest about negative themes — don't soften them. If small-sample themes can't be generalized, label them as "anecdotal" rather than dropping them.