Prompt library

AI status update prompt.

Turn rough notes into a clear status update that answers the questions people usually ask next: what is done, what is moving, what is blocked, and what needs a decision.

Why this matters

Good updates reduce friction, not just words.

Status updates are one of the safest places to practise AI because the work is already structured. The gain is not sounding fancier. The gain is reducing back-and-forth and making the next step obvious, especially when you always cover outcomes, movement, blockers, and support needed.

Source signal

Inspired by OpenAI Academy operations workflows.

Read source

Before you paste update notes into AI.

Remove

  • Customer names.
  • Private financial details.
  • Anything not approved for the tool.

Include

  • The audience.
  • The reporting period.
  • What kind of decision or support is needed.

Check

  • Facts and dates.
  • Dependencies and owners.
  • Whether the ask is actually clear.

Copy-paste prompt: build a clearer status update.

# ROLE You are my workplace status update editor. # TASK Turn these rough notes into a clear status update for work. # AUDIENCE [manager / project lead / stakeholder group / team] # REPORTING WINDOW [today / this week / this sprint / this month] # NOTES [paste non-sensitive rough notes] # OUTPUT FORMAT 1. One-sentence summary 2. Done 3. In progress 4. Blocked or at risk 5. Decision or support needed 6. Next step 7. What I should verify before sending # RULES - Do not invent facts, dates, owners, or progress. - Mark uncertainty clearly. - Keep the tone calm, direct, and useful. - Reduce follow-up questions where possible.

What a useful status update answers.

1

What changed?

Name the actual progress, not only the activity.

2

What is moving now?

Show the live work without sounding defensive or vague.

3

What is blocked?

Surface dependencies early so the update is useful, not cosmetic.

4

What decision is needed?

If someone must choose, approve, or unblock, say it directly.

5

What happens next?

End with the next step and who owns it so the update creates motion.

Narrow this for manager updates Use the wider writing prompt pack Review the output before sending Take the private check