ESEN

AI prompts for status reports: weekly updates, project reports and executive summaries

How to use ChatGPT, Claude or Gemini to turn notes, tickets and meeting minutes into clear status reports: what to paste, how to separate progress from risks, how to avoid invented progress, and how to adapt one update for your team and for leadership. Copy-paste templates included.

← Back to guides

What a good status report answers

  • Where are we against the plan: on track, at risk or off track, with one sentence on why.
  • What changed since the last update — finished work, not activity ('shipped X', not 'worked on X').
  • Risks and blockers, each with an owner and what is needed to unblock it.
  • Decisions or help needed from the reader, stated as explicit asks with a date.
  • What comes next, limited to the few items that matter for the next period.

What to give the model

  • Your raw material inside delimiters: notes, ticket titles and states, meeting minutes, the previous report.
  • The reader: your team, a client, leadership. Each needs a different level of detail.
  • The plan or milestones you report against, so 'on track' means something.
  • Your format: the headings your organization already uses, length limit, and whether to use bullets.
  • A rule that the model may only report what appears in the material, and must flag anything unclear instead of guessing.

Mistakes to watch for

  • Invented progress: models tend to smooth over gaps. Ask for '[unclear: …]' markers and check every 'done' against the source.
  • Optimistic tone: ask for plain wording and an explicit status label instead of adjectives.
  • Hidden risks: a blocker mentioned once in the notes can disappear in a summary. Ask the model to list every risk it found before writing.
  • Too long: set a word or bullet limit per section, and move detail to an appendix or links.
  • Sensitive information: remove personal data, HR matters or confidential client details before pasting, or use an approved tool.

Templates

Weekly status update from raw notes

Write this week's status update for [project] for [audience].

<plan>
[milestones and dates]
</plan>

<notes>
[paste notes, ticket titles with their status, meeting minutes]
</notes>

Format:
- Status: On track / At risk / Off track — one sentence why
- Done this week (max 5 bullets, finished work only)
- Risks and blockers (owner, what's needed)
- Asks (who, what, by when)
- Next week (max 3 bullets)

Rules:
- Use only information from the notes. If something is unclear, write [unclear: …] instead of guessing.
- Before the update, list every risk or blocker you found in the notes, so I can check none was dropped.
- Plain language, no adjectives like "great" or "significant".
Opens the analyzer with the prompt prefilled.
Open in Promptea

Executive summary of a longer report

Turn the team report below into an executive summary for [leadership audience].

<report>
[paste the detailed status report]
</report>

Output:
1. One-line status with the reason.
2. Up to 3 points leadership needs to know, each one sentence.
3. Decisions needed from leadership, with the deadline and the consequence of not deciding.
4. Nothing else — no background, no list of activities.

Every number and date must appear in the report. If the report doesn't say what decision is needed, write "No decision needed this period".
Opens the analyzer with the prompt prefilled.
Open in Promptea

Check a draft report before sending

Review my status report draft before I send it to [audience].

<draft>
[paste your draft]
</draft>

<source>
[paste the notes or tickets it is based on]
</source>

List, in this order:
1. Claims in the draft that the source doesn't support.
2. Risks or blockers in the source that the draft leaves out.
3. Sentences that describe activity instead of results, with a rewrite.
4. Any ask that has no owner or date.
Don't rewrite the whole report.
Opens the analyzer with the prompt prefilled.
Open in Promptea

FAQ

Can AI write my status report from Jira or other ticket data?
Yes, if you give it the ticket titles, statuses and any comments that explain changes. Ticket data alone rarely explains why something slipped, so add a few lines of your own context, and check the result before sending. Some tools connect to ticket systems directly; check what your plan and your company allow.
How do I keep the same format every week?
Save the template with your headings and rules, paste last week's report as an example of the format, and tell the model to keep the same sections and order. A saved prompt in your team's library makes the reports comparable from week to week.
Should I tell readers the report was drafted with AI?
Follow your organization's policy. Either way, you are responsible for the content: verify every status, date and number against the source before you send it.