Write a Weekly Status Update from Evidence, Not Memory

“Good progress this week” tells the reader almost nothing. “Measurements approved; material order waiting on a finish decision” tells them where the work stands and what needs to happen next. Build your update from records, then use AI to tighten the writing. Do not ask it to reconstruct the week from a vague impression.

Choose your evidence Use completed tasks, current milestones, blocked items, and decisions awaiting approval. Start with the confirmed meeting actions and your inquiry or work tracker. Define the reporting period, including the time zone. A Friday evening update should not count in different weeks depending on who runs the report. If you summarize a sheet, consult Google’s pivot-table guide.

Use four short sections Completed: result plus source reference. In progress: next milestone and owner. Blocked: obstacle, effect, and decision needed. Next: planned work, clearly labeled as a plan. For a fictional workshop project, “Supplier contacted; reply pending” belongs under In progress. It must not become “Materials secured.” The dashboard guide covers definitions that stop numbers from making the same mistake.

Ask for the decision directly Weak: “There is an issue with the finish.” Useful: “We need the finish approved before ordering. Daniel owns the choice. Please confirm the option or request another sample by the agreed review date.” Do not invent that date or owner. Use the handoff checklist when responsibility is unclear.

Try this drafting instruction “Write a concise update using only these records. Preserve incomplete and blocked statuses. Include source references. Flag conflicts and stale records. Separate completed work from plans. Do not infer dates, spending, or customer commitments.” Refer to OpenAI’s prompting documentation for instruction design. For shared working documents, Google’s version-history tools can help you inspect what changed.

Check what the report cannot know “No blockers reported” is not the same as “Every owner confirmed no blockers.” Display when important source records were last checked. Investigate contradictions using the first-wrong-step method rather than polishing around them. Review any statement about cost, completion, or promises through the approval process. Measure whether the update reduces follow-up questions and preparation time. Your finished update should let a busy reader answer three questions quickly: What changed? What needs me? What happens next?