Write a weekly update with evidence behind the status
Build a concise weekly report that separates completed work, blockers and decisions needed, using a fictional example and a review checklist.
A useful task, worked through.
A weekly update should let a reader decide whether to intervene. Long activity lists rarely do that. Give AI a small set of approved notes and ask it to distinguish an activity from an outcome. Keep the evidence close enough that you can defend every “done” and every claimed change.
Collect facts before asking for a narrative
Our fictional project is a workshop registration page. The notes say: “Form built in a local preview. Three sample registrations tested. Confirmation email still a draft. Venue details pending. Launch date proposed for Friday, not approved.” A report that says “registration launched successfully” would turn preparation into a result that did not happen.
Give the assistant the reporting period, audience and definitions of status. If “complete” means approved and live, a local prototype cannot receive that status. Include links or record identifiers when your workplace permits them, and keep confidential material within approved systems. Missing evidence should remain a gap in the report.
Organize around what the reader needs to know
An authored update begins: “The registration form works in a local preview with three sample submissions. Launch remains unapproved; venue details and the confirmation email need review.” It then lists the next action and the decision owner, if actually known. This opening explains the state without making the reader infer it from a dozen tasks.
A useful structure is current state, evidence, blocker, next step and decision needed. Ask for a short main update with a supporting appendix only if the audience needs it. Keep the subject of each sentence clear so “reviewed” cannot be mistaken for “approved” or “tested locally” for “used by customers.”
A request you can adapt
Draft a weekly update from these approved notes. Lead with the current state and what needs attention. Separate completed outcomes from activities and proposed work. Preserve local, draft and unapproved labels. Include evidence references and mark missing owners or dates. Do not invent progress percentages.
Check the denominator behind every number
Suppose the notes say “three of five planned sample cases passed.” The update can report exactly that, with the remaining cases identified. It should not call the page “60% ready” unless your team has defined and justified that measure. Passing sample cases and overall launch readiness are different things.
When comparing weeks, keep the time window and counting rules consistent. A larger number of completed items may reflect smaller items or a longer reporting period. Ask the assistant to show the underlying counts before writing an improvement claim. If the input is stale, include its date instead of making the report sound current.
Write a useful update when little changed
For practice, assume the venue details are still missing next week and no new tests ran. A truthful report says the state is unchanged, names the blocking information and identifies the requested decision. It does not manufacture momentum by rephrasing last week’s work as a new achievement.
Before sending, check one completed item against its evidence, one blocker against its actual owner and every date against the calendar. Keep a short record of corrections to improve the next run. Once the manual report is useful across several different weeks, you can consider whether a repeatable workflow would help; the template alone does not justify automation.
Check the data behind a report
Take it further with a changed example
If a report sounds positive but leaves the reader unsure what to do, inspect its verbs. “Progressed,” “advanced” and “worked on” may conceal the actual state. Replace one with the artifact produced, the check performed and the decision still needed.
Try writing the report’s first sentence for a colleague returning after a week away. It should distinguish what changed from what remains blocked. Put the decision request near the relevant evidence, with an owner only when that responsibility has been agreed.
For a further exercise, take a fictional draft marked “locally checked, awaiting review” and imagine a new requirement arrives. Update the report so the earlier check does not imply that the changed version is ready. Explain which part needs another review and why.
Take this into your next task
Lead with the state and the decision needed; use evidence to keep “done” meaningful.
Questions people ask
Can I report a percentage complete?
Use it only when the team has a clear definition and the underlying evidence supports it. Otherwise report completed and remaining work directly.
What if the week was mostly blocked?
Say so and make the blocking input or decision easy to act on.
How long should the update be?
Long enough to state the current position, evidence and action needed. Put optional detail below the main update.
How do I make a short report without hiding uncertainty?
Use precise status words and keep the most consequential open decision. Remove background repetition before removing a qualification that changes the meaning.
Sources and editorial notes
Reviewed 2026-09-07. Product capabilities depend on the app, plan, region and workspace settings. Workflows and prompts are authored teaching material, not recorded model results or measured time-saving claims.
Keep going
- AI at Work: Practical Skills, Examples and a Learning Roadmap
- Ask better questions of a spreadsheet before trusting a chart
- AI Mission Control: From Idea to Verified Result
Related Power of AI pages
Keep reading with Start here, everyday uses, the tool guide, the writing workshop, and sources and standards.