Reports Prompts

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.