TaskbyTask.Practical AI guides for work
ChatGPT · Practical walkthrough

Use ChatGPT to draft a weekly update from your notes

It's Friday afternoon and the weekly update is due. The supplier said "probably Monday", which can become a firm commitment after passing through enough presentations.

Task by Task13 min read + practice
Loose progress notes beside a weekly calendar and a clear briefing with completed and unresolved items.

What you'll make

a short weekly update that shows what moved, what’s blocked and what you need from the reader, without making anything sound more certain than your notes do.

What you'll need

your notes for the week, a ChatGPT work account (Claude, Gemini or Copilot work too) and about 10 minutes. No connection to your project system is needed.

Example result.

Decision needed (operations director): please name an escalation owner by Tuesday 13 October so we can chase the supplier test account. Completed: eight of ten planned booking-form checks have passed. Still open: two checks are blocked. The supplier suggested Monday 12 October for the test account; that date is unconfirmed. Risk: the effect on the 16 October launch target is unknown until testing is complete.

1. Choose the period, the reader and the facts

Write down the reporting period and who will read the update. Gather short notes on completed work, blockers, risks and any decision that genuinely needs the reader. Keep confirmed facts, estimates and targets distinguishable, and keep words such as “probably” and “target”.

If a decision is needed, note who can make it, what it is and by when. If none is needed, don’t invent one to fill a heading.

Why this works: the update can only be as precise as the notes. “Probably” in the notes is the only thing that stops “Monday” in the draft.

What you should see: a reader, a period and a short list of facts, each marked as done, blocked, estimated or needed.

2. Ask for the update

Write a weekly update for [reader] covering [reporting period], using only the notes below. Keep it under 150 words. Use these headings: [your headings].
If the notes support a decision or request, put it first, once. If none is needed, say so or leave that heading out.
Keep dates and numbers exact. Distinguish confirmed facts from estimates and targets. Don't infer an overall completion percentage, invent a status colour or make progress sound healthier than the evidence supports.
Flag missing facts, owners or deadlines separately. Don't invent progress to fill a heading.

[your notes]

[your headings] can be your team’s, or “Decision needed, Completed, Still open, Risk”. Paste your notes in place of [your notes].

Why this works: the reader and period set the scope; keeping uncertainty stops a supplier’s “probably” becoming your promise. Change the word limit to suit your team; it keeps the update readable but never justifies dropping a risk.

What you should see: the request first, then short sections that use your notes’ own words for anything uncertain.

3. Check the wording against your notes

Read the draft once looking only for claims, and compare each with the notes:

If the notes say… Keep it as… Not…
8 of 10 checks passed Eight passed; two blocked 80% of the project complete
Probably Monday An unconfirmed estimate Delivery confirmed for Monday
Target launch 16 October A target, impact unknown On track for launch
Need an escalation owner A decision still required Escalation in progress

Then read it as the recipient: can they see what changed, what’s blocked and what’s being asked of them, and is the decision theirs to make?

Why this works: “on track”, “minor delay” and “expected Monday” are where uncertainty usually disappears.

What you should see: every number and date matching the notes, and the request stated once.

Check the result

  • Every number and date matches the notes.
  • Estimates and targets still read as estimates and targets.
  • The request names who decides, what and by when, and appears once.
  • Nothing in the update claims an action you haven’t taken: drafting the update hasn’t escalated anything.

The usual failure: unsupported optimism. “Probably Monday” becomes “arrives Monday”, a target becomes “on track”, and the blocker shrinks to “a few final things”. Spot it with the table in step 3.

Remove status claims the notes don't support and restore their uncertainty, using the notes' own words. Keep the supported facts and the request unchanged.

Worked example: a blocked test account

Fictional example. Notes for the week ending Friday 9 October 2026:

New booking form: 8 of 10 planned checks passed
Remaining 2 need a supplier test account
Supplier said "probably Monday 12 October"; no confirmation
Target launch: Friday 16 October
Need the operations director to name an escalation owner by Tuesday 13 October
Launch impact can't be confirmed until testing is complete

The first draft read: “Good progress this week: 80% of checks complete. The supplier test account arrives Monday, and we remain on track for the 16 October launch. Decision needed: escalation owner.”

The repair prompt, followed by “Put the decision request first, with its deadline from the notes”, produced the update at the top of this page.

  • “80%” was a different measure. Eight of ten checks passed; that says nothing about how much of the project is done.
  • “Arrives Monday” and “on track” were both promotions. The notes say “probably” and “target”.
  • The request moved to the top and gained a deadline. At the bottom with no date, it read as an afterthought, and the reader could miss that it was theirs.

Try it

Choose a brief, then inspect what the response hides

Example responses, written to show what each prompt tends to produce.

Weak: Broad request

The prompt

Write a weekly project update.

Fictional notes: eight of ten checks passed; two blocked by a supplier test account. Supplier says probably Monday 12 October. Target launch 16 October; impact unknown until tests finish. An escalation owner is needed.

Example response

Select a phrase in the response to inspect its support or weakness.

Why this prompt changes the task

The request supplies no reader, structure or review criteria. These notes deserve a decision request and explicit uncertainty; a pleasant general update is not enough.

Source and shape, loose commitments

The prompt

Summarise these fictional notes in three short bullets for the project team.

Eight of ten checks passed; two blocked by a supplier test account. Supplier says probably Monday 12 October. Target launch 16 October; impact unknown until tests finish. An escalation owner is needed.

Example response

Select a phrase in the response to inspect its support or weakness.

Why this prompt changes the task

A source and bullet limit help scope the task, but they do not define how to handle tentative dates or an unsupported status assessment. Check the missing constraints and the answer.

Decision, source and uncertainty

The prompt

Write a short update for the operations director from these fictional notes. Put the escalation-owner request first. Separate passed checks, blocked checks and launch risk. Preserve “probably” and “target”; do not turn them into promises or claim overall project completion. Use only the notes.

Eight of ten checks passed; two blocked by a supplier test account. Supplier says probably Monday 12 October. Target launch 16 October; impact unknown until tests finish. An escalation owner is needed.

Example response

Select a phrase in the response to inspect its support or weakness.

Why this prompt changes the task

The reader and decision set the order. Source boundaries and qualification rules address concrete risks. This prepared sample follows them; a live result would still need checking.

Task kit for this job: Download (ZIP) · Reusable instructions

Go deeper

Sharpen the decision request

The reader should see who must decide, what and by when. If one of those is missing, keep the gap visible rather than filling it.

Review this draft against my notes. Make the decision request explicit: who needs to decide, what they need to decide and by when. Mark anything missing. List any factual claim the notes don't support. Don't invent a workaround, owner or date.
Cut length without cutting uncertainty

If the draft is too long, remove background before removing uncertainty. “Unconfirmed” is often more useful than another sentence about the work everyone has been doing. Keep the four headings and one line under each before you trim the risks.

Make it a weekly routine

Save the step 2 prompt with your usual headings and reader, and paste fresh notes each week, so last week’s facts never carry over. In Gemini, you can save it as a Gem: see create a Gem for a weekly task.

Sources

Optional analytics

With your permission, Google Analytics uses cookies to measure visits and which guides people read. It stays off until you accept. Use Analytics choices in the footer to change your choice. Rejecting after accepting refreshes this page. Privacy details.