Review edition · Complete text lesson. Platform screenshots are being prepared.
Suppose you could…
Write a project update people can act on
Separate completed work, risks and requests in an evidence-based status update.
Separate completed work, risks and requests in an evidence-based status update.
Time is a practice estimate. Pause or return whenever you need.A useful little possibility.
Your goal is a usable work artifact, not a perfect-looking AI answer. Separate completed work, risks and requests in an evidence-based status update.
Let’s make a start.
Use a fresh conversation in an AI tool you are permitted to use. Copy the fictional sample below, then paste the starter prompt with it. No file upload, web search or paid integration is required.
1. Sort the evidence into done and not done.
2. Run the prompt.
3. Check each status against the original plan.
4. Ask for a handoff that another coordinator could pick up without reading the whole chat.
Your sample material
Fictional training material. No real customer information needed.
Last week’s plan: finish guide, test form, confirm room. Current evidence: guide draft completed 15 September but not approved; form test found a required-field bug, still open; room inquiry sent but no reply. Review milestone: Friday. Noor can investigate the form on Wednesday but has not committed to a fix date.Download sample .txt ↓
Write a concise status update with completed work, open risks, next proposed actions and decisions needed. Cite the sample fact supporting each status. Do not call drafting approval, an inquiry a booking, or investigation a guaranteed fix. Make the Friday milestone conditional where appropriate.
Keep personal and confidential information out of external AI tools. Start with the sample material.
Turn a first try into your thing.
Compare the result with the checklist before opening the worked example. Identify one specific weakness and ask for a targeted revision, referring to the original sample. If all checks pass, tighten the wording without changing the facts. Save the reviewed result in your own document; do not send or publish it as part of this exercise.
Pause for the “aha.”
Status is a claim about evidence, not optimism. A useful handoff exposes what the next person must decide or verify.
Useful beats convincing.
Check these against your actual output. Your answers stay on this device; this is self-review, not automated grading.
Finished your first try? Reveal a worked example ↓
Completed: guide draft, 15 September. Open: guide approval; required-field bug; room reply. Proposed next steps: confirm an approver, ask Noor to investigate Wednesday, follow up on the room inquiry. Friday review is at risk if the form or required approvals remain unresolved. Needed decisions: who approves the guide, whether a review can proceed with the form bug, and whether to seek another room. Noor’s availability does not establish a fix deadline.
A new case. Your own approach.
Apply the review principles to these new facts, not the previous sample’s specific numbers or answers.
Plan: publish a report Monday. Evidence: draft finished, one source unverified, reviewer away until Tuesday. Write a status and a decision request without claiming the deadline will be met.
One possibility leads to another.
Repeat on a small, permitted task of your own. Record what you changed and which check caught a problem. Keep using fictional inputs if workplace material is not approved for your chosen tool.
Your reusable workflow card ↓
Task: Write a project update people can act on Audience: [who will use this] Approved source material: [paste] Required output: Separate completed work, risks and requests in an evidence-based status update. Constraints and unknowns: [list] Review before use: - Draft completion is distinguished from approval. - Room inquiry is not reported as a booking. - The bug remains open. - Noor is not given an invented fix deadline. - The update names actionable decisions or questions.Download workflow .txt ↓
You tried something. That counts.
Keep a note of what you made or what surprised you. It stays in this browser.