Everyday work · Practical guide
Build a weekly update people can act on
- Tools
- Multi-tool
- Audience
- People getting started with AI
- Topic
- Everyday work

You’ll finish with: a weekly update that directs attention to progress, blockers, decisions and owned next actions.
A weekly update should make the next action easier to see. “Lots of progress across several areas” sounds busy, but gives the reader nowhere to go. Start with what changed.
Set up
Allow 15 minutes. Use notes from one reporting period in a chat tool. Keep older notes separate so last week’s success does not accidentally happen twice.
Try this example
FICTIONAL PRACTICE MATERIAL
This week: 8 support cases closed; 3 remain open; one needs supplier input. Training guide drafted, not reviewed. Next week: Jo reviews guide Tuesday. Decision needed: who owns the supplier follow-up?Do the task
- Group the notes into completed work, current blockers and next steps.
- Ask for a concise update with a distinct decision-needed line.
- Verify counts, dates and the difference between drafted and approved.
Your reusable prompt
Write a weekly update under 160 words. Use Completed, In progress, Next week and Decision needed. Preserve the facts and identify unresolved ownership.
PRACTICE INPUT
This week: 8 support cases closed; 3 remain open; one needs supplier input. Training guide drafted, not reviewed. Next week: Jo reviews guide Tuesday. Decision needed: who owns the supplier follow-up?
Refine your result
Move the supplier follow-up question into the final line. Keep the training guide out of Completed because its review is pending.Check the result
The update should show 8 closed and 3 open cases without inventing a closure rate. Jo’s Tuesday review is a next step, not a completed approval.
Save and reuse
Save the update with its reporting dates. Keep the structure for next week, but replace every fact.
Sources and notes
- Writing clear prompts Checked 2026-10-05
- The practice input and teaching prompt are original 5HO material. Examples are fictional; they are not screenshots or claims of a completed real-world task.
- Official documentation supports the relevant product concepts. Setup availability depends on your account; where a guide offers a fallback, it does not prove the connected capability worked.