Most weekly reports are dumped activity logs that nobody opens past the second paragraph — “I attended 12 meetings, reviewed 8 PRs, helped with…” — and end up training the boss to skip them. These prompts force the structure managers actually want: 3 wins with a metric, 3 risks with owners, 2 specific asks, and 1 commitment for next week. Pair with executive summary prompts when rolling up to leadership.
Best for
- Engineering and PM weekly status
- Design and cross-functional updates
- Manager-to-manager rollups
- Founder weeklies to investors
- New-hire week-1, launch week, behind-schedule, and vacation-week reports
1. WROUT format (Wins / Risks / Outlook / Updates / Tasks)
Draft my weekly report in WROUT format. Inputs: {paste raw notes / standup logs / Linear tickets}. Each section 3-5 bullets, each bullet ≤25 words. Mark each risk with severity (low / med / high) and a named owner.2. Manager-friendly 1-page report
Compress my work this week into a 1-page report my manager will actually read. Sections: 3 wins (each with a metric), 3 risks (each with mitigation), 2 specific asks, 1 commitment for next week. Cut all activity-log filler.3. Engineering weekly with metrics
Draft an engineering weekly report. Include: shipped (with PR / commit link), in flight (with % complete + ETA), blocked (with what unblocks), and 1 chart-worthy metric (latency / error rate / on-call load / build-time). ≤300 words.4. Founder weekly to investors
Draft a 250-word founder weekly to investors. Sections: 3 wins, 3 challenges, 2 specific asks (intros / advice / hires), key metric ({MRR / ARR / users / retention}). Tone: honest, not promotional. Bad news first, addressed head-on.5. Cross-functional rollup
I lead 3 sub-teams: {names}. Draft a rollup weekly that names each team's top win, top risk, and any cross-team dependency. ≤200 words. Add 1 line of "decisions I need from my manager / leadership" at the bottom.6. Activity-log → outcomes converter
Below is my raw activity log for the week. Convert each entry from "what I did" to "what outcome it produced". Drop entries that produced no outcome. Group remaining entries by impact tier.
{paste log}7. “Boring week” honest report
I had a boring week — mostly maintenance and 2 small fixes. Draft an honest 150-word report that does not inflate. Explain why the quiet week is OK (planned, deserved, or a different team is the bottleneck) and what next week's priorities are.8. Behind-schedule weekly
My project is behind schedule. Draft a 200-word weekly report that owns the slip in the first sentence, names the cause specifically (not "unforeseen issues"), names the new ETA, and lists the 2 things I'm doing about it. Avoid blame language.9. New-hire week-1 weekly
I just joined the team this week. Draft a 150-word week-1 weekly report: what I learned, who I met, what I shipped (small things count), what I'm still confused about, what I'd like help with next week. Earnest tone.10. Project-launch week weekly
I just launched {project}. Draft a 200-word launch-week weekly: outcome metric vs target, what surprised us (good and bad), top 2 follow-ups, 2 lessons for the next launch. Avoid victory-lap tone — assume a skeptical reader.11. Vacation / no-show week
I was out 3 days this week. Draft a 100-word weekly that acknowledges the gap, names the 1 thing I shipped before leaving, what's continuing without me, and what next week will pick up.12. Director-level rollup with manager summaries
Below are 6 manager weeklies. Roll them into a 300-word director-level summary. Sections: top 3 wins across orgs, top 3 risks, top 3 asks. Pick the items that would land for an exec audience — anything below "important to a director" gets cut.
{paste}13. Weekly with attached metrics dashboard
My report is paired with a metrics dashboard ({URL}). Draft a 200-word weekly that interprets the dashboard — what moved, why it moved, what it means for next week. Do not re-state the numbers; explain them and flag the 1 number readers will misread without context.Common mistakes
- Dumping the full activity log — readers stop at paragraph 2
- No metric or outcome attached to wins — “made progress on X” tells the reader nothing
- Hiding risks until they explode — every “surprise” risk is a credibility hit
- Asks buried in the middle paragraph — put them in a labeled “Asks” section at the top or bottom
- Same report copied week to week with cosmetic edits — readers notice and tune out
- Listing meetings attended as wins — meetings are activity, not outcome