Meetings & notes21 categories
Write a weekly update for my manager
Friday afternoon, summarising a week you can barely remember.
Write my weekly update from these notes. Structure, under 250 words: 1. **Done**: what completed, with the outcome where there is one. 2. **In flight**: with a plain read on whether it is on track. Use on track, at risk, or slipping, and nothing softer. 3. **Blocked or need from you**: specific asks, with what happens if they do not come. 4. **Heads up**: anything they should not learn from someone else first. Rules: no adjectives about how hard the week was, no listing effort where there is no result. If something slipped, state it early and say what I am doing about it. Flag anything in my notes that reads as busywork, so I can decide whether it belongs in the update at all. Notes:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Updates and follow-ups. The message after the meeting: status for a manager, a team update, and chasing what stalled.
Related prompts
Chase actions nobody clearly ownsA week after a meeting, when half the actions have quietly not happened.Summarise a week of standupsTurning daily noise into something a stakeholder can read on Friday.Compress an update into a chat messageWhen the status belongs in Slack, not in a document nobody opens.Turn this into a team updateNotes that need to become a message people will actually read.One-line statusA stakeholder asks how it is going and wants the honest one-liner.Write the follow-up messageThe message you send an hour after the meeting to make it stick.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free