How do I write weekly status reports with AI?

Status reports are one of the quickest wins with AI, because the information already exists in your notes and the format repeats every week. Chapter 7 of the book, The Weekly Report, covers the method and claims it can bring a multi-hour report down to about 20 minutes.

The weekly routine

1. Collect the inputs. This week's meeting notes, decisions, milestone progress, budget figures, and new risks or issues. If you keep a Project Brain, most of this is already in its News tier.
2. Use a saved report prompt. Define the sections once, for example overall RAG status with a one-line reason, accomplishments, next week's plan, risks and issues, and decisions needed, and reuse it every week.
3. Name the audience. "Write for the steering committee: short, outcome-focused, no jargon" produces a very different report from a team update.
4. Edit as the editor. Check every number, date, and commitment against your sources. The AI drafts; you're accountable for what's sent.
5. Set the RAG status yourself. Let the AI suggest one, but the judgment call is yours.

Make it better over time

• Keep last week's report in context so the AI can show what changed.
• Ask for an executive summary of three sentences or fewer at the top.
• Save good examples. When a report lands well, keep it as a model for future weeks.
• Add a chart if your audience likes visuals. See Can AI create Gantt charts and dashboards?.

Common pitfalls

• Letting the AI fill gaps with invented progress. Tell it to write "no update" when there's no data.
• Reports that grow longer every week. Set a word limit.
• Sending without review. See How do I catch AI mistakes and hallucinations?.

For more, read Weekly Status Reports in 20 Minutes Instead of Hours, How to Write Project Status Reports Executives Read, and Your Executive Summaries Are Too Long: AI Can Fix That.